
data-breach-response-skills
13 breach response skills: 72h notification, forensics, remediation, simulation, multi-jurisdiction, credit monitoring
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install data-breach-response-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 13
Executing GDPR 72-Hour Breach Notification
Overview
Article 33 of the GDPR requires controllers to notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it. This skill provides the complete operational workflow from breach discovery through supervisory authority notification, including deadline calculation that accounts for weekends and public holidays, mandatory notification content, and the decision framework for determining whether notification is required.
Notification Trigger — "Becoming Aware"
The 72-hour clock starts when the controller has a reasonable degree of certainty that a security incident has occurred that has led to personal data being compromised. Per EDPB Guidelines 9/2022, Section 2.3:
- A processor must notify the controller "without undue delay" after becoming aware — the controller's 72-hour window then begins upon the controller's receipt of that notification.
- An initial suspicion of a breach (e.g., an anomalous log entry) does not start the clock. A brief investigation period is permitted to establish whether a breach has actually occurred.
- Once the controller's IT security team confirms data compromise, the controller is deemed "aware" regardless of whether the DPO or senior management has been informed.
Decision Tree: Is Notification Required?
A controller must notify the supervisory authority unless the breach is "unlikely to result in a risk to the rights and freedoms of natural persons" (Art. 33(1)).
Step 1: Classify the Breach Type
| Type | Description | Example |
|---|---|---|
| Confidentiality breach | Unauthorized or accidental disclosure of, or access to, personal data | Database exposed via misconfigured firewall revealing 12,000 customer records |
| Integrity breach | Unauthorized or accidental alteration of personal data | Malware modifying patient medication dosage records in clinical database |
| Availability breach | Accidental or unauthorized loss of access to, or destruction of, personal data | Ransomware encrypting the HR payroll system containing 3,400 employee records |
Step 2: Assess Likelihood of Risk
Evaluate each factor on a scale of 1 (low) to 4 (severe):
| Factor | Assessment Question |
|---|---|
| Data sensitivity | Does the breach involve special categories (Art. 9), financial data, or government identifiers? |
| Volume | How many data subjects are affected? Under 100 / 100-1,000 / 1,000-100,000 / Over 100,000? |
| Identifiability | Can the breached data be used to directly identify individuals without significant effort? |
| Consequences | What concrete harm could result? Financial loss, discrimination, identity theft, reputational damage? |
| Vulnerable subjects | Are minors, patients, employees, or other vulnerable categories involved? |
| Controller-specific factors | Does the controller's role amplify risk (e.g., healthcare provider, financial institution)? |
Step 3: Apply the Threshold
- Aggregate score 6 or below: Breach unlikely to result in risk — notification not required under Art. 33(1), but must be documented in the breach register per Art. 33(5).
- Aggregate score 7-15: Breach likely to result in risk — supervisory authority notification required within 72 hours.
- Aggregate score 16 or above: Breach likely to result in high risk — supervisory authority notification required within 72 hours AND data subject notification required under Art. 34.
Required Notification Content — Art. 33(3)
The notification to the supervisory authority must contain, at minimum:
(a) Nature of the Breach
- Description of the nature of the personal data breach.
- Categories of data subjects concerned (e.g., customers, employees, patients).
- Approximate number of data subjects concerned.
- Categories of personal data records concerned (e.g., names, email addresses, financial account numbers).
- Approximate number of personal data records concerned.
(b) DPO Contact Details
- Name of the Data Protection Officer: Dr. Elena Vasquez
- Email: dpo@stellarpayments.eu
- Direct phone: +49 30 7742 8001
- Postal address: Stellar Payments Group, Friedrichstraße 191, 10117 Berlin, Germany
(c) Likely Consequences
- Detailed description of the likely consequences of the breach, categorized by:
- Physical harm (if applicable)
- Material harm (financial loss, fraud risk)
- Non-material harm (distress, discrimination, reputational damage)
- Loss of control over personal data
- Limitation of rights
(d) Measures Taken or Proposed
- Immediate containment measures already implemented
- Measures to mitigate adverse effects on data subjects
- Planned longer-term remediation actions
- Whether data subjects have been or will be notified under Art. 34
Phased Notification
Art. 33(4) permits information to be provided in phases where it is not possible to provide all details simultaneously. The initial notification must:
- State that additional information will follow.
- Provide reasons for the delay in furnishing complete information.
- Include whatever information is available at the time of initial notification.
- Be supplemented with additional details as they become available, without undue further delay.
Notification Channels by Supervisory Authority
| Authority | Jurisdiction | Notification Method |
|---|---|---|
| BfDI | Germany (federal) | Online portal at bfdi.bund.de — electronic form submission |
| CNIL | France | Online notification via notifications.cnil.fr/notifications |
| ICO | United Kingdom | Online form at ico.org.uk/for-organisations/report-a-breach |
| DPC | Ireland | Online breach notification form via forms.dataprotection.ie |
| AEPD | Spain | Electronic submission via sedeagpd.gob.es |
| Garante | Italy | PEC (certified email) to protocollo@pec.gpdp.it |
| AP | Netherlands | Online form at autoriteitpersoonsgegevens.nl/meldplicht-datalekken |
72-Hour Deadline Calculation Rules
- The 72-hour period is calculated in continuous hours, including weekends and public holidays.
- If the breach is discovered at 14:30 CET on a Friday, the deadline is 14:30 CET on the following Monday.
- Art. 33(1) uses the phrase "where feasible" — if notification exceeds 72 hours, the controller must provide reasons for the delay alongside the notification.
- The EDPB has confirmed that the 72-hour period runs from the moment the controller "becomes aware," not from the moment of the breach itself.
Late Notification — Justifying Delay
When notification exceeds 72 hours, Art. 33(1) requires the controller to accompany the notification with reasons for the delay. Acceptable justifications per EDPB guidance include:
- Complex forensic investigation needed to determine scope and affected data categories
- Large-scale breach requiring coordination with law enforcement before notification
- Discovery during a period where key personnel were unavailable and no adequate delegation was in place (though this itself may be a compliance gap)
Unacceptable justifications:
- Internal approval processes delayed sign-off
- The DPO was on annual leave and no deputy was appointed
- The organization wanted to complete its own public communications before notifying the authority
Post-Notification Obligations
- Supplementary information: Provide any outstanding details from the initial notification as they become available.
- Breach register update: Record the full details of the breach, its effects, and remedial actions in the Art. 33(5) register.
- Data subject notification assessment: Determine whether Art. 34 notification to individuals is also required.
- Supervisory authority engagement: Respond promptly to any follow-up inquiries from the authority.
- Remediation evidence: Document all corrective measures implemented and provide evidence to the authority if requested.
Managing Breach Credit Monitoring
Overview
Offering credit monitoring and identity protection services to affected individuals is a standard post-breach measure that mitigates harm, demonstrates organizational responsibility, and may reduce regulatory and litigation exposure. While not explicitly required by the GDPR, it is considered a best practice under Art. 34 and is frequently required under US state breach notification laws for breaches involving SSN or financial data. This skill covers the end-to-end process of vendor selection, enrollment logistics, coverage management, and communication.
Vendor Selection Criteria
Tier 1 Providers (Global Capability)
| Provider | Product | Coverage | Identity Theft Insurance | Dark Web Monitoring | Geographic Coverage |
|---|---|---|---|---|---|
| Experian | IdentityWorks | Credit monitoring (1 bureau or 3 bureau), SSN tracking, address change alerts | Up to $1M / EUR 25,000 | Yes | US, UK, EU (select markets) |
| TransUnion | TrueIdentity | Credit monitoring, credit lock, credit score tracker | Up to $1M | Yes | US, Canada |
| Equifax | ID Patrol | Credit monitoring, SSN monitoring, lost wallet protection | Up to $1M | Yes | US, UK, Canada |
| Kroll | Identity Monitoring | Credit monitoring, cyber monitoring, identity restoration | Up to $1M | Yes | US, EU, APAC |
| AllClear ID | Identity Repair | Credit monitoring, identity repair, fraud investigation | Up to $1M | Yes | US |
Selection Criteria Weighted Scoring
| Criterion | Weight | Description |
|---|---|---|
| Geographic coverage | 25% | Must cover all jurisdictions where affected data subjects reside |
| Enrollment capacity | 20% | Must handle peak enrollment volume (target: 50% of affected in first 7 days) |
| Speed of activation | 15% | Time from contract signing to enrollment portal availability |
| Language support | 15% | Portal and communications must be available in languages of affected population |
| Identity theft insurance | 10% | Coverage amount, deductible, claim process simplicity |
| Dark web monitoring | 10% | Real-time scanning of dark web forums and marketplaces for compromised data |
| Cost per individual | 5% | Price point per monitored individual per month |
Recommended Selection for Stellar Payments Group
Primary vendor: Experian IdentityWorks — selected for EU + US coverage, multilingual portal (German, English, French, Dutch, Spanish), enrollment capacity for 50,000+ individuals, and established enterprise breach response program.
Contract terms negotiated under retainer SPG-EXP-2025-003:
- Per-individual cost: EUR 8.50/month (12-month term), EUR 7.20/month (24-month term)
- Enrollment portal activation: within 48 hours of contract activation
- Languages: German, English, French, Dutch, Spanish, Italian, Polish
- Identity theft insurance: EUR 25,000 per individual (EU), $1,000,000 per individual (US)
- Dark web monitoring: included
- Dedicated account manager and weekly enrollment reporting
Coverage Duration Guidelines
| Breach Type | Recommended Duration | Rationale |
|---|---|---|
| Financial data (card numbers, bank accounts) | 12 months | Financial fraud typically occurs within 6-9 months of breach |
| Government identifiers (SSN, national ID, tax ID) | 24 months | Identity theft using government IDs can surface 12-18 months post-breach |
| Credential compromise (username + password) | 12 months | Credential stuffing attacks typically peak within 3-6 months |
| Health data (medical records, insurance) | 24 months | Medical identity theft is harder to detect and may take longer to surface |
| Combined (financial + government ID + health) | 24 months | Maximum exposure requires maximum monitoring duration |
Enrollment Logistics
Enrollment Process
- Generate unique activation codes: One code per affected individual. Codes must be unique, non-guessable, and time-limited (90-day enrollment window).
- Include activation details in breach notification letter: Provide the enrollment URL, activation code, and step-by-step instructions in the Art. 34 / individual notification letter.
- Set up dedicated enrollment portal: stellarpayments.eu/breach-support/enroll — branded co-portal with Experian.
- Provide alternative enrollment channels: Toll-free phone enrollment for individuals who cannot or prefer not to enroll online: +49 30 7742 9200 (EU) / 1-888-555-0199 (US).
- Enrollment support: Dedicated operators available during enrollment window to assist with technical issues.
Enrollment Timeline
| Phase | Timeline | Target |
|---|---|---|
| Portal activation | Within 48 hours of vendor contract activation | Before individual notification dispatch |
| First notification dispatch | Day 1 of individual notification | All affected individuals |
| Peak enrollment | Days 1-14 after notification | 40% enrollment rate |
| Follow-up reminder | 30 days after notification | Target individuals who have not enrolled |
| Final enrollment deadline | 90 days after notification | Final enrollment rate target: 70%+ |
Enrollment Tracking Metrics
| Metric | Target | Reporting Frequency |
|---|---|---|
| Enrollment rate (cumulative) | 70% by deadline | Weekly |
| Daily enrollment volume | N/A (monitoring) | Daily |
| Support call volume | N/A (capacity planning) | Daily |
| Failed enrollment attempts | Under 5% | Weekly |
| Identity theft alerts generated | N/A (monitoring) | Monthly |
| Insurance claims filed | N/A (monitoring) | Monthly |
Communication to Affected Individuals
Initial Notification (Included in Breach Letter)
Include in the Art. 34 / breach notification letter:
Free Identity Protection: We are offering [12/24] months of complimentary identity protection through Experian IdentityWorks, at no cost to you. This service includes:
- Credit monitoring and alerts
- Dark web surveillance for your personal information
- Identity theft insurance up to [EUR 25,000 / $1,000,000]
- Identity restoration services if you become a victim of identity theft
To enroll:
- Visit: stellarpayments.eu/breach-support/enroll
- Enter your activation code: [UNIQUE CODE]
- Enrollment deadline: [DATE — 90 days from notification]
Or call our enrollment hotline: [+49 30 7742 9200 / 1-888-555-0199]
Follow-Up Reminder (30 Days After Notification)
Subject: Reminder — Enroll in Free Identity Protection by [Deadline]
Dear [Name],
On [notification date], we notified you about a security incident that may have affected your personal information. We want to remind you that we are offering [12/24] months of complimentary identity protection at no cost.
If you have not yet enrolled, your activation code [CODE] is still active. Visit stellarpayments.eu/breach-support/enroll before [deadline] to activate your protection.
Cost Management
Budget Estimation Formula
Total cost = (affected individuals x enrollment rate x per-individual monthly cost x coverage months) + (enrollment portal setup) + (support staffing)
Example for SPG-BREACH-2026-003:
- Affected: 15,230 individuals
- Estimated enrollment rate: 70% = 10,661 enrollees
- Monthly cost: EUR 8.50 (12-month term)
- Coverage: 12 months
- Total monitoring cost: EUR 1,087,422
- Portal setup: EUR 15,000
- Support staffing (3 months): EUR 45,000
- Total estimated cost: EUR 1,147,422
Insurance Recovery
Cyber insurance policy (Stellar Payments Group — Allianz Cyber Enterprise, policy SPG-CYB-2025-001):
- Credit monitoring costs are covered under "breach response costs" up to EUR 2,000,000 per incident.
- Claim must be filed within 60 days of breach notification.
- Deductible: EUR 50,000.
Implementing Breach Detection System
Overview
Effective breach detection is the prerequisite for timely Art. 33 notification. The GDPR does not prescribe specific detection technologies, but Art. 32 requires appropriate technical and organisational measures, and Art. 33(1) creates a de facto obligation to detect breaches promptly — a controller cannot notify within 72 hours if it takes months to discover a breach. This skill covers the technical architecture for personal data breach detection, including SIEM integration, DLP alerting, behavioral analytics, and insider threat monitoring.
Breach Classification Taxonomy
Level 1: CIA Triad Classification
| Type | Definition | Detection Method |
|---|---|---|
| Confidentiality | Unauthorized disclosure or access to personal data | DLP alerts, access log anomalies, data exfiltration detection |
| Integrity | Unauthorized modification of personal data | File integrity monitoring, database audit logs, checksum validation |
| Availability | Loss of access to or destruction of personal data | System health monitoring, backup verification, ransomware detection |
Level 2: Attack Vector Classification
| Vector | Description | Primary Detection |
|---|---|---|
| External attack | Unauthorized access from outside the network perimeter | IDS/IPS, firewall logs, authentication failures |
| Insider threat | Authorized user acting beyond their authorized scope | UEBA, DLP, access pattern analysis |
| Third-party compromise | Breach originating from a processor or vendor | Vendor monitoring, API anomaly detection |
| Accidental disclosure | Human error leading to data exposure | DLP content inspection, email gateway filters |
| System failure | Technical failure causing data loss or corruption | Infrastructure monitoring, backup validation |
| Physical breach | Loss or theft of physical devices containing data | Asset tracking, device encryption verification |
Level 3: Data Sensitivity Classification
| Level | Data Types | Detection Priority |
|---|---|---|
| Critical | Art. 9 special categories, Art. 10 criminal data, financial credentials | Real-time alerting, immediate escalation |
| High | Government identifiers, financial account data, authentication credentials | Real-time alerting, 15-minute escalation |
| Medium | Contact details, employment records, purchase history | Near-real-time (5-minute batching), 1-hour escalation |
| Low | Publicly available business contact data, non-personal metadata | Batch processing (hourly), daily review |
SIEM Integration Architecture
Event Source Configuration
Stellar Payments Group deploys Splunk Enterprise Security as the primary SIEM platform. The following log sources are ingested for breach detection:
| Source | Log Type | Ingestion Method | Events/Day |
|---|---|---|---|
| Active Directory | Authentication, authorization, group changes | Splunk Universal Forwarder | 2.4M |
| AWS CloudTrail | API calls, console logins, resource changes | S3-to-Splunk via SQS | 8.7M |
| PostgreSQL audit | Query logs, schema changes, failed authentications | syslog-ng to Splunk HEC | 14.2M |
| Palo Alto PA-5260 | Firewall sessions, URL filtering, threat prevention | syslog to Splunk | 45.3M |
| CrowdStrike Falcon | Endpoint detections, process execution, file writes | Falcon SIEM Connector | 6.1M |
| Microsoft 365 | Email audit, SharePoint access, Teams DLP | Microsoft Graph API via Splunk Add-on | 3.8M |
| Okta | SSO authentications, MFA events, admin changes | Okta Event Hook to Splunk HEC | 890K |
| AWS GuardDuty | Threat intelligence findings, anomaly detections | CloudWatch to Splunk | 12K |
Correlation Rules for Breach Detection
Rule 1: Mass Data Access Anomaly
Trigger: Single user account accesses more than 500 unique personal data records within a 30-minute window.
Data sources: PostgreSQL audit logs, application access logs.
Severity: High
Action: Create incident ticket, alert SOC analyst, notify DPO on-call.
False positive mitigation: Whitelist batch processing service accounts (reviewed quarterly). Flag whitelisted accounts if access occurs outside scheduled batch windows.
Rule 2: Data Exfiltration Indicator
Trigger: Outbound data transfer exceeding 50MB to an unclassified external destination from a system containing personal data.
Data sources: Palo Alto firewall, CrowdStrike network telemetry, DLP alerts.
Severity: Critical
Action: Automated network isolation of source endpoint, SOC analyst investigation, DPO notification.
False positive mitigation: Baseline normal data transfer patterns per endpoint. Whitelist approved SaaS destinations (Salesforce, Workday, etc.).
Rule 3: Privileged Account Anomaly
Trigger: Database administrator account performs SELECT queries on personal data tables outside of change management windows OR from an unrecognized source IP.
Data sources: PostgreSQL audit logs, Okta authentication logs, IP geolocation.
Severity: High
Action: Alert SOC lead and database security team. Log full query text for forensic review.
Rule 4: Ransomware Behavior Pattern
Trigger: More than 20 file rename/encrypt operations per second on file servers or database storage volumes, OR known ransomware file extension creation (.lockbit, .encrypted, .crypt).
Data sources: CrowdStrike Falcon, Windows file audit logs, storage IOPS monitoring.
Severity: Critical
Action: Automated isolation of affected system, activate incident response team, preserve forensic image.
Rule 5: Authentication Brute Force
Trigger: More than 50 failed authentication attempts against personal data systems within 10 minutes from a single source, OR more than 200 failed attempts across multiple accounts from the same source within 30 minutes (password spray).
Data sources: Active Directory, Okta, application authentication logs.
Severity: Medium (escalates to High if followed by successful authentication).
Action: Block source IP at firewall, SOC investigation, check for compromised credentials.
DLP Alert Configuration
Email DLP Policies
| Policy Name | Detection Content | Action | Severity |
|---|---|---|---|
| PII Outbound | Regex: German ID (Personalausweisnummer), IBAN, credit card numbers, health insurance numbers | Block + encrypt + alert DPO | High |
| Bulk PII | More than 10 rows of structured personal data (name + email/phone/address) in email body or attachment | Block + alert sender manager + SOC | Critical |
| Special Category | Keywords/patterns matching health diagnoses, genetic markers, biometric templates, trade union references | Block + alert DPO | Critical |
| Cross-Border Transfer | Personal data sent to recipients in non-adequate countries without approved transfer mechanism | Hold for review + alert privacy team | Medium |
Endpoint DLP Policies
| Policy Name | Detection Content | Action |
|---|---|---|
| USB Copy PII | Copy of files containing personal data to removable media | Block (exceptions via DPO-approved ticket) |
| Cloud Upload PII | Upload of personal data files to non-approved cloud services | Block + alert SOC |
| Print PII Bulk | Print job containing more than 50 records of personal data | Alert line manager + SOC |
| Screenshot PII | Screen capture of application displaying personal data records | Log + alert SOC (for pattern analysis) |
Anomaly Detection and UEBA
Behavioral Baselines
User and Entity Behavior Analytics (UEBA) establishes normal patterns for each user and system account:
| Baseline Metric | Normal Range | Anomaly Threshold | Detection Window |
|---|---|---|---|
| Daily record access count | Per-user historical average | 3x standard deviation above mean | Rolling 30-day baseline |
| Access time patterns | Historical working hours | Access outside 95th percentile time range | Rolling 90-day baseline |
| Data download volume | Per-user historical average | 2x standard deviation above mean for 2+ consecutive hours | Rolling 14-day baseline |
| Geographic access location | Historical IP geolocation | New country not seen in 90-day history | Rolling 90-day baseline |
| Application access pattern | Historical application mix | Access to new personal data application not in 60-day history | Rolling 60-day baseline |
Insider Threat Indicators
Composite risk scoring for insider threat detection combines multiple low-severity indicators:
| Indicator | Weight | Source |
|---|---|---|
| Access outside normal hours to personal data systems | 15 | Okta + application logs |
| Bulk data download from HR or customer databases | 25 | DLP + database audit |
| Use of personal email or cloud storage from corporate device | 10 | CrowdStrike + proxy logs |
| Notice period or performance improvement plan status | 20 | HR system integration (Workday) |
| Access to data outside role scope | 20 | Role-based access comparison |
| Disabling or circumventing security controls | 30 | Endpoint agent tampering alerts |
| Repeated failed access to restricted personal data | 10 | Application access logs |
Composite scores above 60 trigger enhanced monitoring. Scores above 80 trigger SOC analyst investigation and DPO notification.
Integration with Privacy Incident Response
Automated Workflow
- SIEM correlation rule or DLP policy triggers an alert.
- Alert is enriched with contextual data: user identity, data classification of affected system, data subject count estimate.
- If the affected system is classified as containing personal data (tagged in the CMDB), the alert is automatically duplicated to the privacy incident queue in ServiceNow.
- Privacy incident coordinator performs initial triage within 30 minutes.
- If personal data breach is confirmed, the Art. 33 72-hour clock activation is triggered and the DPO is notified.
Detection-to-Notification Timeline Target
| Phase | Target | Owner |
|---|---|---|
| Detection to alert | Under 5 minutes | SIEM platform (automated) |
| Alert to triage | Under 30 minutes | SOC analyst |
| Triage to breach confirmation | Under 4 hours | SOC lead + privacy coordinator |
| Breach confirmation to DPO notification | Under 1 hour | Privacy incident coordinator |
| DPO notification to 72-hour clock start | Immediate | DPO |
Monitoring and Tuning
Monthly Review Cadence
- Review false positive rates for all breach detection correlation rules. Target: under 15% false positive rate.
- Analyze detection gap assessments against known breach scenarios from EDPB Guidelines 01/2021.
- Update behavioral baselines following organizational changes (new hires, departures, role changes).
- Validate that all new personal data systems have been onboarded to the SIEM and DLP platforms.
- Test end-to-end detection-to-notification workflow with a simulated breach scenario quarterly.
Maintaining Breach Documentation Records
Overview
Article 33(5) of the GDPR requires every controller to document all personal data breaches, regardless of whether the breach triggered supervisory authority notification. The documentation must include "the facts relating to the personal data breach, its effects and the remedial action taken" and must "enable the supervisory authority to verify compliance with this Article." This creates a comprehensive breach register that serves as a primary accountability document under Art. 5(2).
Mandatory Documentation Requirements — Art. 33(5)
Facts Relating to the Breach
Every breach register entry must document:
| Field | Description | Example |
|---|---|---|
| Breach reference number | Unique sequential identifier | SPG-BREACH-2026-003 |
| Discovery date and time | UTC timestamp when controller became aware | 13 March 2026, 14:30 UTC |
| Breach date and time | UTC timestamp of the breach itself (if different from discovery) | 13 March 2026, 11:15 UTC |
| Breach type | Confidentiality, integrity, availability, or combined | Availability (primary), Confidentiality (under investigation) |
| Breach description | Factual narrative of what occurred | LockBit 3.0 ransomware encrypted production customer database cluster. Attack vector: compromised service account obtained via spear-phishing. |
| Affected systems | Systems involved in the breach | db-prod-eu-west-01 through db-prod-eu-west-04 |
| Data subject categories | Types of individuals affected | Individual account holders, business account holders, joint account holders |
| Data subject count | Approximate number of affected individuals | 15,230 |
| Personal data categories | Types of data compromised | Names, postal addresses, emails, payment card last-4, transaction histories, account balances |
| Record count | Approximate number of affected records | 48,720 |
| Root cause | Identified cause of the breach | Stale privileged service account + phishing + push-fatigue MFA bypass |
| Containment timestamp | When the breach was contained | 13 March 2026, 12:45 UTC |
Effects of the Breach
| Field | Description | Example |
|---|---|---|
| Risk assessment score | Aggregate score from the risk assessment methodology | 18/24 |
| Risk level | Resulting risk determination | Approaching high risk |
| Actual harm identified | Any confirmed harm to data subjects | No confirmed harm as of assessment date |
| Potential harm | Likely consequences if data is misused | Financial fraud, identity theft, targeted phishing |
| Duration of impact | How long data subjects were affected | 36 hours (database unavailability); ongoing (potential confidentiality impact) |
Remedial Actions Taken
| Field | Description | Example |
|---|---|---|
| Containment measures | Immediate actions to stop the breach | Network isolation, credential revocation, backup restoration |
| Remediation measures | Longer-term corrective actions | MFA upgrade to FIDO2, service account lifecycle management, network segmentation |
| Remediation status | Current status of each action | 4 of 7 measures completed; 3 in progress |
| Remediation deadline | Target completion date | 15 June 2026 |
Notification Decision Documentation
Every breach entry must also record the notification decision and rationale:
| Field | Description |
|---|---|
| Art. 33 SA notification decision | Required / Not required |
| Art. 33 notification rationale | Why notification was or was not required (reference risk assessment) |
| Art. 33 notification date | Date and time of SA notification (if applicable) |
| SA reference number | Reference number assigned by the supervisory authority |
| SA follow-up status | Any follow-up inquiries or actions from the authority |
| Art. 34 DS notification decision | Required / Not required / Exempt under Art. 34(3) |
| Art. 34 notification rationale | Why DS notification was or was not required |
| Art. 34 notification date | Date of DS communication (if applicable) |
| Art. 34 notification method | Channels used (email, postal, public communication) |
Register Structure and Maintenance
Single Centralized Register
All breaches must be recorded in a single centralized register maintained by the DPO's office. Stellar Payments Group uses a dedicated module in the OneTrust Privacy Management Platform with the following access controls:
- Write access: DPO, Deputy DPO, Privacy Incident Coordinator
- Read access: CISO, General Counsel, Internal Audit, Board Audit Committee
- No access: Business unit managers, IT operations staff (access to individual breach records provided on a need-to-know basis via separate reports)
All Breaches Documented — Including Non-Notifiable
The register must include every personal data breach, regardless of severity or whether SA/DS notification was triggered. This explicitly includes:
- Misdirected emails containing personal data (even single-recipient incidents)
- Temporary availability breaches resolved from backup
- Unsuccessful exfiltration attempts where personal data was targeted but not accessed
- Breaches at processors that affected the controller's data
- Physical breaches (lost devices, unauthorized office access)
Retention Period
Breach register entries are retained for a minimum of 7 years from the date of breach closure. This accounts for:
- The 5-year statute of limitations for GDPR enforcement actions in most EU member states
- The need to demonstrate patterns (or absence of patterns) to supervisory authorities
- Litigation time limits for data subject compensation claims under Art. 82
After the 7-year retention period, entries are anonymized (data subject counts retained, specific identifiers removed) and maintained indefinitely for trend analysis.
Audit Readiness
Supervisory Authority Access — Art. 33(5)
The breach register must be available to the supervisory authority "on request." Audit readiness requires:
- Instant availability: The register must be exportable in a structured format (CSV, JSON, PDF) within 24 hours of a supervisory authority request.
- Completeness verification: Monthly self-audit to verify all reported security incidents were assessed for personal data impact and, where applicable, added to the register.
- Cross-reference integrity: Each register entry must link to supporting documentation (risk assessment form, SA notification copy, DS notification copy, investigation report, remediation evidence).
- Trend reporting: The register must support generation of trend reports showing: breach frequency over time, breach types, root cause categories, notification rates, and remediation completion rates.
Annual Breach Register Review
The DPO conducts an annual review of the breach register covering:
- Completeness: Are all known breaches documented? Cross-reference against the security incident management system.
- Accuracy: Sample 20% of entries and verify accuracy against source documentation.
- Timeliness: Were entries created within 72 hours of breach discovery?
- Remediation closure: Are remediation actions tracked to completion? Flag overdue actions.
- Pattern identification: Are there recurring breach types or root causes indicating systemic issues?
- Board reporting: Prepare an annual breach summary report for the Board Audit Committee.
Integration with Other Records
| Related Record | Integration Point |
|---|---|
| Art. 30 RoPA | Link affected processing activities to the breach entry |
| DPIA Register | Update DPIAs for affected processing activities with breach as risk event |
| Vendor Register | Update processor risk assessment if breach originated at a processor |
| Training Records | Document post-breach training delivered to relevant personnel |
| Audit Log | Reference internal audit findings related to the breach |
| Insurance Records | Link to cyber insurance claim reference (if applicable) |
Common Documentation Deficiencies
- Breaches documented in security incident systems but not in the Art. 33(5) register: The security incident ticket is not a substitute for the breach register entry.
- Missing notification decision rationale: Recording "not notified" without documenting why the breach was assessed as unlikely to result in risk.
- Incomplete remediation tracking: Remedial actions listed but never updated to reflect completion status.
- Delayed documentation: Entries created weeks after the breach, making it difficult to demonstrate timely awareness and response.
- No processor breach entries: Breaches that occur at processors but affect the controller's data are not recorded in the controller's register.
Conducting Breach Investigation Forensics
Overview
When a personal data breach is confirmed, a thorough forensic investigation is essential to determine the breach scope (which personal data and data subjects were affected), the attack vector, the timeline of unauthorized activity, and the root cause. The investigation findings directly feed into the Art. 33 supervisory authority notification, the Art. 34 data subject communication, and the post-breach remediation plan. This skill provides the complete forensic investigation workflow, evidence handling procedures, and analysis techniques.
Evidence Preservation Protocol
Golden Rule: Preserve First, Analyze Second
The first priority upon breach confirmation is to preserve volatile evidence before it is overwritten or destroyed. Evidence must be collected in order of volatility:
- CPU registers and cache — captured via live memory acquisition tools (Volatility, WinPmem, LiME).
- Memory (RAM) contents — full memory dump of affected systems. Contains running processes, network connections, encryption keys, and malware artifacts that may not exist on disk.
- Network connections and routing tables — current active connections may reveal command-and-control (C2) infrastructure or ongoing data exfiltration.
- Running processes and services — process trees, loaded DLLs, open file handles, and user context.
- Disk contents — forensic disk images (bit-for-bit copies) of affected system storage. Use write blockers for physical media.
- Log files — system logs, application logs, security logs, database audit logs. Prioritize logs that may be subject to rotation or overwrite.
- Network traffic captures — packet captures (PCAP) from network taps, SPAN ports, or inline capture points.
- External evidence — cloud service logs (AWS CloudTrail, Azure Activity Log), SaaS audit logs, third-party vendor logs.
Forensic Image Acquisition
| System Type | Tool | Method | Hash Verification |
|---|---|---|---|
| Windows server | FTK Imager 4.7 | Bit-for-bit disk image to external write-blocked storage | SHA-256 + MD5 dual hash |
| Linux server | dc3dd | Bit-for-bit using /dev/sda source to external storage | SHA-256 hash with dcfldd verification |
| AWS EC2 instance | AWS CLI + EBS snapshot | Create EBS snapshot, then convert to forensic image | SHA-256 of snapshot export |
| Database | pg_dump (logical) + disk image | Logical export for data analysis + physical disk image for artifact recovery | SHA-256 of both outputs |
| Mobile device | Cellebrite UFED / GrayKey | Physical extraction where legally permitted | SHA-256 of extraction package |
| Cloud storage (S3) | AWS CLI sync with versioning | Download all object versions including deleted objects | SHA-256 of manifest |
Chain of Custody Documentation
Every piece of evidence must be tracked from acquisition through analysis to storage using a formal chain of custody record:
Evidence Tracking Fields
| Field | Description |
|---|---|
| Evidence ID | Unique identifier: SPG-BREACH-2026-003-EV-001 |
| Description | Full RAM dump of db-prod-eu-west-01 (PostgreSQL primary) |
| Date/time acquired | 13 March 2026, 15:47 UTC |
| Acquired by | Thomas Brenner, CISO, Stellar Payments Group |
| Acquisition tool | WinPmem 4.0 — Memory acquisition |
| Hash at acquisition | SHA-256: a3f8b2c1d9e... (full hash recorded in evidence log) |
| Storage location | Forensic evidence vault, Building A, Room 104, Safe #3, Shelf B |
| Access log | All access to evidence is logged with name, date, time, and purpose |
Chain of Custody Transfer Record
| Transfer # | Date/Time | Released By | Received By | Purpose | Hash Verified |
|---|---|---|---|---|---|
| 1 | 13 March 2026, 16:00 UTC | Thomas Brenner (CISO) | Mandiant IR Analyst (Sarah Mitchell) | Forensic analysis | Yes — SHA-256 match |
| 2 | 20 March 2026, 10:00 UTC | Sarah Mitchell (Mandiant) | Thomas Brenner (CISO) | Return after analysis | Yes — SHA-256 match |
Log Analysis Methodology
Tool Selection and Application
Splunk Enterprise Security
- Use case: Centralized log correlation, timeline reconstruction, behavioral analysis.
- Key searches for breach investigation:
- Authentication events:
index=auth sourcetype=okta:log action=authentication.login | stats count by user, result, client.ipAddress, client.geographicalContext.country - Database queries:
index=database sourcetype=postgresql:audit query_type=SELECT table IN (customers, transactions, accounts) | stats count, values(query_text) by user, source_ip - Data exfiltration:
index=network sourcetype=pan:traffic dest_zone=untrust bytes_sent>50000000 | stats sum(bytes_sent) by src_ip, dest_ip, app
- Authentication events:
ELK Stack (Elasticsearch, Logstash, Kibana)
- Use case: Large-volume log ingestion, full-text search, visualization of access patterns.
- Key queries for breach investigation:
- Anomalous access timing: Filter by timestamp outside of business hours (before 07:00 or after 20:00 local time) against personal data system indices.
- Geo-anomaly detection: Aggregate authentication source IPs by geolocation; flag countries not present in the 90-day baseline.
- Volume anomaly: Aggregate data access events by user per hour; identify spikes exceeding 3 standard deviations above the 30-day mean.
Wireshark / tshark
- Use case: Packet-level analysis of network traffic to/from compromised systems.
- Key filters for breach investigation:
- Identify data exfiltration:
ip.src == 10.0.1.50 && tcp.dstport != 443 && frame.len > 1000(non-HTTPS outbound from compromised host) - Identify C2 communication:
dns.qry.name contains ".onion" || dns.qry.name contains "dga"(DNS queries to suspicious domains) - Reconstruct data transfers: Follow TCP streams to recover transferred file contents from PCAP captures.
- Identify data exfiltration:
Additional Tools
| Tool | Purpose | Application |
|---|---|---|
| Volatility 3 | Memory forensics | Analyze RAM dumps for malware, injected code, credential harvesting |
| Autopsy / Sleuth Kit | Disk forensics | Recover deleted files, analyze file system timelines, extract artifacts |
| YARA | Malware identification | Scan disk images and memory dumps against malware signature rules |
| Plaso / log2timeline | Super-timeline creation | Create unified timeline from multiple evidence sources |
| Chainsaw | Windows event log analysis | Rapid triage of Windows EVTX logs using Sigma detection rules |
Scope Determination Process
Step 1: Identify All Compromised Systems
- Starting from the initially identified compromised system, trace lateral movement through authentication logs, network connection logs, and endpoint detection alerts.
- For each system identified, determine whether it stores, processes, or transmits personal data by cross-referencing with the data processing inventory (Art. 30 records).
- Document each compromised system with: hostname, IP address, function, data classification, personal data categories stored, and estimated data subject count.
Step 2: Determine Accessed Data
- For each compromised system containing personal data, analyze access logs to determine which specific tables, files, or records were accessed by the attacker.
- Distinguish between "system compromised" (attacker had access to the system) and "data accessed" (attacker actually queried or downloaded personal data).
- Apply the precautionary principle: if logs are insufficient to determine whether specific data was accessed, assume all data on the compromised system was potentially accessed.
Step 3: Determine Exfiltration
- Analyze network traffic logs for data transfers from compromised systems to external destinations during the breach window.
- Review DNS logs for DNS tunneling indicators (unusually long subdomain strings, high query volume to unusual domains).
- Check for encrypted channel usage (VPN, SSH, HTTPS) to external IPs not in the organization's approved destination list.
- Examine endpoint logs for evidence of compression, encryption, or staging of files prior to transfer.
- Report findings as: "Exfiltration confirmed," "No evidence of exfiltration (with confidence level)," or "Exfiltration cannot be ruled out."
Step 4: Establish Breach Timeline
- Determine the earliest evidence of unauthorized access (initial compromise date).
- Identify the timeline of attacker activity — what actions were taken and when.
- Determine when the breach was detected.
- Calculate the dwell time (time between initial compromise and detection).
- Document any periods where log coverage gaps prevent timeline reconstruction.
Root Cause Analysis
5-Whys Framework Applied to Data Breaches
Example: Stellar Payments Group Ransomware Incident
- Why did the ransomware execute? The attacker deployed ransomware using a compromised service account with administrative privileges on the database cluster.
- Why did the attacker have a compromised service account? The service account credentials were obtained from a spear-phishing email that an IT operations engineer clicked on 10 March 2026, which installed a credential-harvesting keylogger.
- Why did the phishing email reach the engineer? The email bypassed the email gateway because it was sent from a compromised legitimate domain and contained no detectable malicious payload (the link pointed to a legitimate-appearing login page).
- Why did the service account have administrative database privileges? The service account was originally created for a migration project in 2024 and was never decommissioned. Its privileges were not reviewed as part of the quarterly access review because service accounts were excluded from the review scope.
- Why were service accounts excluded from the access review? The access review policy defined its scope as "user accounts" and did not explicitly include service accounts, machine accounts, or API keys.
Root cause: Access review policy gap — service accounts excluded from periodic access certification, combined with stale elevated-privilege service account from completed project.
Investigation Report Structure
Section 1: Executive Summary
- Breach type and classification
- Date range of unauthorized activity
- Number of affected data subjects and records
- Root cause (one sentence)
- Current status (contained/ongoing)
- Key remediation recommendations
Section 2: Investigation Scope and Methodology
- Investigation objectives
- Evidence sources analyzed
- Tools and techniques used
- Investigation team members and roles
- Timeline of investigation activities
Section 3: Findings
- Detailed breach timeline with evidence citations
- Systems compromised and personal data affected
- Attack vector and technique (mapped to MITRE ATT&CK framework)
- Exfiltration assessment
- Root cause analysis
Section 4: Impact Assessment
- Data subjects affected (count and categories)
- Personal data compromised (categories and sensitivity)
- Risk assessment for Art. 33/34 notification purposes
- Regulatory exposure assessment
Section 5: Remediation Recommendations
- Immediate actions (already taken)
- Short-term actions (within 30 days)
- Medium-term actions (within 90 days)
- Long-term systemic improvements
Section 6: Evidence Inventory
- Complete list of all evidence collected
- Chain of custody records
- Hash verification log
- Evidence retention and disposal schedule
Managing Multi-Jurisdiction Breach Notification
Overview
When a data breach affects individuals across multiple legal jurisdictions, the controller must navigate overlapping and sometimes conflicting notification requirements. The EU GDPR imposes a 72-hour supervisory authority notification deadline; US state laws impose varying timelines and content requirements; and other jurisdictions (Canada, Australia, Brazil, Japan, South Korea) have their own regimes. This skill provides the framework for coordinated notification across jurisdictions.
Jurisdiction Mapping — Notification Requirements
European Union — GDPR (All Member States)
| Element | Requirement |
|---|---|
| SA notification timeline | 72 hours from awareness (Art. 33(1)) |
| SA notification threshold | Unless breach is "unlikely to result in a risk" |
| DS notification timeline | Without undue delay when "high risk" (Art. 34(1)) |
| Lead SA determination | One-stop-shop: Art. 56 lead SA based on main establishment |
| Cross-border mechanism | Lead SA notified; other concerned SAs informed via Art. 60 |
| Content requirements | Art. 33(3)(a)-(d) for SA; Art. 34(2) for data subjects |
United States — State Breach Notification Laws
| State | Timeline | AG Notification | Threshold | Key Differences |
|---|---|---|---|---|
| California | Most expedient time possible, no unreasonable delay | Yes, if 500+ CA residents | Name + specified data element | Substitute notice for 500,000+ affected; specific template for health data |
| New York | Most expedient time possible, no unreasonable delay | AG, DFS, DOCS simultaneously | Private information (name + data element) | SHIELD Act: 30-day AG notification for NY residents |
| Texas | 60 days from determination | AG if 250+ TX residents | Name + sensitive personal information | Expanded definition of sensitive data includes biometric identifiers |
| Florida | 30 days from determination | FDLE within 30 days if 500+ | Name + specified data element | One of the shortest statutory deadlines |
| Massachusetts | As soon as practicable | AG + OCABR simultaneously | Name + specified data element | Requires description of remedial services offered |
| Illinois | Most expedient time possible, no unreasonable delay | AG if 500+ IL residents | Name + specified data element | BIPA adds biometric data breach notification requirements |
| Virginia | 60 days from discovery | AG + affected individuals | Name + specified data element | VCDPA adds consumer data rights context |
| Colorado | 30 days from determination | AG within 30 days if 500+ | Name + specified data element | Among the shortest deadlines alongside Florida |
| Pennsylvania | Without unreasonable delay | AG if notifying | Name + specified data element | Broad definition of personal information |
| Washington | 30 days from discovery | AG within 30 days if 500+ | Name + specified data element | Biometric and health data included |
Other International Jurisdictions
| Jurisdiction | Law | SA Timeline | DS Timeline | Notable |
|---|---|---|---|---|
| United Kingdom | UK GDPR + DPA 2018 | 72 hours (ICO) | Without undue delay | Mirrors EU GDPR; ICO is sole SA |
| Canada | PIPEDA + provincial laws | "As soon as feasible" to OPC | "As soon as feasible" | Real risk of significant harm (RROSH) threshold |
| Australia | Privacy Act 1988 (NDB scheme) | 30 days to OAIC | As soon as practicable | "Eligible data breach" = serious harm likely |
| Brazil | LGPD | "Reasonable time" to ANPD | "Reasonable time" | ANPD defines timeframes by regulation |
| Japan | APPI | Promptly to PPC (3-5 days recommended) | Promptly | Mandatory for 1,000+ subjects or sensitive data |
| South Korea | PIPA | Within 72 hours to PIPC | Without delay | Mirrors GDPR timeline |
| Singapore | PDPA | 3 calendar days to PDPC | As soon as practicable | Significant harm or significant scale threshold |
Conflict Resolution Framework
Principle 1: Meet the Shortest Deadline First
When notification timelines conflict, always prepare to meet the shortest applicable deadline. This typically means:
- EU/UK GDPR 72-hour deadline drives the primary notification timeline.
- US state notifications are prepared in parallel and dispatched as soon as the statutory requirement is met.
- The 72-hour GDPR notification often satisfies the "without unreasonable delay" standard in most US states.
Principle 2: Superset Content Approach
Prepare a single core notification document containing the superset of all content requirements across jurisdictions, then adapt for jurisdiction-specific formatting:
| Content Element | GDPR Art. 33(3) | California CC §1798.82 | New York GBL §899-aa | Texas BCC §521.053 |
|---|---|---|---|---|
| Nature of breach | Required | Required | Required | Required |
| Data categories affected | Required | Required (specific elements) | Required | Required |
| Data subject count | Required (approximate) | Not required but recommended | Required | Required |
| DPO/contact details | Required | Contact details required | Contact details required | Contact details required |
| Likely consequences | Required | Not explicitly required | Not explicitly required | Not explicitly required |
| Measures taken | Required | Remedial actions required | Remedial actions required | Required |
| Credit monitoring offer | Not required (but common) | Required for SSN/financial | Recommended | Required for SSN |
| SA notification reference | Required | AG notification required | AG notification required | AG notification required |
Principle 3: Parallel Execution Tracks
Manage notifications through parallel workstreams:
Track 1: EU/UK GDPR (72-hour priority)
- Lead SA notification within 72 hours
- Phased notification under Art. 33(4) if investigation is ongoing
- Art. 34 data subject notification within 7 days of high-risk determination
Track 2: US State Notifications (varies by state)
- AG notifications for each state where affected residents reside
- Individual notifications per state-specific requirements
- Substitute notice where individual notification is not feasible
Track 3: Other International Jurisdictions
- OAIC notification (Australia) within 30 days
- OPC notification (Canada) as soon as feasible
- Other jurisdictions as applicable
Lead Supervisory Authority Determination
For Stellar Payments Group with main establishment in Berlin, Germany:
- Lead SA: Berliner Beauftragte für Datenschutz und Informationsfreiheit
- Concerned SAs: Any SA in an EU member state where affected data subjects reside
- One-stop-shop mechanism: The lead SA coordinates with concerned SAs under Art. 60
- Exception: If the breach relates solely to an establishment in another member state, or substantially affects data subjects only in that state, the local SA may be the competent authority under Art. 56(2)
Notification Coordination Checklist
Pre-Notification (Within 24 Hours of Awareness)
- Determine which jurisdictions are affected based on data subject residency analysis
- Map applicable notification laws for each jurisdiction
- Identify the shortest notification deadline and set as primary driver
- Assign jurisdiction-specific notification leads (EU: DPO; US: General Counsel; APAC: Regional Privacy Manager)
- Engage external counsel in each jurisdiction as needed
EU/UK Track (72-Hour Deadline)
- Identify lead SA and prepare notification form
- Complete Art. 33(3) content requirements
- Submit notification to lead SA within 72 hours
- If cross-border, inform lead SA that multiple member states are affected
- Prepare Art. 34 data subject notification in languages of affected member states
US Track (Varies by State)
- Determine affected residents per state using postal/billing addresses
- For each state with 500+ affected residents, prepare AG notification
- Draft individual notification letters per state content requirements
- Include credit monitoring offer where required (SSN/financial data states)
- Engage outside US counsel for state-specific compliance review
- Submit AG notifications per each state's required timeline
- Dispatch individual notifications per each state's required timeline
International Track
- Prepare OAIC notification (Australia) within 30 days
- Prepare OPC notification (Canada) "as soon as feasible"
- Assess other jurisdictions (Brazil, Japan, South Korea, Singapore) based on affected populations
- Engage local counsel for jurisdiction-specific requirements
Coordination with Law Enforcement
In some jurisdictions, law enforcement authorities may request a delay in data subject notification to avoid prejudicing a criminal investigation:
- EU: EDPB Guidelines 9/2022 acknowledge that law enforcement may request delay; the controller should document the request and comply while still notifying the SA within 72 hours.
- US: Many state laws explicitly permit delay at law enforcement request. The delay must be documented and notification must proceed promptly upon law enforcement clearance.
- Best practice: Always notify the supervisory authority/AG on time even if data subject notification is delayed at law enforcement request.
Conducting Post-Breach Remediation
Overview
Post-breach remediation transforms the findings from a breach investigation into concrete corrective actions that prevent recurrence and demonstrate accountability under GDPR Art. 5(2) and Art. 24. Effective remediation goes beyond fixing the immediate vulnerability — it addresses root causes, closes systemic control gaps, updates policies and training, enhances monitoring, and satisfies regulatory follow-up requirements.
Lessons Learned Framework
Step 1: Root Cause Remediation (Immediate — Within 30 Days)
Address the direct technical and procedural cause of the breach:
| Root Cause Category | Remediation Approach | Example (SPG-BREACH-2026-003) |
|---|---|---|
| Stale privileged account | Decommission account, implement lifecycle management | Revoked svc-migration-2024; deployed automated service account expiry (90-day review cycle) |
| Phishing vulnerability | Deploy phishing-resistant MFA, enhance email filtering | Migrated from push-based MFA to FIDO2/WebAuthn for all privileged accounts |
| Insufficient network segmentation | Implement micro-segmentation | Deployed database-tier isolation; access only via approved bastion host with session recording |
| Inadequate access review scope | Expand access review to include all account types | Added service accounts, API keys, and machine accounts to quarterly access certification |
Step 2: Control Gap Closure (Short-Term — Within 90 Days)
Identify and close broader security and privacy control gaps revealed by the breach:
- Detection gap: Was the breach detected by the organization's own controls, or was it reported externally? If detection was delayed, strengthen monitoring.
- Response gap: Were response procedures followed? Where did the team deviate from the plan? Update procedures based on actual experience.
- Communication gap: Were internal and external communications timely and accurate? Update communication templates and escalation matrices.
- Documentation gap: Were the Art. 33(5) documentation requirements met in real-time? Improve documentation tools and checklists.
- Vendor/processor gap: If a processor was involved, was the Art. 28 DPA adequate? Were processor security requirements sufficient? Update vendor risk assessment and DPA terms.
Step 3: Policy Updates (Medium-Term — Within 90 Days)
Review and update affected policies based on breach findings:
| Policy | Update Required | Owner | Deadline |
|---|---|---|---|
| Access Control Policy | Include service accounts in scope; define lifecycle management requirements | CISO | 15 April 2026 |
| Incident Response Plan | Update awareness definition; add holding statement template; revise escalation matrix | DPO + CISO | 30 April 2026 |
| Ransom Payment Policy | Document Board-approved position on ransom payments | General Counsel | 31 May 2026 |
| Vendor Risk Management | Add security assessment questionnaire updates based on processor breach lessons | Procurement + DPO | 30 June 2026 |
| Data Retention Policy | Verify that expired data was actually deleted per schedule (breach may have revealed retention failures) | DPO | 30 June 2026 |
Step 4: Training Modifications (Medium-Term — Within 90 Days)
Update training programs to address the human factors contributing to the breach:
| Training Module | Target Audience | Update | Delivery Method |
|---|---|---|---|
| Phishing awareness | All employees | Add scenario based on the actual phishing email that initiated SPG-BREACH-2026-003 (with identifying details removed) | Interactive simulation via KnowBe4 |
| MFA security | All employees with MFA | Add push-fatigue attack awareness; train on rejecting unexpected MFA prompts | Mandatory e-learning module |
| Incident reporting | All employees | Clarify that unusual system behavior must be reported immediately, even if uncertain | Updated in annual privacy awareness training |
| Breach response | Incident response team | Tabletop exercise based on this breach scenario | Semi-annual tabletop exercise |
| Privileged access management | IT operations, DBAs | Service account lifecycle management procedures | Department-specific workshop |
Step 5: Monitoring Enhancements (Medium-Term — Within 90 Days)
Strengthen detection and monitoring based on gaps the breach revealed:
| Enhancement | Description | Owner | Deadline |
|---|---|---|---|
| Service account anomaly detection | SIEM rule to alert when service accounts authenticate outside scheduled batch windows or from non-whitelisted IPs | SOC Lead | 15 April 2026 |
| MFA push-fatigue detection | Alert when an account receives more than 3 MFA push notifications in 5 minutes without successful authentication | SOC Lead | 30 April 2026 |
| Tor exit node blocking | Block authentication attempts from known Tor exit nodes for all production systems | Network Security | 15 April 2026 |
| Network flow baseline for database tier | Establish outbound data transfer baselines for database VLAN; alert on anomalies | SOC Lead | 31 May 2026 |
Step 6: Regulatory Follow-Up (Ongoing)
Manage ongoing obligations to supervisory authorities:
- Supplementary notifications: Provide any outstanding information committed to in the initial Art. 33 notification (e.g., exfiltration determination, final data subject count).
- Authority inquiries: Respond promptly and comprehensively to any follow-up questions from the supervisory authority.
- Remediation evidence: Be prepared to provide evidence of remediation actions to the authority upon request. Maintain a remediation tracker with completion dates and evidence references.
- Regulatory proceedings: If the authority initiates formal proceedings, coordinate response with external counsel.
- Annual DPO report: Include the breach and remediation status in the DPO's annual report to the Board and supervisory authority.
Remediation Tracking
Remediation Register Structure
| Field | Description |
|---|---|
| Action ID | Unique identifier (SPG-BREACH-2026-003-REM-001) |
| Breach reference | Link to the source breach |
| Description | What needs to be done |
| Root cause addressed | Which root cause or gap this action closes |
| Owner | Person responsible for completion |
| Priority | Critical / High / Medium / Low |
| Target date | Planned completion date |
| Actual completion date | When the action was verified as complete |
| Evidence | Documentation proving completion (screenshot, policy version, test report) |
| Verified by | Person who verified the action was effectively implemented |
Escalation for Overdue Actions
| Days Overdue | Escalation |
|---|---|
| 1-7 days | Reminder to action owner |
| 8-14 days | Escalation to action owner's manager |
| 15-30 days | Escalation to DPO and CISO |
| 30+ days | Escalation to CEO; inclusion in Board Audit Committee report |
Post-Breach Review Meeting
Agenda (Conducted 30 Days After Breach Closure)
- Breach summary: 5-minute recap of the incident.
- Root cause review: Confirm root cause analysis is accurate and complete.
- Remediation status: Review all remediation actions — completed, in progress, overdue.
- Effectiveness assessment: Have the implemented remediations been tested and proven effective?
- Residual risk: What risk remains after remediation? Is it within the organization's risk appetite?
- Lessons for next time: What would we do differently? What worked well?
- Documentation closure: Confirm all Art. 33(5) documentation is complete.
Demonstrating Accountability
Under GDPR Art. 5(2), the controller must demonstrate compliance. Post-breach remediation evidence serves this purpose:
- Before the breach: Risk assessments, security measures, training records, and policies demonstrate preventive efforts.
- During the breach: Incident response documentation, notification records, and communication logs demonstrate responsive handling.
- After the breach: Remediation tracker, updated policies, enhanced controls, and improved training demonstrate learning and improvement.
A supervisory authority reviewing the organization's breach response will assess not only whether the breach was handled correctly but whether the organization took meaningful steps to prevent recurrence.
Building Breach Response Team Playbook
Overview
A breach response team playbook is the operational manual that enables rapid, coordinated response when a personal data breach occurs. It pre-defines roles and responsibilities, escalation paths, communication templates, and external contact information so that the response team can act immediately without spending critical hours on logistics during an actual incident.
Team Structure — CSIRT + Privacy Integration
Core Response Team
| Role | Primary | Backup | Contact | Responsibility |
|---|---|---|---|---|
| Incident Commander (IC) | Thomas Brenner (CISO) | Marcus Weber (SOC Lead) | +49 30 7742 8100 / ic@stellarpayments.eu | Overall coordination, resource allocation, containment decisions |
| Data Protection Officer | Dr. Elena Vasquez | Anna Schmidt (Deputy DPO) | +49 30 7742 8001 / dpo@stellarpayments.eu | Notification decisions, risk assessment, regulatory liaison, data subject communication |
| Legal Counsel | Sarah Chen (General Counsel) | External: Dr. Klaus Fischer (Freshfields) | +49 30 7742 8200 / legal@stellarpayments.eu | Legal advice, privilege management, regulatory strategy, law enforcement coordination |
| IT Forensics Lead | Petra Hoffmann (IT Director) | External: Sarah Mitchell (Mandiant) | +49 30 7742 8300 / it-forensics@stellarpayments.eu | Evidence preservation, forensic investigation, scope determination, root cause analysis |
| Communications Lead | Martin Keller (Comms Director) | Lisa Braun (Senior Comms Manager) | +49 30 7742 8400 / comms@stellarpayments.eu | Media response, customer communication, internal communication, social media monitoring |
| Executive Sponsor | Marcus Lindqvist (CEO) | CFO: Dr. Andrea Hoffmann | +49 30 7742 8000 / ceo@stellarpayments.eu | Strategic decisions, board notification, public statements, regulatory engagement |
| Customer Relations | James Park (VP Customer Success) | Maria Santos (Customer Success Director) | +49 30 7742 5000 / customers@stellarpayments.eu | Customer inquiry management, B2B client communication, service status updates |
| HR Lead | Claudia Richter (CHRO) | Stefan Müller (HR Director) | +49 30 7742 7500 / hr-confidential@stellarpayments.eu | Employee communication, Works Council coordination, insider threat scenarios |
Extended Team (Activated as Needed)
| Role | Contact | Activation Trigger |
|---|---|---|
| Board Liaison | Board Secretary (Dr. Friedrich Weber) | Breach affecting 10,000+ data subjects or likely to result in high risk |
| Cyber Insurance | Allianz Claims: +49 89 3800 0 (ref: SPG-CYB-2025-001) | Any breach likely to exceed EUR 50,000 in response costs |
| External IR Firm | Mandiant: +1 703 935 1700 (retainer: SPG-IR-2025-007) | Any breach requiring forensic investigation beyond SOC capability |
| External Legal | Freshfields: +49 30 20 28 39 000 (ref: SPG-LEG-2025-012) | Breach involving regulatory risk, litigation risk, or cross-border notification |
| External Communications | Brunswick Group: +49 69 2400 5510 | Breach with media exposure or affecting 50,000+ individuals |
| Credit Monitoring Vendor | Experian Enterprise: +44 115 941 0888 (retainer: SPG-EXP-2025-003) | Breach involving financial data, government IDs, or health data |
Escalation Matrix
Severity Classification
| Severity | Criteria | Response Time | Escalation Level |
|---|---|---|---|
| SEV-1 (Critical) | 10,000+ data subjects; special category data (Art. 9); ongoing exfiltration; ransomware with encryption | Immediate (within 15 minutes) | IC + DPO + CEO + General Counsel |
| SEV-2 (High) | 1,000-10,000 data subjects; financial data; credentials; media exposure | Within 30 minutes | IC + DPO + General Counsel |
| SEV-3 (Medium) | 100-1,000 data subjects; non-sensitive personal data; contained breach | Within 2 hours | IC + DPO |
| SEV-4 (Low) | Under 100 data subjects; low-sensitivity data; contained with no exfiltration | Within 4 hours | SOC Lead + Privacy Coordinator |
Escalation Flow
SOC Analyst detects alert
↓
SOC Lead validates (within 15 min)
↓
Personal data involved? → No → Standard security incident process
↓ Yes
Classify severity (SEV-1 to SEV-4)
↓
SEV-1/2: Activate Incident Commander + DPO immediately
SEV-3: Notify IC + DPO within 2 hours
SEV-4: Notify Privacy Coordinator within 4 hours
↓
IC convenes Core Response Team
↓
72-hour Art. 33 clock determination
↓
Investigation → Risk Assessment → Notification Decision
Communication Templates
Template 1: Internal Breach Alert (Email to Core Response Team)
Subject: [SEV-X] PERSONAL DATA BREACH — Immediate Action Required
From: SOC / Incident Commander To: Core Response Team distribution list
A personal data breach has been identified requiring immediate response.
Incident Summary:
- Discovery time: [UTC timestamp]
- Affected system(s): [system names]
- Breach type: [Confidentiality / Integrity / Availability]
- Estimated data subjects: [count or range]
- Personal data categories: [list]
- Containment status: [Contained / Active / Unknown]
Immediate Actions Required:
- IC: Convene response team call at [time] on [bridge/Teams link]
- DPO: Begin risk assessment; determine 72-hour deadline
- IT Forensics: Preserve evidence on affected systems
- Legal: Review for privilege and law enforcement considerations
- Communications: Prepare holding statement; monitor media
Response Team Bridge: [Teams meeting link] Incident Channel: Signal group "SPG-IR-Active"
Template 2: Media Holding Statement
Stellar Payments Group is aware of a security incident affecting [some of our systems / our customer database]. We immediately activated our incident response procedures and are working with leading cybersecurity experts to investigate the matter. The protection of our customers' data is our highest priority. We will provide further information as our investigation progresses. For media inquiries, please contact press@stellarpayments.eu.
Template 3: Customer Service Talking Points
For customer-facing staff during an active breach:
If a customer asks about a security incident:
- "We are aware of a security issue and our team is actively working to resolve it."
- "The security of your information is our top priority."
- "We will communicate directly with any affected customers as soon as our investigation allows."
- "I can take your contact details and ensure you are notified if your account is affected."
Do NOT:
- Confirm or deny specific details of the breach
- Speculate on the number of affected customers
- Provide information not in the approved talking points
- Discuss the incident on social media
Template 4: Board Notification (Email to Board Chair)
Subject: Data Breach Notification to the Board — [Breach Reference]
Dear [Board Chair],
I am writing to inform you of a personal data breach that occurred on [date]. This notification is provided in accordance with our Board-approved Incident Escalation Policy.
Summary: [2-3 sentence description] Scale: [approximate data subjects and data categories] Status: [contained/under investigation] Regulatory notification: [filed/pending/not required] Financial exposure: [estimated response costs and potential regulatory penalties]
A full briefing will be provided at [scheduled time]. In the interim, [CEO name] is overseeing the organizational response.
Template 5: Employee Communication (All-Staff)
Subject: Important Update from [CEO] Regarding a Security Incident
Dear Colleagues,
I want to share an important update. On [date], we identified a security incident affecting [description]. Our security and privacy teams are working around the clock to investigate and resolve the situation.
What we know: [brief, factual description] What we are doing: [containment and investigation actions] What this means for you: [if employee data was involved, say so directly; if not, clarify] What we ask of you: Report any unusual system activity to security@stellarpayments.eu. Do not discuss this matter externally or on social media.
We will provide updates as we learn more. Thank you for your professionalism and support during this time.
[CEO Name]
Regulatory Authority Contact Directory
European Union
| Country | Authority | Breach Portal / Contact | Phone |
|---|---|---|---|
| Germany (Berlin) | Berliner BfDI | datenschutz-berlin.de | +49 30 13889 0 |
| Germany (Federal) | BfDI | bfdi.bund.de | +49 228 997799 0 |
| France | CNIL | notifications.cnil.fr/notifications | +33 1 53 73 22 22 |
| Ireland | DPC | forms.dataprotection.ie | +353 57 868 4800 |
| Netherlands | AP | autoriteitpersoonsgegevens.nl | +31 70 888 8500 |
| Spain | AEPD | sedeagpd.gob.es | +34 91 266 35 17 |
| Italy | Garante | protocollo@pec.gpdp.it | +39 06 696 77 1 |
| Belgium | APD/GBA | gegevensbeschermingsautoriteit.be | +32 2 274 48 00 |
| Austria | DSB | dsb.gv.at | +43 1 52 152 0 |
| Poland | UODO | uodo.gov.pl | +48 22 531 03 00 |
United Kingdom
| Authority | Portal | Phone |
|---|---|---|
| ICO | ico.org.uk/for-organisations/report-a-breach | +44 303 123 1113 |
United States
| Authority | Portal | Phone |
|---|---|---|
| HHS/OCR (HIPAA) | ocrportal.hhs.gov | +1 800 368 1019 |
| California AG | oag.ca.gov/privacy/databreach/reporting | +1 916 210 6276 |
| New York AG | ag.ny.gov/internet/filing-a-complaint | +1 800 771 7755 |
| FTC | ftc.gov/enforcement | +1 877 382 4357 |
Other International
| Jurisdiction | Authority | Contact |
|---|---|---|
| Canada | OPC | priv.gc.ca |
| Australia | OAIC | oaic.gov.au/privacy/notifiable-data-breaches |
| Brazil | ANPD | gov.br/anpd |
| Singapore | PDPC | pdpc.gov.sg |
Pre-Negotiated Vendor Contacts
| Service | Vendor | Contract Reference | Activation Contact | SLA |
|---|---|---|---|---|
| Incident Response | Mandiant | SPG-IR-2025-007 | +1 703 935 1700 / ir@mandiant.com | On-site within 24 hours, remote within 4 hours |
| External Legal (EU) | Freshfields Bruckhaus Deringer | SPG-LEG-2025-012 | +49 30 20 28 39 000 | Partner-level response within 2 hours |
| External Legal (US) | Covington & Burling | SPG-LEG-2025-013 | +1 202 662 6000 | Partner-level response within 2 hours |
| Credit Monitoring | Experian IdentityWorks | SPG-EXP-2025-003 | +44 115 941 0888 | Portal activation within 48 hours |
| Crisis Communications | Brunswick Group | SPG-COM-2025-001 | +49 69 2400 5510 | Team mobilized within 4 hours |
| Cyber Insurance | Allianz Cyber Enterprise | SPG-CYB-2025-001 | +49 89 3800 0 | Claims acknowledgment within 24 hours |
| eDiscovery / Legal Hold | Relativity / Exterro | SPG-LIT-2025-004 | +1 312 263 1333 | Legal hold activation within 4 hours |
Playbook Maintenance
| Activity | Frequency | Owner |
|---|---|---|
| Review and update contact information | Quarterly | DPO Office |
| Verify vendor retainer agreements are current | Annually | Procurement + DPO |
| Update regulatory authority contact details | Semi-annually | DPO Office |
| Tabletop exercise using playbook | Semi-annually | DPO + CISO |
| Full playbook revision | Annually or after any SEV-1/SEV-2 incident | DPO |
| Distribute updated playbook to Core Response Team | After every revision | DPO Office |
Conducting Breach Risk Assessment
Overview
When a personal data breach occurs, the controller must assess whether the breach is "likely to result in a risk to the rights and freedoms of natural persons" (Art. 33(1)) to determine whether supervisory authority notification is required, and whether it is "likely to result in a high risk" (Art. 34(1)) to determine whether data subject notification is required. This skill provides a structured, repeatable methodology based on EDPB Guidelines 9/2022 and Guidelines 01/2021.
Breach Type Classification (CIA Triad)
Every breach must first be classified according to the type of security compromise:
Confidentiality Breach
Unauthorized or accidental disclosure of, or access to, personal data.
| Scenario | Severity Indicator |
|---|---|
| Email containing 50 customer records sent to wrong internal department | Low — limited exposure, same organization |
| Database export of 200,000 records posted on public file-sharing service | Severe — mass exposure, publicly accessible |
| Employee accesses medical records of a colleague without authorization | Medium — limited scope but sensitive data |
| Backup tape containing unencrypted payroll data lost during transport | High — financial data, unknown accessor |
Integrity Breach
Unauthorized or accidental alteration of personal data.
| Scenario | Severity Indicator |
|---|---|
| Malware modifies patient medication dosages in a clinical database | Severe — potential physical harm |
| Software bug overwrites postal codes in 5,000 customer records | Low — non-sensitive field, reversible from backup |
| Unauthorized modification of employee performance review scores | Medium — potential employment consequences |
| SQL injection alters financial transaction records | High — financial integrity compromised |
Availability Breach
Accidental or unauthorized loss of access to, or destruction of, personal data.
| Scenario | Severity Indicator |
|---|---|
| Ransomware encrypts the HR system for 48 hours; clean backup restored | Medium — temporary unavailability, data recovered |
| Fire destroys the only copy of archived patient records | Severe — permanent loss, healthcare impact |
| DDoS attack renders the customer portal unavailable for 6 hours | Low — temporary, no data loss or compromise |
| Cryptographic key destruction makes encrypted dataset permanently unreadable | Severe — irreversible data loss |
Risk Assessment Methodology
Factor 1: Data Sensitivity (Weight: High)
| Score | Criteria | Examples |
|---|---|---|
| 1 — Low | Non-sensitive data already in the public domain or easily obtainable | Business contact details, publicly listed addresses |
| 2 — Medium | Personal data that could cause minor inconvenience if disclosed | Email addresses, phone numbers, purchase history |
| 3 — High | Sensitive personal data or data with significant impact potential | Financial account details, government ID numbers, employment records |
| 4 — Severe | Special category data (Art. 9), criminal conviction data (Art. 10), or data enabling significant harm | Health records, biometric data, genetic data, sexual orientation, political opinions |
Factor 2: Volume of Affected Data Subjects
| Score | Data Subject Count | Rationale |
|---|---|---|
| 1 | Fewer than 100 | Limited scale — individual assessment feasible |
| 2 | 100 to 1,000 | Moderate scale — structured response required |
| 3 | 1,000 to 100,000 | Large scale — significant organizational impact |
| 4 | More than 100,000 | Mass scale — potential for widespread societal impact |
Factor 3: Ease of Identification
| Score | Criteria |
|---|---|
| 1 | Data is pseudonymized or encrypted; re-identification requires additional data held separately and securely |
| 2 | Data contains indirect identifiers only; re-identification possible with moderate effort |
| 3 | Data contains direct identifiers (name + one other element); individuals readily identifiable |
| 4 | Data contains multiple direct identifiers, photographs, or biometric data; immediate identification possible |
Factor 4: Consequence Severity
| Score | Potential Consequences |
|---|---|
| 1 | Minor inconvenience — e.g., receiving unsolicited marketing, needing to change a password |
| 2 | Moderate impact — e.g., targeted phishing risk, minor financial exposure, reputational inconvenience |
| 3 | Significant impact — e.g., identity theft risk, substantial financial loss, employment consequences, discrimination risk |
| 4 | Severe impact — e.g., physical safety threat, significant financial fraud, denial of essential services, threat to life |
Factor 5: Individual Characteristics
| Score | Criteria |
|---|---|
| 1 | General adult population with no heightened vulnerability |
| 2 | Population includes some individuals in dependent relationships (employees, tenants) |
| 3 | Population includes elderly, financially vulnerable, or individuals in unequal power dynamics |
| 4 | Population includes minors, patients, asylum seekers, or individuals whose safety depends on data confidentiality |
Factor 6: Controller-Specific Factors
| Score | Criteria |
|---|---|
| 1 | Controller processes personal data as an ancillary activity (e.g., office administration) |
| 2 | Controller processes personal data as a core activity for service delivery |
| 3 | Controller is in a position of trust (financial institution, healthcare provider, education) |
| 4 | Controller processes data at scale as a core business (data broker, payment processor, social media platform) |
Scoring Matrix and Thresholds
| Aggregate Score | Risk Level | Art. 33 SA Notification | Art. 34 DS Notification | Required Action |
|---|---|---|---|---|
| 6-8 | Unlikely to result in risk | Not required | Not required | Document in Art. 33(5) breach register only |
| 9-12 | Risk present but below high threshold | Required within 72 hours | Not required | Notify supervisory authority; document fully |
| 13-18 | Likely to result in risk, approaching high | Required within 72 hours | Recommended | Notify SA; strongly consider DS notification |
| 19-24 | Likely to result in high risk | Required within 72 hours | Required without undue delay | Notify both SA and data subjects |
EDPB Breach Scenario Analysis (Guidelines 01/2021)
Scenario 1: Ransomware with Backup Available
- Facts: Hospital hit by ransomware. Patient data encrypted. Clean backup restored within 24 hours. No evidence of exfiltration.
- Classification: Availability breach.
- Risk assessment: Data sensitivity = 4 (health data), Volume = 3 (2,500 patients), Identifiability = 4, Consequences = 3 (delayed treatment), Vulnerable = 4 (patients), Controller = 3 (healthcare). Total = 21.
- EDPB conclusion: Notify SA and data subjects. Even though backup was available, the temporary unavailability of health data during the 24-hour restoration window posed high risk to patient safety.
Scenario 2: Ransomware Without Backup
- Facts: Small manufacturing company hit by ransomware. Employee payroll data permanently lost. No backup exists.
- Classification: Availability breach (permanent).
- Risk assessment: Data sensitivity = 3, Volume = 1 (45 employees), Identifiability = 4, Consequences = 3, Vulnerable = 2, Controller = 2. Total = 15.
- EDPB conclusion: Notify SA and data subjects. Permanent loss of payroll data directly impacts employees' financial interests.
Scenario 3: Data Exfiltration from Website
- Facts: SQL injection attack extracts usernames, hashed passwords, and email addresses of 1.2 million registered users from an e-commerce platform.
- Classification: Confidentiality breach.
- Risk assessment: Data sensitivity = 2, Volume = 4, Identifiability = 3, Consequences = 2, Vulnerable = 1, Controller = 3. Total = 15.
- EDPB conclusion: Notify SA and data subjects. The combination of email addresses with hashed passwords enables credential-stuffing attacks against other services.
Scenario 4: Misdirected Email (Single Recipient)
- Facts: HR department sends a single employee's salary slip to the wrong internal colleague by email. Error discovered within 10 minutes. Recipient confirms deletion.
- Classification: Confidentiality breach.
- Risk assessment: Data sensitivity = 3, Volume = 1, Identifiability = 4, Consequences = 1, Vulnerable = 2, Controller = 1. Total = 12.
- EDPB conclusion: Notify SA (marginal). No DS notification required. The breach is contained, the recipient is known and cooperative, and financial data exposure is limited.
Scenario 5: Lost Unencrypted USB Drive
- Facts: Employee loses an unencrypted USB drive containing names, addresses, and national insurance numbers of 3,500 pension scheme members.
- Classification: Confidentiality breach.
- Risk assessment: Data sensitivity = 3, Volume = 3, Identifiability = 4, Consequences = 3, Vulnerable = 3 (elderly/retirees), Controller = 3. Total = 19.
- EDPB conclusion: Notify SA and data subjects. Government identifiers combined with vulnerable population (retirees) creates high identity theft risk.
Scenario 6: Accidental Publication of Student Grades
- Facts: University accidentally publishes exam results with student names on a publicly accessible web page for 36 hours before removal.
- Classification: Confidentiality breach.
- Risk assessment: Data sensitivity = 2, Volume = 2 (800 students), Identifiability = 4, Consequences = 2, Vulnerable = 2, Controller = 3 (education). Total = 15.
- EDPB conclusion: Notify SA and data subjects. Academic performance data linked to names, public exposure for 36 hours, potential impact on students' academic and professional prospects.
Assessment Documentation Requirements
Every breach risk assessment must be documented with the following elements:
- Assessment metadata: Date, assessor name, breach reference number, version
- Breach description: Factual summary of what occurred
- CIA classification: Which type(s) of breach
- Factor-by-factor scoring: Each factor scored with written justification
- Aggregate score and threshold determination: Which notification obligations apply
- DPO recommendation: DPO's concurrence or dissent with the assessment
- Management decision: Final notification decision with sign-off
- Re-assessment trigger: Conditions that would require re-scoring (e.g., exfiltration later confirmed)
Common Assessment Errors
- Underscoring consequences because exfiltration is "unconfirmed": The absence of evidence of exfiltration is not evidence of absence. Score consequences based on what could happen if the data is in unauthorized hands.
- Treating encrypted data as automatically low-risk: Encryption is only mitigating if the encryption keys were not also compromised and the encryption standard is robust (AES-256 or equivalent).
- Aggregating multiple small breaches: Recurrent similar breaches (e.g., repeated misdirected emails) may indicate a systemic issue that elevates the aggregate risk beyond what each individual incident would suggest.
- Ignoring availability breaches: Temporary loss of access to health records, financial data, or safety-critical information can cause harm even if confidentiality is not compromised.
- Applying the 250-employee exemption to notification: Art. 30(5) provides a limited RoPA exemption for small organizations, but there is no such exemption for Art. 33/34 breach notification obligations.
Designing Breach Simulation Exercise
Overview
Breach simulation exercises (tabletop exercises) test an organization's ability to detect, respond to, and recover from a personal data breach without the consequences of an actual incident. A well-designed exercise validates the breach response plan, identifies gaps in procedures, communication, and decision-making, and builds institutional muscle memory. This skill covers the end-to-end design process from scenario creation through after-action reporting.
Exercise Design Framework
Exercise Types
| Type | Duration | Participants | Complexity | Purpose |
|---|---|---|---|---|
| Tabletop (discussion-based) | 2-4 hours | 8-15 senior stakeholders | Medium | Test decision-making, communication, and policy application |
| Functional exercise | 4-8 hours | 15-30 cross-functional team members | High | Test operational procedures and tool usage |
| Full-scale simulation | 1-3 days | Organization-wide (50+ participants) | Very high | Test end-to-end response including technical, legal, communications, and executive functions |
Recommended Exercise Cadence
| Exercise Type | Frequency | Audience |
|---|---|---|
| Tabletop | Semi-annually | Executive team, DPO, legal, communications, CISO |
| Functional | Annually | SOC, privacy team, IT operations, HR, customer service |
| Full-scale | Every 2 years | Organization-wide |
Scenario Design
Scenario 1: Ransomware Attack on Customer Database
Complexity: High Duration: 3 hours Primary objectives: Test Art. 33 72-hour notification decision-making, executive communication, and vendor coordination.
Background briefing (distributed 24 hours before exercise): Stellar Payments Group processes payment transactions for 15,230 account holders across 18 EU member states and 12 US states. The production customer database is hosted on a PostgreSQL cluster in AWS eu-west-1. The DPO is Dr. Elena Vasquez. The CISO is Thomas Brenner. Mandiant is the retained incident response firm.
Inject timeline:
| Time | Inject | Expected Action |
|---|---|---|
| T+0 min | SOC alert: CrowdStrike detects rapid file encryption on db-prod-eu-west-01. 500+ file renames per second. Known ransomware indicators (LockBit 3.0). | SOC initiates incident response. Incident Commander activated. |
| T+15 min | Update: Encryption spreading to db-prod-eu-west-02 and 03. Customer portal returning database errors. Customer complaints arriving via support channels. | Decision point: Isolate database cluster? Accept service disruption vs. further damage? |
| T+30 min | Forensic initial finding: Attack vector appears to be compromised service account (svc-migration-2024). Account authenticated from Tor exit node 3 days prior. | Update risk assessment. Determine scope of potentially compromised data. |
| T+60 min | Customer database confirmed encrypted. 48,720 records across 15,230 data subjects. Backup from 12 hours ago available and verified clean. | Decision point: Restore from backup? Art. 33 notification clock — when did we "become aware"? |
| T+90 min | Ransom note found: 50 BTC demanded. Threat to publish data on dark web if not paid within 48 hours. Media outlet (Handelsblatt) calls communications team for comment. | Decision points: Pay ransom? Engage law enforcement? Media statement? |
| T+120 min | Mandiant confirms no evidence of exfiltration but cannot rule it out. Backup restoration is 60% complete. Berliner BfDI opens office in 2 hours. | Decision point: File Art. 33 notification now or wait for more information? Prepare Art. 34 data subject notification? |
| T+150 min | Second media outlet (Bloomberg) publishes story. Social media discussion begins. 50+ customer support calls in past hour. Three enterprise clients demand written assurance. | Communications crisis management. Customer and B2B stakeholder communication. |
| T+180 min | Exercise conclusion. Facilitator reveals exercise end state and leads debrief discussion. | After-action discussion. |
Scenario 2: Insider Threat — Employee Data Exfiltration
Complexity: Medium Duration: 2.5 hours
Inject timeline:
| Time | Inject | Expected Action |
|---|---|---|
| T+0 min | DLP alert: HR database export (3,400 employee records) copied to personal OneDrive by departing employee (last day is Friday). | Validate alert. Determine whether personal data is involved. |
| T+20 min | Records include names, home addresses, salaries, bank details, and national ID numbers. Employee's manager confirms the employee submitted resignation 2 weeks ago. | Decision point: Confront employee? Preserve evidence? Involve legal? |
| T+45 min | IT confirms the file was synced to the employee's personal laptop. The employee is currently in the office. | Decision points: Device seizure? HR involvement? Works Council (Betriebsrat) notification? |
| T+75 min | Legal advises on employee rights under German labor law. Works Council representative requests consultation before any confrontation. | Balance breach response urgency against employee rights and Works Council obligations. |
| T+105 min | Employee is interviewed with Works Council representative present. Claims data was for "reference purposes." Refuses to allow personal laptop examination. | Decision point: Law enforcement referral? Court order for device examination? Art. 33 notification? |
| T+135 min | DPO completes risk assessment: 3,400 employees, government IDs + financial data = high risk. Art. 33 and Art. 34 notification recommended. | Notification preparation. Employee communication planning (how to tell 3,400 employees their data was compromised by a colleague). |
| T+150 min | Exercise conclusion and debrief. | After-action discussion. |
Scenario 3: Third-Party Processor Breach
Complexity: Medium Duration: 2 hours
Inject timeline:
| Time | Inject | Expected Action |
|---|---|---|
| T+0 min | Email from cloud payroll processor (PayrollCloud GmbH): "We are writing to inform you of a security incident affecting customer data hosted on our platform." No details provided. | Contact processor for details. Review Art. 28 DPA for incident notification obligations. |
| T+20 min | Processor confirms: SQL injection attack. Unclear which clients affected. Estimated timeline for client-specific impact assessment: 5-7 days. | Decision point: Can we wait 5-7 days? How does this affect our 72-hour clock? |
| T+45 min | Processor provides partial information: "Your organization's data was on the affected server, but we cannot confirm whether it was accessed." 3,400 employee payroll records potentially exposed. | Assess when the controller "became aware" for Art. 33 purposes. Begin parallel risk assessment. |
| T+75 min | Media reports the processor breach. Several of the processor's other clients have publicly acknowledged being affected. | Decision point: Proactive disclosure? Wait for confirmed impact? |
| T+105 min | Processor confirms: Stellar Payments Group data was accessed. 3,400 employee records including names, salaries, bank account numbers, and tax IDs. | Art. 33 notification preparation. Employee communication planning. Processor accountability assessment. |
| T+120 min | Exercise conclusion and debrief. | After-action discussion. |
Participant Roles
| Role | Participant | Responsibilities During Exercise |
|---|---|---|
| Incident Commander | CISO (Thomas Brenner) | Overall incident coordination, resource allocation, containment decisions |
| Privacy Lead | DPO (Dr. Elena Vasquez) | Notification decisions, risk assessment, data subject communication |
| Legal Counsel | General Counsel (Sarah Chen) | Legal advice, privilege management, law enforcement coordination, regulatory strategy |
| Communications Lead | Communications Director (Martin Keller) | Media response, customer communication, internal communication |
| IT Operations | IT Director (Petra Hoffmann) | Technical containment, backup restoration, system recovery |
| Executive Sponsor | CEO (Marcus Lindqvist) | Strategic decisions, board notification, public statements |
| Customer Relations | VP Customer Success (James Park) | Customer communication, B2B client management |
| HR Lead | CHRO (Claudia Richter) | Employee communication, Works Council coordination (insider threat scenarios) |
| Exercise Facilitator | External consultant or internal audit | Scenario delivery, inject timing, discussion facilitation, observation |
| Observer/Recorder | DPO office analyst | Document decisions, actions, timelines, and gaps for after-action report |
Decision Points to Evaluate
- Breach awareness determination: When exactly did the controller "become aware" for Art. 33 clock purposes?
- Containment vs. evidence preservation: Did the team balance immediate containment with the need to preserve forensic evidence?
- Notification timing: Was the 72-hour deadline tracked and met?
- Risk assessment quality: Was the risk assessment methodology applied consistently and documented?
- Communication coordination: Were media, customer, and internal communications coordinated and consistent?
- Escalation effectiveness: Were the right people involved at the right time?
- Cross-functional coordination: Did legal, privacy, IT, and communications work together effectively?
- Regulatory coordination: Was the correct supervisory authority identified and notification prepared?
- Data subject communication: Was Art. 34 notification considered at the appropriate threshold?
- Documentation: Was the decision-making process documented in real-time?
After-Action Report Structure
Section 1: Exercise Summary
- Exercise date, duration, scenario, and participants.
- Exercise objectives and whether they were met.
Section 2: Timeline Analysis
- Actual timeline of decisions and actions during the exercise.
- Comparison against expected/ideal timeline from the breach response plan.
- Identification of delays and bottlenecks.
Section 3: Findings
- What worked well (strengths to maintain).
- What needs improvement (gaps and deficiencies).
- Severity rating for each finding: Critical, Major, Minor, Observation.
Section 4: Recommendations
- Specific, actionable remediation recommendations with owners and deadlines.
- Prioritized by severity.
Section 5: Metrics
- Time from detection to containment decision.
- Time from awareness to DPO notification.
- Time from awareness to notification preparation completion.
- Communication consistency score (number of conflicting messages identified).
- Decision quality score (percentage of decisions aligned with policy and regulation).
Managing Data Subject Breach Communication
Overview
Article 34 of the GDPR requires controllers to communicate a personal data breach to affected data subjects "without undue delay" when the breach is "likely to result in a high risk to the rights and freedoms of natural persons." This obligation is separate from and additional to the Art. 33 supervisory authority notification. The communication must be in clear and plain language, directly accessible to the affected individuals, and must contain specific information prescribed by Art. 34(2).
High Risk Threshold — When Art. 34 Applies
Art. 34 notification is triggered when the breach risk assessment yields a "high risk" determination. Per EDPB Guidelines 9/2022, Section 3.2, high risk is present when:
- The breach involves special category data (Art. 9) or criminal conviction data (Art. 10) in combination with direct identifiers.
- The breach enables identity theft — the compromised data includes government identifiers (national ID, tax ID, social security number) combined with other identifying information.
- The breach involves financial data (bank account numbers, payment card details) that could be used to commit fraud.
- The breach involves data of vulnerable individuals (minors, patients, employees in dependent relationships) where the consequences are amplified.
- The breach involves a large volume of personal data (more than 1,000 individuals) with direct identifiers, even if the data is not special category.
- The breach could lead to physical harm, discrimination, or threat to the life or safety of individuals.
Required Content — Art. 34(2)
The data subject communication must contain, at minimum, the information specified in Art. 33(3)(b), (c), and (d):
(b) DPO or Contact Point Details
- Name and contact details of the DPO or other designated contact point where data subjects can obtain further information.
- At Stellar Payments Group: Dr. Elena Vasquez, dpo@stellarpayments.eu, +49 30 7742 8001.
- A dedicated breach response hotline should be established for breaches affecting more than 1,000 individuals.
(c) Likely Consequences
- Description of the likely consequences of the breach written in plain language that a non-technical data subject can understand.
- Avoid legal jargon and technical terminology.
- Be specific about what could happen: "Your name, email address, and partial payment card number were exposed. This means someone could attempt to use this information to send you convincing phishing emails or attempt fraudulent transactions."
(d) Measures Taken or Proposed
- What the controller has done to address the breach.
- What the controller is doing to mitigate adverse effects.
- What the data subject can do to protect themselves (specific, actionable steps).
Additional Required Element: Nature of the Breach
- Although Art. 34(2) references only (b), (c), and (d) of Art. 33(3), the introductory text of Art. 34(1) requires the controller to "communicate the personal data breach to the data subject." This inherently requires describing the nature of the breach.
Exemptions Under Art. 34(3)
A controller may be exempt from direct data subject notification in three circumstances:
(a) Technical Protection Measures
The controller has applied appropriate technical and organisational protection measures that render the personal data unintelligible to any person who is not authorized to access it, such as encryption.
Requirements for this exemption:
- The encryption must be state-of-the-art (AES-256 or equivalent).
- The encryption keys must not have been compromised in the same breach.
- The encryption must have been applied to all affected data, not just a subset.
- The controller must be able to demonstrate that the encryption was in place before the breach occurred.
(b) Subsequent Measures
The controller has taken subsequent measures which ensure that the high risk to the rights and freedoms of data subjects is no longer likely to materialise.
Requirements for this exemption:
- The measures must definitively eliminate the risk, not merely reduce it.
- The controller must have high confidence that the data has not been accessed or used by unauthorized persons.
- The window of exposure must have been very brief.
(c) Disproportionate Effort
Individual notification would involve disproportionate effort, in which case a public communication or similar measure shall be made instead.
Requirements for this exemption:
- The controller must demonstrate why individual notification is disproportionate (e.g., outdated contact details for a large proportion of affected individuals).
- The public communication must be equally effective in reaching affected individuals.
- Channels: prominent website banner, national newspaper advertisements, coordinated social media announcements, broadcast media notification.
Communication Channels and Timing
Preferred Channels (in order of priority)
- Direct email to the email address on file — fastest and most verifiable delivery.
- Postal letter to the physical address on file — required fallback when email is unavailable or unreliable.
- SMS notification with link to detailed information — supplementary channel for time-sensitive breaches.
- In-app notification — for breaches affecting users of mobile or web applications.
- Public communication — only when Art. 34(3)(c) disproportionate effort exemption applies.
Timing Requirements
- "Without undue delay" under Art. 34(1) means as quickly as possible.
- EDPB guidance suggests data subject notification should occur within days, not weeks, of the breach determination.
- Stellar Payments Group internal standard: data subject notifications dispatched within 7 calendar days of the risk assessment confirming high risk.
Language and Accessibility Requirements
- Clear and plain language: Art. 34(2) explicitly requires the communication to describe the breach "in clear and plain language." Avoid legal terminology, technical jargon, and acronyms.
- Language of the data subject: Notifications must be in the language in which the controller normally communicates with the data subject. For a controller operating across Europe, this means multilingual notifications.
- Accessibility: Notifications must be accessible to individuals with disabilities (WCAG 2.1 AA compliance for digital channels; large print or audio alternatives for postal communications upon request).
- Separate communication: The breach notification should not be bundled with marketing communications, invoices, or other routine correspondence. It must be clearly identifiable as a data breach notification.
Scenario-Specific Communication Templates
Scenario 1: Financial Data Breach — Payment Card Compromise
Subject: Important Security Notice — Your Payment Information May Have Been Affected
Dear [Data Subject Name],
We are writing to inform you of a security incident that may have affected your personal and payment information held by Stellar Payments Group.
What happened: On 13 March 2026, we detected unauthorized access to our payment processing database. Our investigation determined that an external attacker gained access to a subset of customer payment records between 10 March and 13 March 2026.
What information was involved: Your name, email address, billing address, and payment card details (card number, expiry date, and CVV) associated with your Stellar Payments account were among the records accessed.
What we are doing:
- We immediately isolated the affected system and engaged Mandiant, a leading cybersecurity firm, to conduct a full forensic investigation.
- We have notified the relevant payment card networks (Visa and Mastercard) and they are monitoring for fraudulent activity on affected card numbers.
- We have reported this incident to the Berliner Beauftragte für Datenschutz und Informationsfreiheit as required by law.
What you can do:
- Contact your bank or card issuer immediately and request a replacement card. Do not wait for signs of fraud.
- Review your bank and card statements for any transactions you do not recognize.
- Be cautious of unsolicited emails, calls, or texts claiming to be from Stellar Payments or your bank — we will never ask for your password or full card number.
- Consider placing a fraud alert with a credit reference agency (SCHUFA in Germany, Experian/Equifax in other jurisdictions).
Free credit monitoring: We are offering all affected customers 12 months of complimentary credit monitoring through Experian IdentityWorks. To enroll, visit stellarpayments.eu/breach-support and use activation code SPG-2026-PROTECT. Enrollment is available until 30 June 2026.
Contact us: If you have questions, our dedicated breach response team is available at:
- Email: breach-support@stellarpayments.eu
- Phone: +49 30 7742 9000 (Monday-Friday, 08:00-20:00 CET; Saturday 09:00-17:00 CET)
- Post: Stellar Payments Group, Data Breach Response Team, Friedrichstraße 191, 10117 Berlin, Germany
Our Data Protection Officer, Dr. Elena Vasquez, can be reached at dpo@stellarpayments.eu or +49 30 7742 8001.
We sincerely regret this incident and are committed to preventing any recurrence.
Regards, Marcus Lindqvist Chief Executive Officer Stellar Payments Group
Scenario 2: Health Data Breach — Unauthorized Access to Medical Records
Subject: Important Notice Regarding Your Health Information
Dear [Data Subject Name],
We are contacting you to inform you of a security incident involving your health information held by Stellar Payments Group's employee wellness programme.
What happened: On 5 March 2026, we discovered that an employee in our IT department accessed the occupational health database without authorization between 1 February and 4 March 2026. This database contains health screening results and sick leave records for employees enrolled in our wellness programme.
What information was involved: Your name, employee number, date of birth, health screening results (including blood pressure, cholesterol, and BMI readings), and sick leave history for 2025-2026.
What we are doing:
- The employee responsible has been suspended pending a disciplinary investigation. Their system access has been revoked.
- We have implemented additional access controls on the occupational health database, including role-based access with multi-factor authentication.
- An audit of all database access logs for the past 12 months has been completed.
- We have notified the Berliner Beauftragte für Datenschutz und Informationsfreiheit.
What you can do:
- If you have concerns about how your health information may be used, contact our DPO for advice.
- You have the right to request a copy of the access logs relating to your health records under your right of access (Art. 15 GDPR).
- If you experience any adverse consequences that you believe are related to this incident, please contact us immediately.
Counselling support: We have arranged confidential counselling support through our Employee Assistance Programme (EAP) provider, Workplace Options, available 24/7 at +49 800 100 0287 (reference: SPG-Health-2026).
Contact us:
- DPO: Dr. Elena Vasquez, dpo@stellarpayments.eu, +49 30 7742 8001
- HR Confidential Line: hr-confidential@stellarpayments.eu, +49 30 7742 7500
Regards, Dr. Elena Vasquez Data Protection Officer Stellar Payments Group
Scenario 3: Credential Breach — Username and Password Exposure
Subject: Action Required — Your Stellar Payments Account Credentials May Be Compromised
Dear [Data Subject Name],
We are writing to inform you that your Stellar Payments account login credentials may have been exposed in a security incident.
What happened: On 20 March 2026, our security monitoring systems detected that a database backup file containing customer account credentials was inadvertently stored on an unsecured cloud storage instance between 15 March and 20 March 2026.
What information was involved: Your email address, username, and hashed password for your Stellar Payments account. While passwords were stored in a hashed format (bcrypt with a cost factor of 12), we are treating this as a high-risk breach because sophisticated attackers may attempt to reverse the hashes.
What we are doing:
- We have secured the cloud storage instance and deleted the exposed backup file.
- All affected account passwords have been force-reset as a precaution.
- We are implementing automated scanning to prevent sensitive data from being stored in unsecured cloud environments.
What you must do immediately:
- You will be prompted to create a new password when you next log in to stellarpayments.eu. Choose a strong, unique password that you do not use for any other service.
- Enable two-factor authentication (2FA) on your account by going to Settings > Security > Enable 2FA.
- If you used the same password on any other website or service, change those passwords immediately.
- Be alert for phishing emails that may reference this incident and attempt to trick you into providing information.
Contact us:
- Email: breach-support@stellarpayments.eu
- Phone: +49 30 7742 9000
- DPO: Dr. Elena Vasquez, dpo@stellarpayments.eu, +49 30 7742 8001
Regards, Thomas Brenner Chief Information Security Officer Stellar Payments Group
Scenario 4: Ransomware — Temporary Data Unavailability
Subject: Service Disruption Notice — Your Data Was Temporarily Unavailable
Dear [Data Subject Name],
We are writing to inform you of a security incident that temporarily affected access to your account data.
What happened: On 13 March 2026, Stellar Payments Group experienced a ransomware attack that encrypted portions of our customer database. This made your account data temporarily unavailable for approximately 36 hours while we restored systems from secure backups.
What information was affected: Your account data (name, contact details, transaction history, and account balance) was rendered inaccessible during the incident. Our forensic investigation has confirmed that no data was exfiltrated (copied or stolen) during the attack. The data was encrypted in place and has been fully restored.
What we are doing:
- We restored all affected data from verified clean backups taken before the attack.
- We have engaged Mandiant to conduct a comprehensive forensic investigation.
- We are implementing enhanced network segmentation and endpoint protection.
- We have reported this incident to the supervisory authority.
What you should do:
- Verify that your recent transactions and account balance are correct by logging into your account at stellarpayments.eu.
- If you notice any discrepancies, contact our support team immediately.
- As a precaution, we recommend changing your account password.
Contact us:
- Customer Support: support@stellarpayments.eu, +49 30 7742 5000
- DPO: Dr. Elena Vasquez, dpo@stellarpayments.eu, +49 30 7742 8001
Regards, Marcus Lindqvist Chief Executive Officer Stellar Payments Group
Scenario 5: Insider Threat — Employee Data Exfiltration
Subject: Important Notice Regarding Your Employment Records
Dear [Data Subject Name],
We are writing to inform you of a security incident involving your employment records held by Stellar Payments Group.
What happened: On 1 March 2026, our data loss prevention system detected that a departing employee in the People Operations department transferred a file containing employee records to a personal cloud storage account on 27 February 2026. We immediately launched an investigation and recovered the data.
What information was involved: Your name, employee number, home address, personal email address, date of birth, salary information, bank account details for payroll, and national insurance/social security number.
What we are doing:
- We obtained a court order requiring the former employee to delete all copies of the data and provide a sworn declaration of deletion.
- Forensic examination of the former employee's personal devices confirmed deletion of all copies.
- We have implemented enhanced DLP controls preventing bulk export of employee records.
- We have added behavioral analytics monitoring for all users with access to HR systems.
- We have reported this incident to the Berliner Beauftragte für Datenschutz und Informationsfreiheit and notified law enforcement (Landeskriminalamt Berlin, case reference LKA-2026-04872).
What you can do:
- Monitor your bank account for any unauthorized transactions.
- Consider placing a SCHUFA fraud alert by contacting SCHUFA at +49 611 9278 0 or visiting meineschufa.de.
- Be cautious of unsolicited contact from recruiters or other organizations that reference specific details of your employment at Stellar Payments.
- Report any suspicious activity to our security team at security@stellarpayments.eu.
Free identity protection: We are providing all affected employees with 24 months of complimentary identity theft protection through Experian IdentityWorks, including dark web monitoring, credit monitoring, and EUR 25,000 identity theft insurance. Enrollment details are available on the HR portal under Benefits > Breach Support, or contact hr-confidential@stellarpayments.eu.
Contact us:
- HR Confidential: hr-confidential@stellarpayments.eu, +49 30 7742 7500
- DPO: Dr. Elena Vasquez, dpo@stellarpayments.eu, +49 30 7742 8001
- Employee Assistance Programme: +49 800 100 0287 (24/7)
Regards, Dr. Elena Vasquez Data Protection Officer Stellar Payments Group
Executing California Breach Notification
Overview
California was the first US state to enact a data breach notification law (SB 1386, 2003). Cal. Civ. Code §1798.82 requires any person, business, or state agency that owns or licenses computerized data containing personal information to notify California residents when unencrypted personal information has been (or is reasonably believed to have been) acquired by an unauthorized person. The California Attorney General must be notified when more than 500 California residents are affected.
Covered Data Elements — Cal. Civ. Code §1798.81.5(d)
A breach notification is triggered when an individual's first name or first initial and last name is combined with any of the following unencrypted or unredacted data elements:
| Data Element | Category |
|---|---|
| Social Security number | Government identifier |
| Driver's license number or California identification card number | Government identifier |
| Financial account number, credit card number, or debit card number, in combination with any required security code, access code, or password | Financial |
| Medical information | Health |
| Health insurance information | Health |
| Unique biometric data (fingerprint, retina, iris image, or other unique physical representation or digital representation used for authentication) | Biometric |
| Information or data collected through automated license plate recognition systems | Surveillance |
| Genetic data | Genetic |
| A username or email address, in combination with a password or security question and answer that would permit access to an online account | Credentials |
| Tax identification number | Government identifier |
Note: "Personal information" does not include publicly available information that is lawfully made available to the general public from federal, state, or local government records.
Notification Timing — "Most Expedient Time Possible"
Cal. Civ. Code §1798.82(a): Notification must be made "in the most expedient time possible and without unreasonable delay."
What Constitutes "Unreasonable Delay"
- The statute does not define a specific number of days.
- California AG guidance interprets this as requiring notification as soon as the investigation has progressed sufficiently to determine that notification is required.
- Investigation and law enforcement coordination are recognized legitimate reasons for delay.
- Internal approval processes and desire to prepare PR responses are NOT legitimate reasons for delay.
Law Enforcement Delay — §1798.82(c)
Notification may be delayed if a law enforcement agency determines that notification would impede a criminal investigation. The notification must be made "promptly" after the law enforcement agency determines notification will not compromise the investigation.
AG Notification — §1798.82(f)
| Requirement | Detail |
|---|---|
| Threshold | 500 or more California residents affected |
| Method | Electronic submission to the California AG's office (oag.ca.gov/privacy/databreach/reporting) |
| Content | Sample copy of the individual notification letter |
| Timing | Concurrent with or before individual notification |
Individual Notification Content Requirements — §1798.82(d)
The notification must include:
- Name and contact information of the notifying entity.
- List of the types of personal information that were or are reasonably believed to have been the subject of the breach.
- Date of the breach (if known) and the date of the notice.
- Whether notification was delayed as a result of a law enforcement investigation (if applicable).
- General description of the breach incident, if that information is possible to determine at the time of notice.
- Toll-free telephone numbers, addresses, and websites for the major credit reporting agencies (if the breach involved a Social Security number, driver's license number, or California identification card number).
- Statement about availability of a security freeze (if SSN is involved): information about the right to place a security freeze on credit files under Cal. Civ. Code §1785.11.2.
Format Requirements — §1798.82(d)
California has specific formatting requirements for breach notification letters:
- Title: "Notice of Data Breach" — must be prominently displayed.
- Headings: Must use the following headings (or substantially similar):
- "What Happened"
- "What Information Was Involved"
- "What We Are Doing"
- "What You Can Do"
- "For More Information"
- Font: 10-point type or larger.
- Language: Written in plain, easily understood language.
Substitute Notice — §1798.82(j)
Substitute notice is permitted when:
- The cost of individual notice exceeds $250,000; OR
- The number of affected persons exceeds 500,000; OR
- The entity does not have sufficient contact information.
Substitute notice must include ALL of the following:
- Email notice to affected persons for whom email addresses are available.
- Conspicuous posting on the entity's website.
- Notification to major statewide media.
Encryption Safe Harbor
Encrypted personal information is excluded from the notification requirement IF:
- The encryption key has not been (and is not reasonably believed to have been) acquired by an unauthorized person.
- The data was encrypted using an algorithm that meets industry standards (AES-128 or higher).
Interaction with CCPA/CPRA
The California Consumer Privacy Act (CCPA) as amended by CPRA provides a private right of action for data breaches under Cal. Civ. Code §1798.150:
- Applies when "nonencrypted and nonredacted personal information" is subject to unauthorized access and exfiltration, theft, or disclosure as a result of the business's failure to implement reasonable security.
- Statutory damages: $100 to $750 per consumer per incident, OR actual damages (whichever is greater).
- Must provide 30-day cure notice before filing suit.
Key Enforcement Actions
- Hanna Andersson (2020): $400,000 settlement for delayed notification of a Magecart web-skimming breach affecting California consumers. AG cited failure to notify "in the most expedient time possible."
- DoorDash (2020): AG investigation into breach affecting 4.9 million individuals. AG scrutinized the adequacy and timeliness of notification.
- T-Mobile (2022): $350 million class-action settlement (national) with significant California consumer component. AG office monitored compliance with California-specific notification requirements.
Sample AG Submission Cover Letter
To: California Office of the Attorney General Privacy Enforcement Section oag.ca.gov/privacy/databreach/reporting
Re: Data Breach Notification — Stellar Payments Group Breach Date: 13 March 2026 California Residents Affected: 2,340
Pursuant to Cal. Civ. Code §1798.82(f), Stellar Payments Group hereby provides notice of a data breach affecting 2,340 California residents. Enclosed is a sample copy of the notification letter being sent to affected individuals. Individual notifications will be dispatched on 28 March 2026.
Contact: Dr. Elena Vasquez, DPO, dpo@stellarpayments.eu, +1 (202) 555-0142.
Executing HIPAA Breach Notification
Overview
The HIPAA Breach Notification Rule (45 CFR §§164.400-414) requires HIPAA covered entities and their business associates to provide notification following a breach of unsecured protected health information (PHI). This skill covers the complete HIPAA breach notification workflow, including the four-factor risk assessment, individual notification requirements, HHS/OCR reporting obligations, state attorney general notification, and media notification thresholds.
Key Definitions
| Term | Definition | Source |
|---|---|---|
| Breach | Acquisition, access, use, or disclosure of PHI in a manner not permitted under the Privacy Rule that compromises the security or privacy of the PHI | 45 CFR §164.402 |
| Unsecured PHI | PHI that is not rendered unusable, unreadable, or indecipherable to unauthorized persons through encryption or destruction per HHS guidance | 45 CFR §164.402 |
| Covered Entity | Health plan, healthcare clearinghouse, or healthcare provider that transmits health information electronically | 45 CFR §160.103 |
| Business Associate | Person or entity that creates, receives, maintains, or transmits PHI on behalf of a covered entity | 45 CFR §160.103 |
| Discovery | The first day the breach is known to the covered entity (or would have been known through reasonable diligence) | 45 CFR §164.404(a)(2) |
Four-Factor Breach Risk Assessment — 45 CFR §164.402(2)
A covered entity must assess the probability that PHI has been compromised using four factors:
Factor 1: Nature and Extent of PHI Involved
- What types of identifiers were involved? (name, SSN, date of birth, diagnosis codes, treatment records)
- How many records were involved?
- Does the PHI include information that increases the risk of identity theft or financial fraud (SSN, financial information)?
- Does the PHI include clinical information that could cause stigma or embarrassment (mental health, substance abuse, HIV status, reproductive health)?
Factor 2: Unauthorized Person Who Used or Received the PHI
- Was the recipient another covered entity or business associate bound by HIPAA?
- Was the recipient a person with no obligation to protect the PHI?
- Is the recipient known or unknown?
- Does the recipient have the ability to re-identify de-identified data?
Factor 3: Whether the PHI Was Actually Acquired or Viewed
- Is there evidence the PHI was actually accessed or viewed?
- Was the PHI returned unopened (e.g., misdirected mail returned by postal service)?
- Do forensic logs show the data was downloaded, copied, or transmitted?
- Was the exposure theoretical (e.g., server was accessible but no evidence of access)?
Factor 4: Extent to Which Risk Has Been Mitigated
- Was the PHI recovered or destroyed?
- Did the unauthorized recipient provide assurances (written attestation) of destruction?
- Were technical controls in place that limited access (password-protected files, short exposure window)?
- Has the covered entity obtained confirmation that the PHI was not further disclosed?
Assessment Outcome
If the four-factor assessment demonstrates a low probability that the PHI has been compromised, the incident is not a reportable breach. The assessment must be documented. If there is any doubt, the incident should be treated as a reportable breach.
Notification Requirements
Individual Notification — 45 CFR §164.404
| Requirement | Detail |
|---|---|
| Timeline | Without unreasonable delay, no later than 60 calendar days from discovery |
| Method | First-class mail to last known address; email if individual has agreed to electronic notice |
| Content — Brief description of breach | What happened and date(s) of breach and discovery |
| Content — Types of information | Description of PHI types involved (not the actual PHI) |
| Content — Protective steps | Steps individual should take to protect from potential harm |
| Content — Entity's actions | Brief description of what the entity is doing to investigate, mitigate harm, and prevent recurrence |
| Content — Contact information | Toll-free number, email, website, or postal address for questions |
| Substitute notice (10+ individuals with insufficient contact info) | Conspicuous posting on entity's website for 90 days OR conspicuous notice in major print or broadcast media serving the area. Must include toll-free number active for 90 days. |
| Urgent notice | If there is possible imminent misuse, notice by telephone or other means in addition to written notice |
HHS/OCR Notification — 45 CFR §164.408
| Breach Size | Reporting Method | Timeline |
|---|---|---|
| 500 or more individuals | HHS Breach Portal (ocrportal.hhs.gov) | Without unreasonable delay, no later than 60 days from discovery. HHS posts on the "Wall of Shame" (breach portal) |
| Fewer than 500 individuals | HHS Breach Portal — annual log | Within 60 days of the end of the calendar year in which the breach was discovered (by March 1 of the following year) |
State Attorney General Notification — 45 CFR §164.412
| Requirement | Detail |
|---|---|
| Threshold | Breaches involving residents of the state; most states require notification for 500+ affected residents |
| Timeline | Concurrent with or prior to individual notification |
| Content | Same as individual notification content |
| Method | Written notice to the attorney general of each state where affected individuals reside |
Media Notification — 45 CFR §164.406
| Requirement | Detail |
|---|---|
| Threshold | Breach affecting 500 or more individuals in a single state or jurisdiction |
| Timeline | Without unreasonable delay, no later than 60 days from discovery |
| Method | Prominent media outlets serving the state or jurisdiction (newspaper, TV, radio) |
| Content | Same as individual notification content |
Breach Exceptions — 45 CFR §164.402(1)
Three exceptions to the definition of "breach" (not reportable even if unsecured PHI is involved):
Exception 1: Unintentional Acquisition
Good-faith, unintentional acquisition, access, or use of PHI by a workforce member or person acting under the covered entity's authority, if made within the scope of authority and without further impermissible use or disclosure.
Exception 2: Inadvertent Disclosure Within Organization
Inadvertent disclosure of PHI by a person authorized to access PHI at a covered entity or business associate to another person authorized to access PHI at the same entity, and the PHI is not further used or disclosed impermissibly.
Exception 3: Good Faith Belief of No Retention
Disclosure of PHI where the covered entity or business associate has a good-faith belief that the unauthorized person would not reasonably have been able to retain the information.
Business Associate Obligations — 45 CFR §164.410
- Business associate must notify the covered entity of a breach without unreasonable delay, and no later than 60 days from discovery (or a shorter period specified in the BAA).
- The notification must include: identification of each individual affected (if known), and any other available information the covered entity needs to provide individual notification.
- The covered entity is ultimately responsible for providing all required notifications.
Penalties for Non-Compliance
| Tier | Knowledge Level | Per Violation | Annual Cap |
|---|---|---|---|
| Tier 1 | Did not know and could not have known | $137 - $68,928 | $2,067,813 |
| Tier 2 | Reasonable cause, not willful neglect | $1,379 - $68,928 | $2,067,813 |
| Tier 3 | Willful neglect, corrected within 30 days | $13,785 - $68,928 | $2,067,813 |
| Tier 4 | Willful neglect, not corrected | $68,928 - $2,067,813 | $2,067,813 |
(Penalty amounts adjusted for inflation per Federal Register notice, effective 2025.)
Integration with State Laws
HIPAA breach notification does not preempt state breach notification laws that provide greater protection or additional requirements. Covered entities must comply with both HIPAA and applicable state laws. In practice:
- HIPAA 60-day deadline is the outer limit; some states impose shorter deadlines.
- State content requirements may exceed HIPAA minimums.
- State AG notification may be required even for breaches under 500 individuals depending on state law.
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/data-breach-response-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- breach-response, breach-notification, incident-response, forensics
More from mukul975/Privacy-Data-Protection-Skills
All 21- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0
- employee-privacy-skillsv1.0.0
- gdpr-compliance-skillsv1.0.0
- global-privacy-regulations-skillsv1.0.0
- healthcare-privacy-skillsv1.0.0
- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0
- vendor-privacy-management-skillsv1.0.0
- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0
- cross-border-transfers-skillsv1.0.0