Two rules differ in one dimension and could be reviewed for consolidation
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
Two rules agree on every behavior-affecting field and differ in exactly one matching dimension. Consolidating them would shorten the rulebase, but whether the resulting match set is what the business wants is a judgment this analysis cannot make.
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.
- Review whether the combined match set is the access the business intends.
- If it is, merge the two and record the resulting Cartesian match set in the change.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 rulebase security rules <rule-to-keep> description "<why-this-rule-exists>"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 rules <object-name>Values to fill in3
- <object-name>
- The object's name, as it appears on your firewall
- <rule-to-keep>
- The rule you are keeping
- <why-this-rule-exists>
- Why this rule exists
Before you type it1
- Compare the two match sets before merging. The merged rule reaches the union of both.
How to confirm the fix
- Compare the match set of the merged rule against both originals before committing.
- Watch the traffic log for one business cycle for sessions the merge newly permits.
Limits
- Two rules kept apart on purpose, for example one per business owner, will match this pattern and should stay apart.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- PAN-SEC-020Rule is redundant
- PAN-SEC-021Broad allow rule generalizes earlier specific rules
- PAN-SEC-022Permissive allow rule is evaluated before restrictive rules
- PAN-SEC-040Two rules are exact duplicates
- PAN-SEC-042Duplicate rules log differently
- PAN-SEC-094Enabled rule names a zone only a disabled tunnel feeds
- PAN-SEC-095Rules can be merged without changing what they permit
- PAN-SEC-104Built-in interzone default rule does not log
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.