4 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 13 controls across our corpus
Belgium CyberFundamentals 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.
- Incident response plan and playbooks
- Tabletop exercise reports
- Incident ticket history with timelines
- Forensic toolkit and chain-of-custody log
- Post-incident review minutes
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.
NIST Cybersecurity Framework 2.06
Nigeria Data Protection Act 2023 (NDPA)8
Nebraska Data Privacy Act50
OSFI B-1337
Ghana Cybersecurity Act25
API 11641
NIST SP 1800-326
SANS Incident Handler's Handbook and PICERL Methodology7
ISO/IEC 27019:20244
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| NIST Cybersecurity Framework 2.0 United States | 6.6% | 7 of 106 |
| Nigeria Data Protection Act 2023 (NDPA) Nigeria | 8.0% | 4 of 50 |
| Nebraska Data Privacy Act United States - Nebraska | 50.0% | 4 of 8 |
| OSFI B-13 Canada | 37.5% | 3 of 8 |
| Ghana Cybersecurity Act Ghana | 25.0% | 3 of 12 |
| API 1164 United States (API; referenced by the TSA Pipeline Security Guidelines and used internationally) | 1.8% | 3 of 163 |
| IEC 62443 International (IEC TC 65/WG 10 with ISA99); adopted as EN IEC 62443 | 0.8% | 3 of 399 |
| NIST SP 1800-32 United States | 6.8% | 3 of 44 |
| SANS Incident Handler's Handbook and PICERL Methodology International (SANS Institute) | 7.5% | 3 of 40 |
| NIST SP 800-53 Rev 5 United States | 0.9% | 3 of 320 |
| PCI P2PE Global (PCI Security Standards Council; P2PE solution providers, component providers, application vendors and merchants operating merchant-managed solutions) | 0.7% | 3 of 407 |
| ISO/IEC 27019:2024 International (ISO/IEC JTC 1/SC 27) | 4.5% | 3 of 67 |
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