GDPR · Control Article 17 · Priority: critical · Component: Chapter III: Rights of the Data Subject

What this control covers

This control ensures that data subjects can request the erasure of their personal data when it's no longer needed, consent is withdrawn, or if the data has been unlawfully processed. Controllers must act without undue delay unless exemptions apply, such as legal obligations or public interest purposes. Publicly disclosed data must also be erased from other controllers. This control addresses Data Subject Rights.

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.

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: Right to erasure ('right to be forgotten').

Quick checklist

  • Right — Consent / Legal Obligations
  • Data — Consent / Legal Obligations
  • Obligations — Consent / Legal Obligations

Related articles on this site