SOC 2Azure Security Benchmark

SOC 2 covers 37.6% of Azure Security Benchmark

32 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for SOC 2. 53 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.

37.6%
of the target already covered
32
controls evidenced
53
genuine gaps
0
claims rejected in review

This number is directional. It says how much of Azure Security Benchmark your SOC 2 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.

73 candidate mappings were examined and 2 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.

Asset Management4 of 5 evidenced, 1 to do
Backup and Recovery3 of 4 evidenced, 1 to do
Endpoint Security2 of 3 evidenced, 1 to do
Data Protection5 of 8 evidenced, 3 to do
Incident Response4 of 7 evidenced, 3 to do
Posture and Vulnerability Management3 of 7 evidenced, 4 to do
Governance and Strategy4 of 10 evidenced, 6 to do
Privileged Access3 of 8 evidenced, 5 to do
Logging and Threat Detection2 of 7 evidenced, 5 to do
Network Security2 of 10 evidenced, 8 to do
DevOps Security0 of 7 evidenced, 7 to do
Identity Management0 of 9 evidenced, 9 to do

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.

SOC2-CC6.1ASB v3 AM-1argued against and upheld
Track asset inventory and their risks

SOC 2 requires an identified and managed inventory of information assets and owners.

SOC2-CC6.5ASB v3 AM-3argued against and upheld
Ensure security of asset lifecycle management

Assets may be decommissioned only after data can no longer be read or recovered.

SOC2-CC6.3ASB v3 AM-4argued against and upheld
Limit access to asset management

Access to functions that modify assets is authorized by role and least privilege.

SOC2-CC6.8ASB v3 AM-5argued against and upheld
Use only approved applications in virtual machine

SOC 2 requires restriction of software execution to authorized software.

SOC2-A1.2ASB v3 BR-1argued against and upheld
Ensure regular automated backups

SOC 2 requires implemented and operated data backup processes for availability.

SOC2-A1.2ASB v3 BR-3argued against and upheld
Monitor backups

A1.2 explicitly requires backup processes to be monitored, not merely configured.

SOC2-A1.3ASB v3 BR-4argued against and upheld
Regularly test backup

SOC 2 requires periodic testing of recovery procedures against backups.

SOC2-C1.1ASB v3 DP-1argued against and upheld
Discover, classify, and label sensitive data

Confidential information must be identified and designated when created or received.

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