Insights · Incident response

Cyber incident response for UK regulated firms: the first 72 hours

A practical playbook for the first three days of a cyber attack: what to do in the first hour, who to notify and by when (FCA, PRA, SRA, ICO, NCSC, Report Fraud, your bank and your insurer), and how to prepare now.
The short answer

In the first hour, contain the attack, preserve evidence and call your IT provider and your insurer’s incident line. If money has been sent to a fraudster, call your bank immediately. Within the first day, decide whether the incident must be reported to your regulator: the FCA and PRA expect prompt notice of significant incidents now, and from 18 March 2027 most FCA firms must report within 24 hours of deciding an incident meets the PS26/2 threshold. Report personal data breaches to the ICO within 72 hours of becoming aware where feasible, and report the crime to Report Fraud.

Key points
  • Contain first, but do not wipe machines or delete mailboxes: you will need the evidence.
  • Call your insurer early. Many cyber policies require you to use their incident response team.
  • FCA and PRA: notify significant incidents promptly now; from 18 March 2027, within 24 hours of deciding the PS26/2 threshold is met (4 hours from detection for payment service providers).
  • SRA: report serious breaches and any attack that affects or could affect clients, promptly.
  • ICO: report a notifiable personal data breach without undue delay and, where feasible, within 72 hours.

The first hour: contain and preserve

  1. Call your IT provider and start an incident log with times, what you saw and who did what. Everything you record now helps every report you make later.
  2. Contain. Disconnect affected devices from the network rather than switching them off, reset compromised passwords, revoke sign-in sessions and remove any mail forwarding or inbox rules the attacker created.
  3. Preserve evidence. Do not wipe laptops, delete mailboxes or restore over affected systems until logs and images have been captured.
  4. Call your insurer’s incident line. Policies often require early notice and use of their appointed responders and lawyers.
  5. If money has moved, call your bank now. Ask it to contact the receiving bank. The chance of recovering funds falls quickly after the first few hours.
  6. Decide who leads. One person coordinates, one person owns regulatory decisions, and one person handles communications.

Who to notify, and by when

WhoWhenNotes
Your bankImmediately, if funds were sent or accounts are at riskAsk for a recall and for the receiving bank to be contacted.
Your insurerAs early as possible, per your policyLate notice can affect cover.
FCAPromptly for significant incidents (Principle 11, SUP 15.3). From 18 March 2027: within 24 hours of deciding the PS26/2 threshold is metPayment service providers: within 4 hours of detection under PS26/2. Some firms also send updates and a final report.
PRAPromptly, for dual-regulated firmsThe PRA has aligned incident reporting rules for the firms it supervises.
SRAPromptlySerious breaches under Rule 3.9, and attacks that affect or could affect clients.
ICOWithout undue delay and, where feasible, within 72 hours of becoming awareFor personal data breaches likely to risk people’s rights and freedoms. Record your reasoning even if you decide not to report.
Affected individualsWithout undue delayWhere a breach is likely to result in a high risk to them.
Report FraudAs soon as practicalThe national cyber crime and fraud reporting service run by City of London Police, which replaced Action Fraud in December 2025: reportfraud.police.uk or 0300 123 2040.
NCSCFor significant incidentsThe National Cyber Security Centre gives confidential support and is not a regulator.

The clocks run in parallel, not one after another. The 72-hour ICO window and a 24-hour regulatory window can both start on the first day, so have your decision-makers lined up in advance.

Deciding whether it is reportable

Under PS26/2, an operational incident must be reported to the FCA when you reasonably believe it could cause intolerable harm to consumers, threaten the safety and soundness of your firm or others, or affect market integrity or confidence. The 24-hour clock starts when you make that decision, so make it promptly and write down why. For the ICO, the question is whether the breach is likely to result in a risk to individuals’ rights and freedoms. If you are unsure, it is usually safer to make an initial report and update it later. Our FCA cyber security guide covers the thresholds in more detail.

Days one to three: investigate, recover, communicate

  • Investigate: how the attacker got in, what they accessed, whether data left the business and whether they still have access.
  • Recover: restore from clean backups, rebuild affected devices, and tighten the control that failed before reconnecting.
  • Communicate: give clients and staff clear, honest updates through a channel you trust. Assume a compromised mailbox is still being watched until proven otherwise.
  • Update regulators: send follow-up information as you learn more, and keep copies of everything you submit.

If it is ransomware

Paying a ransom does not guarantee you get your data back, may mark you as a future target and, if the criminals are subject to sanctions, can be an offence. The government has confirmed it intends to legislate to ban ransom payments by public bodies and critical national infrastructure and to require other organisations to report attacks and tell the authorities before paying. At the time of writing those proposals are not yet law, but regulators, insurers and the NCSC all expect you to involve them before making any decision. The best defence is a backup the attacker cannot reach, tested regularly.

Prepare now: a one-page plan

  • Names and mobile numbers for your incident lead, regulatory decision-maker and communications lead, plus deputies.
  • Your IT provider’s 24/7 number, your insurer’s incident line and policy number, and your bank’s fraud line.
  • How to report to your regulator, who has access to the portal, and the PS26/2 thresholds written in plain English.
  • How to reach staff and clients if email is down.
  • Where your backups are and how long a full restore takes.
  • A date for your next tabletop exercise. An hour each year is enough to find the gaps.

We help clients write and test this plan as part of our cyber security services.

Sources and further reading

Written by
CEO, Cre8 IT
Rob Crossley is CEO of Cre8 IT, a managed IT and cyber security company that has supported businesses across the UK, the UAE and Saudi Arabia since 2012. Cre8 IT is certified to ISO 27001:2022 and ISO 9001 and is a certified Microsoft Partner.
FAQ

Frequently asked questions

How long do we have to report a cyber attack to the FCA?

Today, significant incidents must be reported promptly under Principle 11 and SUP 15.3. From 18 March 2027, PS26/2 requires most firms to report within 24 hours of deciding an incident meets a threshold, and payment service providers within 4 hours of detection.

Do we have to report every data breach to the ICO?

No. You must report a personal data breach that is likely to result in a risk to people’s rights and freedoms, without undue delay and, where feasible, within 72 hours of becoming aware. Record every breach and your reasoning, even if you do not report it.

Is it illegal to pay a ransom in the UK?

Not in general for private firms, but paying a sanctioned group can be an offence, and the government has said it will legislate to ban payments by public bodies and critical national infrastructure and to require advance notice from others. Speak to your insurer, lawyers and the NCSC before making any decision.
Related guides

Keep reading

Each guide links to the regulator’s own text and shows when it was last reviewed.
FCA cyber security

FCA cyber security requirements in 2026: what firms must actually do

The rules behind the FCA’s expectations, PS26/2 incident reporting and the controls smaller firms need.
8 min read · Reviewed 15 October 2026
Law firms

Cyber security for law firms: SRA expectations, payment diversion and email compromise

What the SRA expects, when to report and how to stop payment diversion.
8 min read · Reviewed 15 October 2026
Vendor management

IT vendor and outsourcing management for FCA, PRA and SRA regulated firms

A register, tiering, due diligence, contract terms, ongoing oversight and the new third-party reporting rules.
4 min read · Reviewed 25 September 2026

Talk to a specialist about your obligations

Tell us about your firm and your regulator, and we will suggest a practical first step, whether that is a gap assessment or ongoing support.