What this control covers
Implement a data subject breach notification procedure including: (i) pre-approved communication template compliant with Rule 7 (nature of breach, potential impact, mitigation steps, contact for queries); (ii) automated notification trigger linked to breach detection systems; (iii) notification mechanism documentation (email, SMS, in-app); (iv) timeline tracking from breach detection to data subject notification; (v) delivery confirmation logs. Objective: Ensure affected data principals are notified promptly and comprehensively upon a personal data breach, enabling them to take protective action.
Why it matters
How quickly and methodically you contain an incident determines the regulatory consequence — most fines are not for the breach itself but for the slow or absent response.
How to implement
AWS
Wire GuardDuty, Security Hub and Macie findings into your ticketing/SIEM via EventBridge. Maintain documented playbooks for IAM-key compromise, EC2 instance compromise, S3 data exposure, and run quarterly tabletop exercises.
Azure
Use Defender for Cloud + Microsoft Sentinel with playbooks (Logic Apps) for automated containment — disable user, isolate VM (NSG), revoke session tokens. Keep an on-call rotation in Teams with PagerDuty.
GCP
Use Cloud KMS with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. Sensitive Data Protection (DLP API) inspects/de-identifies PII at scale.
Google Workspace
Enable client-side encryption for Drive/Docs and turn on Drive Labels + DLP rules to prevent external sharing of regulated data classes.
GitHub
Subscribe to secret-scanning alerts and Dependabot security advisories; require triage SLAs by severity. For exposed secrets, rotate at the cloud provider FIRST then revoke at GitHub — order matters.
Evidence to collect
ticketing_workflow— See the iCompaas Evidence library for the canonical source for this evidence type.policy_document— A signed, version-controlled policy stating leadership intent and the named owner.
Signed policies, procedures, and registers document the safeguard. Service management or grievance ticketing records prove timely handling. Focus: Personal Data Breach - Data Subject Notification.
Quick checklist
- Implement — Personal Data Breach / Data Subject Notification
- Document — Personal Data Breach / Data Subject Notification
- Ensure — Personal Data Breach / Data Subject Notification
Related articles on this site
- GDPR Article 34: Communication of a Personal Data Breach to the Data Subject
- GDPR Article 33: Notification of a Personal Data Breach to the Supervisory Authority
- GDPR Article 12: Transparent Information, Communication, and Modalities for Exercising Data Subject Rights
- GDPR Article 13: Information to be Provided Where Personal Data Are Collected from the Data Subject