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 19 controls across our corpus
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.
- Annual review record
- The approved endpoint policy with approver and date
- The endpoint types in scope, including mobile and personally owned devices where permitted
- Evidence of communication to endpoint users
- The approved malware protection policy
- The asset classes in scope and the protection required for each
What closing it also buys you
The 19 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.
PCI DSS 4.010
NIST SP 800-53 Rev 53
FedRAMP High7
FedRAMP Moderate9
ISO 27002:202222
ISO 27001:202219
C5 (Germany)19
NIST SP 800-161 Rev 111
SOC 227
Azure Security Benchmark18
CIS Controls v89
NIST Cybersecurity Framework 2.012
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| PCI DSS 4.0 International (payment card industry; enforced contractually by payment brands and acquirers) | 10.6% | 38 of 360 |
| NIST SP 800-53 Rev 5 United States (federal information systems; voluntary for other organizations) | 3.6% | 37 of 1037 |
| FedRAMP High United States | 7.6% | 31 of 410 |
| FedRAMP Moderate United States | 9.6% | 31 of 323 |
| ISO 27002:2022 International | 22.9% | 25 of 109 |
| ISO 27001:2022 International | 19.5% | 25 of 128 |
| C5 (Germany) Germany | 19.8% | 24 of 121 |
| NIST SP 800-161 Rev 1 United States | 11.5% | 22 of 191 |
| SOC 2 United States | 27.9% | 17 of 61 |
| Azure Security Benchmark International | 18.8% | 16 of 85 |
| CIS Controls v8 International | 9.8% | 15 of 153 |
| NIST Cybersecurity Framework 2.0 United States | 12.3% | 13 of 106 |
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