What evidence do auditors commonly ask for on DE.AE-06 Information on adverse events is provided to authorized staff and tools?

Notification matrix mapping event severity to recipient roles; Ticketing workflow with mandatory acknowledgement step; On-call rotation roster with paging path tested quarterly; Distribution list governance with review log; Sample notification trace from event detection to receipt.

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

Recipients lists outdated when staff change roles

NIST CSF 2.0 · DE - Detect

`DE.AE-06` Information on adverse events is provided to authorized staff and tools

Information on adverse events is provided to authorized staff and tools

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

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Notification matrix mapping event severity to recipient roles · Policy repository / GRC workspace
Ticketing workflow with mandatory acknowledgement step · HR system / LMS
On-call rotation roster with paging path tested quarterly · Document repository
Distribution list governance with review log · Policy repository / GRC workspace
Sample notification trace from event detection to receipt · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Recipients lists outdated when staff change roles
Pager fatigue causes acknowledgement timeouts
Critical vendors not in notification matrix
No closed loop confirming receipt by named individual

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-04 The estimated impact and scope of adverse events are understood · DE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis