PRI-39.4: Notice of Correction or Processing Change
Mechanisms exist to notify affected data subjects if their Personal Data (PD) has been corrected, amended or deleted.
Renumbered: Formerly PRI-06.2 in SCF 2025.4.
Control Question: Does the organization notify affected data subjects if their Personal Data (PD) has been corrected, amended or deleted?
General (5)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | P3.1-POF4 P5.2 P5.2-POF2 P5.2-POF3 |
| NIST 800-53 R5.2 | SI-18(05) |
| NIST 800-82 R3 | SI-18(05) |
| NIST Privacy Framework 1.0 | CT.PO-P4 CM.PO-P1 |
| SCF DPMP 2026 | 6.4 |
US (3)
| Framework | Mapping Values |
|---|---|
| USA Federal HIPAA Administrative Simplification 2013 | § 164.526(c) § 164.526(c)(1) § 164.526(c)(2) § 164.526(c)(3) § 164.526(c)(3)(i) § 164.526(c)(3)(ii) |
| USA California CCPA 2025 | 7022(e) 7023(f) |
| USA Tennessee TIPA 2025 | 47-18-3203(b)(1) |
EMEA (5)
| Framework | Mapping Values |
|---|---|
| EMEA Austria FAPPD 2000 | § 45(5) |
| EMEA Belgium Act 8 1992 | Title 2, Chapter III, Art. 39(5) Title 2, Chapter III, Art. 39(6) |
| EMEA Germany FDPA 2017 | 3.3.58(1) 3.3.58(5) 3.4.75(3) |
| EMEA UK DPA 2018 | Section 48(1) Section 48(1)(a) Section 48(1)(b) Section 48(1)(b)(i) Section 48(1)(b)(ii) Section 48(1)(b)(iii) Section 48(1)(b)(iv) Section 48(2) Section 48(2)(a) Section 48(2)(b) Section 48(3) Section 48(3)(a) Section 48(3)(b) Section 48(3)(c) Section 48(3)(e) Section 48(4) Section 48(4)(a) Section 48(4)(b) Section 48(4)(c) Section 48(4)(d) Section 48(5) Section 48(6) Section 48(6)(a) Section 48(6)(b) Section 48(7) Section 48(9) Section 48(9)(a) Section 48(9)(b) Section 48(10) |
| EMEA South Africa POPIA 2013 | 3.A.8.24(3) 3.A.8.24(4) |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC Australian Privacy Principles 2026 | 5.13.2 5.13.2.a 5.13.2.b 5.13.3 5.13.3.a 5.13.3.b 5.13.3.c |
| APAC Hong Kong PDO 2022 | 19(3)(b) 19(3)(c) 19(3)(c)(i) 19(3)(c)(i)(A) 19(3)(c)(i)(B) 19(3)(c)(ii) 19(3)(c)(iii) 19(3)(c)(iii)(A) 19(3)(c)(iii)(B) 19(3)(c)(I) 19(3)(c)(II) 19(3)(c)(iv) 19(3)(c)(v) 23(1)(b) |
| APAC Malaysia PDPA 2010 | 37(1) 37(1)(a) 37(1)(b) |
| APAC New Zealand Privacy Act of 2020 | 3.1.22.7(3)(b) |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | IV.26(3)(a) IV.26(3)(b) |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
Level 3 — Well Defined
Privacy (PRI) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRI domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are well-documented and kept current by process owners. ▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to notify affected data subjects if their Personal Data (PD) has been corrected, amended or deleted.
Level 4 — Quantitatively Controlled
Privacy (PRI) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- PRI-39.4_A01 recipients of Personal Data (PD) to be notified when the Personal Data (PD) has been corrected or deleted are defined.
- PRI-39.4_A02 recipients and individuals are notified when the Personal Data (PD) has been corrected or deleted.
Technology Recommendations
Micro/Small
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Small
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Medium
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Large
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Enterprise
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management