Static NAT publishes a host an inbound rule reaches
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 static NAT to an internal host combined with a broad inbound allow puts the host on 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.
- In FMC (or cdFMC): Devices > NAT > edit the policy > remove or restrict the NAT rule; Policies > Access Control > tighten the matching rule's source networks and ports. Save, Deploy.
- In FDM: Policies > NAT > edit the rule; Policies > Access Control > edit the matching rule, then Deploy.
Command line
This analyzer version writes no command text for this control. The steps above are the remediation it offers.
How to confirm the fix
- On the FTD CLI (read only): show running-config nat and show xlate, and confirm the translation is gone or restricted.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in NAT
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.