Who warns about it
Every framework below independently names this failure. They were written by different
bodies, in different jurisdictions, for different industries, and they agree.
What an auditor asks for
The artefacts named on the controls that warn about this failure. This is what closes
it, and what you will be asked to produce when somebody checks.
- Monitoring configuration and alert rules
- Anomaly detection logs
- Security event evaluation records
- Incident response playbooks
- Recovery and post incident reports
- Change management tickets with approvals
What closing it also buys you
The 13 controls that warn about this failure map onto controls in other
frameworks. Close them here and this much of each of those is closed too. It is the same work
counted once, which is usually the difference between a programme that finishes and one that
does not.
| Also progresses | Covered |
Controls reached |
|---|
| NIST SP 800-53 Rev 5 United States | 5.7% | 11 of 192 |
| NIST Cybersecurity Framework 2.0 United States | 9.4% | 10 of 106 |
| NIST SP 800-171A Rev 3 United States (NIST) | 25.7% | 9 of 35 |
| IEC 62443 International | 11.1% | 9 of 81 |
| APRA CPS 230 Operational Risk Management Australia | 19.1% | 9 of 47 |
| ISO/IEC 27557:2022 International (ISO/IEC) | 22.0% | 9 of 41 |
| Azure Security Benchmark International | 14.8% | 8 of 54 |
| API 1164 United States | 33.3% | 8 of 24 |
| ISO/IEC 27011:2024 International | 18.2% | 8 of 44 |
| PCI SSF International | 16.3% | 8 of 49 |
| NIST AI Risk Management Framework (AI RMF 1.0) United States (NIST) | 15.4% | 8 of 52 |
| NIST SP 800-190 United States | 17.8% | 8 of 45 |
Read as: closing this failure reaches that share of the named
framework's control library through cross-framework mappings held in our corpus. It is not a
claim of compliance with that framework, it is a measure of how much of it you have already
touched.
Where this comes from
Harvested from the control library itself. Every control in our corpus carries the evidence an
auditor expects and the ways implementations commonly fail, recorded when that control was
verified against its source document. This page is those two fields, for one failure, across
every framework that names it.
The overlap is computed by traversing
332,959 cross-framework control mappings out from the specific controls that
warn about this failure, not from the frameworks they sit in. Those mappings were built control
by control against source documents.
Nothing here is inferred, predicted or scored. The number at the top
is a count of frameworks.
All failure modes ยท
The index