10.7.1 Critical security control failure detection (SP)
Additional requirement for service providers: failures of critical security control systems are detected, alerted, and addressed promptly, including responses documented.
5
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
- List of critical security controls and health monitoring · SIEM / log platform
- Alerting configuration for control failures · SIEM / log platform
- Time-to-detect and time-to-restore metrics · Backup / DR tooling
periodic reviewEvidence produced at each review
- Incident records of past failures · SIEM / log platform
governing documentDocuments that govern the control
- Response runbooks · 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
- No health monitoring
- Failures missed
- Response runbooks absent
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.6.3 Time settings protected · 10.7.2 Critical security control failure detection (all entities)