5 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 45 controls across our corpus
FedRAMP High 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.
- Denial of service protection configuration and capacity test results
- Cryptographic standards specifying approved algorithms and key lengths
- TLS configuration scan results across in scope endpoints
- Network segmentation diagrams with VLAN and zone mapping
- Boundary protection architecture with firewall and proxy rule documentation
- Key management procedures including rotation and escrow
What closing it also buys you
The 10 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.09
SOC 223
NIST SP 800-53 Rev 54
Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.15
ISO 27002:202210
ISO 27001:202211
CIS Controls v87
C5 (Germany)8
Azure Security Benchmark9
NIST SP 800-171 Rev 37
AWS Well-Architected Security Pillar9
CMMC 2.04
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 | 9.6% | 24 of 249 |
| SOC 2 United States | 23.0% | 14 of 61 |
| NIST SP 800-53 Rev 5 United States | 4.4% | 14 of 320 |
| Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 International | 5.6% | 11 of 197 |
| ISO 27002:2022 International | 10.6% | 11 of 104 |
| ISO 27001:2022 International | 11.0% | 11 of 100 |
| CIS Controls v8 International | 7.2% | 11 of 153 |
| C5 (Germany) Germany | 8.3% | 10 of 121 |
| Azure Security Benchmark International | 9.4% | 8 of 85 |
| NIST SP 800-171 Rev 3 United States | 7.2% | 7 of 97 |
| AWS Well-Architected Security Pillar International | 9.5% | 6 of 63 |
| CMMC 2.0 United States | 4.5% | 5 of 110 |
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