APEC Cross-Border Privacy Rules (CBPR) System
Risk

APEC Cross-Border Privacy Rules (CBPR) System CBPR-09: Preventing Harm

Design protections to prevent misuse of personal information taking into account risks of harm to individuals.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 23 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

HIPAA Security Rule · 3 controls

  • ASBv3-DP-1 Discover, classify, and label sensitive data
  • ASBv3-GS-3 Define and implement data protection strategy

CCPA/CPRA · 2 controls

GDPR · 2 controls

ISO 27701:2019 · 2 controls

  • 5.4.1 Actions to address risks and opportunities
  • 7.2.5 Privacy impact assessment

NIST SP 800-66 Rev 2 · 2 controls

APPI · 1 control

  • AUCDR-PS-12 Privacy Safeguard 12 - Security of CDR data and destruction or de-identification of redundant CDR data
  • MYHR-CUD-6 Prohibition on use for a prohibited purpose

C5 (Germany) · 1 control

FedRAMP High · 1 control

  • SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 1 control

  • SA-8 Security and Privacy Engineering Principles

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of APEC Cross-Border Privacy Rules (CBPR) System have you already done?

APEC Cross-Border Privacy Rules (CBPR) System CBPR-09 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APEC Cross-Border Privacy Rules (CBPR) System your existing evidence covers. Hold GDPR and 43 of 59 APEC Cross-Border Privacy Rules (CBPR) System controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.

Query this from an agent

The graph holds this control, the 23 it maps to, and the evidence behind each claim, over MCP and REST.