NIST SP 800-172 covers 23.5% of Azure Security Benchmark
20 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for NIST SP 800-172. 65 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-172 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.
53 candidate mappings were examined and 9 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.
Automated discovery maintaining a current, complete and accurate resource inventory is this control.
Restricting deployment to an authoritative source of approved and vetted components is this control.
Automated detection then removal of unauthorized components blocks unauthorized software from running.
An authoritative repository of approved vetted software is the allow list this control requires.
Verifying correctness of security critical software by review and analysis is static application security testing.
Verifying correctness of security critical software by testing and evaluation is dynamic security testing.
Automated generation, rotation and management of credentials for accounts without multifactor is this control.
Bidirectional cryptographic replay resistant authentication is exactly server-to-server strong authentication.
Claims that did not hold
9 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.
control identity corrected 2026-08-19: issued 3.14.3e is scope inclusion or segregation into purpose-specific networks; these mappings are supply chain provenance, a subject absent from the issued 800-172
Claimed at high confidence before it was rejected.
control identity corrected 2026-08-19: issued 3.13.2e is introducing unpredictability into operations; these mappings are least privilege and secure engineering, a subject that appears nowhere in the issued 800-172
Claimed at high confidence before it was rejected.
corrected 2026-08-19: judged from a title claiming multifactor authentication, while the control carried 3.5.2e password-management text. Issued 800-172 3.5.3e is comply-to-connect: prohibit connection of unknown or unverified components. Authentication evidence does not satisfy it.
Claimed at high confidence before it was rejected.
corrected 2026-08-19: judged from a title claiming multifactor authentication, while the control carried 3.5.2e password-management text. Issued 800-172 3.5.3e is comply-to-connect: prohibit connection of unknown or unverified components. Authentication evidence does not satisfy it.
Claimed at high confidence before it was rejected.
control identity corrected 2026-08-19: issued 3.13.1e is component diversity to limit malicious code propagation; these mappings are boundary protection and segmentation, judged against 3.1.3e's content which this control was wrongly carrying
Claimed at high confidence before it was rejected.
control identity corrected 2026-08-19: issued 3.13.1e is component diversity to limit malicious code propagation; these mappings are boundary protection and segmentation, judged against 3.1.3e's content which this control was wrongly carrying
Claimed at high confidence before it was rejected.
control identity corrected 2026-08-19: issued 3.13.1e is component diversity to limit malicious code propagation; these mappings are boundary protection and segmentation, judged against 3.1.3e's content which this control was wrongly carrying
Claimed at high confidence before it was rejected.
control identity corrected 2026-08-19: issued 3.13.2e is introducing unpredictability into operations; these mappings are least privilege and secure engineering, a subject that appears nowhere in the issued 800-172
Claimed at high confidence before it was rejected.
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