What this control covers

Implement a consent management system ensuring all consents meet DPDPA requirements: free from duress, specific (per-purpose), informed, unconditional, unambiguous, and expressed through clear affirmative action. Prohibit: pre-ticked boxes, bundled consent, and retrospective consent. Maintain immutable, timestamped consent logs for the duration of processing. Objective: Ensure the quality and validity of all consents collected, making all consent-based processing lawful and auditable.

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: Consent Quality & Management.

Quick checklist

  • Maintain — Consent Quality / Management
  • Implement — Consent Quality / Management
  • Ensure — Consent Quality / Management

Related articles on this site