PRI-16: Information Sharing With Third Parties
Mechanisms exist to disclose Personal Data (PD) to third-parties only for the purposes identified in the data privacy notice and with the implicit or explicit consent of the data subject.
Renumbered: Formerly PRI-07 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, PRI-16 was Potential Human Rights Abuses. That control is now CPL-21.
Control Question: Does the organization disclose Personal Data (PD) to third-parties only for the purposes identified in the data privacy notice and with the implicit or explicit consent of the data subject?
General (23)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | D6.1-POF3 D6.1-POF4 D6.4-POF1 S7.3 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | P6.1 P6.1-POF1 |
| CSA CCM 4.1.0 | DSP-13 |
| GovRAMP | AC-21 |
| GovRAMP Moderate | AC-21 |
| GovRAMP High | AC-21 |
| ISO 27002 2022 | 5.33 |
| ISO 27017 2015 | 18.1.4 |
| ISO 27018 2025 | 5.33 |
| ISO 29100 2024 | 6.10 |
| NIST 800-53 R4 | UL-2 |
| NIST 800-53 R5.2 | AC-21 |
| NIST 800-53B R5 (moderate) (source) | AC-21 |
| NIST 800-53B R5 (high) (source) | AC-21 |
| NIST 800-82 R3 | AC-21 |
| NIST 800-82 R3 MODERATE OT Overlay | AC-21 |
| NIST 800-82 R3 HIGH OT Overlay | AC-21 |
| NIST 800-161 R1 | AC-21 |
| NIST 800-161 R1 Level 1 | AC-21 |
| NIST 800-161 R1 Level 2 | AC-21 |
| NIST Privacy Framework 1.0 | CT.PO-P2 |
| SCF DPMP 2026 | 10.2 |
| TISAX ISA 6.0.3 | 9.5.2 |
US (9)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | AC-21 UL-2 UL-2.a UL-2.b UL-2.c UL-2.d |
| USA Federal CJIS Security Policy 6.0 | AC-21 |
| USA Federal FedRAMP R5 (moderate) | AC-21 |
| USA Federal FedRAMP R5 (high) | AC-21 |
| USA Federal 45 CFR 155.260 | 155.260(e) |
| USA Federal IRS 1075 2021 | AC-21 |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.506(c)(1) § 164.506(c)(2) § 164.506(c)(3) § 164.506(c)(4) § 164.508(a)(1) § 164.508(a)(4)(i) |
| USA Montana CDPA 2025 | 30-14-2812(5)(c) 30-14-2812(5)(d) |
| USA Oregon CPA 2023 | Section 6(1)(a) Section 6(1)(c) |
EMEA (8)
| Framework | Mapping Values |
|---|---|
| EMEA Germany FDPA 2017 | 3.5.79(1)2 3.5.81(1) 3.5.81(1)1 3.5.81(1)2 3.5.81(1)3 3.5.81(2) 3.5.81(3) 3.5.81(4) |
| EMEA Greece PIRPPD 1997 | B.9.1 B.9.2.a B.9.2.b B.9.2.b.i B.9.2.b.ii B.9.2.b.iii B.9.2.c B.9.2.d B.9.2.e |
| EMEA Hungary Act CXII 2011 | II.7.8(1)(b) II.8.9(3) II.8.9(5) |
| EMEA Kenya DPA 2019 | IV.25(h) |
| EMEA Nigeria DPR 2019 | 2.12(a) |
| EMEA Qatar PDPPL 2020 | 3.12 |
| EMEA Saudi Arabia PDPL | Article 8 |
| EMEA Turkey LDDP 2016 | 8(1) 8(2) 8(2)(a) 8(2)(b) 8(3) |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC India DPDPA 2023 | 8(2) |
| APAC New Zealand Privacy Act of 2020 | 3.1.22.11(1) 3.1.22.11(1)(a) 3.1.22.11(1)(b) 3.1.22.11(1)(c) 3.1.22.11(1)(d) 3.1.22.11(1)(e) 3.1.22.11(1)(e)(i) 3.1.22.11(1)(e)(ii) 3.1.22.11(1)(e)(iii) 3.1.22.11(1)(e)(iv) 3.1.22.11(1)(f) 3.1.22.11(1)(f)(i) 3.1.22.11(1)(f)(ii) 3.1.22.11(1)(g) 3.1.22.11(1)(h) 3.1.22.11(1)(h)(i) 3.1.22.11(1)(h)(ii) 3.1.22.11(1)(i) |
| APAC Singapore PDPA 2012 | 4.1.17(1)(c) 5.22(2)(b) 5.22(3) |
Americas (3)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | VI.53(1) VI.54 VI.54(a) VI.54(b) VI.54(b)(i) VI.54(b)(ii) VI.54(b)(iii) VI.54(b)(iv) VI.54(b)(v) VI.54(b)(vi) VI.54(c) |
| Americas Brazil LGPD 2018 | V.33 |
| Americas Colombia Law 1581 2012 | VI.17(h) |
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
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
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 disclose Personal Data (PD) to third-parties only for the purposes identified in the data privacy notice and with the implicit or explicit consent of the data subject.
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-16_A01 information-sharing circumstances where user discretion is required to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions are defined.
- PRI-16_A02 authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for information-sharing circumstances.
- PRI-16_A03 automated mechanisms or manual processes that assist users in making information-sharing and collaboration decisions are defined.
- PRI-16_A04 automated mechanisms are employed to assist users in making information-sharing and collaboration decisions.
Evidence Requirements
- E-PRI-05 Data Sharing Agreement
-
Documented evidence of formal data sharing practices that address, at a minimum: • The business justification for the data sharing; • The type / category of data being shared; • The third-parties the data is being shared with; • Lawful bases for data sharing; and • Data subject rights.
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