GDPR·Article Article 46·high·Component: Chapter V: Transfers of Personal Data to Third Countries

What this control requires

Personal data transfers to third countries without an adequacy decision require appropriate safeguards, such as binding corporate rules, standard clauses, approved codes, or certifications, ensuring enforceable data subject rights and legal remedies, with supervisory authority oversight where needed. This control addresses International Data Transfers.
— GDPR, Article Article 46

In plain English

Personal data transfers to third countries without an adequacy decision require appropriate safeguards, such as binding corporate rules, standard clauses, approved codes, or certifications, ensuring enforceable data subject rights and legal remedies, with supervisory authority oversight where needed. In practice, this means you can prove you data transfers-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 high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

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 V: Transfers of Personal Data to Third Countries, the assessor will trace your implementation back to the catalogue reference (Article Article 46) and look for objective evidence on the latest two assessment cycles.

How to implement

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Data. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Codes. Document the trigger, the owner and the cadence.
  • Transfers. Document the trigger, the owner and the cadence.
  • International. Document the trigger, the owner and the cadence.
  • Scope: transfers, supervisory authority, standard clauses, certifications, corporate rules, rights.

Evidence to collect

  • Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Transfers subject to appropriate safeguards.

Common pitfalls

  • CI security checks set to warn-only; the merge button is faster than the security feedback.
  • 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.

Related controls in GDPR

References

Topics: application securitysecure developmentcode review testingdevsecopspolicy management