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 4 controls across our corpus
EASA Part-IS Aviation Information Security 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.
- Risk assessment methodology
- Risk register
- Aviation impact mapping
- Annual reassessment
- Periodic assessment reports
- Change-triggered reassessments
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/IEC 23894:20233
Bank Secrecy Act / Anti-Money Laundering (BSA/AML)9
NIST SP 800-3037
BSI IT-Grundschutz1
ISO/IEC 29134:20233
UAE Virtual Asset Regulatory Authority (VARA) Regulations10
SSAE 181
ISO 310007
ISO 2700511
Responsible Minerals Initiative (RMI)16
UNESCO Recommendation on the Ethics of AI5
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| ISO/IEC 23894:2023 International | 3.3% | 4 of 121 |
| Bank Secrecy Act / Anti-Money Laundering (BSA/AML) United States | 9.1% | 4 of 44 |
| NIST SP 800-30 United States | 37.5% | 3 of 8 |
| BSI IT-Grundschutz Germany (used across the German-speaking countries and by German public bodies under the UP Bund) | 1.7% | 3 of 180 |
| ISO/IEC 29134:2023 International (ISO/IEC JTC 1/SC 27); adopted as CSA ISO/IEC 29134:24 and nationally | 3.5% | 3 of 85 |
| UAE Virtual Asset Regulatory Authority (VARA) Regulations United Arab Emirates — Dubai | 10.0% | 3 of 30 |
| SSAE 18 United States (AICPA attestation standards; every CPA attestation engagement, including SOC 1, SOC 2 and SOC 3) | 1.0% | 3 of 308 |
| ISO 31000 International | 7.0% | 3 of 43 |
| NIST SP 800-53 Rev 5 United States | 0.9% | 3 of 320 |
| ISO 27005 International | 11.5% | 3 of 26 |
| Responsible Minerals Initiative (RMI) International (RBA/RMI) | 16.7% | 3 of 18 |
| UNESCO Recommendation on the Ethics of AI International | 5.3% | 2 of 38 |
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