Outbound policy has no deny rules
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
Every internal network can reach every destination on every port, including other internal networks routed through the MX.
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 the Meraki Dashboard: Security & SD-WAN > Firewall > Layer 3 rules: add deny rules between internal networks and toward services that must not be reached.
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
- In the Meraki Dashboard: Security & SD-WAN > Firewall shows deny rules above the default rule.
Limits
- The Meraki default outbound rule always allows; the finding is about the rules above it.
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.