What this control covers
Attach data tags to elements of personally identifiable information (PII) that convey processing purposes. This ensures tracking of PII processing and verifies if changes in processing align with documented purposes. Data tags also support the use of automated tools.
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: Data Tagging.
Quick checklist
- Policy — Management / Information
- Information — Management / Information
- Data — Management / Information
- Changes — Management / Information
- Privacy — Management / Information
- Risk — Management / Information