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.
- Segmentation diagram
- DMARC reject record
- Encrypted DNS policy
- Firewall rule review
- Network segmentation diagram
- Network segmentation (VPC/subnets/security groups)
What closing it also buys you
The 91 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 progresses | Covered |
Controls reached |
|---|
| NIST SP 800-53 Rev 5 United States | 13.5% | 26 of 192 |
| NIST Cybersecurity Framework 2.0 United States | 19.8% | 21 of 106 |
| 3GPP 5G Security Architecture (TS 33.501) International (3GPP) | 41.9% | 18 of 43 |
| ASD Strategies to Mitigate Cyber Security Incidents Australia | 48.6% | 18 of 37 |
| NIST SP 800-171A Rev 3 United States (NIST) | 48.6% | 17 of 35 |
| Azure Security Benchmark International | 31.5% | 17 of 54 |
| AWS Well-Architected Security Pillar International | 18.0% | 16 of 89 |
| NIST SP 800-171A United States | 50.0% | 16 of 32 |
| API 1164 United States | 66.7% | 16 of 24 |
| ISO 27019 International | 34.8% | 16 of 46 |
| NIST SP 1800-32 United States | 36.4% | 16 of 44 |
| ISO 27017 International | 40.5% | 15 of 37 |
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