APEC Cross-Border Privacy Rules (CBPR) System
CBPR Program Requirements: Integrity of Personal Information

APEC Cross-Border Privacy Rules (CBPR) System CBPR-PR-24: Corrections communicated after disclosure

Where corrections are made after the information has been disclosed, and the inaccuracy affects the purposes of use, the applicant communicates the corrections to the third parties concerned.

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

What else in your programme already covers this

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

APPI · 1 control

  • APPI-A34 Request for Correction, Addition or Deletion
  • AUCDR-PS-13 Privacy Safeguard 13 - Correction of CDR data
  • APP-13 APP 13 - Correction of personal information

GDPR · 1 control

  • GDPR-Art.19 Notification obligation regarding rectification, erasure or restriction

ISO 27701:2019 · 1 control

  • 7.3.7 PII controllers' obligations to inform third parties
  • NIST800-PM-22 PM-22 Personally Identifiable Information Quality Management

SOC 2 · 1 control

  • SOC2-P5.2 P5.2 Correction of personal information

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.

Other controls in CBPR Program Requirements: Integrity of Personal Information

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-PR-24 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 8 it maps to, and the evidence behind each claim, over MCP and REST.