Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Breach Notification?

Breach notification is the legal duty to tell a regulator, and sometimes the people affected, that personal data has been lost, exposed, or altered. In the UK the clock runs for 72 hours.

Illustration for the cybersecurity term Breach Notification
Home / Blog / Cybersecurity Terms / What Is Breach Notification?
17 November 2026

What Is Breach Notification?

What Is Breach Notification?

Breach notification is the obligation to report a personal data breach to a supervisory authority and, where the risk is high enough, to the individuals affected. In the United Kingdom the duty comes from Article 33 of the UK GDPR, and it bites 72 hours after the controller becomes aware of the breach, not 72 hours after the investigation finishes. That distinction catches out more organisations than any other part of the regime.

When the Clock Starts

Awareness means having a reasonable degree of certainty that a security incident has compromised personal data. A single alert is not awareness; a confirmed exfiltration of a customer database is. Between those two points sits a short period of verification, and the Information Commissioner’s Office expects that period to be measured in hours rather than days. Weekends and bank holidays do not pause the count.

A breach is not limited to data being stolen. Loss of availability counts, so ransomware that encrypts the only copy of a personnel file is reportable even if nothing left the building. Accidental disclosure counts, which is why a misdirected email with special category data in it accounts for a large share of the reports the ICO receives each year.

What the Report Must Contain

Article 33(3) sets out four elements: the nature of the breach including the categories and approximate number of data subjects and records involved, the contact point for more information, the likely consequences, and the measures taken or proposed. Article 33(4) allows phased reporting where the full picture is not yet available, so an incomplete report filed inside the deadline is far better than a complete one filed late. Article 33(5) requires you to document every breach internally, including those you decide not to report, with the reasoning — the ICO asks to see that register during an investigation.

If you conclude the breach is unlikely to result in a risk to people’s rights and freedoms, you need not notify, but you must be able to defend the assessment. Record who made the decision, on what evidence, and when.

The Other Deadlines You Are Probably Subject To

If your group includes a Turkish entity, add another clock. Under a Board decision of the Turkish data protection authority, a controller subject to Law No. 6698 (KVKK) must notify the Board within 72 hours of becoming aware and inform affected individuals in the shortest reasonable time; unlike the UK regime, there is no risk threshold that removes the duty to report, so incidents the ICO would never see still have to be filed in Ankara.

Why Accuracy Matters More Than Speed Alone

UK enforcement has focused on the security failures behind the breach rather than on late reporting, but the report shapes the investigation. The ICO fined Interserve £4.4 million in October 2022 and Advanced Computer Software Group £3.07 million in March 2025, in both cases citing inadequate technical measures found during the follow-up. A report that understates the scope and is corrected three times tells the regulator something about your incident management before anyone looks at your controls.

Write the notification template, the decision tree, and the internal escalation path into your incident response plan before you need them, and rehearse the 72-hour decision in a tabletop exercise. Our regulation and compliance services include reviewing that process against UK GDPR and sector rules.

FAQ – Frequently Asked Questions

Do I Have to Report Every Personal Data Breach to the ICO?

No. The duty applies where the breach is likely to result in a risk to the rights and freedoms of individuals. A single internal email sent to the wrong colleague usually falls below that line, while exposure of financial or health data rarely does. You must still record every breach internally, including the ones you decide not to report, with the reasoning behind the decision.

What Happens if I Miss the 72-Hour Deadline?

Report anyway, and include the reasons for the delay, which Article 33(1) expressly requires. Late notification is a breach of the regulation in its own right, but the ICO has generally treated it as an aggravating factor rather than the main offence. Filing a partial report inside the window and updating it afterwards is always better than waiting for certainty.

Does Ransomware Count as a Notifiable Breach?

Frequently, yes. Loss of availability is a breach under UK GDPR, so encryption of personal data you cannot restore promptly is reportable even without exfiltration. Modern ransomware usually steals data before encrypting it, which makes the confidentiality question live as well. Assume notifiability and work to disprove it rather than the other way round.

Who Notifies When a Processor Is Breached?

The controller notifies the ICO. Under Article 33(2) the processor must tell the controller without undue delay, and the contract should set a deadline short enough for the controller to meet its own 72 hours. In practice a 24-hour processor deadline is common. Check that your supplier contracts say so, because many still repeat the statutory wording without a figure.

Related Terms

You May Be Interested In These

What Are GIAC Certifications?

Cybersecurity Terms

17 November 2026

What Are GIAC Certifications?

Read More
What Is Railway Signalling Security?

Cybersecurity Terms

17 November 2026

What Is Railway Signalling Security?

Read More
What Is IPsec?

Cybersecurity Terms

17 November 2026

What Is IPsec?

Read More