Legally sound reporting procedures for data breaches under the GDPR

GDPR Breach Notification: Reporting Process Guide

Structured processes for the timely and legally sound notification of data breaches to supervisory authorities and affected individuals in accordance with Art. 33 and 34 GDPR.

  • 01Timely notification within 72 hours to supervisory authorities
  • 02Structured assessment of reporting obligations and risk assessment
  • 03Legally sound notification of affected individuals in high-risk cases
  • 04Complete documentation for compliance evidence
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

How to Report Data Breaches on Time and in Full Compliance With GDPR

The GDPR requires data breaches to be reported to the competent supervisory authority within 72 hours. A clearly defined notification process is essential for meeting deadlines, avoiding fines, and properly informing affected individuals. We develop practical, proven reporting procedures that fully meet the requirements of Article 33 and Article 34 GDPR.

We support you in developing and implementing legally sound reporting processes for data breaches that fully comply with GDPR requirements and are practically implementable.

2 service modules

Service scope

01

Incident Response Process Design

Development of structured procedures for the identification, assessment, and reporting of data breaches.

  • Definition of incident response teams and escalation paths
  • Assessment criteria for reporting obligations pursuant to Art. 33 GDPR
  • Schedules and deadlines for the 72-hour notification
  • Integration into existing IT security processes
02

Notification of Affected Individuals — Art. 34 GDPR

Structured processes for notifying affected individuals in cases of high risk to their rights and freedoms.

  • Risk assessment for notification of affected individuals
  • Templates for clear and comprehensible notifications
  • Communication channels and timing strategies
  • Documentation of notification measures

5 phases

Our Approach

We work with you to develop tailored reporting processes that meet both legal requirements and are practically implementable.

  1. Analysis of organizational structures and existing processes

  2. Definition of roles and responsibilities in the reporting process

  3. Development of structured assessment and decision criteria

  4. Implementation of processes with practical tools

  5. Testing and continuous improvement of procedures

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

Our Expertise

  • 01In-depth knowledge of GDPR reporting obligations and supervisory practice
  • 02Experience in implementing efficient incident response processes
  • 03Proven templates and checklists for reporting procedures
  • 04Close collaboration with data protection officers and legal departments

Legal Notice

Data breaches must be reported to the supervisory authority within 72 hours. Late or omitted notifications can result in substantial fines — up to 10 million euros or 2% of global annual turnover.

10 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about GDPR Processes for Reporting Data Breaches

When must a data breach be reported under GDPR?

Under Article 33 GDPR, a personal data breach must be reported to the competent supervisory authority without undue delay, and no later than 72 hours after becoming aware of it. The notification obligation does not apply if the breach is unlikely to result in a risk to the rights and freedoms of natural persons. If the deadline is exceeded, the delay must be justified.

What information must a breach notification to the supervisory authority include?

Under Article 33(3) GDPR, the notification must contain at minimum: a description of the nature of the breach including the categories and approximate number of affected individuals and data records, the name and contact details of the Data Protection Officer, a description of the likely consequences, and the measures taken or proposed to address and mitigate the effects of the breach.

When must affected individuals be notified about a data breach?

Under Article 34 GDPR, affected individuals must be notified without undue delay when the breach is likely to result in a high risk to their rights and freedoms. The notification must use clear and plain language. It may be waived if appropriate safeguards such as encryption were in place, or if subsequent measures have eliminated the high risk.

What does a structured data breach notification process look like?

A structured process typically involves: first, detection and internal escalation to the Data Protection Officer. Second, assessment of whether notification is required and the level of risk to affected individuals. Third, timely notification to the supervisory authority with all required information. Fourth, evaluation of whether affected individuals must be informed. Fifth, comprehensive documentation of all facts, impacts, and remedial measures.

What happens if the 72-hour deadline is not met?

A late or omitted notification can result in fines of up to 10 million euros or 2 percent of global annual turnover under Article 83(4) GDPR. If there is a delay, the notification must be accompanied by reasons for the delay. The GDPR allows phased reporting, meaning an initial preliminary notification can be submitted and supplemented later as more information becomes available.

What documentation obligations apply to data breaches?

Under Article 33(5) GDPR, the controller must document every data breach, including all facts, effects, and remedial actions taken. This documentation must enable the supervisory authority to verify compliance. Even breaches that do not trigger a notification obligation must be documented to demonstrate that the decision not to report was justified.

How does notification to the supervisory authority differ from informing affected individuals?

Notification to the supervisory authority under Article 33 GDPR is required for any breach posing a risk and includes detailed technical information. Notification to affected individuals under Article 34 GDPR is only triggered when there is a high risk and must communicate the nature of the breach, potential consequences, and protective measures in plain language. The two obligations have different thresholds and audiences.

What must be considered for cross-border data breaches?

For cross-border breaches, the lead supervisory authority at the controller's main establishment in the EU must be notified. When individuals in multiple member states are affected, the consistency mechanism applies. Organizations need pre-defined reporting channels and clear responsibilities to meet the 72-hour deadline even for complex, multinational incidents.

What role does the data processor play in the notification process?

Under Article 33(2) GDPR, the processor must notify the controller without undue delay after becoming aware of a data breach. The obligation to notify the supervisory authority remains with the controller. The data processing agreement should specify concrete reporting timelines, contact persons, and the processor's information obligations.

How do you assess whether a data breach must be reported?

The risk assessment considers the type of data affected, the number of individuals involved, the severity of potential consequences, and whether the data was protected by encryption or other measures. If the assessment concludes there is likely no risk to the rights and freedoms of affected individuals, the notification obligation to the supervisory authority does not apply. The assessment and its outcome must be documented in all cases.