Skip to the content
Eureka The General Data Protection Regulation
EN language

Topics

Security and personal data breaches

Eureka's summary

Controllers and processors must ensure appropriate security. The controller must notify a personal data breach to the supervisory authority unless it is unlikely to result in a risk, and communicate it to data subjects where the risk is high.

Notifying a breach to the authority In the case of a personal data breach: the processor notifies the controller without undue delay. The controller notifies the supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of the breach; a later notification must give reasons for the delay. This does not apply to a breach that is unlikely to result in a risk to the rights and freedoms of natural persons. Separately, the controller documents every breach, with its facts, effects and the remedial action taken. if: a personal data breach processor notify controller without undue delay Controller notify supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware; later only with reasons not for: a breach unlikely to result in a risk Controller documents every breach facts, effects, remedial action
The controller must notify a personal data breach to the supervisory authority without undue delay and, where feasible, within 72 hours, unless it is unlikely to result in a risk; a processor must notify the controller. The act in pictures

Article 4 · Definitions

Article 4 defines the Regulation's terms in 26 points.

‘Personal data’ means ‘any information relating to an identified or identifiable natural person’, the ‘data subject’; the ‘controller’ determines, alone or jointly with others, the purposes and means of the processing, and a ‘processor’ processes personal data on behalf of the controller.

Other defined terms include ‘processing’, ‘profiling’, ‘pseudonymisation’, ‘consent’, ‘personal data breach’, ‘genetic data’, ‘biometric data’, ‘data concerning health’, ‘main establishment’ and ‘cross-border processing’.

Who is who Three actors in a row. The data subject, a person, is an identified or identifiable natural person; personal data are any information relating to him or her, drawn as a card on a line joining the data subject and the controller. The controller, an office block with a target badge, determines, alone or jointly with others, the purposes and means of the processing of personal data. The processor, the same block with a gear badge, processes personal data on behalf of the controller; a thin arrow runs from the controller to the processor. A note under both says that each may be any natural or legal person, public authority, agency or other body. data subject identified or identifiable natural person personal data controller determines purposes and means processor processes on the controller's behalf person, authority or body
Personal data relate to a natural person, the data subject; the controller determines the purposes and means of processing them, and a processor processes them on the controller's behalf. The act in pictures

Read Article 4

Article 32 · Security of processing

The controller and the processor must implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risk for the rights and freedoms of natural persons.

These include, among others and as appropriate:

  • pseudonymisation and encryption;
  • the ability to ensure ongoing confidentiality, integrity, availability and resilience;
  • the ability to restore access to personal data after an incident; and
  • regular testing of the measures.
Security of processing The controller or the processor, drawn as two office blocks, must implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risk for the rights and freedoms of natural persons. Four tiles show what the measures include, as appropriate: (a) 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 after a physical or technical incident; (d) a process for regularly testing, assessing and evaluating the effectiveness of the measures. Controller or Processor appropriate technical and organisational measures security appropriate to the risk taking into account: state of the art, costs of implementation, nature, scope, context and purposes, risk to rights and freedoms including, as appropriate: (a) pseudonymisation and encryption (b) ongoing confidentiality, integrity, availability and resilience (c) restoring access in a timely manner after an incident (d) regular testing of the measures
The controller and the processor must implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk. The act in pictures

Read Article 32

Article 33 · Notification of a personal data breach to the supervisory authority

In the case of a personal data breach, the controller must notify the supervisory authority competent under Article 55 without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons.

A notification made after 72 hours must be accompanied by reasons for the delay, and information that cannot be provided at the same time may be provided in phases without undue further delay.

The processor must notify the controller without undue delay, and the controller must document any personal data breaches.

Read Article 33

Article 34 · Communication of a personal data breach to the data subject

When a personal data breach is likely to result in a high risk to the rights and freedoms of natural persons, the controller must communicate it to the data subject without undue delay, in clear and plain language.

This is not required if any of three conditions is met:

  • appropriate protection measures, in particular ones such as encryption that render the data unintelligible to unauthorised persons, were applied to the affected data;
  • subsequent measures ensure that the high risk is no longer likely to materialise; or
  • it would involve disproportionate effort, in which case an equally effective public communication or similar measure is required instead.

Where the controller has not communicated the breach, the supervisory authority may require it to do so or decide that a condition is met.

Telling data subjects of a breach If a personal data breach is likely to result in a high risk to the rights and freedoms of natural persons, the controller communicates it to the data subject without undue delay, drawn as an envelope sent along an arrow, in clear and plain language. It is not required if one of three conditions applies: protection measures that make the data unintelligible to unauthorised persons, such as encryption, were applied to the affected data; subsequent measures ensure the high risk is no longer likely to materialise; or it would involve disproportionate effort, in which case a public communication or similar, equally effective measure is required instead. The supervisory authority may require the communication, or decide that one of the conditions is met. if: a breach is likely to result in a high risk controller data subject Message sent without undue delay in clear and plain language not required if one applies: protection applied to the data making them unintelligible, such as encryption subsequent measures high risk no longer likely to materialise disproportionate effort then a public communication instead Supervisory authority may require the communication, or decide a condition is met
When a personal data breach is likely to result in a high risk, the controller must tell the data subjects without undue delay, unless one of three conditions is met. The act in pictures

Read Article 34

Recitals

  1. 83
  2. 85
  3. 86
  4. 87
Eureka is adding links and definitions…