Study guide

3.6 Governing Internal & External Data Sharing and Disclosure

Certified Information Privacy Manager CIPM

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 CIPM Exam Facts & Format 1.2 The CIPM Body of Knowledge: Six Domains & How the Exam Is Built 1.3 Study Strategy, Timeline & How to Use This Guide

2 Domain I: Developing a Privacy Program Framework

2.1 Program Scope, Strategy & Governance Model 2.2 Stakeholders, Privacy Team Structure & Common Vocabulary 2.3 Applicable Regulations, Oversight Agencies & Non-Compliance Impact 2.4 Personal Information Sources, Cross-Border Operations & AI Privacy Risk 2.5 Business Model, Operating Environment & Risk Appetite 2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing 2.7 Vision, Mission & the Privacy Program Communication Plan 2.8 Policy Access, Version Control & Role-Relevant Updates 2.9 Codes of Conduct, Certifications & Self-Certification Mechanisms

3 Domain II: Establishing Program Governance

3.1 Privacy Policies & Life-Cycle Processes 3.2 Breach, Complaint, DSR & Retention Plans 3.3 Roles, Responsibilities, Metrics & Continuous Legal Monitoring 3.4 Training & Awareness Activities 3.5 Governance Bodies, Program Charter & Escalation Paths 3.6 Governing Internal & External Data Sharing and Disclosure 3.7 Retention Schedules & Defensible Disposal 3.8 Regulatory Change Monitoring & Enforcement Systems

4 Domain III: Operational Life Cycle — Assessing Data

4.1 Data Inventories, Flows & Life-Cycle Mapping 4.2 Data Discovery, System Integrations & Keeping the Inventory Current 4.3 Policy Compliance Measurement & Gap Analysis 4.4 Processor/Vendor Evaluation & Physical/Environmental Controls 4.5 Third-Party Risk Life Cycle & Sub-Processor Chains

5 Domain III (continued): Assessing Data — Technical & Physical Controls, M&A Risk

4.6 Technical Controls, Use/Retention Limits & Data Location 4.7 Physical & Environmental Controls in Depth 4.8 Mergers, Acquisitions & Divestitures Data Risk

6 Domain IV: Operational Life Cycle — Protecting Personal Data

5.1 Information Security Practices, Data Classification & Access Controls 5.2 Privacy by Design Principles & the SDLC 5.3 Organizational Guidelines for Data Use & Secondary-Use Governance 5.4 Privacy-Enhancing Technologies & Technical Control Enforcement 5.5 Technical, Administrative & Organizational Measures 5.6 Access Reviews, Monitoring & Enforcing Technical Controls

7 Domain V: Operational Life Cycle — Sustaining Program Performance

6.1 Privacy Metrics for Program Performance 6.2 Auditing the Privacy Program 6.3 Continuous Assessment: PIA, DPIA, TIA, LIA & PTA 6.4 Risk Mitigation, Post-M&A Assessment & Ethical AI Use

8 Domain VI: Operational Life Cycle — Responding to Requests & Incidents

7.1 Data Subject Access Requests & Consent/Rights Processes 7.2 Global Privacy Legislation on Data Subject Rights 7.3 Incident Handling, Breach Response & Records 7.4 Post-Incident Review & IR Plan Improvement 7.5 Privacy Notices & Transparency Obligations 7.6 Complaint Handling & Regulator Interaction 7.7 Breach Communications to Regulators, Individuals & Other Stakeholders

9 Final Review & Exam Strategy

8.1 Mixed-Domain Scenarios & Common Exam Traps 8.2 Test-Day Logistics, Score Strategy & Credential Maintenance

3.6 Governing Internal & External Data Sharing and Disclosure

Key Takeaways Explain This Topic AI

Indicator II.B.2 requires defined roles and responsibilities for managing the sharing and disclosure of data for internal and external use — internal sharing is expressly in scope.

The first question in any sharing scenario is the relationship: controller-to-processor, controller-to-controller, or joint controllers under GDPR Article 26 — each needs a different instrument.

Joint controllers must agree in a transparent arrangement who fulfils which obligation, and the essence of that arrangement must be made available to data subjects.

