Incidents and Breaches

How to recognise an incident, assess the risk to individuals and decide whether to report it, with the deadlines that apply.

Legal status: November 2026

Support during an incident

See also: DPO and GDPR NIS2 and KSC Training and workshops AI Act

A structured response to incidents and breachesThe first hours decide what you are able to demonstrate later. If you want the sequence of steps agreed before anything happens, let us talk about your processes. Explore the service

A CSIRT report is four documents — LabLogic article graphic by Michał Rutkowski
Incidents and Breaches

What does a significant incident report to a CSIRT contain?

A significant incident report is not one document but a sequence of submissions to the CSIRT via S46. An early warning within 24 hours and an incident notification within 72 hours of detection, an interim report at the CSIRT’s request and a final report within a month. Incomplete knowledge is no reason to wait.

What should a breach register contain? — LabLogic article graphic by Michał Rutkowski
Incidents and Breaches

What should a personal data breach register contain?

Article 33(5) GDPR requires documentation, not a register in a prescribed form. The documentation has to let the supervisory authority verify compliance with the whole article, which is why the entries that call for the most content are those on breaches the controller did not notify.

What to do after detecting an incident? — LabLogic article graphic by Michał Rutkowski
Incidents and Breaches

What to do after detecting an incident?

First confirm the event and secure the evidence, then limit the effects, and run the legal assessment in parallel from the first hours. Detection starts several independent clocks, depending on the entity’s status and whether personal data are affected. In technical work the order of steps matters more than speed.

Scroll to Top