What evidence do auditors commonly ask for on DE.AE-03 Information is correlated from multiple sources?

Log source inventory with coverage matrix against asset register; Data normalization schema for SIEM ingest pipelines; Cross-source correlation queries (network, endpoint, identity, cloud); SOAR playbooks that enrich events with threat intelligence; Sample correlated alert with multi-source citation trail.

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

SaaS and PaaS logs not piped to the SIEM

NIST CSF 2.0 · DE - Detect

`DE.AE-03` Information is correlated from multiple sources

Information is correlated from multiple sources. Control from NIST Cybersecurity Framework 2.0 framework, domain: DE - Detect.

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

Sample correlated alert with multi-source citation trail · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Log source inventory with coverage matrix against asset register · Policy repository / GRC workspace
Data normalization schema for SIEM ingest pipelines · Policy repository / GRC workspace
Cross-source correlation queries (network, endpoint, identity, cloud) · Policy repository / GRC workspace
SOAR playbooks that enrich events with threat intelligence · 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

SaaS and PaaS logs not piped to the SIEM
Timestamp skew across sources defeats correlation joins
Identity provider logs not joined to endpoint telemetry
Enrichment relies on stale threat feeds

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-02 Potentially adverse events are analyzed to better understand associated activities · DE.AE-04 The estimated impact and scope of adverse events are understood