Article 32 GDPR: Difference between revisions
(+citation) |
No edit summary |
||
Line 2: | Line 2: | ||
![[Article 31 GDPR|←]] Article 32 - Security of processing [[Article 33 GDPR|→]] | ![[Article 31 GDPR|←]] Article 32 - Security of processing [[Article 33 GDPR|→]] | ||
|- | |- | ||
|style="padding: 20px; background-color:#003399;"|[[File:Gdpricon.png|100px|center|link=Overview_of_GDPR]] | | style="padding: 20px; background-color:#003399;" |[[File:Gdpricon.png|100px|center|link=Overview_of_GDPR]] | ||
|- | |- | ||
| | | | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 1: General provisions</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 1: General provisions</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 17: | Line 17: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 2: Principles</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 2: Principles</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 31: | Line 31: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 3: Rights of the data subject</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 3: Rights of the data subject</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 50: | Line 50: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible | <div class="toccolours mw-collapsible" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 4: Controller and processor</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 4: Controller and processor</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 77: | Line 77: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 5: Transfers of personal data</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 5: Transfers of personal data</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 91: | Line 91: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 6: Supervisory authorities</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 6: Supervisory authorities</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 107: | Line 107: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 7: Cooperation and consistency</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 7: Cooperation and consistency</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 131: | Line 131: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 8: Remedies, liability and penalties</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 8: Remedies, liability and penalties</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 146: | Line 146: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 9: Specific processing situations</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 9: Specific processing situations</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 160: | Line 160: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 10: Delegated and implementing acts</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 10: Delegated and implementing acts</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 169: | Line 169: | ||
</div></div> | </div></div> | ||
<div class="toccolours mw-collapsible mw-collapsed | <div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"> | ||
<div style="font-weight:bold;line-height:1.6;">Chapter 11: Final provisions</div> | <div style="font-weight:bold;line-height:1.6;">Chapter 11: Final provisions</div> | ||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
Line 184: | Line 184: | ||
|} | |} | ||
== Legal Text == | ==Legal Text== | ||
<br /><center>'''Article 32 - Security of processing'''</center><br /> | <br /><center>'''Article 32 - Security of processing'''</center><br /> | ||
Line 203: | Line 203: | ||
<span id="4">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.</span> | <span id="4">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.</span> | ||
== Relevant Recitals== | ==Relevant Recitals== | ||
{{Recital/75 GDPR}}{{Recital/76 GDPR}}{{Recital/77 GDPR}}{{Recital/78 GDPR}}{{Recital/79 GDPR}}{{Recital/83 GDPR}} | {{Recital/75 GDPR}}{{Recital/76 GDPR}}{{Recital/77 GDPR}}{{Recital/78 GDPR}}{{Recital/79 GDPR}}{{Recital/83 GDPR}} | ||
== Commentary == | ==Commentary== | ||
As a key principle of data protection, data security was also codified in Article 32. For this purpose, the controller and the processor must implement appropriate technical and organizational measures, taking into account the state of the art, the implementation costs and the nature, scope, context and purposes of processing. Consideration must, however, also be given to the varying likelihood and the severity for the rights and freedoms of natural persons. | === Overview === | ||
As a key principle of data protection, data security was also codified in Article 32. For this purpose, the controller and the processor must implement appropriate technical and organizational measures, taking into account the state of the art, the implementation costs and the nature, scope, context and purposes of processing. Consideration must, however, also be given to the varying likelihood and the severity for the rights and freedoms of natural persons. The ECJ has consequently recognised data security as an integral part of the right to data protection in Article 8 of the Charter of Fundamental Rights of the European Union. [[Article 32 GDPR#%20ftn1|[1]]] | |||
=== Risk assessment === | |||
Article 32 reaffirms the need for the data controller and data processor to adopt technical and organizational measures to minimize the risk of data breach, especially with regard to the rights and freedoms of individuals. Article 32 places an obligation to implement measures that ensure an appropriate level of security. | |||
== Decisions == | The first step, therefore, shall be the permormance of an assessment that identifies the risks tied to the processing operations. The provision applies to all types of risks although, according to Article 32(2), specific attention should be paid to certain categories of risks. Precisely, the “''accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed''”. | ||
Recital 83, which seems to confirm this interpretation, also suggests that not all the risks mentioned above are relevant. In fact, the risk should also “''lead to physical, material or non-material damage''”. It can be argued, therefore, that a potential risk of, say, “destruction” will not be relevant if it is structurally unable to inflict a tangible harm to the data subject. | |||
=== Technical and organisational measures === | |||
The second step consists of the identification of the security measures that can mitigate the identified risks. The lists of measures that a controller or processor can adopt are various. However, Article 32(1) lists four types of security measures that are generally deemed 'as appropriate'. | |||
Such a list includes pseudonymisation and encryption of personal data (Article 32(l)(a) GDPR); the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems (Article 32(1)(b) GDPR); the ability to restore the availability and access to personal data in a timely manner in case of an incident (Article 32(1)(c) GDPR) and a process for regularly testing, assessing and evaluating the effectiveness of security measures (Article 32(1)(d) GDPR). | |||
In addition to technical measures, organisational measures should also be implemented. Examples are the distribution of responsibility between controller and processor, as well as the training activities of each person authorised to process personal data, internal policies, disciplinary measures, internal guidelines as well as adherence to codes of conduct or certification mechanisms. | |||
=== Impact assessment and implementation === | |||
After having identified a list of theoretically applicable measures, controllers and processor must make a choice and implement the measure or measures which can ensure a level of security “appropriate” to the risk. | |||
This indicates that controllers and processors must implement the measures that are able to mitigate (at least) those risks which are the most likely to materialise and those whose impact would be the most severe. [[Article 32 GDPR#%20ftn2|[2]]] | |||
Article 32(1) provides a (non-exhaustive) list of criteria to be taken into account, namely: the state of the art; the costs of implementation; the nature, scope, context and purposes of the processing; and the risk of varying likelihood and severity for the rights and freedoms of individuals. [[Article 32 GDPR#%20ftn3|[3]]] | |||
=== Codes of conduct and certification mechanisms === | |||
In line with the accountability principle, Article 32(3) stipulates that adherence to codes of conduct or certification mechanisms can be used as an element to demonstrate compliance with the Regulation. Neither of these two requirements shall automatically reduce the liability of the data controller and/or data processor (Art. 42(4) GDPR). However, they will undoubtedly be facilitated should they be called upon to prove that they have done everything possible to avoid the violation.[[Article 32 GDPR#%20ftn4|[4]]] | |||
----[[Article 32 GDPR#%20ftnref1|[1]]] ECJ, Judgment of 8. April 2014 in the joint cases ''Digital Rights Ireland Ltd'', C‑293/12 and ''Kärntner Landesregierung'', C‑594/12, ECLI:EU:C:2014:238, par. 29 | |||
[[Article 32 GDPR#%20ftnref2|[2]]] Kuner C, ''The EU General Data Protection Regulation (GDPR): A Commentary'', Oxford University Press 2020, pg 636. | |||
[[Article 32 GDPR#%20ftnref3|[3]]] For an analysis of these concept, please check the comment under Article 33 of this Commentary. | |||
[[Article 32 GDPR#%20ftnref4|[4]]] Riccio, Scorza, Belisario, ''GDPR e normativa privacy – Commentario'', Wolters Kluwer 2018, pg. 299. | |||
==Decisions== | |||
→ You can find all related decisions in [[:Category:Article 32 GDPR]] | → You can find all related decisions in [[:Category:Article 32 GDPR]] | ||
== References == | ==References== | ||
<references /> | <references /> | ||
[[Category:GDPR Articles]] | [[Category:GDPR Articles]] |
Revision as of 09:14, 4 November 2020
Legal Text
1. 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.
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 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.
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.
Relevant Recitals
Commentary
Overview
As a key principle of data protection, data security was also codified in Article 32. For this purpose, the controller and the processor must implement appropriate technical and organizational measures, taking into account the state of the art, the implementation costs and the nature, scope, context and purposes of processing. Consideration must, however, also be given to the varying likelihood and the severity for the rights and freedoms of natural persons. The ECJ has consequently recognised data security as an integral part of the right to data protection in Article 8 of the Charter of Fundamental Rights of the European Union. [1]
Risk assessment
Article 32 reaffirms the need for the data controller and data processor to adopt technical and organizational measures to minimize the risk of data breach, especially with regard to the rights and freedoms of individuals. Article 32 places an obligation to implement measures that ensure an appropriate level of security.
The first step, therefore, shall be the permormance of an assessment that identifies the risks tied to the processing operations. The provision applies to all types of risks although, according to Article 32(2), specific attention should be paid to certain categories of risks. Precisely, the “accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed”.
Recital 83, which seems to confirm this interpretation, also suggests that not all the risks mentioned above are relevant. In fact, the risk should also “lead to physical, material or non-material damage”. It can be argued, therefore, that a potential risk of, say, “destruction” will not be relevant if it is structurally unable to inflict a tangible harm to the data subject.
Technical and organisational measures
The second step consists of the identification of the security measures that can mitigate the identified risks. The lists of measures that a controller or processor can adopt are various. However, Article 32(1) lists four types of security measures that are generally deemed 'as appropriate'.
Such a list includes pseudonymisation and encryption of personal data (Article 32(l)(a) GDPR); the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems (Article 32(1)(b) GDPR); the ability to restore the availability and access to personal data in a timely manner in case of an incident (Article 32(1)(c) GDPR) and a process for regularly testing, assessing and evaluating the effectiveness of security measures (Article 32(1)(d) GDPR).
In addition to technical measures, organisational measures should also be implemented. Examples are the distribution of responsibility between controller and processor, as well as the training activities of each person authorised to process personal data, internal policies, disciplinary measures, internal guidelines as well as adherence to codes of conduct or certification mechanisms.
Impact assessment and implementation
After having identified a list of theoretically applicable measures, controllers and processor must make a choice and implement the measure or measures which can ensure a level of security “appropriate” to the risk.
This indicates that controllers and processors must implement the measures that are able to mitigate (at least) those risks which are the most likely to materialise and those whose impact would be the most severe. [2]
Article 32(1) provides a (non-exhaustive) list of criteria to be taken into account, namely: the state of the art; the costs of implementation; the nature, scope, context and purposes of the processing; and the risk of varying likelihood and severity for the rights and freedoms of individuals. [3]
Codes of conduct and certification mechanisms
In line with the accountability principle, Article 32(3) stipulates that adherence to codes of conduct or certification mechanisms can be used as an element to demonstrate compliance with the Regulation. Neither of these two requirements shall automatically reduce the liability of the data controller and/or data processor (Art. 42(4) GDPR). However, they will undoubtedly be facilitated should they be called upon to prove that they have done everything possible to avoid the violation.[4]
[1] ECJ, Judgment of 8. April 2014 in the joint cases Digital Rights Ireland Ltd, C‑293/12 and Kärntner Landesregierung, C‑594/12, ECLI:EU:C:2014:238, par. 29
[2] Kuner C, The EU General Data Protection Regulation (GDPR): A Commentary, Oxford University Press 2020, pg 636.
[3] For an analysis of these concept, please check the comment under Article 33 of this Commentary.
[4] Riccio, Scorza, Belisario, GDPR e normativa privacy – Commentario, Wolters Kluwer 2018, pg. 299.
Decisions
→ You can find all related decisions in Category:Article 32 GDPR