OPS-12 Logging and Monitoring - Access, Storage and Deletion
Implement the logging and metadata rules through technically supported procedures so that only authorised users and systems can reach the records, records are retained for exactly the specified period, and they are delet
4
artefacts
3
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
system holds itEvidence a system already holds
- Permission listing for the log platform showing groups and their read or admin rights · Identity provider / directory
- Retention and lifecycle rules configured inside the log store · SIEM / log platform
- Deletion job output confirming expired records were removed · SIEM / log platform
periodic reviewEvidence produced at each review
- Access review record covering log platform accounts · Identity provider / directory
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
- Anyone in operations able to read raw logs regardless of their role
- Retention written into policy but never configured in the tool, so data lives indefinitely
- Archived log buckets exempted from the lifecycle rules
- Service accounts holding standing log export rights that are never reviewed
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 sheetOPS-11 Logging and Monitoring - Metadata Management Concept · OPS-13 Logging and Monitoring - Identification of Events