A Simple Incident Response Plan for Small Businesses

By Information Security Asia · Updated November 21, 2026 · 4 min read

Short answer: a small business needs a short written plan that names who is in charge, who to call, how to contain the problem, what evidence to keep and who must be told. One or two pages, printed and stored where you can reach it when systems are down, beats a long document nobody reads.

A Simple Incident Response Plan for Small Businesses

Last reviewed: November 2026.

Why plan before an incident

In a real incident, people are stressed, systems may be offline and decisions made in a hurry are often poor ones. A prepared plan removes guesswork. The widely used framework from NIST describes four phases: prepare, detect and analyse, contain, eradicate and recover, and learn from the incident afterwards. The plan below follows the same order, scaled down.

Part 1: prepare

  1. Name a lead who makes decisions during an incident, and a deputy. In a very small business this may be the owner and an IT provider.
  2. Write a contact sheet, on paper and offline: your IT provider, internet provider, bank, insurer, lawyer, key suppliers and staff phone numbers.
  3. List your critical systems and data: email, accounting, customer records, payment systems and website, and where each is hosted.
  4. Keep backups that survive an attack, including an offline copy, and know how to restore them. See the 3-2-1 rule and our ransomware checklist.
  5. Know your cyber insurance terms, if you have a policy, including the claims hotline and any rule requiring you to call before you hire help.
  6. Turn on logging for email, firewall and key cloud services, so there is something to investigate.
  7. Tell staff whom to tell and how, if they see something odd, and that reporting a mistake quickly is welcome.

Part 2: detect and decide

Typical signs include ransom notes, locked files, unexpected logins, forwarding rules in email, payment requests from a hijacked account, or a security alert. When someone reports a sign:

A Simple Incident Response Plan for Small Businesses
  1. Record the time, who reported it and what was seen.
  2. Decide whether it is an incident. If unsure, treat it as one until shown otherwise.
  3. Notify the lead.

Part 3: contain

  • Isolate affected devices by disconnecting the network cable or turning off Wi-Fi. Do not power them off unless advised, because memory can hold evidence, though in a spreading ransomware attack, isolation comes first.
  • Disable compromised accounts and reset passwords from a clean device. See the first-hour checklist.
  • Stop payments in progress by calling the bank, if money is involved.
  • Protect backups by disconnecting them so they cannot be encrypted.
  • Do not wipe or rebuild yet. Evidence is needed to understand what happened.

Part 4: preserve evidence and investigate

  • Keep a timeline of events and actions, with times.
  • Save logs, screenshots, ransom notes and suspicious emails.
  • Call your IT provider or a specialist incident response firm if the scope is unclear. Insurers often have approved providers.

Part 5: notify

Legal duties vary by country, state and industry, and the deadlines can be short. Ask a lawyer or your regulator early. Common groups to consider are:

  • Your insurer, usually first.
  • Law enforcement, such as the FBI’s IC3 or your national cyber agency, which can also help with ransomware.
  • Regulators and affected individuals, if personal data was exposed. Many places set a deadline, for example 72 hours under the EU GDPR for notifying the regulator of a personal data breach.
  • Customers, partners and staff, honestly and without speculation.
  • Your payment processor, if card data may be involved.

Part 6: eradicate and recover

  1. Remove the cause: close the access path, patch the hole, remove malware. See malware removal and patching.
  2. Rebuild or restore from clean backups, and check that they are clean first.
  3. Reset all relevant credentials, and enable stronger sign-in. See two-factor methods.
  4. Return to service in stages and watch closely for repeat activity.

Part 7: learn

Within a couple of weeks, hold a short review: what happened, how it was found, what worked, what failed and what will change. Update the plan, fix the root cause, and brief the staff.

Practise it

Once a year, run a tabletop exercise: a one-hour discussion of a scenario such as ransomware or a hijacked mailbox, and walk through the plan. It will expose gaps, such as an outdated phone number, at no cost.

Frequently asked questions

Should we pay a ransom?

Law enforcement agencies generally advise against it, since payment does not guarantee recovery and funds crime. Get advice from your insurer, lawyer and law enforcement before deciding.

Do we need a plan if we are very small?

Yes, though it can be one page. Small firms are often targeted because they have weaker defences.

Sources

Keep reading