← Back to blog

Phishing Incident Response: A Practical UK Guide

November 6, 2026
Phishing Incident Response: A Practical UK Guide

When a phishing email gets through, the first hour decides how big the problem becomes. Confirm what the message is, find out who received it and who interacted with it, contain any compromised account or device, preserve evidence, and decide whether the ICO must be told. If personal data is at risk, the ICO's reporting window is 72 hours from when you become aware of the breach. This guide walks UK small businesses, schools and charities through each step in order.

Solusec
Find Vulnerabilities Before They’re Exploited
Solusec provides expert-led penetration testing and practical cybersecurity support to help organisations identify vulnerabilities before they are exploited.
Explore penetration testing

Key Takeaways

  • Treat every report as real until triage says otherwise, and thank the person who reported it, even if they clicked.
  • Sort the incident into one of four levels: received only, received by many, clicked or entered details, or confirmed compromise. Your actions depend on the level.
  • If a user entered credentials, reset the password, end active sessions and check for mailbox forwarding rules before doing anything else.
  • A personal data breach likely to risk people's rights and freedoms must go to the ICO within 72 hours of you becoming aware of it.
  • Review every incident afterwards: MFA, email filtering, DMARC and a simple reporting route prevent the next one.

Table of Contents

Step 1: Receive the report and triage it

Your response starts the moment someone says "this looks odd". The NCSC advises having a clear, simple and quick process for reporting phishing, giving fast feedback on what action was taken, and supporting users who report, even when they have already clicked. People who fear blame stay quiet, and silence is what turns a single click into a breach.

Keep the first triage short. Ask the reporter four things:

  1. What did the message say, and when did it arrive?
  2. Did you click a link, open an attachment or reply?
  3. Did you type a password, card number or any other details into a page?
  4. Which device and account were you using?

Tell the reporter not to delete anything yet, and not to click anything else. Signs that a message is phishing include pressure to act quickly, an unexpected link, a request for personal information, or an email that looks like it comes from a genuine organisation but feels wrong.

If the message turns out to be a genuine phish, forward it to the NCSC's Suspicious Email Reporting Service at report@phishing.gov.uk. The NCSC says it analyses the email and the websites it links to, and may work with hosting companies to take malicious sites down. That is a useful public service and costs you one forward.

Step 2: Decide how serious it is

Not every phishing email is an incident that needs a full response. A useful way to sort them comes from a New Zealand public body, the Tertiary Education Commission. Its phishing response flow diagram separates four situations, which translate well to UK organisations:

LevelWhat happenedTypical response
1. A phish, not an eventOne person received it and did nothingDelete, report to SERS, give feedback
2. An event, not a breachSeveral people received it, nobody interactedRemove it from every mailbox, block the sender and any linked domain, warn staff
3. A breach, not yet a compromisePeople clicked or entered details, no attacker activity seen yetReset credentials, end sessions, scan devices, watch closely
4. CompromisedThe attacker has used the access to reach data or systemsFull incident response: contain, investigate, preserve evidence, assess notification duties

Write the level in your incident log with the time you decided it. You can raise it later as facts emerge. Never lower it without a recorded reason.

Step 3: Scope who received it and who interacted

To scope an incident properly, you need to answer the same questions whether you have one mailbox or five hundred. Microsoft's phishing investigation playbook sets out a five-stage workflow:

  1. Identify and confirm the phishing message, including its Message-ID.
  2. Scope the impact: who received it and whether it was delivered.
  3. Assess user interaction and credential exposure.
  4. Identify downstream activity, such as lateral movement or follow-on attacks.
  5. Contain the threat and prevent recurrence.

If you use Microsoft 365 or Google Workspace, your admin console can search every mailbox for the same sender, subject or link and remove matching messages. If you have no such tooling, ask your IT provider to do it the same day. Do not rely on staff each deleting their own copy.

The NCSC also advises using a security logging system to pick up incidents that users are not aware of. Some people click and never mention it. Sign-in logs and mail logs are how you find them.

