Rule names a zone the template stack of its firewalls does not define
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
Zones reach a firewall from its template stack, and a rule reaches it from its device group. A rule naming a zone the firewall does not receive cannot be pushed to it as written, so the policy the device group intends is not what that firewall enforces.
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.
- Add the zone to a template the stack reads, with the interfaces that belong in it.
- If the rule is not meant for these firewalls, narrow its target or move it to a device group they are not in.
- If the zone was renamed, update the rule to the name the stack uses.
Command line
Panorama CLI
set template <template> config vsys <vsys> zone <zone> network layer3 <interface>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 template <template> config vsys <vsys> zone <zone>Values to fill in4
- <template>
- The template that holds this setting
- <vsys>
- The virtual system this object belongs to
- <zone>
- The zone this interface belongs in
- <interface>
- The interface to change
Before you type it4
- The managed devices keep running their current policy until you push.
- This setting lives on a device or in a template. On a Panorama, name the template it belongs to.
- Where this is defined depends on your configuration, so the scope is left for you to fill in.
- Once the interface is in a zone, policy applies to traffic that is passing today.
How to confirm the fix
- Preview the push to one firewall the finding lists and confirm the rule is accepted.
- Confirm the zone holds the interfaces the rule is meant to govern before relying on it.
Limits
- A zone is looked for in every vsys of the stack and of its templates; PAN-OS places a zone in one vsys, so a zone in another vsys of the stack is counted as present.
- A NAT rule's target is not read, so a NAT rule is not reported here.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Panorama Advanced
- 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
- PAN-MGT-011Template variable used with no declaration
- PAN-MGT-012Template variable declared and never used
- PAN-MGT-013Device group with no managed devices assigned
- PAN-MGT-014Managed device in a device group but in no template stack
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.