NIST SP 800-218 covers 9.4% of Azure Security Benchmark
8 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for NIST SP 800-218. 77 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.
This number is directional. It says how much of Azure Security Benchmark your NIST SP 800-218 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.
33 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.
Where the gaps are
Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.
Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.
Claims that held
A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.
Threat modelling to identify how an attacker could abuse the system is stated directly here.
Tracking security risks and design decisions is how mitigating controls get enumerated and kept.
Dependency and known vulnerability analysis of components is software composition analysis.
Tracking origin and version of each component and verifying provenance secures the software supply chain.
A machine readable bill of materials per release is the third party component inventory required.
Protecting source, infrastructure as code and build scripts from unauthorized change secures the pipeline.
Secure environments covering repositories and build systems is exactly securing DevOps infrastructure.
Version controlled toolchain configuration keeps build and repository security settings under control.
Claims that did not hold
Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.
The full report
Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.
Buy this crosswalk