What to check once someone has interacted

For a confirmed breach, the New Zealand flow diagram lists three checks worth copying:

  • Suspicious account activity: sign-ins from unusual locations, unknown IP addresses or concurrent sessions.
  • New emails sent from the affected account, and any mail forwarding rules that have appeared.
  • Malware on the user's device, based on a scan.

Forwarding rules matter more than people expect. An attacker who cannot keep a session open will often create a rule that quietly copies incoming mail elsewhere. Resetting the password alone does not remove it.

Step 4: If someone clicked, opened a file or entered credentials

This is the case most readers are searching for. Act in this order:

  1. Disconnect the device if malware is possible. Take it off the network, but leave it powered on if your IT provider wants to take a forensic copy.
  2. Reset the password from a clean device. The NCSC advises changing passwords immediately if the same one is used on other accounts. Treat every account sharing that password as exposed.
  3. End all active sessions and tokens so the attacker is signed out, not just locked out of the next login.
  4. Check MFA settings. Attackers sometimes register their own authenticator or phone number. Remove anything the user does not recognise.
  5. Run a full antivirus scan. The NCSC recommends a full scan after opening a suspicious link or installing software.
  6. Look for forwarding rules and sent mail, as above.
  7. Contact the bank at once if payment details were shared. If money was lost, tell the bank and report it as a crime to Report Fraud in England, Wales and Northern Ireland, or to Police Scotland in Scotland, as the NCSC's guidance directs.

If an attachment was opened on a work laptop and you cannot be sure it is clean, do not just run a scan and hope. A device that may hold malware is rebuilt from a trusted image, not trusted again.

Step 5: Contain, eradicate and recover

The Chichester District Council phishing playbook, a public UK document, breaks the work into three phases that make a good checklist for any small organisation. The playbook describes:

Containment: identify impacted systems, block remote access tools and communication with command-and-control servers, quarantine affected systems, reset credentials and end active sessions.

Eradication: remove malware, rebuild systems from trusted backups or clean images, and reset suspected compromised accounts.

Recovery: scan for vulnerabilities, reset credentials and sessions again, enable MFA where it is not yet on, restore systems, data and services, monitor for suspicious activity and apply outstanding patches.

Three phases of phishing incident response

The NCSC's Response and Recovery Guide adds that resolving an incident may mean replacing infected hardware, restoring from backups, patching software and changing passwords. Know before an incident how to restore a backup, because working it out under pressure is slow.

Monitor for at least a few weeks after you think it is over. Credentials stolen in one phishing email are often used days later, or sold on.

Step 6: Preserve evidence and keep a log

Evidence is easy to destroy by accident when everyone is trying to help. The Chichester playbook says the initial investigation record should include relevant antivirus, system-event and network-monitoring logs, secured artefacts such as suspected malware and forensic copies of affected systems, and a record of ongoing actions.

In practice:

  • Save the original email as a file (not a screenshot) with full headers.
  • Record times in one time zone, with who did what.
  • Keep copies of mailbox audit and sign-in logs before they roll over.
  • Do not wipe a device until someone has decided whether a forensic image is needed.

This log is what you will rely on if you must explain yourself to the ICO, an insurer or a customer. It is also the raw material for your review.

If the incident goes beyond what your team can handle, our incident response service puts you in touch directly with experienced responders rather than a sales queue.

Step 7: Decide who must be told

The ICO and the 72-hour rule

If a phishing attack leads to a personal data breach, the ICO says organisations should report it within 72 hours of becoming aware of it. The clock runs from when you become aware, not from when the email arrived or when your investigation finishes. Under UK GDPR, that duty applies where the breach is likely to risk people's rights and freedoms. Where the risk to individuals is high, you must also tell the people affected without undue delay. If you want a plain explanation of how these reporting duties under UK GDPR work in a small business holding client data, that guide is a good starting point.

