Threat detection off
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
Basic threat detection records drop-rate attacks and scanning threat detection spots and can shun scanners; without them a scan or flood leaves no ASA statistic behind.
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 ASDM: Configuration > Firewall > Threat Detection, enable Basic Threat Detection and Scanning Threat Detection. Apply and save.
- On the CLI: threat-detection basic-threat and threat-detection scanning-threat, and write memory.
Command line
Cisco ASA CLI
configure terminalthreat-detection basic-threatthreat-detection scanning-threatendwrite memory
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Typed in configuration mode; write memory saves it, with no separate commit. Read every line first.
Read it back
show running-config threat-detectionBefore you type it2
- Written from the ASA 9.x command reference and not run on a device: read each line before you paste it.
- In multiple context mode, type it in the context it applies to (changeto context <name>).
How to confirm the fix
- Run show threat-detection rate and show running-config threat-detection.
Limits
- Scanning threat detection costs memory and CPU on busy devices; size it before turning shun on.
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.