Study guide
7.7 Breach Communications to Regulators, Individuals & Other Stakeholders
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
7.7 Breach Communications to Regulators, Individuals & Other Stakeholders
Key Takeaways Explain This Topic AI
Indicator VI.B.2 requires communicating to stakeholders in compliance with jurisdictional, global and business requirements — the audiences and clocks are different for each.
GDPR Article 33(3) fixes the content of a regulator notification: nature of the breach, categories and approximate numbers of individuals and records, DPO contact, likely consequences, and measures taken or proposed.
Article 34 requires communication to individuals without undue delay only where the breach is likely to result in a HIGH risk to their rights and freedoms — a higher bar than the Article 33 regulator threshold.
Article 34(3) provides three exceptions: data rendered unintelligible by measures such as encryption, subsequent measures making high risk unlikely, or disproportionate effort — which requires a public communication instead.
Processors notify their controller without undue delay under Article 33(2); they do not notify the supervisory authority on the controller's behalf.
Last updated: August 2026
Different Audiences, Different Thresholds, Different Clocks
Competency VI.B 's second indicator is communicate to stakeholders in compliance with jurisdictional, global and business requirements. The exam tests whether you know that "notify" is not one action. A single incident can generate a regulator filing on one clock, individual notices on a different threshold, customer notifications on contractual deadlines shorter than any statute, and internal and market communications with no statutory basis at all.
The two GDPR thresholds
Article 33 — supervisory authority Article 34 — data subjects
Trigger A personal data breach, unless unlikely to result in a risk to rights and freedoms Likely to result in a high risk to rights and freedoms
- Clock Without undue delay and, where feasible, within 72 hours of becoming aware Without undue delay
- If late Notify anyway, with reasons for the delay —
Content Article 33(3) list Nature of the breach in clear and plain language, plus Art. 33(3)(b),(c),(d) elements
The asymmetry is the point: the regulator threshold is any risk , the individual threshold is high risk . A breach can be notifiable to the authority and not to individuals; the reverse is not how the tiers work.
Article 33(3) fixes the content of the regulator notification: the nature of the breach including, where possible, the categories and approximate number of data subjects and of personal data records concerned; the name and contact details of the DPO or other contact point; the likely consequences; and the measures taken or proposed, including mitigation. Article 33(4) permits providing information in phases where it is not all available at once, which is the answer to the common panic that you cannot possibly know everything within 72 hours.
The three Article 34 exceptions
Communication to individuals is not required where:
The controller had applied appropriate technical and organisational protection measures to the affected data — in particular measures rendering it unintelligible , such as strong encryption with keys not compromised;
The controller has taken subsequent measures ensuring the high risk is no longer likely to materialise ; or
It would involve disproportionate effort — in which case there must instead be a public communication or similar measure by which individuals are informed in an equally effective manner.
Note what exception one actually requires: the encryption must have rendered the data unintelligible to the attacker . Encrypted data whose key was taken in the same incident gets no benefit.
Everyone else who must be told
- Audience Basis Typical timing
- Supervisory authorities Statute GDPR 72 hours; other regimes vary
- Affected individuals Statute, at the high-risk threshold Without undue delay
- Controller (if you are the processor) Article 33(2) — without undue delay Contract often sets 24-48 hours
- Business customers Contract, often stricter than statute Frequently 24-72 hours by DPA
Media HIPAA requires prominent media notice for breaches affecting 500+ residents of a state or jurisdiction Within 60 days of discovery
Sector regulators, exchanges, insurers Sectoral rules, listing rules, policy conditions Varies — often immediate
Internal: executives, board, support, sales Business necessity As soon as facts are stable
The processor row is heavily tested. A processor's duty under Article 33(2) is to notify its controller without undue delay; it does not notify the supervisory authority in the controller's place. Conversely, a controller cannot outsource its own notification duty to its processor.
The internal row is underrated. If support and sales learn about a breach from the customer notification email, the organization will spend the next week generating inconsistent answers — which is itself a regulatory and reputational risk. Brief the front line before the external send, with an approved holding statement.
The multi-jurisdiction matrix
For an incident spanning several regimes, build the matrix during preparation, not during the incident:
- Column Content
- Jurisdiction Where affected individuals are resident
- Trigger definition What counts as personal information and as a breach there
- Harm threshold Risk-based, or notification regardless of harm
- Regulator clock Deadline and recipient
- Individual clock Deadline and required content
- Extra recipients Consumer reporting agencies, state AGs, media
- Content requirements Mandatory elements and any prescribed template
When deadlines conflict, the operational answer is to work to the shortest applicable clock and the union of content requirements , then tailor per jurisdiction.
Writing the individual notice
Article 34(2) requires clear and plain language . A usable notice states what happened and when, what data was involved, what the likely consequences are, what the organization has done, what the individual should do — in concrete steps, not "remain vigilant" — and how to get help, with a real contact point that is staffed. Avoid the two failure modes the exam likes: minimising language that misstates severity, and legal hedging so dense the reader cannot tell whether they are affected.
Worked scenario
A processor detects unauthorised access to a database holding one controller's EU customer records, encrypted at rest with keys held in the same compromised environment. The processor notifies the controller within 12 hours per its DPA. The controller's clock starts on becoming aware , files under Article 33 within 72 hours using phased information under Article 33(4), and cannot rely on the Article 34(3)(a) encryption exception because the keys were compromised — so individuals must be notified without undue delay. Meanwhile the controller's own business customers get contractual notice on a 24-hour clock, and support receives an approved holding statement before any external send.