PRI-24.3: Revoke Consent
Mechanisms exist to allow data subjects to revoke consent to collect, receive, process, store, transmit, share and/or update their Personal Data (PD).
Renumbered: Formerly PRI-03.4 in SCF 2025.4.
Control Question: Does the organization allow data subjects to revoke consent to collect, receive, process, store, transmit, share and/or update their Personal Data (PD)?
General (5)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | N2.1-POF5 |
| NIST AI 600-1 | MS-2.2-003 |
| NIST 800-53 R5.2 | PT-04(03) |
| NIST 800-82 R3 | PT-04(03) |
| SCF DPMP 2026 | 2.3 |
US (5)
| Framework | Mapping Values |
|---|---|
| USA Federal COPPA 2024 | Sec. 6502.(b)(1)(B)(ii) |
| USA Montana CDPA 2025 | 30-14-2812(1)(c) |
| USA Nevada Privacy Law 2023 | 603A.500.3(d) 603A.505.1(c) 603A.535.4 |
| USA Oregon CPA 2023 | Section 5(1)(d) |
| USA Oregon 646A 2025 | 646A.576(7) 646A.578(1)(d) |
EMEA (10)
| Framework | Mapping Values |
|---|---|
| EMEA Germany FDPA 2017 | 3.2.51(3) |
| EMEA EU GDPR 2016 | Article 7.3 |
| EMEA UK DPA 2018 | Section 47(4) |
| EMEA Hungary Act CXII 2011 | II.15.21(1)(a) II.15.21(1)(b) |
| EMEA Kenya DPA 2019 | IV.26(c) IV.32(2) IV.32(3) |
| EMEA Nigeria DPR 2019 | 2.8(a) 3.1(9)(b) |
| EMEA Qatar PDPPL 2020 | 2.5.1 |
| EMEA Saudi Arabia PDPL | Article 5.2 |
| EMEA Serbia 87/2018 | III.3.30-1(2) III.4.37 |
| EMEA South Africa POPIA 2013 | 3.A.2.11(2)(b) 3.A.2.11(3) 3.A.2.11(3)(a) 3.A.2.11(3)(b) 3.A.2.11(4) |
APAC (7)
| Framework | Mapping Values |
|---|---|
| APAC China Privacy Law 2021 | Article 15 |
| APAC Hong Kong PDO 2022 | 35G(1) 35L(1) 35L(1)(a) 35L(1)(b) 35L(2) 35L(3) 35L(4) |
| APAC India DPDPA 2023 | 5(2)(b) 6(4) 6(7) 8(7)(a) 8(8)(b) |
| APAC Japan APPI 2020 | IV.1.30(1) |
| APAC South Korea PIPA 2011 | V.37(1) |
| APAC Malaysia PDPA 2010 | 38(1) 43(1) |
| APAC Singapore PDPA 2012 | 4.1.16(1) 9.3.47(1) |
Americas (4)
| Framework | Mapping Values |
|---|---|
| Americas Brazil LGPD 2018 | II.I.8.5 II.IV.15.III |
| Americas Canada PIPEDA 2000 | P3-4.3.8 |
| Americas Colombia Law 1581 2012 | IV.8(e) |
| Americas Mexico FDPA 2010 | II.8 III.25 |
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
Privacy (PRI) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). 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. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Data privacy management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Data privacy management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and/or contractual data privacy obligations for Personal Data (PD) are properly identified and implemented.
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 allow data subjects to revoke consent to collect, receive, process, store, transmit, share and/or update their Personal Data (PD).
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
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-24.3_A01 the tools or mechanisms to be implemented for revoking consent to the processing of Personal Data (PD) are defined.
- PRI-24.3_A02 the tools or mechanisms are implemented for individuals to revoke consent to the processing of their Personal Data (PD).
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