Skip to main content

PRI-03: Choice & Consent

PRI 7 — High Identify

Mechanisms exist to enable data subjects to authorize the collection, receiving, processing, storage, transmission, sharing, updating and/or disposal of their Personal Data (PD), where prior to collection the data subject is provided with: (1) Plain language to illustrate the potential data privacy risks of the authorization; (2) A means for users to decline the authorization; and (3) All necessary choice and consent-related criteria required by applicable statutory, regulatory and contractual obligations.

Control Question: Does the organization enable data subjects to authorize the collection, receiving, processing, storage, transmission, sharing, updating and/or disposal of their Personal Data (PD), where prior to collection the data subject is provided with: (1) Plain language to illustrate the potential data privacy risks of the authorization; (2) A means for users to decline the authorization; and (3) All necessary choice and consent-related criteria required by applicable statutory, regulatory and contractual obligations?

General (13)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) P2.0 P2.1 P2.1-POF1 P2.1-POF2 P2.1-POF3 P2.1-POF5 P2.1-POF6 P3.2 P3.2-POF2
APEC Privacy Framework 2015 2(e) 4(a) 5
Generally Accepted Privacy Principles (GAPP) 3.2.1 3.2.2 3.2.3 3.2.4
ISO 27002 2022 5.33
ISO 27017 2015 18.1.4
ISO 27018 2014 A.1.1
ISO 29100 2024 6.2
NIST Privacy Framework 1.0 CT.PO-P1 CT.PO-P3
NIST 800-53 R4 IP-1
NIST 800-53 R5 (source) PT-4
NIST 800-53B R5 (privacy) (source) PT-4
OECD Privacy Principles 1 4(a)
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) PRI-03
US (13)
Framework Mapping Values
US CERT RMM 1.2 EF:SG1.SP2 KIM:SG2.SP1 OTA:SG1.SP2
US CMS MARS-E 2.0 IP-1
US Data Privacy Framework (DPF) II.2.a II.2.c
US FERPA (source) 1232g
US HHS 45 CFR 155.260 155.260(a)(3)(iv)
US HIPAA Administrative Simplification 2013 (source) 164.506(b)(1) 164.508(a)(2) 164.508(c)(1)(v) 164.508(c)(3) 164.510(b)(2)(i) 164.510(b)(2)(ii) 164.510(b)(2)(iii) 164.510(b)(3) 164.514(f)(2)(ii) 164.514(f)(2)(iv) 164.514(f)(2)(v)
US - CA CCPA 2025 7002(e) 7010(b) 7012(a) 7012(b) 7012(c) 7012(d) 7012(e) 7012(e)(1) 7012(e)(2) 7012(e)(3) 7012(e)(4) 7012(e)(5) 7012(e)(6) 7027(c) 7027(d)
US - CO Colorado Privacy Act 6-1-1306(1) 6-1-1306(1)(a)(I)(A) 6-1-1306(1)(a)(I)(B) 6-1-1306(1)(a)(I)(C) 6-1-1306(1)(a)(II) 6-1-1306(1)(a)(III) 6-1-1306(1)(a)(IV)(A) 6-1-1306(1)(a)(IV)(B) 6-1-1306(1)(a)(IV)(C)
US - IL BIPA 15(b)(3)
US - OR CPA 5(2)(b) 5(2)(c)
US - TN TIPA 47-18-3203(a)(2)(E) 47-18-3203(b) 47-18-3204(a)(6)
US - TX CDPA 541.101(b)(4) 541.107(a)
US - VA CDPA 2025 59.1-578.A.5 59.1-578.D
EMEA (20)
Framework Mapping Values
EMEA EU GDPR (source) 21.1 21.2 21.3 21.4 21.5 21.6 7.1 7.2 9.2(a)
EMEA Austria Sec 8
EMEA Belgium 45754
EMEA Germany Sec 4a Sec 11
EMEA Greece 5
EMEA Hungary 6
EMEA Ireland 2
EMEA Italy 23 24
EMEA Kenya DPA 2019 32(1) 32(4)
EMEA Netherlands 8
EMEA Nigeria DPR 2019 2.2(a) 2.3(2) 2.3(2)(a) 2.3(2)(b) 2.3(2)(c) 2.3(2)(d) 2.3(2)(e)
EMEA Poland 23
EMEA Qatar PDPPL 4 5.2 10
EMEA Russia 6 9
EMEA Saudi Arabia PDPL 10.1 15.1 24.1 25.1 25.2 25.3 26 5.1
EMEA Serbia 87/2018 12.1 15 31 31.1 31.2 31.3 31.4
EMEA South Africa 11
EMEA Spain 1720/2007 8 12
EMEA Sweden 10
EMEA Turkey 10
APAC (13)
Framework Mapping Values
APAC Australia Privacy Act APP Part 3
APAC Australian Privacy Principles APP 3
APAC China Cybersecurity Law 22
APAC China Privacy Law 13(1) 14 23 27 29 30 44
APAC India DPDPA 2023 4(1)(a) 6(1) 6(10) 6(3) 6(7) 7(a) 7(b)(i) 8(8)(b)
APAC India ITR 5
APAC Japan APPI 16(1) 16(3)(i) 16(3)(ii) 16(3)(iii) 16(3)(iv) 24(1) 24(2)
APAC Japan ISMAP 18.1.4
APAC Malaysia 7
APAC Philippines 19
APAC Singapore 13
APAC South Korea 3 4 22
APAC Taiwan 5
Americas (10)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to enable data subjects to authorize the collection, receiving, processing, storage, transmission, sharing, updating and/or disposal of their Personal Data (PD), where prior to collection the data subject is provided with: (1) Plain language to illustrate the potential data privacy risks of the authorization; (2) A means for users to decline the authorization; and (3) All necessary choice and consent-related criteria required by applicable statutory, regulatory and contractual obligations.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to enable data subjects to authorize the collection, receiving, processing, storage, transmission, sharing, updating and/or disposal of their Personal Data (PD), where prior to collection the data subject is provided with: (1) Plain language to illustrate the potential data privacy risks of the authorization; (2) A means for users to decline the authorization; and (3) All necessary choice and consent-related criteria required by applicable statutory, regulatory and contractual obligations.

