Broad allow rule generalizes earlier specific rules
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
A later allow rule is broad enough to cover several earlier specific rules. Traffic it matches beyond them is allowed without the limits those rules set, so the specific rules above it may constrain less than they appear to.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- Narrow the broad rule to the applications, services and addresses actually required.
- Or remove the specific rules it makes redundant, so the policy states its real intent.
Command line
PAN-OS CLI, standalone firewall, vsys1
move vsys vsys1 rulebase security rules <object-name> before <anchor-rule-name>An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here commits. Review the candidate configuration, then commit it yourself.
Read it back
show vsys vsys1 rulebase security rulesValues to fill in2
- <object-name>
- The object's name, as it appears on your firewall
- <anchor-rule-name>
- The rule to place this one before
Before you type it1
- Rule order decides who reaches what. Choose the anchor deliberately.
How to confirm the fix
- Decide whether the broad rule or the specific ones state the real intent.
- Run a policy match query for each of the specific rules before removing anything.
Limits
- A broad rule that exists as a deliberate catch-all for a trusted internal zone can be intentional.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- PAN-SEC-008Rule does not log at session end
- PAN-SEC-009Rule has no log forwarding profile
- PAN-SEC-019Earlier rule covers this rule with different behavior
- PAN-SEC-020Rule is redundant
- PAN-SEC-022Permissive allow rule is evaluated before restrictive rules
- PAN-SEC-040Two rules are exact duplicates
- PAN-SEC-041Two rules differ in one dimension and could be reviewed for consolidation
- PAN-SEC-042Duplicate rules log differently
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.