FedRAMP Moderate covers 78.8% of Azure Security Benchmark
67 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for FedRAMP Moderate. 18 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 FedRAMP Moderate 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.
165 candidate mappings were examined and 1 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.
A current component inventory with owners and defined information is the same requirement
Restricting the use of functions, ports, protocols and services to those approved matches
Sanitisation before disposal, release or reuse makes decommissioning secure
Inventory updates during installation and removal cover the decommission path
Inventory ownership and accountability information is required and reviewed
Preventing program execution blocks unauthorised software from running
Deny all, allow by exception authorised software is the allow list requirement
System backups at a defined frequency with retention and recovery objectives match directly
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