Rule references an object outside its inheritance chain
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
Panorama pushes a device group the objects defined in that group, in its ancestors and in Shared. An object defined elsewhere does not travel with the rule that names it, so the rule as pushed is not the rule as written.
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.
- Move the object to Shared, or to the nearest scope both device groups inherit from.
- Alternatively define the object in the device group that uses it.
- Commit and confirm the push validates before applying it to the estate.
Command line
Panorama CLI
set shared address <object-name> ip-netmask <address-value>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 <rule-name>Values to fill in5
- <object-name>
- The object's name, as it appears on your firewall
- <address-value>
- The address or range this name should mean
- <device-group>
- The device group that holds the rule
- <rulebase>
- Whether this rule is a pre-rule or a post-rule
- <rule-name>
- The rule's name, as it appears on your firewall
Before you type it3
- The managed devices keep running their current policy until you push.
- Moving an object up the hierarchy changes what every group below it resolves.
- 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 object is not intended to be specific to the device group that defines it.
- Run a Panorama commit validation and confirm the reference resolves.
Limits
- 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-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-005Inherited rule treated differently in a child device group
- 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
- PAN-MGT-010Template stack names a template that does not exist
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.