Level 2 — Planned & Tracked

Privacy (PRI) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Privacy management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and contractual data privacy obligations for Personal Data (PD) are properly identified and implemented across the enterprise.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for data privacy management.
  • A qualified individual is formally assigned as the Chief Privacy Officer (CPO), or similar role, to lead the organization's data privacy program. This individual may be assigned to multiple duties, including that as a Data Protection Officer (DPO).
  • The CPO, or similar role, identifies “data privacy principles” that systems, applications, services, processes and third-parties must adhere to, based on leading data privacy practices.
Level 3 — Well Defined

Privacy (PRI) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • A Chief Privacy Officer (CPO), or similar function with technical competence to address data privacy concerns, analyzes the organization's business strategy to develop and publish authoritative guidance on the organization's data privacy program.
  • A Privacy program, run by a CPO, or similar role, ensures that applicable statutory, regulatory and contractual data privacy obligations are properly identified and implemented to limit and secure Personal Data (PD) that the organization stores, transmits and processes.
  • As part of the organization's data privacy program, the CPO publishes a clear set of “data privacy principles”, based on leading data privacy practices, that systems, applications, services, processes and third-parties must adhere to.
  • A Project Management Office (PMO), or project management function, ensures both cybersecurity and data privacy principles are identified and implemented within ongoing or planned projects.
  • The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns, analyzes the organization's business strategy to determine prioritized and authoritative guidance for cybersecurity-related data privacy practices.
  • The CISO, or similar function, develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures to apply defense-in-depth techniques across the enterprise for cybersecurity-related data privacy practices.
  • A Governance, Risk & Compliance (GRC) function, or similar function, provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to data privacy.
  • A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program.
  • Data/process owners operationalize data privacy controls into the processes they control.
  • Third-party contracts included data protection requirements, including flow-down requirements to subcontractors.
  • Data Protection Officers (DPOs) are assigned to work closely with business units and project teams to ensure data privacy principles are being implemented.
  • CPO and DPO determine and document the legal authority that permits the collection, use, maintenance and sharing of PD, either generally or in support of a specific program or system need.
Level 4 — Quantitatively Controlled

Privacy (PRI) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • 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.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to enable data subjects to authorize the collection, receiving, processing, storage, transmission, sharing, updating and/or disposal of their Personal Data (PD), where prior to collection the data subject is provided with: (1) Plain language to illustrate the potential data privacy risks of the authorization; (2) A means for users to decline the authorization; and (3) All necessary choice and consent-related criteria required by applicable statutory, regulatory and contractual obligations.

Assessment Objectives

  1. PRI-03_A01 the tools or mechanisms to be implemented for individuals to consent to the processing of their Personal Data (PD) are defined.
  2. PRI-03_A02 tools or mechanisms are implemented for individuals to consent to the processing of their Personal Data (PD) prior to its collection that facilitates individuals’ informed decision-making.

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

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.