Skip to main content

PRI-04.1: Authority To Collect, Process, Store & Share Personal Data (PD)

PRI 7 — High Identify

Mechanisms exist to determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process.

Control Question: Does the organization determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process?

General (13)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC8.1-POF18 P3.1 P6.7-POF1
APEC Privacy Framework 2015 4(c)
CSA CCM 4 DSP-12
Generally Accepted Privacy Principles (GAPP) 1.2.5 1.2.11 4.2.2
ISO 29100 2024 6.3
NIST Privacy Framework 1.0 CT.DP-P4
NIST 800-53 R4 AP-1
NIST 800-53 R5 (source) PT-2
NIST 800-53B R5 (privacy) (source) PT-2
OECD Privacy Principles 1 4(b)
Shared Assessments SIG 2025 P.6
TISAX ISA 6 9.5.2
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) PRI-04.1
US (12)
Framework Mapping Values
US CERT RMM 1.2 COMP:SG2.SP1
US CMS MARS-E 2.0 AP-1
US FIPPS 3
US HIPAA Administrative Simplification 2013 (source) 164.502(a)(1)(i) 164.502(a)(1)(ii) 164.502(a)(1)(iii) 164.502(a)(5)(i) 164.502(i)
US IRS 1075 1.2 1.4 PT-2
US - CO Colorado Privacy Act 6-1-1308(4)
US - IL BIPA 15(b)
US - IL IPA 10(b)(1) 10(b)(3)
US - OR CPA 5(2)(b)
US - TN TIPA 47-18-3204(a)(5) 47-18-3204(b)
US - VA CDPA 2025 59.1-578.F.1.b 59.1-578.F.1.c
US - VT Act 171 of 2018 2433(a)(2)(A) 2433(a)(2)(B) 2433(a)(2)(C)
EMEA (21)
Framework Mapping Values
EMEA EU GDPR (source) 10 9.2(b) 9.2(c) 9.2(d) 9.2(e) 9.2(f) 9.2(g) 9.2(h) 9.2(i) 9.2(j) 9.3
EMEA Austria Sec 6
EMEA Belgium 45754
EMEA Germany Sec 4
EMEA Greece 4
EMEA Hungary 4 5
EMEA Ireland 2
EMEA Italy 11
EMEA Kenya DPA 2019 25(c) 28(2)(a) 28(2)(b) 28(2)(c) 28(2)(d) 28(2)(e) 28(2)(f) 28(2)(f)(i) 28(2)(f)(ii) 28(2)(f)(iii) 28(3) 30(1)(a) 30(1)(b)(i) 30(1)(b)(ii) 30(1)(b)(iii) 30(1)(b)(iv) 30(1)(b)(v) 30(1)(b)(vi) 30(1)(b)(vii) 30(1)(b)(viii) 30(2) 30(3) 33(1)(a) 33(1)(b) 33(2) 33(3)(a) 33(3)(b) 33(3)(c) 33(3)(d) 33(3)(e) 33(4) 36 37(1)(a) 37(1)(b) 37(2)
EMEA Netherlands 8
EMEA Nigeria DPR 2019 2.1(1)(a) 2.1(1)(a)(i) 2.1(1)(a)(ii) 2.2(a) 2.2(b) 2.2(c) 2.2(d) 2.2(e) 2.4(a)
EMEA Poland 23
EMEA Qatar PDPPL 9.2 18.1 18.2 18.3 18.4
EMEA Russia 5
EMEA Saudi Arabia PDPL 13.1
EMEA Serbia 87/2018 5.1 5.2 6.1 6.2 6.3 6.4 6.5 7 7.1 7.2 14 20
EMEA South Africa 2 3 4
EMEA Spain 1720/2007 8
EMEA Sweden 10
EMEA Switzerland 4
EMEA Turkey 10
APAC (10)
Framework Mapping Values
APAC Australia Privacy Act APP Part 3
APAC Australian Privacy Principles APP 3 APP 7
APAC China Privacy Law 5 10 13 13(1) 13(2) 13(3) 13(4) 13(5) 13(6) 13(7) 18 26 29 30 47
APAC India DPDPA 2023 4(1)(b)
APAC India ITR 5
APAC Japan APPI 17(1) 17(2) 17(2)(i) 17(2)(ii) 17(2)(iii) 17(2)(iv) 17(2)(v) 17(2)(vi)
APAC Philippines 19
APAC Singapore 17
APAC South Korea 3 15
APAC Taiwan 5 19
Americas (9)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process.

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 determine and document the legal authority that permits the organization to collect, receive, process, store, transmit, share, update and/or dispose Personal Data (PD), either generally or in support of a specific business process.

Assessment Objectives

  1. PRI-04.1_A01 the authority to permit the processing of Personal Data (PD) is defined.
  2. PRI-04.1_A02 the authority that permits the processing of Personal Data (PD) is determined and documented.
  3. PRI-04.1_A03 the processing of Personal Data (PD) is restricted to only that which is authorized.

Evidence Requirements

E-PRI-02 Authorized Use

Documented evidence of authorized use definitions for privacy-related data operations.

Privacy

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.