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.
- Scope statement
- Privacy risk assessment
- Definitions glossary
- Reference catalog
- Site list
- Process map
What closing it also buys you
The 6 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 |
|---|
| ISO/IEC 27557:2022 International (ISO/IEC) | 19.5% | 8 of 41 |
| ISO/IEC 23894:2023 International | 8.2% | 7 of 85 |
| NIST Privacy Framework United States | 75.0% | 6 of 8 |
| ISO/IEC 29100:2024 International | 15.0% | 6 of 40 |
| NIST AI Risk Management Framework (AI RMF 1.0) United States (NIST) | 11.5% | 6 of 52 |
| IEC 62304:2015 Medical Device Software Lifecycle Processes International | 18.2% | 6 of 33 |
| ISO 15189:2022 International (ISO) | 7.8% | 6 of 77 |
| Trinidad and Tobago Data Protection Act 2011 Trinidad and Tobago | 100.0% | 5 of 5 |
| Nigeria Data Protection Act 2023 (NDPA) Nigeria | 62.5% | 5 of 8 |
| Nebraska Data Privacy Act United States - Nebraska | 62.5% | 5 of 8 |
| Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (UAE PDPL) United Arab Emirates | 41.7% | 5 of 12 |
| Austria Data Protection Act (Datenschutzgesetz, DSG, amended 2018) Austria | 35.7% | 5 of 14 |
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