When a cyber attack hits, the businesses that recover fastest are rarely the ones with the most technology — they are the ones who knew exactly what to do in the first hour. An incident response (IR) plan turns panic into process. For a London SME juggling client obligations, tight margins and lean IT resources, that clarity is the difference between a contained incident and a business-threatening crisis. This guide explains what a genuinely useful IR plan looks like for a UK small or medium business: the phases it should cover, who does what, the legal duties you cannot ignore, and how to keep the plan alive rather than filed away.
Why an SME needs a written incident response plan
Smaller businesses are targeted precisely because attackers assume defences and processes are weaker. Ransomware, business email compromise and credential theft do not discriminate by company size — and for an SME, the operational and reputational impact of downtime is often proportionally greater than for a large enterprise.
A written plan matters because incidents create pressure and confusion. Staff need to know who to call, what not to touch, and how to communicate without tipping off an attacker or breaching client contracts. Improvising these decisions at 2am rarely ends well.
There is also a commercial angle. Increasingly, London clients, insurers and tenders ask whether you have a documented response capability. A clear IR plan supports certifications like Cyber Essentials and demonstrates the due diligence that professional services, finance and legal clients expect from their suppliers.
The core phases of incident response
Most credible frameworks — including guidance from the NCSC and NIST — break response into a recognisable lifecycle. Your SME plan does not need to be lengthy, but it should address each stage clearly.
The value is not in reciting theory but in mapping each phase to your actual tools, people and suppliers. A phase without a named owner and a concrete first action is just paperwork.
- Preparation — policies, backups, logging, training and contact lists in place before anything happens.
- Detection and analysis — how you spot an incident (alerts, staff reports, monitoring) and confirm it is real.
- Containment — isolating affected devices or accounts to stop the spread without destroying evidence.
- Eradication — removing the attacker's access, malware and any persistence mechanisms.
- Recovery — restoring systems from clean backups and returning to normal operations safely.
- Lessons learned — a post-incident review to fix root causes and update the plan.
Who does what: roles and responsibilities
An IR plan lives or dies on clear ownership. In a smaller business you will not have a dedicated security team, so roles are usually assigned to existing people plus external partners. What matters is that everyone knows their remit in advance.
Name an incident lead (often a director or operations manager) who makes decisions and authorises actions such as taking systems offline. Identify who handles technical containment — this is frequently your managed IT or security provider. Assign someone to communications, covering staff, clients and, where relevant, regulators.
Because most London SMEs outsource part of their IT, your plan should clearly define the boundary between internal staff and providers. If you run a shared model such as co-managed IT support, spell out who leads and who supports during an incident. Include an escalation path to a specialist team such as managed detection and response if the incident exceeds your in-house capability.
Detection: you cannot respond to what you cannot see
The earlier you detect an incident, the cheaper and simpler containment becomes. Yet many SMEs discover a breach only when a client complains or systems stop working — by which point the attacker has had days or weeks inside.
Effective detection combines technology and people. Modern endpoint security with EDR flags suspicious behaviour on laptops and servers, while continuous monitoring through a managed SIEM and SOC correlates activity across your environment. Just as important, staff should know how to report something odd — a strange login prompt, an unexpected password reset, a supplier invoice that looks slightly off.
Your plan should define what counts as an 'incident' versus routine noise, and how a report is triaged. A simple severity scale (low, medium, high, critical) helps everyone respond proportionately rather than treating a single phishing email like a full breach.
Containment, eradication and recovery in practice
Containment is about buying time and limiting damage. Typical first actions include isolating affected machines from the network, disabling compromised accounts, and revoking active sessions — while deliberately preserving logs and disk images so you can investigate later. Wiping a machine too early can destroy the evidence you need to understand how far the attack spread.
Eradication removes the attacker's foothold entirely: malware, unauthorised accounts, rogue email forwarding rules and any backdoors. For account-based attacks, strong identity protection and enforced multi-factor authentication are central to shutting the door properly.
Recovery is where reliable backups prove their worth. Your plan should state where backups live, how quickly they can be restored, and how you verify they are clean before reconnecting them. Immutable, offsite cloud backup solutions protect against ransomware that deliberately targets backup files. Test a restore before you need it — an untested backup is a hope, not a plan.
Legal and regulatory duties for UK businesses
A cyber incident that involves personal data is not just a technical problem — it is a compliance event. Under UK GDPR and the Data Protection Act 2018, a notifiable personal data breach must be reported to the Information Commissioner's Office (ICO) without undue delay, and where feasible within 72 hours of becoming aware of it. Your plan should make clear who assesses whether the threshold is met and who submits the report.
Where a breach is likely to result in a high risk to individuals, you may also need to notify the affected people directly. Keeping an internal record of all incidents — even those you decide not to report — is itself a requirement and helps demonstrate accountability.
Beyond regulators, consider contractual obligations. Many London client contracts and cyber insurance policies require notification within a set timeframe. List these obligations in the plan so nobody has to read the small print during a crisis. If you are unsure of your exposure, our team can help you review this as part of a broader cyber security assessment.
Communication: getting the message right under pressure
Poor communication turns a manageable incident into a reputational one. Decide in advance who is allowed to speak on behalf of the business, and route all external statements through that person. Loose talk on social media or in client emails can create legal exposure and cause unnecessary alarm.
Prepare simple holding templates now: an internal staff notice, a client notification, and a short statement for suppliers. During an active attack, assume your normal email may be compromised — agree an out-of-band channel such as phones or a messaging app so the response team can coordinate securely.
Be honest and factual. Clients generally respond better to a calm, timely acknowledgement than to silence followed by a leak. Say what you know, what you are doing, and when you will update them next.
Keeping the plan alive: testing and improvement
An IR plan written once and never revisited will fail when it matters. Treat it as a living document tied to your actual environment. Whenever you add a major system, change providers or restructure the team, update the plan and its contact list.
The most effective way to build confidence is a tabletop exercise: gather the response team, walk through a realistic scenario — say, a finance mailbox compromise or a ransomware note on a shared drive — and see whether your steps hold up. These sessions almost always reveal gaps, such as missing admin credentials or a backup that takes far longer to restore than assumed.
Finally, use every real incident and near miss as fuel for improvement. A structured lessons-learned review that feeds fixes back into your systems and processes is what turns a static document into genuine resilience. If you would like help building, testing or maturing your plan, get in touch with our team.
