Data breaches: what UK businesses are legally required to do within 72 hours
If your business suffers a personal data breach, the clock starts the moment you become aware of it, not when you've finished investigating. Here's what UK GDPR actually requires, and what to do in the first hour.
In short
- UK GDPR gives you 72 hours from becoming aware of a qualifying breach to notify the ICO, unless it's unlikely to risk people's rights and freedoms, and "becoming aware" starts the clock, not "finishing the investigation."
- A reportable breach is any breach of confidentiality, integrity or availability of personal data: that includes a misdirected email or a lost laptop, not only a hack.
- Where the breach is likely to cause high risk to the people affected, they must also be told directly, without undue delay, in plain language.
What counts as a reportable breach
Under UK GDPR, a personal data breach is any breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. That's a much wider definition than "we got hacked". It also covers:
- An email containing personal data sent to the wrong recipient.
- A lost or stolen laptop, phone or USB drive containing personal data, especially if unencrypted.
- A ransomware attack that encrypts (not even necessarily steals) personal data, since it affects availability.
- Personal data accidentally published or left accessible, such as a misconfigured file-sharing link.
- Personal data deleted or altered without a valid backup, where that loss can't be reversed.
The 72-hour clock, precisely
You must notify the ICO without undue delay and, where feasible, within 72 hours of becoming aware of the breach, unless it's unlikely to result in a risk to the rights and freedoms of the people affected. Two details catch businesses out:
- "Becoming aware" starts the clock, not the point at which you've finished your investigation. If you can't complete it in time, you report what you know within 72 hours and provide further information in phases as it becomes available: you don't wait and report everything at once late.
- Weekends and holidays count. The 72 hours is a continuous period, not 72 working hours.
If you miss the window, you must include an explanation for the delay in your notification. A late report with a genuine explanation is treated very differently to no report at all.
What the ICO report needs to include
- The nature of the breach, including (where possible) the categories and approximate number of people and records affected.
- The name and contact details of your data protection officer or another relevant contact point.
- The likely consequences of the breach.
- The measures taken, or proposed, to address the breach and mitigate its effects.
Keeping an internal breach log, even for incidents you decide not to report, is itself a requirement, and is usually the first thing the ICO asks for if it ever investigates separately.
When you must also tell the people affected
Separately from notifying the ICO, you must also tell the affected individuals directly, without undue delay, if the breach is likely to result in a high risk to their rights and freedoms: for example, a risk of identity theft, financial loss, or discrimination. This notification must be in clear, plain language, describe the likely consequences, and explain the measures taken or recommended in response.
There are limited exceptions: for instance, if the data was properly encrypted and the key wasn't compromised, or if direct notification would involve disproportionate effort, in which case a public communication can be used instead.
If employee personal data is involved in the breach, your obligations to those employees are the same as to any other individual under UK GDPR: see our guide on why employee data protection matters for your business for the broader picture.
What to do in the first hour
- Contain it. Isolate affected systems, revoke compromised credentials, or stop the data flow if it's ongoing (e.g. recall or ask the recipient to delete a misdirected email).
- Record the time you became aware: this is the actual start of your 72-hour clock, and you'll need it in your report.
- Loop in whoever handles this (your DPO, IT lead, or outside counsel) immediately, not once you've "figured out how bad it is."
- Start the breach log, even with incomplete information. You can update it as the picture becomes clearer.
- Assess risk to individuals to decide whether ICO notification, individual notification, both or neither are required, and document that decision either way.
Frequently asked questions
No, only where it's likely to result in a risk to people's rights and freedoms. You must still keep an internal record of every breach, including ones you assess as not requiring notification, and be able to explain that decision.
A late notification with a genuine, documented explanation is treated differently to failing to report at all. Include the reasons for the delay in your notification rather than skipping it.
Your processors are contractually required to notify you without undue delay once they become aware of a breach: your 72-hour clock as the controller starts from when you, the controller, become aware, which your processor's notification to you triggers.
Sources
- Report a breach (Information Commissioner's Office)
- Personal data breaches guidance (Information Commissioner's Office)
- Data Protection Act 2018 (legislation.gov.uk)