3 standards bodies wrote this down separately. None of them consulted the others. That is not a preference you can argue with, it is what happens.From 8 controls across our corpus
COSO 2013 Internal Control Integrated Framework Evidence & Implementation Kit
This is the complete documentation set: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
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.
- Risk register with likelihood, impact, and treatment owners
- Penetration test report with retest evidence
- Risk acceptance memos signed by accountable executives
- Threat intelligence feed subscriptions and triage workflow
- Vulnerability scan reports for internal, external, and authenticated scopes
- Risk assessment methodology approved by leadership
What closing it also buys you
The 4 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.
PCI DSS 4.07
NIST Cybersecurity Framework 2.017
Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.15
SOC 213
CIS Controls v84
CFTC System Safeguards (17 CFR 37, 38, 39, 49)15
APRA CPS 230 Operational Risk Management14
C5 (Germany)5
NIST SP 800-53 Rev 51
ISO 27701:20194
Azure Security Benchmark5
ISO 22301:20198
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| PCI DSS 4.0 International | 7.2% | 18 of 249 |
| NIST Cybersecurity Framework 2.0 United States | 17.0% | 18 of 106 |
| Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 International | 5.1% | 10 of 197 |
| SOC 2 United States | 13.1% | 8 of 61 |
| CIS Controls v8 International | 4.6% | 7 of 153 |
| CFTC System Safeguards (17 CFR 37, 38, 39, 49) United States (CFTC) | 15.4% | 6 of 39 |
| APRA CPS 230 Operational Risk Management Australia | 14.0% | 6 of 43 |
| C5 (Germany) Germany | 5.0% | 6 of 121 |
| NIST SP 800-53 Rev 5 United States | 1.9% | 6 of 320 |
| ISO 27701:2019 International | 4.1% | 6 of 145 |
| Azure Security Benchmark International | 5.9% | 5 of 85 |
| ISO 22301:2019 International | 8.8% | 5 of 57 |
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