Government and law-enforcement disclosure requests need a standing procedure: validate legal authority, scope-minimise, log, and notify the individual unless legally prohibited.

Every disclosure needs a log entry; without one, an organization cannot answer a rights request, scope a breach, or evidence lawful sharing.

Last updated: August 2026

Sharing Is Where Programs Quietly Leak

Competency II.B requires clarifying roles and responsibilities, and its second indicator is specific: define the roles and responsibilities for managing the sharing and disclosure of data for internal and external use. The word internal is deliberate. Moving customer data from the support platform into the marketing warehouse is a disclosure decision as surely as sending it to a vendor, and it is far more likely to happen without anyone approving it.

Classify the relationship first

Every credited answer in a sharing scenario starts with the relationship, because the relationship determines the instrument.

Relationship Test Instrument Common trap

Controller to processor Recipient processes only on documented instructions Article 28 DPA with the mandatory clauses Assuming a standard vendor MSA covers it

Controller to controller Recipient determines its own purposes Data sharing agreement; each party needs its own lawful basis and notice Treating the recipient as a processor to avoid the notice duty

Joint controllers Parties jointly determine purposes and means Article 26 arrangement allocating obligations transparently Assuming joint control means shared liability only

Intra-group transfer Between entities of the same corporate family Intra-group agreement plus a transfer tool if borders are crossed Treating group companies as one legal person

Internal cross-purpose Same controller, new purpose Compatible-purpose assessment; new lawful basis if incompatible Assuming one controller means one purpose

The last row is the one most often missed. A single legal entity cannot repurpose data freely just because no third party is involved — purpose limitation binds the controller to itself.

Joint controllership under Article 26

Where two parties jointly determine the purposes and means, Article 26 requires them to determine their respective responsibilities in a transparent manner by means of an arrangement , covering in particular who provides the Article 13-14 information and who handles rights requests. The essence of the arrangement must be made available to data subjects , and — critically — the data subject may exercise rights against each of the controllers , regardless of what the arrangement says between them. The arrangement allocates work; it does not carve up the data subject's rights.

Government and law-enforcement requests

A standing procedure is expected because these requests arrive under time pressure, often to someone who has never seen one:

Route every request to a single named function; front-line staff never respond directly.

Validate the legal authority — is it a subpoena, warrant, court order, statutory notice, or an informal request with no compulsion behind it? An informal request can usually be declined.

Check jurisdiction and conflict of laws — a foreign demand may conflict with GDPR, where Article 48 makes third-country judgments enforceable only through mutual legal assistance or another international agreement.

Scope-minimise — produce only what the instrument actually compels, and push back on overbroad demands.

Log the request, the authority relied on, what was produced, who approved and when.

Notify the data subject unless legally prohibited by a gag provision.

Report in aggregate through a transparency report where the organization publishes one.

Internal sharing controls

The practical governance moves are: purpose tags on datasets so a warehouse copy carries its original purpose; an approval gate for cross-functional data movement; access provisioned by role and reviewed periodically; and a rule that analytics copies inherit the retention schedule of their source rather than living forever in a lake.

The disclosure log

The log is the connective tissue. Without a record of who received what and when, an organization cannot answer an access request that asks about recipients, cannot scope a breach to downstream copies, cannot honour a deletion request across recipients, and cannot evidence lawful sharing to a regulator. GDPR Article 19 even requires the controller to communicate rectification, erasure or restriction to each recipient unless impossible or disproportionate — an obligation that is unmeetable without a recipient list.

Worked scenario

A support team exports a customer list to a spreadsheet and hands it to an agency running a re-engagement campaign. No DPA, no notice update, no log entry. Three failures stack: the agency is an undocumented processor (Article 28), the marketing purpose was not assessed for compatibility with the support purpose it was collected for (Article 5(1)(b)), and the absence of a log means a subsequent deletion request cannot be propagated under Article 19. The credited remediation is not "tell the team off" — it is a sharing approval gate with a named owner, a standing DPA template, and a log entry as a mandatory step in the export process itself.