Breach notices
Data breach and incident notification in the European Union
Short answer
- GDPR authority deadline
- 72 hours where feasible, with reasons if later 1
- GDPR notice to people
- Without undue delay when the risk is high 1
- NIS2 early warning
- 24 hours after becoming aware of a significant incident 2
- NIS2 final report
- One month after the incident notification 2
- Telecoms providers
- 24 hours after detection, where feasible 4
- DORA start date
- 17 January 2025 3
The GDPR duty: Articles 33 and 34
The General Data Protection Regulation has applied since 25 May 2018 1. Article 33 says the controller must notify the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach 1. No notice is needed where the breach is unlikely to result in a risk to the rights and freedoms of natural persons 1. A late notice must carry reasons for the delay 1.
A processor does not report to the authority under Article 33. It must notify the controller without undue delay after becoming aware of the breach 1. Information can be given in phases where it is not all available at once 1. The controller must document every breach, its effects and the remedial action taken, so the authority can check compliance 1.
Article 34 covers the people affected. When a breach is likely to result in a high risk to them, the controller must tell them without undue delay, in clear and plain language 1.
- Exception 1: the data was protected by measures such as encryption that make it unintelligible to anyone not authorised to access it 1.
- Exception 2: the controller has taken later measures so the high risk is no longer likely to materialise 1.
- Exception 3: individual notice would involve disproportionate effort. A public communication or similar measure is then used instead 1.
- The authority can require the controller to tell people, or decide that an exception applies 1.
NIS2: incident reporting for critical sectors
Directive (EU) 2022/2555, known as NIS2, was adopted on 14 December 2022 2. Member States had to adopt and publish national measures by 17 October 2024 and apply them from 18 October 2024 2. NIS2 repealed the earlier NIS Directive 2016/1148 from 18 October 2024 2.
NIS2 reports go to the national CSIRT or competent authority and concern significant incidents, not only personal data 2. The CSIRT or authority should reply within 24 hours of the early warning where possible, with initial feedback 2. Trust service providers must notify within 24 hours of becoming aware of a significant incident affecting their trust services 2.
| NIS2 stage | Deadline | Content |
|---|---|---|
| Early warning | Within 24 hours of becoming aware 2 | Whether unlawful or malicious acts are suspected and any cross-border impact 2 |
| Incident notification | Within 72 hours of becoming aware 2 | Initial assessment of severity and impact, and indicators of compromise where available 2 |
| Final report | Not later than one month after the incident notification 2 | The items listed in point (d) of Article 23(4) 2 |
| Progress report | When the incident is ongoing at the final report date 2 | Final report within one month of handling the incident 2 |
Fines for missed notices
Under GDPR Article 83(4), breaches of the controller and processor duties in Articles 25 to 39 can bring fines up to EUR 10,000,000 or 2% of total worldwide annual turnover of the preceding financial year, whichever is higher 1. Articles 33 and 34 fall within that range of articles 1.
Under NIS2, Member States must set maximum fines of at least EUR 10,000,000 or 2% of worldwide turnover for the Directive's top tier of entities that break the reporting duty in Article 23 2. For important entities, the minimum maximum is EUR 7,000,000 or 1.4% of worldwide turnover 2.
Telecoms and financial firms
Providers of publicly available electronic communications services follow Commission Regulation (EU) No 611/2013 of 24 June 2013 4. They must notify all personal data breaches to the competent national authority, no later than 24 hours after detection where feasible 4. If information is missing, they can send an initial notice within 24 hours and a second notice within three days after the initial one 4.
Financial entities report major ICT-related incidents under the Digital Operational Resilience Act, Regulation (EU) 2022/2554, which applies from 17 January 2025 3. DORA sets three stages: an initial notification, an intermediate report and a final report once the root cause analysis is complete 3. Significant credit institutions report to their national competent authority, which passes the report to the ECB 3. The European Supervisory Authorities must publish a yearly anonymised report on major ICT-related incidents 3.
Guidance from the EDPB
The European Data Protection Board publishes Guidelines 9/2022 on personal data breach notification under the GDPR 5. The current text is version 2.0, which followed a public consultation on version 1 with comments due by 29 November 2022 5. The Board publishes a short summary as well, titled Guidelines at a Glance: personal data breaches, what to do 5.
Common questions
How long does a company have to report a data breach in the EU?
Without undue delay and, where feasible, within 72 hours of becoming aware of it, under GDPR Article 33 1.
Does every breach have to be reported to the regulator?
No. A breach that is unlikely to result in a risk to people's rights and freedoms does not need to be notified, but it must still be documented 1.
When must affected people be told under the GDPR?
When the breach is likely to result in a high risk to them, without undue delay 1.
What is the NIS2 24 hour early warning?
A first alert to the CSIRT or authority within 24 hours of becoming aware of a significant incident, followed by a 72 hour notification and a final report 2.
Which rule applies to banks and insurers?
DORA, which applies from 17 January 2025 and requires initial, intermediate and final reports on major ICT-related incidents 3.
Rules and charges change. Check the official source linked on this page before you pay or travel. Spotted an error? Email hello@noticeofrecord.com.
Sources
- EUR-Lex: Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (General Data Protection Regulation)
- EUR-Lex: Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 (NIS 2 Directive)
- EUR-Lex: Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector
- EUR-Lex: Commission Regulation (EU) No 611/2013 of 24 June 2013 on the measures applicable to the notification of personal data breaches
- European Data Protection Board: Guidelines 9/2022 on personal data breach notification under GDPR
Related
- Data breach notification laws compared
How breach notice rules differ in the EU, UK, US, Australia, Canada and India: who must notify, the deadline and who receives the notice.
- Data breach and incident notification in the United Kingdom
UK breach reporting duties under the UK GDPR, the Data Protection Act 2018, PECR and the NIS Regulations, with deadlines and fine caps.
- How to check whether a notice was given
Where to look up official notices: state breach lists, the HHS breach portal, SEC EDGAR, FDA warning letters, FCA notices, WARN reports and recall lists.
- What a formal notice is
What makes a notice formal: who gives it, who receives it, the deadline and the form. Breach, recall, regulatory, layoff and court notices compared.