GDPR · Control Article 7 · Priority: critical · Component: Chapter II: Principles

What this control covers

Ensures consent for processing personal data is freely given, specific, informed, and unambiguous, with clear documentation, easy withdrawal, and distinguishable consent requests. This control addresses Consent Management System.

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.
  • infra_scan — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Conditions for consent.

Quick checklist

  • Principles — Consent
  • Conditions — Consent
  • Data — Consent

Related articles on this site