Allow rule matches any source and any destination
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
An enabled allow rule whose source and destination both resolve to any permits every address pair the zones can reach. Its addresses put no limit on traffic from its source zones to its destination zones, including inbound traffic when a source zone faces the internet.
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.
- Replace the any source with the address objects or groups that actually need access.
- Replace the any destination with the specific servers or subnets being reached.
- Re-test the rule with a policy match query before committing.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 rulebase security rules <object-name> source <specific-source>set vsys vsys1 rulebase security rules <object-name> destination <specific-destination>
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
- <specific-source>
- The source this rule should allow
- <specific-destination>
- The destination this rule should reach
Before you type it1
- Narrowing this changes who reaches what. Confirm the new set covers the traffic the application needs.
How to confirm the fix
- Run a policy match query for a representative flow and confirm it now matches the narrowed rule.
- Confirm the applications that used this rule still work after the change.
Limits
- A deliberate internal any to any rule between two trusted layer 3 zones can be intentional during migrations. Exposure is scored lower when neither zone looks internet facing.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- PAN-SEC-002Allow rule matches any application
- PAN-SEC-003Allow rule matches any service
- PAN-SEC-004Disabled rule left in the rulebase
- PAN-SEC-005Rule has no description and no tag
- PAN-SEC-006Temporary rule with no schedule or expiry
- PAN-SEC-007Allow rule with logging fully disabled
- PAN-SEC-008Rule does not log at session end
- PAN-SEC-009Rule has no log forwarding profile
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.