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
DAMA-DMBOK2 Data Management Body of Knowledge 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.
- security charter
- board reporting pack
- risk register
- policy library
- data policy catalog
- standards register
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.
ISO/IEC 27557:202217
ISO 15189:20227
ISO/IEC 23894:20237
IEC 62304:2015 Medical Device Software Lifecycle Processes18
NIST SP 800-171A Rev 314
NIST Cybersecurity Framework 2.04
PIC/S Guide to Good Manufacturing Practice for Medicinal Products44
PCI P2PE9
IEC 60601-110
FFIEC IT Examination Handbook5
ISO 560022
ISO 22320:201810
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| ISO/IEC 27557:2022 International (ISO/IEC) | 17.1% | 7 of 41 |
| ISO 15189:2022 International (ISO) | 7.8% | 6 of 77 |
| ISO/IEC 23894:2023 International | 7.1% | 6 of 85 |
| IEC 62304:2015 Medical Device Software Lifecycle Processes International | 18.2% | 6 of 33 |
| NIST SP 800-171A Rev 3 United States (NIST) | 14.3% | 5 of 35 |
| NIST Cybersecurity Framework 2.0 United States | 4.7% | 5 of 106 |
| PIC/S Guide to Good Manufacturing Practice for Medicinal Products International (PIC/S — 54 member authorities) | 44.4% | 4 of 9 |
| PCI P2PE International | 9.1% | 4 of 44 |
| IEC 60601-1 International | 10.5% | 4 of 38 |
| FFIEC IT Examination Handbook United States | 5.1% | 4 of 78 |
| ISO 56002 International | 2.4% | 4 of 164 |
| ISO 22320:2018 International | 10.8% | 4 of 37 |
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