GDPR Article 25 — Data protection by design and by default

What this control requires

The controller must embed data protection by design and default, using technical and organizational measures like pseudonymisation to ensure only necessary personal data is processed, minimizing collection, processing, storage, and access while safeguarding data subjects' rights. This control addresses Privacy by Design.

In plain English

The controller must embed data protection by design and default, using technical and organizational measures like pseudonymisation to ensure only necessary personal data is processed, minimizing collection, processing, storage, and access while safeguarding data subjects' rights. In practice, this means you can prove you data controller-level controls on a defined cadence.

Why it matters

GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does.

Within Chapter IV: Controller and Processor, the assessor will trace your implementation back to the catalogue reference (Article Article 25) and look for objective evidence on the latest two assessment cycles.

How to implement

Cloud Posture

CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

Configuration Management

Policy-as-code. Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises.

IaC. Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production.

Drift. Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register.

Network Security

AWS. VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation.

Azure. NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift.

GCP. VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services.

Operational checklist

• Data. Document the trigger, the owner and the cadence.
• Processor. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Scope: controller, rights, data subjects, pseudonymisation.

Evidence to collect

• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.
• Policy Document. A signed and version-controlled policy / standard / procedure document.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Signed policy or standard documents the safeguard. Focus: Data protection by design and by default.

Common pitfalls

• Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.
• Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation.
• Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.
• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• CIS Controls v8 16.14 — Conduct Threat Modeling
• BSI C5:2020 COM-03 — Internal audits of the information security management system
• NIST SP 800-53 Rev. 5 CM-10 — Software Usage Restrictions

Related controls in GDPR

• Article Article 27 — Representatives of controllers or processors not established in the Union
• Article Article 79 — Right to an effective judicial remedy against a controller or processor
• Article Article 28 — Processor
• Article Article 21 — Right to object
• Article Article 33 — Notification of a personal data breach to the supervisory authority
• Article Article 34 — Communication of a personal data breach to the data subject

References

• European Union — GDPR
• Catalogue identifier: Article Article 25

Topics: governance riskcloud infrastructurecloud postureconfiguration managementnetwork securitypolicy management