A firewall rule audit is a structured review of every rule in a firewall policy to confirm that each one is still needed, documented, correctly ordered and no more permissive than the business requires. Over time, rule bases grow through urgent change requests, temporary access that was never removed and migrations that copied old rules forward. The result is a policy nobody fully understands, with hidden paths an attacker can use. A rule audit finds those paths and gives you a cleanup plan.

This guide focuses on the rule-level work: what to look for, how to prioritize findings and how to keep the rule base clean afterwards. For the wider firewall review process, including configuration hardening and firmware, see our step-by-step firewall security audit guide.

Why Firewall Rules Drift

  • Urgent changes. A project needs access today, so a broad rule is added with the intention of tightening it later.
  • Temporary access. Vendor, testing or migration rules stay in place long after the work ends.
  • Decommissioned systems. Servers are retired but the rules pointing to their IP addresses remain, and the addresses may later be reused.
  • Migrations. Moving to a new platform often copies the entire old rule base rather than rebuilding it.
  • Weak documentation. Rules with no owner, ticket or business justification are hard to remove because nobody knows if they are still needed.

NIST’s guidance on firewalls, SP 800-41 Rev. 1, recommends that firewall policies be based on a default-deny approach and reviewed regularly. Payment environments have a specific requirement: PCI DSS v4.0.1 requires configurations of network security controls to be reviewed at least once every six months.

The Seven Rule Types to Look For

1. Overly Permissive Rules

Rules that use “any” in the source, destination or service field are the highest priority. An inbound rule allowing any source to reach an internal server on any port effectively removes the firewall for that host. Look for broad network ranges, large port ranges and “any any” rules, then work out what traffic is actually needed.

2. Unused Rules

Rules with zero hit counts over a meaningful period, such as 90 days or a full business cycle, are candidates for removal. Confirm that logging and hit counters were enabled for the whole period, and check for seasonal or annual processes before deleting anything.

3. Shadowed Rules

A rule is shadowed when an earlier rule already matches all of its traffic, so it never takes effect. Shadowed rules add confusion and can hide intent: a carefully written deny rule that sits below a broad allow rule does nothing.

4. Redundant and Duplicate Rules

Two or more rules that permit the same traffic make the policy harder to read and maintain. Consolidating them reduces mistakes during future changes.

5. Risky Services

Flag rules that allow clear-text or high-risk protocols such as Telnet, FTP, SMB, RDP or database ports, especially from the internet or between trust zones. These should be restricted to specific sources or replaced with secure alternatives and bastion access.

6. Undocumented and Orphaned Rules

Every rule should have an owner, a business justification, a change reference and ideally a review or expiry date. Rules with none of these are a governance finding even if they look harmless.

7. Rules Referencing Stale Objects

Objects pointing to decommissioned hosts, old subnets or deleted users can become dangerous if those addresses are reassigned. Clean up unused objects along with unused rules.

How to Run a Firewall Rule Audit

  1. Collect the configuration. Export the full rule base, object definitions, NAT rules and hit counts from each firewall in scope, including cloud security groups if they are part of the review.
  2. Gather context. Obtain network diagrams, zone definitions, the list of critical assets and recent change records.
  3. Analyze the rules. Use automated analysis to flag permissive, unused, shadowed and redundant rules, then review high-risk results manually.
  4. Validate with owners. Ask application and network owners to confirm which flagged rules are still needed and what the minimum required access is.
  5. Prioritize. Rank findings by exposure: internet-facing and cross-zone rules to critical assets come first.
  6. Remediate safely. Disable before deleting, make changes in controlled windows and keep a rollback plan.
  7. Report and re-test. Document what changed, confirm traffic still flows as intended and record residual risks.

Prioritizing Findings

PriorityTypical findingSuggested action
CriticalInbound “any” source to internal hosts or management interfacesRestrict immediately to known sources or remove
HighRisky services exposed between zones or from the internetLimit to required hosts, move to secure protocols
MediumUnused rules, broad internal rules, stale objectsValidate with owners, disable then remove
LowDuplicates, shadowed rules, missing commentsConsolidate and document during cleanup

Hypothetical Example

A review of a perimeter firewall finds an inbound rule allowing any source to reach a subnet on TCP 3389, created three years earlier for a vendor project. Hit counts show recent connections from unknown external addresses. The rule is disabled during an emergency change, the affected servers are checked for signs of compromise and vendor access is moved behind a VPN with MFA. The same audit removes dozens of zero-hit rules and documents an owner for every remaining rule.

Keeping the Rule Base Clean

  • Require a ticket, owner and business justification for every new rule
  • Set expiry dates for temporary rules and review them automatically
  • Review high-risk rules more often than the full rule base
  • Track hit counts continuously and review zero-hit rules on a schedule
  • Align rules with network segmentation and zero trust principles
  • Repeat a full audit at a defined interval and after major network changes

A broader firewall security review adds configuration hardening, logging and architecture checks to this rule-level work.

Key Takeaways

  • A firewall rule audit checks every rule for need, ownership, order and least privilege.
  • Overly permissive rules and exposed risky services are the highest priority.
  • Unused, shadowed and duplicate rules should be validated with owners before removal.
  • Ongoing change control and scheduled reviews stop the rule base drifting again.

Frequently Asked Questions

What is a firewall rule audit?

A firewall rule audit is a review of every rule in a firewall policy to confirm it is needed, documented, correctly ordered and no more permissive than the business requires.

How often should firewall rules be reviewed?

It depends on risk and regulation. PCI DSS v4.0.1 requires network security control configurations to be reviewed at least every six months, and many organizations review high-risk rules more often.

What is a shadowed firewall rule?

A shadowed rule is one that never matches traffic because an earlier rule in the policy already matches everything it would have matched.

Can unused firewall rules be deleted straight away?

It is safer to validate with owners, check for seasonal traffic, disable the rule first and delete it only after a monitoring period with a rollback plan.

Should cloud security groups be included in a firewall rule audit?

Yes. Cloud security groups and network ACLs act as firewalls and often contain broad rules, so they should be reviewed with the same criteria.

Not sure what is hiding in your rule base? Securis360’s firewall security review services combine automated rule analysis with expert validation and a prioritized cleanup plan. Request a firewall rule audit.