DE.AE-04 The estimated impact and scope of adverse events are understood
The estimated impact and scope of adverse events are understood.
5
artefacts
1
held by a system
0
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
- Severity decision log with assessor identity and timestamp · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Impact scoring rubric tied to business service catalog · Document repository
- Blast radius assessment template populated for recent events · Document repository
- Service dependency map referenced during triage · Document repository
- Data classification overlay used to estimate exposure · Policy repository / GRC workspace
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
- Impact estimates not linked to the service catalog
- No method to estimate scope when telemetry is partial
- Data classification missing on cloud storage assets
- Severity overridden without rationale captured
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-03 Information is correlated from multiple sources · DE.AE-06 Information on adverse events is provided to authorized staff and tools