Inbound destination NAT may lack a restrictive security rule
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
No allow rule was found that narrows both the source and the service for this published server. If the service is meant only for named clients on specific ports, the rules that could match it may admit more than intended. NAT alone does not grant access, and a public service may be meant to accept any source, so this is a candidate to review rather than a proven defect.
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.
- Inspect existing security rules using the original pre-NAT destination address and port, with the destination's post-NAT zone. Do not create an allow rule solely to clear this finding.
- Confirm whether the service is public or limited to named clients. Restrict source and service only where that matches its purpose.
- Validate rule order, forwarding, logging and threat-prevention profiles before changing access.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 rulebase security rules <rule-name> from <external-zone>set vsys vsys1 rulebase security rules <rule-name> to <internal-zone>set vsys vsys1 rulebase security rules <rule-name> destination <published-address>set vsys vsys1 rulebase security rules <rule-name> service <published-service>set vsys vsys1 rulebase security rules <rule-name> action allowset vsys vsys1 rulebase security rules <rule-name> log-end yes
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 <rule-name>Values to fill in5
- <rule-name>
- The rule's name, as it appears on your firewall
- <external-zone>
- The zone facing the internet
- <internal-zone>
- The zone on the inside
- <published-address>
- The address this service is published on
- <published-service>
- The service the application actually uses
Before you type it1
- A NAT rule matches the address before translation and a security rule matches the zone after it.
How to confirm the fix
- Check Panorama policies, the post-NAT destination zone and the first matching security rule for the original packet.
- Test permitted and denied clients and inspect traffic logs before and after an approved change.
Limits
- Critical is this control's configured review priority, not an AI judgment or confirmed exposure. The candidate search does not simulate ordered policy, post-NAT routing or live traffic. Panorama policies may be outside this assessment.
Compliance references
No benchmark recommendation is mapped to this control in this version.
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.