GDPR · CELEX 02016R0679-20160504
Article 32
Verbatim text of the current consolidated version (consolidated 2016-05-04) · status: in force. Check it on EUR-Lex ↗
GDPR, Article 32(1) — Security of processing
Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the 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 and encryption of 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.
GDPR, Article 32(2) — Security of processing
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.
GDPR, Article 32(3) — Security of processing
Adherence to an approved code of conduct as referred to in Article 40 or an approved certification mechanism as referred to in Article 42 may be used as an element by which to demonstrate compliance with the requirements set out in paragraph 1 of this Article.
GDPR, Article 32(4) — Security of processing
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.
This text is not written by an AI. It is rendered from a corpus built from the official EUR-Lex source, where every fragment is content-hashed and signed at ingestion — which is what lets you cite it and defend the citation. Ask a question about this article →
Other articles of the GDPR
Art. 1Art. 2Art. 3Art. 4Art. 5Art. 6Art. 7Art. 8Art. 9Art. 10Art. 11Art. 12Art. 13Art. 14Art. 15Art. 16Art. 17Art. 18Art. 19Art. 20Art. 21Art. 22Art. 23Art. 24Art. 25Art. 26Art. 27Art. 28Art. 29Art. 30Art. 31Art. 32Art. 33Art. 34Art. 35Art. 36Art. 37Art. 38Art. 39Art. 40Art. 41Art. 42Art. 43Art. 44Art. 45Art. 46Art. 47Art. 48Art. 49Art. 50Art. 51Art. 52Art. 53Art. 54Art. 55Art. 56Art. 57Art. 58Art. 59Art. 60Art. 61Art. 62Art. 63Art. 64Art. 65Art. 66Art. 67Art. 68Art. 69Art. 70Art. 71Art. 72Art. 73Art. 74Art. 75Art. 76Art. 77Art. 78Art. 79Art. 80Art. 81Art. 82Art. 83Art. 84Art. 85Art. 86Art. 87Art. 88Art. 89Art. 90Art. 91Art. 92Art. 93Art. 94Art. 95Art. 96Art. 97Art. 98Art. 99
Acquis returns official sources verbatim with citations; it is not legal advice. Texts © European Union, reuse permitted (Decision 2011/833/EU) — only the EUR-Lex original is authentic. Why legal AI fails · Coverage