Named by 3 frameworks

no governance

3 of the 723 frameworks in our corpus warn about this same failure, across 3 separate controls. That convergence is the measurement: it is not one standard's opinion.

Data measured , page built 22 September 2026 at 16:18 UTC.

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 3 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.

What closing it also buys you

The 3 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.04
ISO 15189:20226
SOC 29
AWS Well-Architected Security Pillar4
ISO 2701710
ISO 270188
NIST SP 800-1908
ISO 560022
PCI P2PE9
ISO/IEC 27557:20229
ISO/IEC 38500:20249
APRA CPS 23411

Scaled against the framework this reaches furthest into, not against a hundred percent. Exact figures below.

Also progressesCovered Controls reached
NIST Cybersecurity Framework 2.0
United States
4.7%5 of 106
ISO 15189:2022
International (ISO)
6.5%5 of 77
SOC 2
United States
9.3%5 of 54
AWS Well-Architected Security Pillar
International
4.5%4 of 89
ISO 27017
International
10.8%4 of 37
ISO 27018
International
8.9%4 of 45
NIST SP 800-190
United States
8.9%4 of 45
ISO 56002
International
2.4%4 of 164
PCI P2PE
International
9.1%4 of 44
ISO/IEC 27557:2022
International (ISO/IEC)
9.8%4 of 41
ISO/IEC 38500:2024
International (ISO/IEC)
9.5%4 of 42
APRA CPS 234
Australia
11.4%4 of 35

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.

Where this goes next

  1. The other failures the whole industry independently agrees on:The full catalogue →
  2. Everything else Azure Security Benchmark asks for, and what it overlaps with:Azure Security Benchmark in full →
  3. Which companies are disclosing the events this failure produces:Who disclosed it →
  4. What changed in those disclosures this week:What changed →
  5. And today's story, which is usually one of these arriving in public:Today's edition →

All failure modes ยท The index