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
ISO 30401:2018 Knowledge Management 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.
- PESTLE analysis
- Stakeholder map
- Context analysis report
- PESTLE assessment
- Internal issues register
- Context analysis document
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.
ISO 27701:20191
ISO 50001:20183
ISO 41001:20182
ISO 560021
ISO/IEC 27003:20173
ISO 39001:20122
ISO/IEC 23894:20231
ISO 27005:20221
ISO 45001:20181
ISO/IEC 42001:20231
ISO 22301:20191
ISO 31000:20182
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| ISO 27701:2019 International | 1.4% | 2 of 145 |
| ISO 50001:2018 International | 3.0% | 2 of 66 |
| ISO 41001:2018 International (ISO/TC 267); adopted as EN ISO 41001:2018 (BS, DIN, SIST, I.S.) and others | 2.3% | 2 of 86 |
| ISO 56002 International (ISO/TC 279); adopted as EN ISO 56002:2021, AS ISO 56002:2020, I.S. EN ISO 56002:2021 and others | 1.5% | 2 of 131 |
| ISO/IEC 27003:2017 International | 3.9% | 2 of 51 |
| ISO 39001:2012 International (ISO/TC 241); adopted as IRAM-ISO 39001:2015, BS ISO 39001:2012, UNE-ISO 39001 and others | 2.4% | 2 of 83 |
| ISO/IEC 23894:2023 International (ISO/IEC JTC 1/SC 42); adopted as EN ISO/IEC 23894:2024 (SIST, I.S. and other national EN editions) and AS ISO/IEC 23894:2023 | 1.7% | 2 of 121 |
| ISO 27005:2022 International (ISO/IEC JTC 1/SC 27); adopted as EN ISO/IEC 27005:2024 | 1.7% | 1 of 58 |
| ISO 45001:2018 International | 1.1% | 1 of 94 |
| ISO/IEC 42001:2023 International | 1.1% | 1 of 88 |
| ISO 22301:2019 International | 1.8% | 1 of 57 |
| ISO 31000:2018 International | 2.6% | 1 of 39 |
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