$title =

Creating an Incident Response Plan for Small Businesses

;

$content = [

A small business does not need a 60-page incident response (IR) framework. It needs a short document that tells a tired person at 2 a.m. who to call, what to unplug, and what to write down. This guide walks through building that plan in ten steps, using a fictional 25-person accounting firm, Harbor Ridge Accounting, as the worked example. It draws on NIST SP 800-61 Rev. 3 (Incident Response Recommendations and Considerations for Cybersecurity Risk Management), the CISA ransomware guidance, and Microsoft's documentation for the tools shown. Adapt the values to your own business.

Identify Your Critical Assets and Most Likely Threats

Start with a one-page inventory of what would hurt most if it were lost, stolen, or unavailable. This mirrors the asset-and-risk preparation that NIST SP 800-61 and the NIST Cybersecurity Framework 2.0 (Identify function) recommend. For Harbor Ridge, that is the client file server (tax returns with SSNs), Microsoft 365 email, the QuickBooks hosted instance, and the payroll portal. Rank each by impact and note where it lives and who owns it.

  • Client file server (NAS at 10.0.10.5): contains SSNs and bank details. Impact: critical. Owner: Dana Whitfield, office manager.
  • Microsoft 365 tenant: email and SharePoint. Impact: critical. Owner: external IT provider.
  • QuickBooks Online: financial records. Impact: high. Owner: Marcus Lee, controller.
  • Staff laptops (22 Windows, 5 Mac): impact: medium each, high in aggregate.

Then list the threats most likely to hit a business of your size. For most small firms the realistic list is short: phishing leading to a compromised email account, ransomware, a lost or stolen laptop, business email compromise (fraudulent wire or invoice changes), and an employee mistakenly sharing data. The Verizon Data Breach Investigations Report has consistently found that the human element (phishing, stolen credentials, errors) is involved in roughly two-thirds or more of breaches, and the FBI's IC3 annual reports rank business email compromise among the costliest cybercrime categories, with losses in the billions of dollars per year. Plan for these five before worrying about nation-state attackers. Tax preparers also carry a legal duty: the FTC Safeguards Rule requires them to maintain a written information security program that includes an incident response plan.

Define What Counts as a Security Incident and Set Severity Levels

An event is something that happens (a failed login). An incident is an event that threatens the confidentiality, integrity, or availability of your data or systems, which follows the NIST definition. Write that definition at the top of the plan, followed by a simple severity scale so people know how fast to move.

  • Severity 1 (Critical): confirmed ransomware, data exfiltration, or compromise of an admin account. Response starts immediately; owner is notified within 15 minutes.
  • Severity 2 (High): a compromised user mailbox, malware on one machine, or a lost unencrypted laptop. Response starts within 1 hour.
  • Severity 3 (Medium): a phishing email clicked but no credentials entered, repeated failed logins from one IP. Response within 1 business day.
  • Severity 4 (Low): a reported suspicious email that nobody interacted with. Log it and move on.

The time targets above are Harbor Ridge's own choices, not a standard; set yours based on how many people you can realistically reach at night. When in doubt, rate it one level higher and downgrade later. Reclassifying costs nothing; a slow response to a real Severity 1 can cost the business.

Assign Response Team Roles and Record 24/7 Contact Details

A small team might be three or four people, each with a named backup. Roles matter more than titles. Harbor Ridge uses this structure:

  • Incident Lead: Dana Whitfield (backup: Marcus Lee). Makes decisions, declares severity, keeps the timeline.
  • Technical Lead: external IT provider, Northgate IT, 24/7 line. Performs containment and recovery.
  • Communications Lead: managing partner, Priya Raman. Handles clients, staff, and press.
  • Legal/Compliance contact: outside counsel, Alvarez & Cho LLP. Advises on notification duties.

Put contact details in the plan itself and also on paper, because email and the file server may be down. CISA's ransomware guidance specifically recommends keeping hard copies of the IR plan and contact lists for this reason. Include mobile numbers, personal email as a fallback, and the after-hours numbers for your IT provider, cyber insurer, bank, and counsel. Store a printed copy in a locked drawer at the office and a copy on the phones of every team member.

INCIDENT CONTACT SHEET (last verified 2026-10-15)

Incident Lead     Dana Whitfield   555-0142 (mobile)  dana.w@personalmail.example
Backup Lead       Marcus Lee       555-0177 (mobile)
Comms Lead        Priya Raman      555-0119 (mobile)
IT Provider       Northgate IT     555-0200 (24/7 line), policy #NG-4471
Cyber Insurer     Example Mutual   1-800-555-0166 (claims hotline), policy CY-882341
Outside Counsel   Alvarez & Cho    555-0133
Bank fraud desk   First Harbor     1-800-555-0188
Local FBI field office / IC3: ic3.gov

Set Up Detection, Logging, and an Incident Reporting Channel

You cannot respond to what you do not see. Three inexpensive measures cover most of the need: turn on audit logging in your cloud services, forward endpoint alerts to someone who will read them, and give staff a dead-simple way to report problems.

In Microsoft 365, confirm that unified audit logging is on (Microsoft Purview auditing is enabled by default for most tenants, but verify it, since retention is 180 days for standard audit as of Microsoft's current documentation) and check for suspicious inbox rules, a classic sign of a compromised mailbox. In PowerShell with the Exchange Online module:

Connect-ExchangeOnline -UserPrincipalName admin@harborridge.example

# Confirm audit logging is enabled
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled

# Turn it on if it is False
Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

# Look for forwarding rules on one mailbox
Get-InboxRule -Mailbox priya@harborridge.example |
  Where-Object { $_.ForwardTo -or $_.RedirectTo -or $_.DeleteMessage } |
  Format-List Name, ForwardTo, RedirectTo, DeleteMessage

For reporting, create one obvious channel: a shared mailbox such as security@harborridge.example, a dedicated phone number, and a rule written in the plan that says "if you are unsure, report it, and no one will be blamed." Staff who fear punishment hide mistakes, and hidden mistakes become Severity 1 incidents.

Write Step-by-Step Playbooks for Your Top Incident Types

A playbook is a one-page checklist for a specific scenario. CISA publishes federal incident and vulnerability response playbooks that are a good model to borrow structure from. Write one for each of your top threats, starting with phishing/compromised account and ransomware. Keep each to a numbered list with the owner of each step.

Example: Compromised Microsoft 365 account playbook for Harbor Ridge.

  • Technical Lead resets the user's password and revokes all sessions (see commands below).
  • Technical Lead checks for inbox forwarding rules and newly registered MFA methods, and removes any the user did not create.
  • Technical Lead reviews sign-in logs for the past 30 days for unfamiliar IPs and countries.
  • Incident Lead checks whether the mailbox had client data and whether any messages were sent from it to outside parties.
  • Communications Lead warns affected contacts if fraudulent emails went out.
  • Incident Lead records every action with a timestamp in the incident log.
Connect-MgGraph -Scopes "User.ReadWrite.All"

# Revoke all refresh tokens and active sessions
Revoke-MgUserSignInSession -UserId priya@harborridge.example

# Force a password reset at next sign-in
$pw = @{ forceChangePasswordNextSignIn = $true; password = (New-Guid).Guid + "Aa1!" }
Update-MgUser -UserId priya@harborridge.example -PasswordProfile $pw

# List registered authentication methods to spot attacker-added ones
Get-MgUserAuthenticationMethod -UserId priya@harborridge.example

Contain the Incident and Preserve Evidence

Containment limits the damage without destroying the evidence you will need later. A common mistake is powering off an infected machine, which wipes volatile memory that forensic investigators can use to find malicious processes and encryption keys. Note that CISA's ransomware guide advises isolating affected systems first and, if you cannot isolate them, powering them down to prevent spread, so the right call depends on whether your IT provider can isolate the device. Where possible, isolate it from the network and leave it powered on.

  • Disconnect the affected device from Wi-Fi and unplug the Ethernet cable. Do not shut it down unless you cannot isolate it and it is still spreading.
  • Disable the affected user accounts and revoke active sessions.
  • Block known malicious IPs or domains at the firewall.
  • Isolate the file server from the network if ransomware is spreading to shares.
  • Photograph the ransom note screen with a phone rather than closing it.
  • Preserve logs: export firewall, M365, and endpoint logs before they roll over.

If you use Microsoft Defender for Endpoint, or a similar tool, the network isolation can be triggered remotely from the device page using the "Isolate device" action. On a Windows machine you can also block all traffic quickly with the built-in firewall as an emergency measure (note this will also cut your remote session, so run it only from the console or with a scheduled rollback):

# Emergency: block all inbound and outbound traffic on every profile
Set-NetFirewallProfile -Profile Domain,Public,Private -DefaultInboundAction Block -DefaultOutboundAction Block

# Record who/what is running before you touch anything else
Get-Process | Sort-Object CPU -Descending | Select-Object -First 15 Name, Id, CPU, Path |
  Out-File C:\IR\processes_2026-11-02_0214.txt
Get-NetTCPConnection -State Established |
  Out-File C:\IR\connections_2026-11-02_0214.txt

In practice, run the two capture commands first and the firewall block second, since blocking traffic will change the connection state you are trying to record. Save these outputs to a removable drive or a separate location, not to a network share that may be compromised. Write down the time you took each action, and who did it.

Eradicate the Threat and Recover Affected Systems

Eradication removes the cause: the malware, the attacker's accounts, the persistence mechanisms, and the vulnerability they used. Recovery returns systems to normal operation. For a small business, the safest approach to a compromised workstation is almost always to wipe and reimage it rather than trying to clean it by hand.

  • Identify the entry point (phishing link, exposed RDP, unpatched VPN) so you do not get reinfected the same way.
  • Reset credentials for every account that touched the affected systems, starting with admin accounts, and rotate any API keys or service passwords.
  • Rebuild affected machines from a known-good image.
  • Restore data from a backup taken before the compromise date, and scan it before reconnecting.
  • Patch the exploited vulnerability and re-enable MFA where it was missing.
  • Monitor closely for 30 days for signs the attacker returned.

Backups decide how painful recovery is. Harbor Ridge follows the 3-2-1 rule popularized by photographer Peter Krogh and endorsed by CISA: three copies, on two media types, one offsite or offline (many practitioners now add immutability). Verify you can actually restore. A quick check using restic, an open-source backup tool with built-in integrity checking, looks like this:

# List snapshots and pick one from before the incident (Oct 28)
restic -r /mnt/offline-backup/harborridge snapshots

# Verify repository integrity
restic -r /mnt/offline-backup/harborridge check

# Restore a snapshot into a clean staging folder, not over live data
restic -r /mnt/offline-backup/harborridge restore 4f9a1c2e --target /mnt/restore-staging

# Scan restored files before reconnecting to the network
clamscan -r --infected /mnt/restore-staging

Notify Staff, Customers, Insurers, and Regulators

Notification is where many small businesses stumble, because deadlines can be short and the rules vary by location and industry. Decide in advance who must be told, by whom, and in what order. For Harbor Ridge, a tax preparer, the FTC Safeguards Rule (16 CFR Part 314) requires notifying the FTC as soon as possible, and no later than 30 days after discovery, when an event involves unencrypted information of 500 or more consumers. Confirm which rules apply to you with counsel.

  • Insurer: call the cyber insurance claims hotline early, often before hiring outside help, because many policies require pre-approved vendors and prompt notice.
  • Legal counsel: engage them before sending external statements so communications are reviewed and, where possible, privileged.
  • Staff: give a short internal message saying what happened, what they should do (for example, change passwords, do not open the file server), and who to ask.
  • Customers: notify affected clients with plain language about what data was involved, what you are doing, and what they should do.
  • Regulators and law enforcement: check breach notification laws. All 50 US states, plus DC and US territories, have one, and the EU GDPR (Article 33) requires notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in risk to individuals. Report cybercrime to the FBI at ic3.gov. Tax preparers should also contact IRS Stakeholder Liaison, as described in IRS Publication 5293.
  • Payment partners: if card data or bank details were exposed, notify your bank and processor.

Prepare a template now. A short, pre-approved draft saves hours when you are under stress:

Subject: Important notice about your information

On November 2, 2026, Harbor Ridge Accounting detected unauthorized access to
one of our email accounts. We believe the following information may have been
viewed: names, email addresses, and tax documents sent between Oct 20-Nov 2.

What we have done: secured the account, engaged a security firm, and
notified law enforcement.

What you can do: be cautious of unexpected emails about your tax filings,
consider placing a fraud alert with the credit bureaus, and contact us at
555-0119 with questions.

We sincerely apologize and will update you as we learn more.

Priya Raman, Managing Partner

Document the Incident and Run a Post-Incident Review

Keep an incident log from the first minute. A shared document or even a paper notebook works. Each entry needs a timestamp, the person, and the action or observation. This log supports your insurance claim, any regulator inquiry, and your own learning.

INCIDENT LOG - IR-2026-011
02:14  Dana W.  Alert from Defender: ransomware behavior on LAPTOP-FIN03. Sev 1 declared.
02:19  Dana W.  Called Northgate IT 24/7 line. Ticket #88231.
02:26  Northgate  LAPTOP-FIN03 isolated via Defender. Account mlee disabled.
02:41  Dana W.  NAS shares set to read-only. Backups confirmed offline and untouched.
03:05  Dana W.  Called insurer hotline. Claim # CY-882341-A opened.
03:40  Northgate  Entry point: phishing email opened Oct 31, 16:52.
09:00  Priya R.  Counsel engaged. Client notification drafted.

Within one to two weeks after the incident is closed, hold a blameless review, which NIST SP 800-61 calls the lessons-learned activity. Ask five questions: What happened? How did we detect it and how long did that take? What worked? What slowed us down? What will we change, by when, and who owns each change? Record 3 to 5 concrete actions, such as "enforce MFA on all accounts by Nov 20" or "add the insurer's number to the printed contact sheet," and track them to completion.

Test the Plan with a Tabletop Exercise and Update It on a Schedule

An untested plan is a guess. A tabletop exercise is a 60 to 90 minute meeting where the response team walks through a realistic scenario without touching any systems. CISA offers free Tabletop Exercise Packages (CTEPs), including ransomware scenarios, that a small team can run without outside help. It is cheap, and it exposes gaps fast.

A sample scenario for Harbor Ridge: "It is Friday at 5:30 p.m. during tax season. Three staff report they cannot open files, and a text file named README_RESTORE.txt appears on the shared drive demanding 4 bitcoin. Your IT provider's phone goes to voicemail." Then ask the team questions and note where answers are missing:

  • Who declares the incident and what severity is it?
  • What is the first thing we do in the next 10 minutes?
  • Where is the contact sheet if email is down?
  • Are the backups reachable and when was the last successful restore test?
  • Who calls the insurer, and what is the policy number?
  • What do we tell clients who call on Monday morning?

Set a maintenance schedule and put it on the calendar so it actually happens:

  • Quarterly: verify every phone number and name on the contact sheet; test one backup restore.
  • Twice a year: run a tabletop exercise with a different scenario each time (ransomware, then lost laptop, then business email compromise).
  • After every real incident: update playbooks based on the review.
  • Whenever something major changes: new cloud service, new office, staff turnover on the response team, or a new insurance policy.

Finally, keep the plan short. If the core document, with roles, severity levels, contact sheet, and top playbooks, fits in 8 to 10 pages, people will read it. Start with the first draft this week, test it within 30 days, and improve it every time you use it.

];

$date =

;

$category =

;

$author =

;