Intrusion policy in detection mode
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
In detection mode, drop rules only alert: nothing is blocked inline, however severe the signature.
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): Policies > Intrusion > Intrusion Policies > edit the policy > Mode: Prevention. Save, Deploy.
- In FDM: Policies > Intrusion > edit the policy > Inspection Mode: Prevention, 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
- Review the intrusion events from detection mode first, so prevention does not drop expected traffic.
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 Security Profiles
- FTD-SEC-004Allow rule without an intrusion policy
- FTD-SEC-006Inbound allow rule without a file policy
- FTD-SEC-015Intrusion policy built on a weak base
- FTD-SEC-016Variable set leaves HOME_NET as any
- FTD-SEC-018Security Intelligence block list missing
- FTD-SEC-019High-risk URL categories not blocked
- FTD-MGT-013Licensing not compliant or features unlicensed
- FTD-MGT-017Threat content updates stale
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.