A failure to know this rule is common. The ICO reprimanded a small firm after a phishing attack. It had told its insurers and regulator within a day but did not report to the ICO until two weeks later, because it did not know about the 72-hour requirement. The ICO advised that staff responsible for data protection should be trained in reporting requirements. Put the rule in your plan and name who makes the call.

Report Fraud, the NCSC and others

  • Report Fraud and Police Scotland: report losses or fraud as a crime, as above.
  • NCSC: the NCSC's small business guidance covers reporting cyber incidents to Action Fraud (now Report Fraud), the ICO where applicable, and the NCSC.
  • Insurers: check your cyber policy. Many require prompt notice, and some provide incident response support.
  • Sector regulators and funders: schools, charities and regulated professions may have their own duties. Check with your regulator, trustees or governors.
  • Customers and staff: tell them what happened, what data was involved and what they should do, in plain words.

The Chichester playbook also says to report data breaches to the data protection officer and keep senior stakeholders updated about suspected or confirmed breaches involving personal or sensitive data. Even without a formal DPO, someone senior should own this decision and record the reasoning, including when you decide a report is not needed.

Our analysis of the UK breaches survey gives context on how common phishing is among UK businesses.

Step 8: Review and prevent the next one

After the incident, the NCSC says to review what happened, learn from mistakes and act to reduce the chance of repeat. Use the NCSC's four layers of phishing defence to frame the review:

  1. Make it hard for attackers to reach users. Filter or block incoming phishing email and honour sender-domain anti-spoofing policies, including DMARC.
  2. Help users spot and report phishing. Make reporting one click or one forward, and give feedback.
  3. Limit the damage from what gets through. Use MFA on accounts, consider password managers that recognise genuine websites, and limit privileged access.
  4. Respond quickly. Have the plan in this article written down, with names and phone numbers.

The NCSC response guide also recommends keeping key information somewhere safe, assigning roles, and documenting who owns each responsibility and how to reach them. Contact details stored only in the email system you have just lost are no use.

Test the plan before you need it. A short exercise with realistic scenarios exposes gaps quickly, and our tabletop agenda with sample injects is free to copy.

Insurers are asking about this too. Our note on how professional indemnity proposal forms now ask about MFA shows how controls from this list affect renewals.

How Solusec can help

We are a CREST-accredited cyber security company. You deal with testers and assessors directly, not a sales team, and we explain findings in plain English with recommendations in proportion to your size.

Solusec

If you want fewer phishing incidents in the first place, the baseline controls in the NCSC's list are the same ones checked by Cyber Essentials certification, which we assess as a certification body. Our published price is £320 to £600 one-off, depending on organisation size, and a gap analysis is £300. Urgent turnaround adds £100. If you need an incident handled or a response plan built, see our incident response page, or start from solusec.co.uk.

FAQ

What is the first thing to do after a phishing email is reported?

Keep the message, tell the person not to click anything further, and find out whether they interacted with it. Then search for the same email in other mailboxes and remove it. Forward genuine phishing to report@phishing.gov.uk once you have saved a copy.

What should I do if an employee entered their password on a phishing page?

Reset the password from a clean device, end all active sessions, and check for new MFA methods and mailbox forwarding rules. Change the password anywhere else it was used. Review sign-in logs for activity you do not recognise, and treat the case as a possible breach.

Do I have to report a phishing attack to the ICO?

Only if it causes a personal data breach likely to risk people's rights and freedoms. In that case the deadline is 72 hours from when you become aware. A phishing email that nobody acted on is normally not a reportable breach. Record your reasoning either way.

Should I report phishing emails to the authorities?

Yes. Forward suspicious emails to the NCSC at report@phishing.gov.uk, and report any financial loss to Report Fraud (or Police Scotland in Scotland). Reporting helps get malicious sites taken down and supports other organisations.

How do I stop phishing happening again?

Use MFA, filter inbound email, set up DMARC, limit admin rights and make reporting easy. Follow each incident with a short review and update your plan. Practising the response before a real event makes the first hour much calmer.

Sources

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.