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.
3
artefacts
3
held by a system
0
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
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
- Investigation records showing correlated analysis · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
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
- Logs collected centrally but never correlated
- Correlation rules present but untuned and unreviewed
- Key sources absent from aggregation
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 sheetAU.L2-3.3.4 Audit Failure Alerting · AU.L2-3.3.6 Reduction & Reporting