EvidenceSheet
CMMC 2.0 · Audit and Accountability

AU.L2-3.3.5 Audit Correlation

Bring audit review, analysis and reporting together across sources so signs of unlawful, unauthorized, suspicious or unusual activity can be investigated and answered.

Source: CMMC 2.0, AU.L2-3.3.5. 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 CMMC 2.0 in the compliance library.

3
artefacts
2
held by a system
1
at each review
easy
to go live
SIEM / log platform
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

  • Correlation capability configuration, for example SIEM rules · SIEM / log platform
  • Evidence logs from multiple sources are aggregated · SIEM / log platform

periodic reviewEvidence produced at each review

  • Investigation records showing correlated analysis · Policy repository / GRC workspace

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.

Common gaps auditors find

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

AU.L2-3.3.4 Audit Failure Alerting · AU.L2-3.3.6 Reduction & Reporting