Identical rule defined in several device groups
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
One intent written in several places is several places to edit. Each copy is a chance for the estate to drift, and none of them is the place a reader looks first.
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.
- Confirm the copies are meant to express one policy.
- Define the rule once in the nearest scope every device group involved inherits from.
- Remove the copies only after confirming the shared definition reaches each of them.
Command line
Panorama CLI
delete device-group <device-group> <rulebase>-rulebase security rules <object-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 or pushes. Review, commit, then push to your devices yourself.
Read it back
show device-group <device-group> <rulebase>-rulebase security rules <object-name>Values to fill in3
- <device-group>
- The device group that holds the rule
- <object-name>
- The object's name, as it appears on your firewall
- <rulebase>
- Whether this rule is a pre-rule or a post-rule
Before you type it4
- The managed devices keep running their current policy until you push.
- A configuration shows definitions and references, not traffic, so review this before you run it.
- A managed firewall can hold local rules that a Panorama export does not contain.
- The same rule name can exist as a pre-rule and a post-rule, evaluated on either side of the managed firewall's own rules. Name the one you mean.
How to confirm the fix
- Confirm every device group involved inherits from the scope you move the rule to.
- Compare the effective policy on one device from each device group before and after.
Limits
- Consolidation changes which scope owns the rule and therefore where it sits in evaluation order. Review before applying.
- This compares the configuration Panorama pushes. It does not read the local rulebase of any managed firewall.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Panorama Advanced
- PAN-MGT-001Rule restated in a device group that already inherits it
- PAN-MGT-002Rule an inherited pre-rule already matches
- PAN-MGT-004Rule defined in every child of a device group
- PAN-MGT-005Inherited rule treated differently in a child device group
- PAN-MGT-006Rule references an object outside its inheritance chain
- PAN-MGT-007Object redefined in a device group that inherits one with the same name
- PAN-MGT-008Templates in one stack set the same value differently
- PAN-MGT-009Template stack member whose settings are all supplied above it
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.