10.7.2 Critical security control failure detection (all entities)
Failures of critical security control systems are detected, alerted, and addressed promptly for all entities (not just service providers), with documented response procedures.
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
- Health monitoring configuration per control · SIEM / log platform
- Alert routing to on-call · SIEM / log platform
- Sample failure tickets with response evidence · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Lessons learned records · Document repository
governing documentDocuments that govern the control
- Documented list of critical security controls · Document repository
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
- List of critical controls missing
- Alerts to no one
- No documented response
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.7.1 Critical security control failure detection (SP) · 10.7.3 Failure response timeline