What this control covers

Implement technical and procedural controls to: (a) verify age before processing personal data (date-of-birth validation with system enforcement); (b) obtain verifiable parental/guardian consent for under-18 data subjects; (c) prohibit behavioural tracking, monitoring, and targeted advertising directed at children; (d) restrict processing likely to cause detrimental effect to child well-being. Objective: Protect children's personal data from unlawful processing and ensure verifiable parental consent is obtained before any processing of child data commences.

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: Children's Data Processing Controls.

Quick checklist

  • Implement — Children'S Data Processing Controls
  • Ensure — Children'S Data Processing Controls
  • Monitor — Children'S Data Processing Controls

Related articles on this site