Cybersecurity
Incident Response Guide for Small Business - 5 Steps
Five steps for responding to an incident in a small business: preparation, identification, resolution, reporting, and lessons learned.
Eugen Wypior
Józef SulwińskiPublished Updated 12 min read

Contents
A ransomware attack or the loss of email stops a small business that nobody prepared for such a situation. Employees do not know whom to notify, and the owner loses hours looking for passwords and phone numbers. Preparation before an incident shortens the break in work.
The five steps below lead from preparation, through identification and resolution, to reporting the incident and lessons learned. They apply to deliberate incidents, such as ransomware or phishing, and to accidental ones, such as equipment failure or fire.
Step 1: Preparation
The business owner names a person who leads the response to an incident, and a deputy. What the business does before an incident decides how fast it gets back to work.
Critical assets
The person assigned to IT records what the business depends on.
| Asset type | Examples | Where it is stored |
|---|---|---|
| Data | Customer data, financial records, contracts, email. | On a local server, in the cloud, or in a provider’s service. |
| Systems | Website, ERP system, accounting software, email. | In an own server room, at a hosting provider, or in the cloud. |
| Access | Administrative passwords, API keys, encryption keys. | In a password manager or a safe. |
At least two people must know where the critical data lies and how to reach it. Why: if the only person who knows the server password is unreachable during an incident, recovery stalls.
Backups
Backups are the last line of defence against ransomware. Every quarter the person assigned to IT confirms in writing that:
- backups run automatically and finish successfully,
- files can actually be restored from a backup,
- several employees know the backup procedure,
- at least one copy is stored off the premises or in the cloud and is disconnected from the production network.
The cyber resilience guide describes the details.
Contact list
The business records the phone numbers and addresses of the people and institutions it will contact during an incident:
- the IT service provider or managed service provider (MSP, a firm that runs the client’s IT),
- cloud service providers,
- customers, if their data was breached,
- suppliers and the bank,
- the insurer, with the cyber insurance policy number and the claims contact,
- legal counsel,
- the supervisory authority, when personal data is breached,
- law enforcement.
Such a list saves hours during an incident.
Response plan
A plan of 2-3 pages is better than a 50-page document nobody read. The plan contains:
- a division of roles and responsibilities,
- a rule for when an incident goes to management,
- a list of internal and external contacts,
- the locations of backups and the restore procedure,
- communication templates: customer notification and report to the supervisory authority,
- insurance policy details and the scope of cover,
- legal reporting obligations.
TIP
Print the plan and keep it where it is accessible even when all IT systems are down.
Cyber insurance
Cyber insurance covers part of the cost of an attack, but the scope depends on the specific policy. Before an incident, read the policy terms and check which costs it covers, for example forensic investigation, losses from business interruption, and customer notification. Many policies set conditions, such as multi-factor authentication being enabled and backups being maintained. Failing a condition can invalidate a claim.
Step 2: Identification
The person assigned to IT checks the warning signs and establishes the scope of the incident as fast as possible. Attackers try to stay undetected, and every day of delay increases the number of compromised accounts and files.
Warning signs
| Sign | Possible cause |
|---|---|
| A computer or the network runs slowly. | Malware, cryptocurrency mining on someone else’s hardware, or data leaving the business. |
| A system behaves unexpectedly: pop-ups appear, toolbars change, the cursor moves on its own. | A remote access trojan or adware. |
| Normal credentials no longer work. | Account takeover, where the attacker changed the password. |
| Files disappear, are renamed, or are inaccessible. | Ransomware or unauthorised deletion. |
| Messages leave the company domain that nobody wrote. | Takeover of a mailbox. |
| Unexpected payment requests or changes on invoices arrive. | Payment fraud by impersonating a supplier or a manager (business email compromise, BEC). |
| A ransom demand appears on screen. | Ransomware. |
| Antivirus raises alarms or the firewall blocks traffic. | An active attack or a malware infection. |
Diagnostic questions
When an incident is suspected, establish:
- Which systems are affected: a single device, the whole network, or cloud accounts.
- When the problem started.
- What changed recently: new software, staff changes, clicked links.
- Whether the problem is spreading.
- Whether backups are available.
- Whether data was captured or stolen.
- Whether customers or partners are affected.
Immediate actions
- Stay calm and follow the plan. Why: hasty decisions, such as deleting files, destroy the traces needed to establish the cause.
- Document everything, meaning times, observations, and actions taken. The record is needed for reports and insurance claims.
- Preserve evidence. Do not clean infected systems before the traces are secured. Take screenshots of the ransom demand or suspicious messages.
- Isolate the affected devices from the network. First unplug the network cable or switch off Wi-Fi. CISA advises isolating infected systems immediately and, when many devices are affected, taking the network offline at the switch. Power devices down only when disconnecting them from the network is impossible, because powering down erases traces in working memory.
Step 3: Resolving the incident
Once it is clear what happened, the person leading the response contains the incident and recovers the systems. The order below protects against reinfection.
Containment
- Disconnect compromised devices from the network.
- Disable compromised accounts.
- Block malicious IP addresses or domains on the firewall.
- If email was compromised, revoke active sessions and change passwords from a clean device.
Recovery
Change all passwords, not only the compromised ones, from a different, uninfected device. The order of changes:
- email accounts,
- banking and financial systems,
- cloud applications and SaaS services,
- network devices: routers, firewalls, Wi-Fi,
- every account that shared a password with a compromised one.
Restore data from a backup created before the incident. Why: a backup created after the infection restores the malware as well. Install all current patches before reconnecting to the network.
Rebuild systems when cleaning is uncertain. In serious cases, especially with ransomware, reinstalling a system from scratch is often faster and more reliable than cleaning. Secure the evidence first and rebuild afterwards.
Verify systems before reconnecting them to the network. An antivirus scan is one step but does not prove that a system is clean. Also check that the attack vector is closed: the vulnerability patched, the password changed, the malware removed.
WARNING
With ransomware, decide on paying a ransom only after other options are exhausted. Check backups and decryption tools (No More Ransom), and consult an incident response specialist and law enforcement. CISA advises contacting law enforcement about possible decryption tools. Consult legal counsel on the decision to pay.
When to call a specialist
Call a cybersecurity specialist when:
- the attack vector, meaning the route the attacker used to enter the business, cannot be established,
- the incident involves theft of personal data,
- ransomware encrypted critical systems and there is no working backup,
- the attacker still has access to the systems,
- evidence is needed for law enforcement or the insurer.
Step 4: Reporting the incident
The business reports the incident to the institutions named in the rules and to those that can help. A report on time protects against penalties, and a late report needs a justification.
Reporting obligations
A personal data breach is reported by the controller to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach. No report is needed when the breach is unlikely to result in a risk to the rights and freedoms of individuals. A late report must give the reasons for the delay. Data subjects are informed without undue delay when the breach is likely to result in a high risk to their rights and freedoms. Every breach, including unreported ones, is documented.
A significant incident at an essential or important entity follows three deadlines. The early warning is due within 24 hours, the incident notification with an initial assessment within 72 hours, and the final report not later than one month after the notification. Reports go to the competent CSIRT, the computer security incident response team. The obligation applies to medium-sized and large enterprises in the sectors listed in the NIS2 Directive and, regardless of size, to some entities, for example the sole provider of an essential service in a Member State. An ordinary small business is usually not covered. Member States had until 17 October 2024 to transpose the directive into national law, so the exact national procedure depends on the country.
Whom to notify
| Recipient | When to notify | What the report contains |
|---|---|---|
| Data protection supervisory authority | When a personal data breach may result in a risk. | The nature of the breach, the categories of data, the approximate number of people, and the measures taken. |
| Customers whose data is affected | When the breach may result in a high risk to individuals. | What happened, which data was breached, what the business is doing about it, and what customers can do. |
| Insurer | As soon as possible, under the policy terms. | A description of the incident, a timeline, the costs incurred, and the preserved evidence. |
| Law enforcement | When a financial crime or a significant data theft occurred. | A timeline, evidence, and financial impact. |
| Suppliers and partners | When the incident affected their data or systems. | The scope of the impact and the remediation actions. |
Why report
Many small businesses avoid reporting incidents for fear of reputational damage. A report helps law enforcement identify and prosecute the perpetrators, may be required by law, and builds the trust of customers and authorities.
Step 5: Lessons learned
After an incident the person leading the response organises a review within two weeks of the end of the incident. Without a review the same vulnerability will be exploited again.
Post-incident review
The review answers these questions:
- How did the attacker get into the business: what was the root cause, not only the symptom?
- Why was the incident not detected earlier?
- Did employees act according to the plan, and were the procedures sufficient?
- What should be done differently?
- Which safeguards should be added or changed?
Root causes and preventive controls
| Root cause | Preventive control |
|---|---|
| An employee clicked a link in a phishing message. | Employee training, mail filtering, and multi-factor authentication. |
| Software was not updated. | Automatic updates and vulnerability management. |
| A password was weak or reused. | A password manager, multi-factor authentication, and changing default credentials. |
| Remote access was not controlled. | VPN with multi-factor authentication, access reviews, and session logging. |
| The network was not divided into segments. | Separating the guest network and IoT devices from the business network. |
| Backups were missing or untested. | Automatic backups and quarterly restore tests. |
Updating safeguards
- Update the response plan on the basis of the lessons learned.
- Train employees on the weakness that was exploited in the incident.
- Review and tighten access control.
- Assess the security of external suppliers if the breach came through a supplier.
- Schedule the next review and exercise of the plan, because readiness fades without regular practice.
Legal basis
| Step / topic | Where it is |
|---|---|
| Reporting a personal data breach to the supervisory authority (72 hours, exception, reasons for delay, documentation) | GDPR, Article 33(1) and (5) |
| Informing data subjects | GDPR, Article 34(1) |
| Early warning 24 hours, notification 72 hours, final report after one month | NIS2 Directive, Article 23(4) |
| Entities in scope of NIS2 | NIS2 Directive, Article 2(1) and (2) |
| Transposition of NIS2 into national law | National law of the Member State, deadline 17 October 2024 |
Where we help
The SEQRED team provides incident response: it helps secure evidence, contain the attack, and restore systems. Penetration tests find vulnerabilities before an attacker exploits them. The virtual CISO service builds a security programme matched to the size of the business.
Source and licence
This article was written on the basis of the response and recovery guide in the Small Business Guide published by the UK National Cyber Security Centre (NCSC). Under the terms of the NCSC website, its content may be reused under the Open Government Licence v3.0 with acknowledgement of the source. The legal requirements and the advice on isolating systems were supplemented with the primary sources listed in the article header.
Sources
- NCSC: Small Business Guide (including Response and Recover guidance) - UK National Cyber Security Centre (accessed: )
- NCSC: Terms and conditions - UK National Cyber Security Centre (accessed: )
- #StopRansomware Guide - CISA (accessed: )
- NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management - NIST (accessed: )
- GDPR Article 33: Notification of a personal data breach to the supervisory authority - gdpr-info.eu (accessed: )
- GDPR Article 34: Communication of a personal data breach to the data subject - gdpr-info.eu (accessed: )
- NIS 2 Directive, Article 23: Reporting obligations - nis-2-directive.com (accessed: )
- NIS 2 Directive, Article 2: Scope - nis-2-directive.com (accessed: )
- NIS2 Directive - European Commission (accessed: )
Need help in this area?
Our experts will help you assess the risk and plan next steps.