What this control covers
Define and implement a protocol for processing personal data under emergency, epidemic, or public interest/disaster grounds (Sec 7(c)(d)(e)). For each instance of reliance on these grounds, document: ground relied upon, start and end date, data categories processed, legal necessity justification, and post-event review. Objective: Ensure emergency-based processing is proportionate, time-limited, and documented, preventing abuse of these exceptional grounds.
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.
GCP
Use Cloud KMS with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. Sensitive Data Protection (DLP API) inspects/de-identifies PII at scale.
Google Workspace
Enable client-side encryption for Drive/Docs and turn on Drive Labels + DLP rules to prevent external sharing of regulated data classes.
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 policies, procedures, and registers document the safeguard. Focus: Emergency & Public Interest Processing Protocol.
Quick checklist
- Implement — Emergency / Public Interest Processing Protocol
- Define — Emergency / Public Interest Processing Protocol
- Document — Emergency / Public Interest Processing Protocol