What this control covers
Ensures data subjects can confirm if their personal data is processed and access it with details on purposes, categories, recipients, and rights, provided promptly and freely. 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 of access by the data subject.
Quick checklist
- Right — Recipients / Rights
- Data — Recipients / Rights
Related articles on this site
- GDPR Article 13: Information to be Provided Where Personal Data Are Collected from the Data Subject
- GDPR Article 14: Information to be Provided Where Personal Data Have Not Been Obtained from the Data Subject
- GDPR Article 15: Right of Access by the Data Subject
- Ensure Diagnostic Setting captures appropriate categories from the control/management plane