DoS protection rule is disabled
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 disabled rule keeps its match and its profile on the screen and does nothing. It may be deliberate, and a protection that was switched off during an incident and never switched back is the case worth catching.
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.
- Enable the rule if the protection is still wanted.
- Delete it if it is retired, so the rulebase says what is in force.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 rulebase dos rules <object-name> disabled noAn 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 dos rules <object-name>Values to fill in1
- <object-name>
- The object's name, as it appears on your firewall
Before you type it1
- Enabling this starts enforcement on traffic that is passing today.
How to confirm the fix
- Confirm the rule's state matches the intended protection.
- Confirm the protected servers still have a DoS rule that applies.
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 DoS and Zone Protection
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.