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.
5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
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