DE.AE-5 Incident alert thresholds established
What the standard requires
Incident alert thresholds are established
Quoted verbatim from NIST Cybersecurity Framework (CSF) 1.1, which is in the public domain.
Maps to 1 control in 1 other framework
| Framework | Control |
|---|---|
| CMMC Level 2 | AU.L2-3.3.4 Audit failure alerting |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
Google Chronicle
Incidents & alerts
Splunk Enterprise Security
Incidents & alerts
VMware Carbon Black
Incidents & alerts
These connectors produce data relevant to NIST Cybersecurity Framework (1.1, legacy)’s Detect (DE) family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
Track DE.AE-5 with evidence behind it
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.