Azure Security Benchmark covers 10.2% of APEC Cross-Border Privacy Rules (CBPR) System
6 of the 59 controls in APEC Cross-Border Privacy Rules (CBPR) System are already satisfied by evidence you collected for Azure Security Benchmark. 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.
This number is directional. It says how much of APEC Cross-Border Privacy Rules (CBPR) System 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.
27 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. Disclosed shape: this pair clears the minimum at exactly 20 high confidence mappings and all of them sit inside Principle VII Security Safeguards, 6 of 59 requirements. Notice, Choice, Collection Limitation, Uses, Integrity, Access and Correction and the Accountability questions are genuine gaps, not omissions. Read it as which Azure Security Benchmark controls evidence CBPR security safeguards.
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.
Enterprise data protection strategy sets the classification and protection standards this principle demands.
Encryption at rest for all storage is a core reasonable safeguard for held personal information.
Phishing resistant multi-factor authentication is a reasonable safeguard against unauthorised access.
Posture management strategy establishes the policy, procedure and standards for secure configuration.
Documented enterprise data protection standards are the written information security policy.
Documented security roles, responsibilities and accountabilities with leadership endorsement form the policy.
Encryption at rest protects personal information against unauthorised access, use and disclosure.
Enforced TLS protects personal information in transit against interception and modification.
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