A small business incident response plan gives your team a calm, repeatable way to contain a problem, preserve useful evidence, communicate responsibly, and restore normal operations. Use this checklist as a working template, then update it whenever your people, software, suppliers, insurance requirements, or legal obligations change.
Overview
An incident response plan is not a prediction of every possible attack. It is a set of decisions your team agrees to make before an event creates pressure. The plan should be short enough to use during an outage and detailed enough that a person who is not a security specialist can follow it.
Store one current copy somewhere accessible if your primary systems are unavailable. Keep an offline or separately protected copy of essential contacts and recovery instructions. Limit sensitive details in broadly shared documents, and make sure the people named in the plan know their responsibilities.
Small business incident response plan template
- Purpose: State that the plan covers suspected or confirmed events affecting accounts, devices, data, systems, physical premises, or critical suppliers.
- Scope: List the business locations, cloud services, endpoints, applications, data types, and third parties included.
- Incident lead: Name the person who coordinates decisions and records actions. Include a backup.
- Technical contact: Identify the person or provider responsible for investigation, isolation, backups, and restoration.
- Business owner: Name the person who decides which operations can pause and which must continue.
- Communications lead: Identify who communicates with employees, customers, suppliers, insurers, legal advisers, and other relevant parties.
- Approval and reporting: Record who can approve notifications, spending, system shutdowns, public statements, and recovery decisions.
- Incident log: Keep a dated record of observations, decisions, actions, evidence locations, and open questions.
- Recovery criteria: Define what must be checked before a device, account, application, or business process returns to normal use.
- Review date: Set a quarterly review and an additional review after a significant incident, tool change, staffing change, or supplier change.
Severity and escalation matrix
Use impact and uncertainty together. When facts are incomplete, escalate rather than assuming the event is minor.
- Low: A suspicious message or isolated device issue with no evidence of access to business data. The assigned contact investigates, records the event, and confirms whether further action is needed.
- Medium: A compromised account, malware alert, lost device, or suspected unauthorized access that may affect one user or limited data. The incident lead coordinates containment and considers notifying the insurer, legal adviser, or affected provider.
- High: Ransomware, confirmed data exposure, widespread account compromise, inability to operate, payment fraud, or a critical supplier compromise. Activate the full response team, preserve evidence, and seek qualified legal, technical, and insurance guidance promptly.
Do not treat this matrix as a legal classification. Notification duties depend on the facts, the data involved, the affected people, and the locations or contracts that apply. Confirm current requirements with qualified advisers before sending formal notices.
Checklist by scenario
Phishing or compromised account
- Ask the employee to stop interacting with the message and report what happened without deleting it.
- Preserve the email, headers if available, screenshots, links, and relevant timestamps.
- Use a trusted channel to reset credentials, revoke active sessions, and review MFA settings and forwarding rules.
- Check sign-in history, mailbox activity, payment instructions, and recent changes to customer or supplier records.
- Warn affected contacts through a verified channel if fraudulent messages may have been sent from the account.
Ransomware or suspected malware
- Disconnect affected devices from networks where practical, without destroying evidence or powering off systems unnecessarily.
- Do not assume that paying, deleting files, or immediately restoring from backup resolves the incident.
- Identify affected systems, shared drives, cloud services, and backups. Protect clean backups from further alteration.
- Contact the technical response provider, insurer, and legal adviser according to your documented requirements.
- Restore only after the cause, access paths, and recovery environment have been assessed.
For recovery preparation, pair this plan with a tested small business backup strategy.
Lost or stolen device
- Record the device, user, location, time, and data or applications it could access.
- Use device-management tools to lock, locate, or erase it when appropriate.
- Revoke sessions, tokens, certificates, and credentials that may have been exposed.
- Check whether encryption, screen lock, MFA, and remote management were enabled.
- Document the assessment and any notification decision.
Vendor or cloud-service compromise
- Verify the alert through a trusted supplier contact, not through a link in an unexpected message.
- Review the contract, security notice, service status, affected tenant or account, and available logs.
- Rotate credentials, keys, or integrations that may be exposed, coordinating carefully to avoid creating an outage.
- Identify data shared with the supplier and whether your customers, employees, or partners may be affected.
- Record the supplier’s response, your decisions, and any follow-up risk review.
Your vendor risk assessment template can help document critical suppliers before an incident occurs.
Evidence-preservation worksheet
For each item, record: what it is; who collected it; the date and time; the system or location; how it was preserved; and where it is stored. Potential items include email messages, sign-in logs, endpoint alerts, payment records, access-control logs, screenshots, call notes, supplier notices, and copies of relevant configurations. Avoid changing files, repeatedly logging into a compromised account, or conducting improvised investigation that could overwrite useful records.
Tabletop exercise checklist
- Choose one scenario, such as a phishing-led account takeover or ransomware on a shared computer.
- Invite the incident lead, technical contact, business owner, communications lead, and a person responsible for customer or supplier relationships.
- Set a 30-to-60-minute session and explain that the goal is to test decisions, not individual performance.
- Introduce facts in stages: the initial alert, a second affected account, an unavailable system, and a request for information.
- Ask who makes each decision, which channel is trusted, what evidence is preserved, and when escalation occurs.
- Record gaps involving contacts, access, backups, logging, contracts, insurance, communications, or legal review.
- Assign an owner and due date to every action, then schedule a follow-up test.
What to double-check
- Contacts: Verify phone numbers, backup contacts, provider support paths, insurer instructions, and emergency communication methods.
- Access: Confirm that responders can reach password-manager entries, backup consoles, device-management tools, logs, and recovery documentation without relying on a potentially compromised account.
- Data: Know what personal, financial, health, employee, customer, or confidential data each system contains.
- Contracts: Review supplier notification clauses, retention terms, cooperation duties, and restrictions on accessing or preserving data.
- Insurance: Check policy conditions, approved providers, reporting windows, and documentation expectations before an incident occurs. See the cyber insurance readiness checklist.
- Privacy and notification: Maintain a current list of the jurisdictions, contracts, and data categories that may affect response. Do not copy a notice from another event without checking the facts and applicable requirements.
- Communications: Prepare holding language that confirms the business is investigating without speculating, assigning blame, or promising outcomes that are not yet known.
Common mistakes
- Keeping the plan in the same account, network, or device that may be unavailable during an incident.
- Listing one responder with no backup or failing to tell named people what they are expected to do.
- Resetting systems too quickly and losing logs or other evidence.
- Contacting customers, regulators, or attackers before confirming facts and obtaining appropriate advice.
- Assuming a backup is usable without regularly testing restoration.
- Focusing only on technical recovery while ignoring payroll, customer support, payments, safety, and continuity decisions.
- Failing to record actions because the team is busy. A simple timeline can later clarify what happened and what remains unresolved.
For related prevention work, review your MFA and password policy workflow and phishing prevention program.
When to revisit
Review the plan at least quarterly and after any meaningful change to staff, offices, devices, cloud applications, payment processes, data flows, suppliers, insurance, or backup arrangements. Recheck it before seasonal planning cycles and whenever workflows or tools change.
At each review, call every listed contact, confirm that the offline copy is readable, test one recovery procedure, remove departed staff, update supplier details, and close or reassign unresolved tabletop actions. Run a different scenario each cycle so the team tests more than phishing. After an actual event, hold a short lessons-learned review and update the plan while the sequence of decisions is still clear.
Start today by completing the contact list, choosing an incident lead and backup, documenting where protected backups and logs are located, and scheduling the first tabletop exercise. A modest plan that is current and practiced is more useful than a detailed document nobody can find or use.