C5 (Germany) covers 65.9% of Azure Security Benchmark
56 of the 85 controls in Azure Security Benchmark are already satisfied by evidence you collected for C5 (Germany). 29 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 C5 (Germany) 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.
97 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.
C5 keeps asset records complete, accurate and valid across the lifecycle with every change logged.
C5 requires documented approval plus complete permanent erasure or physical destruction of media before hardware leaves production.
C5 approves hardware into production only after verifying error handling, logging, encryption, authentication and authorisation are securely configured.
C5 issues privileged access personally for a risk based limited period, logs the activity and alerts on misuse indicators.
C5 lets the customer restrict which images its users may launch and hardens provider supplied images to industry standards.
C5 fixes backup scope, frequency and retention against recovery targets, mandates encryption of backups and recovery testing.
C5 holds backup copies at a remote location, encrypted in transit, matching the main site's physical security level.
C5 watches backup execution and has qualified staff investigate and rectify malfunctions promptly.
Claims that did not hold
1 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.
judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion; C5-OPS-16 restricts access to the logging and monitoring components and controls their configuration changes; producing high quality alerts from log data is OPS-13
Claimed at high confidence before it was rejected.
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