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.
- A ‘personal data breach’ is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed.
- The controller and the processor must implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including as appropriate pseudonymisation and encryption, the ability to ensure ongoing confidentiality, integrity, availability and resilience, the ability to restore access after an incident and regular testing.
- The controller must notify a personal data breach to 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 later notification must give reasons for the delay.
- The processor must notify the controller without undue delay after becoming aware of a personal data breach.
- The notification must at least describe the nature of the breach, give the contact details of the data protection officer or another contact point, and describe the likely consequences and the measures taken or proposed.
- The controller must document any personal data breaches, including the facts, their effects and the remedial action taken.
- When a 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.
- That communication is not required where protection measures such as encryption rendered the data unintelligible to unauthorised persons, where subsequent measures ensure the high risk is no longer likely to materialise, or where it would involve disproportionate effort, in which case a public communication or similar equally effective measure is required instead.
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’.
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.
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.
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.