GDPR · Control Article 33 · Priority: critical · Component: Chapter IV: Controller and Processor

What this control covers

Controllers must notify the supervisory authority of a personal data breach within 72 hours, unless unlikely to risk rights and freedoms, detailing breach nature, data subjects, records, consequences, and mitigation measures. Processors must inform controllers promptly. Breaches must be documented. This control addresses Breach Notification.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

Google Workspace

Use Data Export (Takeout-style) and Vault search to scope DSARs. Apply Drive labels + DLP so personal data classes are discoverable.

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.

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.

Signed policy or standard documents the safeguard. Focus: Notification of a personal data breach to the supervisory authority.

Quick checklist

  • Notification — Controller / Controllers
  • Data — Controller / Controllers
  • Processor — Controller / Controllers
  • Records — Controller / Controllers
  • Supervisory — Controller / Controllers

Related articles on this site