Azure Security Benchmark covers 33.3% of PCI DSS 4.0
83 of the 249 controls in PCI DSS 4.0 are already satisfied by evidence you collected for Azure Security Benchmark. 166 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 PCI DSS 4.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.
177 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.
Documented network security guidance, policy and standards is the network control policy required.
Defined secure configuration baselines per resource type include network control standards.
Detecting services and protocols at operating system, application and package layers inventories them.
Applying compensating controls where insecure protocols cannot be disabled is this requirement.
Edge firewall with documented rules controls inbound traffic to the environment.
Security group rules on subnets restrict inbound traffic to the sensitive environment.
Edge firewall control of outbound traffic restricts egress from the environment.
A firewall at the enterprise edge is the control between trusted and untrusted networks.
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