Replacing an End-of-Support Server in an Organization
16 November 2026SSL/TLS Inspection: What It Lets You See, and What It Asks of an Organization
16 November 2026A firewall only protects as well as its rules. Each rule says which traffic gets through: where it comes from, where it
goes, and through which service or application. An ANY rule leaves one of those fields open to everything.
1. What an ANY rule is
An ANY rule puts "any" in place of a source, a destination, a service or an application. Palo Alto Networks recommends
rules that are as specific as possible, to apply the principle of least privilege, and points out that a rule that is
too broad increases the attack surface. Fortinet gives the same advice: only allow the networks and services that are
required. The firewall guidelines of NIST, the US standards body, go further: generally, all inbound and outbound
traffic not expressly permitted should be blocked.
2. Why they pile up
NIST puts it simply: firewall rulesets can become increasingly complicated with age, and a review can uncover rules
that are no longer needed. Palo Alto Networks adds that unused rules
clutter the rulebase and offer avenues of attack.
3. Finding them
Today’s firewalls keep track of what each rule lets through.
- On a Fortinet firewall: the policy list can be filtered by hit count and
last use, and the FortiGate’s security rating flags unused policies. - On a Palo Alto Networks firewall: the Policy Optimizer shows
the rules with the application set to "any" and the rules no traffic has matched over the chosen timeframe, with the
last time a rule was used.
A rule with no traffic is not necessarily useless. Palo Alto Networks warns that an application used only quarterly or
annually can look unused, and that a rule can also be shadowed by another one placed before it.
4. Cleaning them up without breaking anything
- Disable before deleting. According to Palo Alto Networks, this is the safest: a disabled rule can be enabled
again if something stops working. Tag the rule with the date it was disabled. - Delete later, after a reasonable period, the disabled rules nobody missed.
- Replace an ANY rule with a specific one: the source, the destination and the service or application the business
really needs. - Write down why each rule exists. NIST asks for a comment on each rule, so others can tell why it was made.
- Review the rules at regular intervals, as NIST recommends, and not only during an audit or an emergency.
This clean-up is part of a business network’s security, just like
segmentation. For the basics, read our guide
Firewalls: what to know before you install one.
Frequently asked questions
Can you delete all the rules with no traffic at once?
Not at once. Palo Alto Networks recommends disabling them first and deleting them after a reasonable period, because a
rule used once a quarter or once a year can look unused.
How often should firewall rules be reviewed?
NIST recommends reviewing them at regular intervals, so that reviews do not only happen during an audit or, worse, an
emergency. Palo Alto Networks recommends making it part of scheduled maintenance.
Is an ANY rule always a mistake?
It opens more than necessary. NIST recommends blocking everything that is not expressly permitted, and each rule should
carry a comment saying why it exists.
What next?
MPJM deploys and manages Fortinet and
Palo Alto Networks firewalls. Reviewing a firewall’s rules is one of
the jobs a monthly block of hours can cover. To find out where your
network stands, ask for the free network analysis. It is offered to
organizations with 40 or more employees.
P.S. Sixteen questions, eight domains, a clear picture of your strengths and blind spots: start the assessment.
