Skip to main content

RSK-19: Data Protection Impact Assessment (DPIA)

RSK 9 — Critical Identify

Mechanisms exist to conduct a Data Protection Impact Assessment (DPIA) on Technology Assets, Applications and/or Services (TAAS) that store, process and/or transmit Personal Data (PD) to identify and remediate reasonably-expected risks.

Renumbered: Formerly RSK-10 in SCF 2025.4.

Control Question: Does the organization conduct a Data Protection Impact Assessment (DPIA) on Technology Assets, Applications and/or Services (TAAS) that store, process and/or transmit Personal Data (PD) to identify and remediate reasonably-expected risks?

General (22)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) M1.3-POF2
AICPA TSC 2017:2022 (used for SOC 2) (source) CC3.2 CC5.2 PI1.1
COBIT 2019 APO12.01 APO12.02 APO12.03 APO12.04
COSO 2013 7.0
CSA CCM 4.1.0 DSP-09
CSA IoT SCF 2 GVN-07 GVN-08 LGL-01 LGL-03
ISO 27002 2022 5.33
ISO 27017 2015 18.1.4
ISO 27018 2025 5.33 5.35(a) 8.31(a)
ISO 27701 2025 6.1.2 6.1.2(a) 6.1.2(a)(1) 6.1.2(a)(2) 6.1.2(b) 6.1.2(c) 6.1.2(c)(1) 6.1.2(c)(2) 6.1.2(d) 6.1.2(d)(1) 6.1.2(d)(2) 6.1.2(d)(3) 6.1.2(e) 6.1.2(e)(1) 6.1.2(e)(2) 8.2
ISO 42001 2023 6.1.4 8.4 A.5.3 A.5.4 A.5.5
NIST AI 100-1 (AI RMF) 1.0 MAP 1.1 MEASURE 2.10
NIST 800-53 R4 AR-2
NIST 800-53 R5.2 RA-08
NIST 800-53B R5 (privacy) (source) RA-08
NIST 800-82 R3 RA-08
NIST Privacy Framework 1.0 ID.IM-P7 ID.RA-P1 ID.RA-P2 ID.RA-P3 ID.RA-P4 ID.RA-P5 ID.DE-P2 ID.DE-P3 GV.MT-P1
PCI DSS 4.0.1 (source) A3.2.2
SCF DPMP 2026 9.5
Shared Assessments SIG 2025 P.5
TISAX ISA 6.0.3 9.4.1
UL 2900-1 2017 12.1
US (10)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AR-2 AR-2.a AR-2.b
USA Federal IRS 1075 2021 RA-8
USA California CCPA 2025 7152(a) 7152(a)(1) 7152(a)(2) 7152(a)(3) 7152(a)(3)(A) 7152(a)(3)(B) 7152(a)(3)(C) 7152(a)(3)(D) 7152(a)(3)(E) 7152(a)(3)(F) 7152(a)(3)(G) 7152(a)(3)(G)(i) 7152(a)(3)(G)(ii) 7152(a)(4) 7152(a)(5) 7152(a)(5)(A) 7152(a)(5)(B) 7152(a)(5)(C) 7152(a)(5)(D) 7152(a)(5)(E) 7152(a)(5)(F) 7152(a)(5)(G) 7152(a)(5)(H) 7152(a)(6) 7152(a)(6)(A) 7152(a)(6)(A)(i) 7152(a)(6)(A)(ii) 7152(a)(6)(A)(iii) 7152(a)(6)(A)(iv) 7152(a)(7) 7152(a)(8) 7152(a)(9) 7154(a) 7155(a) 7156(a) 7156(b)
USA Montana CDPA 2025 30-14-2813(1)(c) 30-14-2814(1) 30-14-2814(1)(a) 30-14-2814(1)(b) 30-14-2814(1)(c) 30-14-2814(1)(d) 30-14-2814(2)(a) 30-14-2814(2)(b) 30-14-2814(3)(a) 30-14-2814(4) 30-14-2814(5) 30-14-2817(3) 30-14-2818(1)(b) 30-14-2819(1) 30-14-2819(1)(a) 30-14-2819(1)(b) 30-14-2819(2)(a) 30-14-2819(2)(b) 30-14-2819(3) 30-14-2819(4) 30-14-2819(5) 30-14-2819(6)
USA Oregon CPA 2023 Section 6(1)(c) Section 8(1)(a) Section 8(1)(c) Section 8(2)
USA Oregon 646A 2025 646A.586(1)(a) 646A.586(1)(b) 646A.586(1)(b)(A) 646A.586(1)(b)(B) 646A.586(1)(b)(C) 646A.586(1)(b)(D) 646A.586(1)(b)(D)(i) 646A.586(1)(b)(D)(ii) 646A.586(1)(b)(D)(iii) 646A.586(1)(b)(D)(iv) 646A.586(1)(c) 646A.586(2) 646A.586(4) 646A.586(5)
USA Tennessee TIPA 2025 47-18-3206(a) 47-18-3206(a)(1) 47-18-3206(a)(2) 47-18-3206(a)(3) 47-18-3206(a)(3)(A) 47-18-3206(a)(3)(B) 47-18-3206(a)(3)(C) 47-18-3206(a)(3)(D) 47-18-3206(a)(4) 47-18-3206(a)(5) 47-18-3206(b) 47-18-3206(c) 47-18-3206(d) 47-18-3206(e) 47-18-3206(f)
USA Texas CDPA 2025 541.105(a)(1) 541.105(a)(2) 541.105(a)(3)(A) 541.105(a)(3)(B) 541.105(a)(3)(C) 541.105(a)(3)(D) 541.105(a)(4) 541.105(a)(5) 541.105(b)(1) 541.105(b)(2)(A) 541.105(b)(2)(B) 541.105(b)(2)(C) 541.105(b)(2)(D) 541.105(c) 541.105(d) 541.105(e) 541.105(f)
USA Texas TRAIGA 2025 Sec. 3 / 541.104(a)(3)
USA Virginia CDPA 2023 59.1-580.A 59.1-580.A.1 59.1-580.A.2 59.1-580.A.3 59.1-580.A.4 59.1-580.A.5 59.1-580.B 59.1-580.C 59.1-580.D 59.1-580.E 59.1-580.F 59.1-580.G
EMEA (11)
Framework Mapping Values
EMEA Switzerland FADP 2025 3.22.1 3.22.2 3.22.2.a 3.22.2.b 3.22.3 3.22.4 3.22.5 3.22.5.a 3.22.5.b 3.22.5.c
EMEA Germany FDPA 2017 3.4.67(1) 3.4.67(2) 3.4.67(3) 3.4.67(4) 3.4.67(4)1 3.4.67(4)2 3.4.67(4)3 3.4.67(4)4 3.4.67(5)
EMEA Spain Royal Decree 311 2022 Article 3(2) Article 12(1)(f)
EMEA EU AI Act Article 26.9
EMEA EU GDPR 2016 Article 35.1 Article 35.3(a) Article 35.3(b) Article 35.3(c) Article 35.7(a) Article 35.7(b) Article 35.7(c) Article 35.7(d) Article 35.8 Article 35.9 Article 35.11 Article 36.1
EMEA UK DPA 2018 Section 64(1) Section 64(2) Section 64(3) Section 64(3)(a) Section 64(3)(b) Section 64(3)(c) Section 64(3)(d) Section 64(4)
EMEA Ireland DPA 2018 s.84
EMEA Kenya DPA 2019 IV.31(1) IV.31(2) IV.31(2)(a) IV.31(2)(b) IV.31(2)(c) IV.31(2)(d) IV.31(3)
EMEA Qatar PDPPL 2020 3.11.1
EMEA Saudi Arabia PDPL Article 22
EMEA Serbia 87/2018 IV.3.54-1 IV.3.54-1(1) IV.3.54-1(2) IV.3.54-1(3) IV.3.54-2 IV.3.54-2(1) IV.3.54-2(2) IV.3.54-2(3) IV.3.54-2(4) IV.3.55-1 IV.3.55-1(1) IV.3.55-1(2) IV.3.55-2 IV.3.55-2(1) IV.3.55-2(2) IV.3.55-2(3) IV.3.55-2(4) IV.3.55-2(5) IV.3.55-2(6)
APAC (4)
Framework Mapping Values
APAC Australia Prudential Standard CPS230 2023 26
APAC China Privacy Law 2021 Article 55 Article 56
APAC India DPDPA 2023 10(2)(c)(i)
APAC Singapore PDPA 2012 4.1.15A(4)(a) 4.1.15A(5)(a)
Americas (3)
Framework Mapping Values
Americas Bahamas DPA 2003 V.50(1) V.50(1)(a) V.50(1)(b) V.50(2) V.50(2)(a) V.50(2)(b) V.50(2)(c) V.50(3) V.50(3)(a) V.50(3)(b) V.50(3)(c) V.50(3)(d) V.50(4) V.50(5) V.50(6) V.50(7) V.50(8) V.50(8)(a) V.50(8)(b) V.50(8)(c) V.50(8)(d) V.50(8)(e) V.50(8)(f)
Americas Brazil LGPD 2018 II.I.10.II.3
Americas Canada PIPEDA 2000 P5-4.5.1

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

