United Kingdom version. Written for UK organisations: the ICO 72-hour clock running from awareness, communicating high-risk breaches to individuals, NCSC reporting, Action Fraud, and sector regulators. US version
Incident Response Checklist (UK)
A notifiable personal data breach goes to the ICO within 72 hours of awareness, including weekends. Report cyber incidents to the NCSC and Action Fraud.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Incident Response Checklist?
The UK clock that dominates incident response is 72 hours from becoming aware of a notifiable personal data breach to notifying the ICO, and awareness is not the same as full understanding. It starts when you have a reasonable degree of certainty that a breach has occurred, not when the investigation concludes, and it does not pause for weekends or bank holidays.
Where a breach is likely to result in a high risk to people, you must also communicate it to the affected individuals without undue delay, in clear language, describing the likely consequences and what you are doing. Both duties exist independently of whether the incident was your fault.
Every breach must be recorded internally whether or not it is reportable, and the ICO expects to see that record. An organisation with no breach log is demonstrating an absence of process rather than an absence of breaches.
- Built on the ICO 72-hour clock running from awareness
- Covers communicating high-risk breaches to individuals
- Includes NCSC, Action Fraud and sector regulator reporting
- Flags cyber insurance notification and panel responder clauses
- Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Updated
How to use the Incident Response Checklist
- Start the 72-hour clock at awareness, and decide reportability on the facts you have rather than waiting for certainty.
- Contain by isolating rather than rebuilding, and preserve logs and volatile evidence before they are lost.
- Assess scope: what data, how many people, encryption status, and whether special category or children’s data is involved.
- Notify the ICO where notifiable, tell individuals where risk is high, and log the breach either way.
- Check your cyber insurance notification clause and panel requirements before engaging responders.
Worked examples
Breach discovered on a Friday evening
Input
Clock section, Essentials only
Output
ICO notified within 72 hours including the weekend
The 72 hours runs from awareness and does not pause for weekends or bank holidays, which is why a Friday discovery is the hardest case to handle well.
Instinct to rebuild the compromised server
Input
Containment items
Output
Isolated instead, with logs preserved
Rebuilding destroys the evidence needed to establish scope, and scope is what determines whether and how you must notify.
Own forensics firm engaged immediately
Input
Insurance items
Output
Policy panel requirement checked first
Cyber policies often require notification within a short period and the use of panel responders, and engaging your own firm first can prejudice the claim.
Ransomware demand received
Input
Ransomware items
Output
NCSC contacted; sanctions exposure considered
Payment does not guarantee recovery and may breach sanctions depending on the recipient, which is a legal exposure on top of the commercial question.
Background and insight
Reporting beyond the ICO depends on the incident: the NCSC takes reports of significant cyber incidents and can provide support, Action Fraud handles fraud and cybercrime for England, Wales and Northern Ireland with Police Scotland for Scotland, and regulated sectors have their own obligations, including financial services firms reporting operational incidents to their regulator with their own timescales.
The first hour technically should be containment without destroying evidence, which is the tension nobody plans for: pulling a server offline can lose volatile evidence, and wiping a compromised machine destroys the ability to establish scope. Isolating rather than rebuilding, and preserving logs before they rotate, is the sequence that preserves both.
Scope assessment drives the notification decision: what data, how many people, whether it was encrypted and whether the key was also lost, whether it has been accessed or merely exposed, and whether the people affected include children or involve special category data. Those factors determine both reportability and risk level.
Communications need preparing before the incident because the pressure during one is extreme. Holding statements, a named spokesperson, a decision on what the website will say, and a plan for employees who will be asked by customers all belong in the plan rather than in the first hour.
For ransomware specifically, UK guidance is clear that paying does not guarantee recovery and may breach sanctions depending on who receives the money, which is a legal exposure beyond the commercial one. The NCSC does not encourage payment and will provide support.
Insurance is the practical item organisations forget: a cyber policy typically requires notification within a short period and may require using the insurer’s panel responders, and engaging your own forensics firm first can prejudice the claim. Reading that clause before an incident is what preserves cover.
Afterwards, the post-incident review matters more than the incident log: what the root cause was, what control failed, what is being changed, and when it will be verified. The ICO looks for that as much as for the notification itself.
Common use cases
The first hour
Containment that preserves evidence.
The notification decision
Reportability, high risk and the clock.
Who else to tell
NCSC, Action Fraud and sector regulators.
Before anything happens
Insurance clauses and holding statements.
Tips and limitations
- The 72 hours starts at awareness, not at understanding, and weekends count.
- Isolate rather than rebuild. Rebuilding destroys the scope evidence.
- Log every breach, including the ones you decide not to report.
- Check the insurance panel clause before you call a forensics firm.
- Paying ransomware may breach sanctions as well as failing to work.
Sources and further reading
- Data protection and your business, UK Government. Breach notification duties and the 72-hour requirement
- Information Commissioner’s Office, UK Government. Reporting breaches and regulatory expectations
- National Cyber Security Centre, National Cyber Security Centre. Incident reporting, ransomware guidance and support
- Report internet scams and phishing, UK Government. Action Fraud and related reporting routes
Frequently asked questions
When does the 72-hour clock start?
When you become aware of the breach, meaning you have a reasonable degree of certainty that one has occurred, rather than when the investigation concludes. It does not pause for weekends or bank holidays.
Do I always have to tell the people affected?
Where the breach is likely to result in a high risk to their rights and freedoms, yes, without undue delay and in clear language describing likely consequences and your response. Where risk is lower, ICO notification may still be required without individual communication.
Who else should be told?
The NCSC for significant cyber incidents, Action Fraud for fraud and cybercrime in England, Wales and Northern Ireland with Police Scotland in Scotland, and your sector regulator where one applies, which may have its own shorter timescale.
Should I take the system offline immediately?
Isolate rather than rebuild. Pulling a machine can lose volatile evidence and rebuilding destroys the ability to establish scope, which is what the notification decision depends on. Preserve logs before they rotate.
What does my cyber insurance require?
Typically notification within a short defined period and often the use of the insurer’s panel responders. Engaging your own forensics firm first can prejudice the claim, so the clause needs reading before an incident rather than during one.
Should we pay a ransomware demand?
UK guidance does not encourage it: payment does not guarantee recovery and may breach sanctions depending on who ultimately receives the funds, which adds legal exposure to the commercial risk. The NCSC provides support instead.
Is there an in-depth guide to the Incident Response Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.