What evidence do auditors commonly ask for on DE.AE-04 The estimated impact and scope of adverse events are understood?

Impact scoring rubric tied to business service catalog; Blast radius assessment template populated for recent events; Service dependency map referenced during triage; Data classification overlay used to estimate exposure; Severity decision log with assessor identity and timestamp.

What is the most common gap auditors find on DE.AE-04?

Impact estimates not linked to the service catalog

NIST CSF 2.0 · DE - Detect

`DE.AE-04` The estimated impact and scope of adverse events are understood

The estimated impact and scope of adverse events are understood

Source: NIST CSF 2.0, DE.AE-04. 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.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Severity decision log with assessor identity and timestamp · SIEM / log platform

periodic reviewEvidence produced at each review

Blast radius assessment template populated for recent events · Document repository

governing documentDocuments that govern the control

Impact scoring rubric tied to business service catalog · 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 sheet

DE.AE-03 Information is correlated from multiple sources · DE.AE-06 Information on adverse events is provided to authorized staff and tools