AU.L2-3.3.1 System Auditing
Generate and retain system audit logs in sufficient scope and detail to support monitoring, analysis, investigation and reporting of unlawful or unauthorized system activity.
4
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
- Logging configuration on in scope systems · SIEM / log platform
- Retention settings and evidence logs are retained for the defined period · SIEM / log platform
- Sample audit records showing captured content · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Defined auditable event list and rationale for its scope · Policy repository / GRC workspace
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
- Logging enabled with default event sets never assessed for sufficiency
- Retention shorter than investigation needs
- In scope systems missing from logging coverage
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 sheetAT.L2-3.2.3 Insider Threat Awareness · AU.L2-3.3.2 User Accountability