Risk Management (RSK) 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 RSK domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with RSK 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 RSK domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Risk management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Risk management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Risk management processes (e.g., risk assessments) and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed. ▪ IT and/or cybersecurity personnel implement and maintain a form of Risk Management Program (RMP) that provides operational guidance on how risk is identified, assessed, remediated and reported. ▪ Data/process owners are expected to self-manage risks associated with their systems, applications, services and data, based on the organization's published policies and standards, including the identification, remediation and reporting of risks. ▪ Business process owners (BPOs) are made aware of cybersecurity and data protection risk(s).

Level 3 — Well Defined

Risk Management (RSK) 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 RSK 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 RSK domain capabilities are well-documented and kept current by process owners. ▪ A risk management team, or similar function, is appropriately staffed and supported to implement and maintain RSK domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of risk management operations (e.g., risk management solution, GRC platform and TPRM tool). ▪ 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 RSK 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 conduct a Data Protection Impact Assessment (DPIA) on Technology Assets, Applications and/or Services (TAAS) that store, process and/or transmit Personal Data (PD) to identify and remediate reasonably-expected risks.

Level 4 — Quantitatively Controlled

Risk Management (RSK) 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

  1. RSK-19_A01 Data Protection Impact Assessments (DPIAs) are conducted for systems, programs or other activities before developing or procuring information technology that processes Personal Data (PD).
  2. RSK-19_A02 Data Protection Impact Assessments (DPIAs) are conducted for systems, programs or other activities before initiating a collection of Personal Data (PD) that will be processed using information technology.
  3. RSK-19_A03 Data Protection Impact Assessments (DPIAs) are conducted for systems, programs or other activities before initiating a collection of Personal Data (PD) that includes Personal Data (PD) permitting the physical or virtual (online) contacting of a specific individual.

Evidence Requirements

E-PRI-04 Data Protection Impact Assessment (DPIA)

Documented evidence of Data Protection Impact Assessment (DPIA).

Privacy

Technology Recommendations

Micro/Small

  • Risk Management Program (RMP)
  • Data Protection Impact Assessment (DPIA)
  • Privacy Impact Assessment (PIA)

Small

  • Risk Management Program (RMP)
  • Data Protection Impact Assessment (DPIA)
  • Privacy Impact Assessment (PIA)

Medium

  • Risk Management Program (RMP)
  • Data Protection Impact Assessment (DPIA)
  • Privacy Impact Assessment (PIA)

Large

  • Risk Management Program (RMP)
  • Data Protection Impact Assessment (DPIA)
  • Privacy Impact Assessment (PIA)

Enterprise

  • Risk Management Program (RMP)
  • Data Protection Impact Assessment (DPIA)
  • Privacy Impact Assessment (PIA)

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.