What this control covers
Implement tools or mechanisms that allow individuals to consent to the processing of their personally identifiable information (PII) prior to its collection, facilitating informed decision-making by individuals. This helps manage the privacy risks associated with the processing of PII.
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: Consent.
Quick checklist
- Policy — Management / Information
- Information — Management / Information
- Mechanisms — Management / Information
- Individuals — Management / Information
- Privacy — Management / Information
- Risk — Management / Information
Related articles on this site
- NIST 800-171 3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
- NIST 800-171 3.3.8 Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
- NIST 800-171 3.4.8 Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.
- NIST 800-171 3.7.2 Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.