Azure Security Benchmark covers 41.5% of NIST Cybersecurity Framework 2.0
44 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for Azure Security Benchmark. 62 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 NIST Cybersecurity Framework 2.0 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.
117 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.
Investigating events across broad log sources is the analysis of potentially adverse activity.
Tuned analytics rules turn raw signals into analysed, high quality adverse event findings.
Requiring diverse data sources without blind spots is exactly multi source correlation.
SIEM aggregation of security logs is the correlation of information from multiple sources.
Combining alert severity with affected asset sensitivity establishes impact and scope.
Notification routing ensures adverse event information reaches the correct responder.
Creating incidents from alerts meeting quality criteria is incident declaration.
Flow, firewall and DNS logging monitors networks and network services for adverse events.
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