OPS-16 Logging and Monitoring - Configuration
Restrict access to the system components used for logging and monitoring to authorised users, and make every change to their configuration through the applicable change management policies.
4
artefacts
4
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
- Role membership list for administrators of the monitoring platform · Identity provider / directory
- Approved change tickets covering the most recent alterations to log collection rules · SIEM / log platform
- Audit trail of edits to detection rules and log source settings · SIEM / log platform
- Segregation evidence separating log administrators from system administrators · SIEM / log platform
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
- Detection rules edited directly in the console with no change record raised
- System owners able to alter or remove logging configuration on their own hosts
- Leavers keeping administrative rights on the monitoring platform
- No approval gate for changes that reduce log 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 sheetOPS-15 Logging and Monitoring - Accountability · OPS-17 Logging and Monitoring - Availability of the Monitoring Software