AWS Well-Architected Security Pillar covers 54.1% of Azure Security Benchmark
46 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 39 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 AWS Well-Architected Security Pillar 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.
98 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.
Organisation level service control policies restrict deployment to approved services, the same enforcement mechanism.
Automated discovery and classification tooling produces the sensitive data inventory required.
Documented classification scheme with handling requirements and owners is the labelling standard this needs.
Enforced TLS 1.2 or higher with legacy ciphers disabled is the identical requirement.
Automated detection and correction of unencrypted stores evidences encryption by default holds.
Encryption at rest enforced by default through account settings and policy matches directly.
Customer managed keys for sensitive data is exactly the option this control requires.
Centralised key management with hierarchies, secured vault and policy driven rotation matches the standard.
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