Policy with no hit in 90 days of readings
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 policy no traffic has matched over a long window is probably obsolete, and an obsolete allow policy widens what the firewall admits.
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.
- Ask the policy's owner whether it is still needed. If not, disable it first, watch for a business cycle, then delete it.
Command line
FortiOS CLI
config firewall policyedit <policy-id>set status disablenextend
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. FortiOS saves a change when you type next or end, with no separate commit. Read every line first.
Read it back
show firewall policy <policy-id>Values to fill in1
- <policy-id>
- The policy id to change
Before you type it3
- Written from the FortiOS CLI Reference, not yet run on a device. Read each line before typing it.
- On a device with VDOMs, type these inside the VDOM (config vdom, edit the VDOM) or inside config global for a global setting.
- A configuration shows definitions and references, not traffic, so review this before you run it.
How to confirm the fix
- In the FortiGate GUI (read only): Policy & Objects, Firewall Policy, and read the policy's Hit Count and Last Used columns.
Limits
- A policy kept for a rare event (disaster recovery, a yearly job) can show no hit and still be needed.
- A counter cleared and counted back to the same value between two readings is not seen.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- FGT-SEC-001Accept policy from every address to every address
- FGT-SEC-002Accept policy on service ALL
- FGT-SEC-003Accept policy does not log its traffic
- FGT-SEC-007Disabled policy left in the table
- FGT-SEC-008Policy covered by an earlier policy
- FMG-MGT-004Managed FortiGate with no policy package installed
- FMG-MGT-005Policy package installed on no FortiGate
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.