10.2.2 Audit log content
Audit logs record at least user identification, type of event, date and time, success or failure indication, origination of event, and identity or name of affected data, system component, resource, or service.
5
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
- Sample logs containing all six required fields · SIEM / log platform
- Log schema documentation per source · SIEM / log platform
- Gap remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- SIEM normalization mapping · Policy repository / GRC workspace
- Coverage matrix verifying field completeness · 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
- Source or affected resource missing
- Cloud logs lack origination
- No normalization
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 sheet10.2.1.7 Log creation and deletion of system level objects · 10.3.1 Read access to logs restricted