Replacing Allow-All Firewall Rules With What Actually Flows

Nov 20, 2026

Reading Time: 3 minutes

Replacing Allow-All Firewall Rules With What Actually Flows

Firewall Policy • Traffic Analysis • Network Security

Key Takeaway: Removing an allow-all firewall rule isn’t difficult; removing it without breaking the business takes patience. Watch what talks to what, build rules for what you find, keep the old rule as a safety net until its hit count reaches zero, and disable it before you delete it.

The Allow-All Firewall Rule Nobody Owns

Almost every firewall we take over has one. Somewhere in the rule base sits a policy that allows anything to talk to anything. Usually it was created for convenience at some point, perhaps to get a new system working quickly, and then it simply stayed. Nobody owns it any more. Often that lack of ownership is the very reason we were asked to take the firewall on.

Working Isn’t the Same as Secure

The usual defence is “it works, so don’t touch it.” That’s true, but only because the rule isn’t stopping anything. A network that works because nothing is blocked isn’t secure, it’s just quiet. And if nobody deliberately tightens it, the gap is left for someone you didn’t invite to find.

How to Remove an Allow-All Firewall Rule Safely

Removing an allow-all rule isn’t difficult. Removing it without breaking the business takes a little patience, so this is how we go about it.

Watch the Traffic First

First, we watch. With the client, we agree a period of traffic analysis, usually somewhere between two weeks and a month. We use the firewall logs to answer a simple question: what talks to what? Which systems connect to which, on which services, and how often.

Question Every Flow

Then we build rules for what we find. Each flow gets a question as well as a rule. Does this make sense? Is it actually needed? Is it being done securely? This is where the surprises turn up. We regularly find insecure protocols such as Telnet and unencrypted web traffic allowed where they never should have been, along with plenty of web requests that look reasonable at first glance but don’t survive a second look. A connection happening isn’t the same as a connection being needed.

Keep the Old Rule as a Safety Net

The new rules go in ahead of the old allow-all rule, which stays in place at the bottom as a safety net. The first batch covers the bulk of the traffic. We then watch whether anything still reaches the allow-all rule. If it does, that traffic gets reviewed and, where it’s legitimate, covered by a second batch.

Disable Before You Delete

The broad rule only goes when its hit count has reached zero. Even then we don’t delete it straight away. We disable it first and leave it disabled for a good while, so there’s a quick way back if something rare, like a month-end process, turns up. Only after that is it removed for good.

How Long Does a Firewall Policy Review Take?

How long does all of this take? It depends far more on people than on technology. A small, decisive organisation can be done in a couple of weeks. A larger one, where every change needs its own change request and approval, can take many months. Both are fine. What matters is that the rule base ends up reflecting what the business needs, rather than what was convenient years ago.

What Is Your Allow-All Firewall Rule Protecting?

If you’ve inherited a firewall and aren’t sure what that broad rule at the bottom is protecting, it’s worth finding out. The traffic is already telling you what you need. You just have to look.

Our managed network security service takes on inherited firewalls and tightens them safely, as part of a proactive security approach. Discuss your needs with our engineers.

Inherited a Firewall You Don’t Fully Trust?

Speak to our engineers about tightening your firewall policy without breaking the business.

SPEAK TO OUR TEAM

author avatar
Jacques v.d Merwe

Let's talk about your business

Tell us where your business is going and what is getting in the way. We'll investigate for free and recommend what you need.

Talk to our team