DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
Incidents are declared when adverse events meet the defined incident criteria
Source: NIST CSF 2.0, DE.AE-08. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Declared incident log with criteria citation · SIEM / log platform
periodic reviewEvidence produced at each review
- Tabletop exercise demonstrating declaration thresholds · Document repository
- Post-incident review on declaration timing · Document repository
governing documentDocuments that govern the control
- Incident declaration criteria document with examples · Document repository
- Triage decision tree from event to incident · Document repository
First move
Common gaps auditors find
- Criteria framed in security jargon, not business outcomes
- Analysts hesitant to declare due to escalation overhead
- No retro on declarations that should have been earlier
- Criteria not refreshed after major architecture changes
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetDE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis · DE.CM-01 Networks and network services are monitored to find potentially adverse events