--- title: "Article 32 — Security of processing" type: regulation legal_status: in_force source: "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504" source_retrieved: 2026-09-28 shortTitle: "Article 32 — Security of processing" instrument_type: level1_regulation authority: Commission binding: true binding_character: binding mica_level2: false legal_basis: "Regulation (EU) 2016/679" instrument: gdpr celex: "32016R0679" regulation: GDPR regulation-full: "Regulation (EU) 2016/679" article: 32 status: in_force object_id: eu.gdpr.legal_text.article.32 text_version: "Consolidated version of 4 May 2016" source_url: "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504" check_status: matched verified: true last_checked: 2026-10-26 --- *In force · Consolidated version of 4 May 2016 · Checked against EUR-Lex on 26 Oct 2026 · [Official source](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504)* 1. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of [processing](https://www.headlesslaw.com/definitions/gdpr/processing) as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the [controller](https://www.headlesslaw.com/definitions/gdpr/controller) and the [processor](https://www.headlesslaw.com/definitions/gdpr/processor) shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: **(a)** the [pseudonymisation](https://www.headlesslaw.com/definitions/gdpr/pseudonymisation) and encryption of [personal data](https://www.headlesslaw.com/definitions/gdpr/personal-data); **(b)** the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services; **(c)** the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident; **(d)** a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. 2. In assessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed. 3. Adherence to an approved code of conduct as referred to in [Article 40](40.md) or an approved certification mechanism as referred to in [Article 42](42.md) may be used as an element by which to demonstrate compliance with the requirements set out in paragraph 1 of this Article. 4. The controller and processor shall take steps to ensure that any natural person acting under the authority of the controller or the processor who has access to personal data does not process them except on instructions from the controller, unless he or she is required to do so by Union or Member State law. ## Related Level 2 and Level 3 ### Guidance and Q&A - [EDPB 01/2025 — Guideline — Pseudonymisation \[consultation\]](../level-3/guidelines/edpb-01-2025-pseudonymisation.md) *** [Chapter IV — Controller and processor](../chapters/iv.md) · [← Article 31](31.md) · [Article 33 →](33.md)