Inherited rule treated differently in a child device group
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 rule that logs in one scope and not in another leaves an evidence gap that only appears on the devices in the quieter scope. The same applies to a dropped profile group: the protection an operator believes is estate-wide is not.
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.
- Decide which treatment is intended for this traffic.
- Apply the same logging and profile settings in both scopes, or record why they differ.
- Where the difference is deliberate, name it in the rule description so the next reader does not treat it as drift.
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 it3
- The managed devices keep running their current policy until you push.
- Removing the local copy restores whatever the parent supplies.
- 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 the logging destination configured for each scope is reachable.
- Generate one test event in each scope and confirm both arrive.
Limits
- This describes the configured logging and profile settings. It is not a statement about which sessions were or were not recorded.
- 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-003Identical rule defined in several device groups
- PAN-MGT-004Rule defined in every child of a 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.