PRI-02: Data Privacy Program
Mechanisms exist to facilitate the implementation and operation of data protection controls throughout the data lifecycle to ensure all forms of Personal Data (PD) are processed lawfully, fairly and transparently.
Renumbered: Formerly PRI-01 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, PRI-02 was Data Privacy Notice. That control is now PRI-21.
Control Question: Does the organization facilitate the implementation and operation of data protection controls throughout the data lifecycle to ensure all forms of Personal Data (PD) are processed lawfully, fairly and transparently?
General (28)
US (12)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | AR-1 AR-1.b AR-1.c AR-1.d AR-1.e AR-1.f |
| USA Federal Data Privacy Framework 2023 | III.15.a |
| USA Federal 45 CFR 155.260 | 155.260(a)(3) |
| USA Federal IRS 1075 2021 | PM-18 PT-1 |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.502(a) § 164.530(a)(1)(i) § 164.530(i)(1) § 164.530(i)(4)(i)(A) § 164.530(i)(4)(i)(B) § 164.530(i)(5) § 164.530(i)(5)(i) § 164.530(i)(5)(ii) |
| USA Federal FIPPS 1973 | 2.0 |
| USA Federal FCA CRM 2023 | 609.930(d) |
| USA California CCPA 2025 | 7002(a) |
| USA Nevada NOGE Reg 5 2024 | 5.260.1 |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.3(k) |
| USA Texas CDPA 2025 | 541.101(a)(2) 541.101(b)(2) 541.204(c) |
| USA Virginia CDPA 2023 | 59.1-578.A.3 |
EMEA (11)
| Framework | Mapping Values |
|---|---|
| EMEA Germany FDPA 2017 | 2.1.2.26(5) |
| EMEA Spain CCN-STIC 825 | org.1 org.2 mp.info.1 |
| EMEA EU AI Act | Article 10.5 |
| EMEA EU GDPR 2016 | Article 5.1(a) Article 9.1 Article 12.2 |
| EMEA Hungary Act CXII 2011 | II.6.7(1) |
| EMEA Israel CDMO 2.0 | Appendix F |
| EMEA Kenya DPA 2019 | IV.25 |
| EMEA LUX CCSF 22/806 2022 | 9 32 |
| EMEA Nigeria DPR 2019 | 4.1(3) |
| EMEA Qatar PDPPL 2020 | 3.11 3.11.5 |
| EMEA Saudi Arabia PDPL | Article 11.2 |
APAC (6)
| Framework | Mapping Values |
|---|---|
| APAC China Privacy Law 2021 | Article 51 |
| APAC India ITR 2011 | 8(1) |
| APAC India RBI Digital Payments 2021 | 8.h |
| APAC Japan APPI 2020 | IV.5.53(1) |
| APAC Japan ISMAP | 5.1.1 5.1.1.19 18.1.4 |
| APAC Philippines DPA 2012 | III.11 |
Americas (3)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | V.45(2)(a) V.45(2)(b) V.45(2)(b)(i) V.45(2)(b)(ii) |
| Americas Colombia Law 1581 2012 | VI.18(a) VI.18(b) VI.18(c) VI.18(d) VI.18(e) VI.18(f) VI.18(g) VI.18(h) VI.18(i) VI.18(j) VI.18(k) VI.18(l) |
| Americas Mexico FDPA 2010 | II.6 II.14 |
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
Privacy (PRI) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with PRI domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Data privacy-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ No formal data privacy team exists. Privacy roles are assigned to existing IT / cybersecurity. ▪ Data/process owners are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data. ▪ No formal data privacy principles are identified for the organization. ▪ Data/process owners perform their own Data Protection Impact Assessment (DPIA).
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. ▪ 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 data privacy-related roles. ▪ 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 facilitate the implementation and operation of data protection controls throughout the data lifecycle to ensure all forms of Personal Data (PD) are processed lawfully, fairly and transparently.
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-02_A01 an organization-wide privacy program plan that provides an overview of the agency’s privacy program is developed.
- PRI-02_A02 the privacy program plan includes a description of the structure of the privacy program.
- PRI-02_A03 the privacy program plan includes a description of the resources dedicated to the privacy program.
- PRI-02_A04 the privacy program plan provides an overview of the requirements for the privacy program.
- PRI-02_A05 the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program.
- PRI-02_A06 the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program.
- PRI-02_A07 the privacy program plan includes the role of the senior organization official for privacy.
- PRI-02_A08 the privacy program plan includes the identification and assignment of the roles of other privacy officials and staff and their responsibilities.
- PRI-02_A09 the privacy program plan describes management commitment.
- PRI-02_A10 the privacy program plan describes compliance.
- PRI-02_A11 the privacy program plan describes the strategic goals and objectives of the privacy program.
- PRI-02_A12 the privacy program plan reflects coordination among organizational entities responsible for the different aspects of privacy.
- PRI-02_A13 the privacy program plan is approved by a senior official with responsibility and accountability for the privacy risk being incurred by organizational operations (including, mission, functions, image and reputation), organizational assets, individuals, other organizations and the Nation.
- PRI-02_A14 the privacy program plan is disseminated.
- PRI-02_A15 the frequency of updates to the privacy program plan is defined.
- PRI-02_A16 the privacy program plan is updated per an organization-defined frequency.
- PRI-02_A17 the privacy program plan is updated to address changes in federal privacy laws and policies.
- PRI-02_A18 the privacy program plan is updated to address organizational changes.
- PRI-02_A19 the privacy program plan is updated to address problems identified during plan implementation or privacy control assessments.
- PRI-02_A20 data privacy operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
- PRI-02_A21 adequate resources (e.g., people, processes, technologies, data and/or facilities) are provided to support data privacy operations.
- PRI-02_A22 responsibility and authority for the performance of data privacy-related activities are assigned to designated personnel.
- PRI-02_A23 personnel performing data privacy-related activities have the skills and knowledge needed to perform their assigned duties.
Evidence Requirements
- E-GOV-08 Charter - Data Privacy Program
-
Documented evidence of a charter to establish and resource the organization's data privacy program.
Security, Compliance & Resilience Governance
Technology Recommendations
Micro/Small
- Data privacy program
Small
- Data privacy program
Medium
- Data privacy program
Large
- Data privacy program
Enterprise
- Data privacy program