Azure Security Benchmark covers 46.4% of NIST SP 800-171 Rev 3
45 of the 97 controls in NIST SP 800-171 Rev 3 are already satisfied by evidence you collected for Azure Security Benchmark. 52 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.
What this leaves you to do
NIST SP 800-171 Rev 3 has 97 controls. Holding Azure Security Benchmark already evidences 45 of them, so the work in front of you is 52 controls, not 97, which is 54% of the standard rather than all of it.
That is the whole claim. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
In money, using only our numbers. The full report is $299 and names 45 controls of NIST SP 800-171 Rev 3 you do not have to implement again, which is $6.64 per control identified. That arithmetic uses our price and our count and assumes nothing about you.
In your hours, using your assumption. We do not know what a control costs you to implement, so pick the column that looks like your organisation. These are your figures, not our claim.
| If a control takes you | 4 hours | 8 hours | 16 hours |
|---|---|---|---|
| the 45 already evidenced are | 180 hours | 360 hours | 720 hours |
| and the 52 remaining are | 208 hours | 416 hours | 832 hours |
Multiply by your own rate. We publish no rate because we have not measured yours, and a number built on an invented rate is the kind of claim this platform exists to argue against.
This number is directional. It says how much of NIST SP 800-171 Rev 3 your Azure Security Benchmark 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.
121 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.
Regular reconciliation of accounts and entitlements is the account review element.
Joiner mover leaver processing with access reviews is account management end to end.
A central identity system is where accounts are created, modified and disabled.
Role based access control enforcing granted permissions is access enforcement.
Conditional access enforces the authorisation decision at each access attempt.
Private endpoints and service firewall rules constrain flows to platform services.
Subnet and security group rules enforce permitted information flows between zones.
An explicit separation of duties strategy across identity and subscriptions is this requirement.
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