Named by 5 frameworks

Nonconformities not logged or trended

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

Updated

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 5 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 progressesCovered Controls reached
ISO/IEC 17025:2017
International (ISO/IEC)
3.3%3 of 90
ISO 15189:2022
International (ISO)
3.9%3 of 77
ISO 56002
International
1.8%3 of 164
ISO 41001:2018
International (ISO)
1.8%3 of 168
ISO 39001:2012
International
1.8%3 of 169
ISO 37002:2021
International (ISO)
1.9%3 of 159
ISO 22313:2020
International (ISO)
1.8%3 of 167
AS9100D
International (Aerospace)
4.9%3 of 61
ISO/IEC 27003:2017
International
4.2%3 of 72
ISO 9001
International
6.2%3 of 48
ISO 45001:2018
International
3.6%2 of 56
ISO/IEC 42001:2023
International
2.5%2 of 80

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