PSS-04 Error handling and Logging Mechanisms
Provide error handling and logging that lets customers see who accessed which data, service or function and when, malfunctions during automatic or manual actions, and changes to security configuration, logging, authentic
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
- Sample audit log entries showing actor, object, action and timestamp · SIEM / log platform
- Configuration listing which security relevant changes generate a log record · SIEM / log platform
- Access control settings that protect log stores from alteration · Identity provider / directory
- Customer facing function allowing deletion or retention control of logs · 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
- Logs capture system events but not access to customer data
- Changes to the logging configuration are themselves not logged
- Customers can read logs while administrators can alter them without trace
- Logging capability shipped disabled by default and left undocumented
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 sheetPSS-03 Online Register of Known Vulnerabilities · PSS-05 Authentication Mechanisms