# GDPR Article 32 — Security of processing - Source: https://support.icompaas.com/compliance/gdpr/article-32-security-of-processing - Section: [Compliance](https://support.icompaas.com/compliance) › [GDPR (Regulation (EU) 2016/679)](https://support.icompaas.com/compliance/gdpr) › Articles 31–40 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **GDPR**·Article `Article 32`·critical·Component: **Chapter IV: Controller and Processor** ## What this control requires > Controllers and processors must implement risk-based technical and organizational measures, like pseudonymisation and encryption, to ensure data security, confidentiality, integrity, and availability, with regular testing and restricted access per controller instructions. This control addresses Security of Processing. > > — GDPR, Article Article 32 ### In plain English Controllers and processors must implement risk-based technical and organizational measures, like pseudonymisation and encryption, to ensure data security, confidentiality, integrity, and availability, with regular testing and restricted access per controller instructions. 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 32) and look for objective evidence on the latest two assessment cycles. ## How to implement #### 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. - **Processor.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Confidentiality.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Scope:** controller, controllers, pseudonymisation. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Security of processing. ## Common pitfalls - 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. - [**ISO/IEC 27701:2025 A.1.2.8** — Joint PII controller](https://support.icompaas.com/compliance/iso-27701-2025/a-1-2-8-joint-pii-controller) - [**ISO/IEC 27001:2022 A.8.33** — Test information](https://support.icompaas.com/compliance/iso-27001-2022/a-8-33-test-information) ## Related controls in GDPR - [**Article Article 34** — Communication of a personal data breach to the data subject](https://support.icompaas.com/compliance/gdpr/article-34-communication-of-a-personal-data-breach-to-the-data-subject) - [**Article Article 31** — Cooperation with the supervisory authority](https://support.icompaas.com/compliance/gdpr/article-31-cooperation-with-the-supervisory-authority) - [**Article Article 27** — Representatives of controllers or processors not established in the Union](https://support.icompaas.com/compliance/gdpr/article-27-representatives-of-controllers-or-processors-not-established-in-the-union) - [**Article Article 36** — Prior consultation](https://support.icompaas.com/compliance/gdpr/article-36-prior-consultation) - [**Article Article 24** — Responsibility of the controller](https://support.icompaas.com/compliance/gdpr/article-24-responsibility-of-the-controller) - [**Article Article 43** — Certification bodies](https://support.icompaas.com/compliance/gdpr/article-43-certification-bodies) ## References - [European Union — GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj) - Catalogue identifier: `Article Article 32` Topics: governance riskdata protectioncode review testingencryption at restpolicy management ## Related compliance guidance - [GDPR compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/gdpr): Start with the full GDPR implementation guide — scope, roadmap, evidence and how the assessment runs. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): The security management system most EU procurement teams ask for alongside a DPA; its controls supply much of the Article 32 evidence. - [India's DPDP Act 2023: a practical compliance guide for cloud teams](https://support.icompaas.com/compliance/india-dpdp-act-2023): If engineering or support teams sit in India, the same data flows are also subject to India’s Digital Personal Data Protection Act.