Owner Briefs
Ransomware Protection for Small Business: Five Protections That Make a Ransom Note Survivable
Tested backups, patched remote access, enforced MFA, limited privileges, and a one-page recovery plan can help your business recover from ransomware. Start with a practical 60-minute check.
OWNER BRIEF / RANSOMWARE PROTECTION
Late in September, a ransomware group claimed it had hit a family-owned pharmacy in Washington state. The tracking reports described a business with fewer than 10 people — the kind of company that still answers its own phone and knows its customers by name.[1]
I am not presenting that case as a confirmed breach. A leak-site listing is still an attacker’s claim, not proof of what happened inside the business. What makes it worth noticing is the target profile. Ransomware groups do not need a Fortune 500 logo to make money. They need a business that cannot afford to be closed, cannot wait three weeks for help, and may not have a clean copy of its own files.
That is why the search term matters. When owners look for ransomware protection for small business, they are usually asking a simpler question: If this lands here, can we reopen?
I spent years in information security. The answer is rarely decided during the incident. It was decided months earlier, when someone either tested the backups or did not, patched the VPN or postponed it, enforced multi-factor authentication (MFA) or left it optional, and wrote down who calls whom. Ransomware rewards whatever your business postponed.
The 30-second answer
What matters most is being able to reopen without depending on a ransom payment. Keep tested backups attackers cannot alter, patch remote access, enforce MFA, limit administrator privileges, and write a recovery plan your team can use.
- Tested, separated backups: offline or immutable, under separate credentials, and actually restore-tested.
- Patched remote access: VPNs, firewalls, remote desktop, and cloud sign-ins inventoried and kept current.
- MFA where it counts: remote, administrator, email, banking, payroll, and backup accounts.
- Limited admin and backup rights: so one stolen password cannot reach everything.
- A one-page recovery plan: order of operations, people to call, and how long you can be down.
Backups help you recover encrypted files; they do not undo stolen data.
| Measure | Finding | Scope |
|---|---|---|
| Small-business share | About 96% | Ransomware victims with known size; SMB means fewer than 1,000 employees [2] |
| Ransomware payments | 69% did not pay; median paid $139,875 | 2026 DBIR ransomware dataset [2] |
| SMB entry points | 38% compromised credentials; 29% unpatched edge vulnerabilities | DBIR SMB breaches [2] |
| Total incident impact | About $38,000 median | SMB segment, all breach types; separate Breach Impact Study [4] |
Each number describes its own dataset. Payment amounts and total incident impact come from different studies; do not add or compare them directly.
If you run a small business, you are the target now
If you own a pharmacy, a dental office, an accounting firm, a repair shop, or any other business where you and a handful of people are the IT department, this part is about you — not about a big company with a security team down the hall.
Verizon’s 2026 Data Breach Investigations Report (DBIR) found that, among ransomware victims whose size could be identified, about 96% were SMBs — Verizon’s broad bucket of fewer than 1,000 employees, not just 10- or 30-person shops.[2] That does not mean 96% of small businesses were hit; it means ransomware victims are usually not large enterprises.
In the same SMB dataset, the two doors were clear: a compromised credential appeared in 38% of breaches, and an unpatched vulnerability in an edge device — your VPN, firewall, or remote-access box — in 29%.[2]
That is the part you can act on. A five-person office is not too small to be worth hitting; with no IT staff watching it, it is often easier to hit. Close those two doors and keep a clean copy of your files that an attacker cannot touch, and you change the whole incident.
How they get in — and why backups alone are not enough
Most attacks start with access that looks legitimate: a stolen VPN login, an exposed remote-desktop service, or an unpatched edge device. At-Bay’s 2025 claims put numbers on it — 73% of ransomware incidents began with VPN compromise.[3] Those are one insurer’s claims, not a census, but the direction matches the DBIR’s credential and edge-device findings.
Attackers also steal data before they encrypt it, then threaten to publish it. Backups defeat the encryption demand; they do not undo theft, notification duties, or lost customer trust. That is why the five protections below pair closing the doors with recovery that does not depend on paying.
The ransom is the wrong number to plan around
Owners often ask what ransomware “costs.” The honest answer is that there is no defensible single average for a Main Street business, and anyone who offers one without naming the dataset is selling certainty they do not have.
Here is what the current numbers can and cannot tell you:
| Reported figure | What it does not tell you |
|---|---|
| FBI IC3 2025: 3,611 complaints; about $32 million reported losses [10] | Reported ransom losses exclude downtime, recovery labor, equipment and lost sales. |
| 2026 DBIR: 69% did not pay; median paid $139,875 [2] | Payment is not total cost; recovery work, legal help and lost revenue are separate. |
| At-Bay: average claim $422,000; firms under $25 million saw a 40% increase [3] | One insurer’s book excludes uninsured businesses and incidents that never became claims. |
| Breach Impact Study: about $38,000 median in the SMB segment [4] | Covers all breach types, not ransomware alone. |
| Breach Impact Study: response and business interruption lead loss categories [4] | The ransom arrives once; closed doors keep costing money each day. |
Do not blend these figures into a single average cost.
My planning advice is unfashionable: budget for being down, not for paying. Ask, “How many days can we operate on paper, phones, and a clean laptop?” Then ask how quickly your systems can actually be restored. If the honest answer is “we think the backup works,” you do not have a recovery plan yet. You have a purchase receipt.
Paying buys you nothing you can count on — no guaranteed decryption key, no guaranteed deletion of stolen data. That is why the shift matters: 69% of victims now refuse to pay. Recovery, not negotiation, is the exit that works.[2] [5]
Five protections that make ransomware survivable
1. Back up like the attacker can see your network — because they may
Backups are the control owners talk about most and verify least. CISA’s #StopRansomware guidance is specific: maintain offline, encrypted backups of critical data and test their availability and integrity in a disaster-recovery scenario. “Offline” matters because ransomware operators actively look for accessible backups to delete or encrypt.[5]
For a small business, I would want proof on four points — the checklist below carries the detail:
| Backup requirement | Evidence to ask for |
|---|---|
| An unreachable copy | Offline or immutable backup; separate account and MFA. A mapped drive is not a separated backup. |
| Full coverage to rebuild | Data plus configuration: accounting, point-of-sale, email, documents, business applications, licenses and installers. |
| A real restore test | Files restored and reopened in the application that uses them. A backup-success notification is not a restore test. |
| A recovery time you know | Measured restore time in hours, with staffing and customer updates planned around it. |
The test is simple enough to say out loud: If every server and workstation were unusable tomorrow morning, what exactly would you restore, from where, using which account, and who has done it before?
2. Patch the edge before you buy another dashboard
The equipment that faces the internet — VPN gateways, firewalls, remote-access software, email gateways, and cloud services — deserves first call on attention. CISA’s small-business guidance tells IT leads to patch promptly, prioritize vulnerabilities listed in CISA’s Known Exploited Vulnerabilities Catalog, and enable automatic updates where possible.[6]
Owners do not need to memorize vulnerability names. You need an inventory and a cadence:
■ A written list of every system reachable from outside the business.
■ A named person responsible for patching each one.
■ A routine deadline for critical fixes and an emergency path when CISA or the vendor says an exploited flaw cannot wait.
■ A search for forgotten services: old remote desktop access, a vendor’s always-on support tool, a former employee’s VPN account, or a firewall rule nobody remembers approving.
At-Bay’s VPN finding is the reason “set and forget” remote access is dangerous. A device installed to help people work from home can become the front door if its software and credentials are not maintained.[3]
3. Put MFA on the accounts that can hurt you
MFA — a second proof beyond a password — should cover email, VPN and remote access, administrator accounts, banking, payroll, accounting, cloud storage, and the backup console. CISA advises requiring MFA for all users where possible and starting with privileged, administrative, and remote-access users.[7]
Do not stop at enrollment. Verify it:
■ Require MFA through settings, not by asking employees to opt in.
■ Remove phone numbers, authenticator apps, and recovery methods that no longer belong to the employee.
■ Restrict administrator accounts to administration; owners and managers should not browse email all day while signed in with keys to the kingdom.
■ Prefer an authenticator app, passkey, or hardware key over text-message codes where the service supports it.
A stolen password should cause a failed login and an alert, not a quiet entrance.
4. Make one bad password too small to run the whole business
Ransomware spreads when a compromised account can reach file shares, servers, backups, and other workstations. Owners cannot redesign a network over lunch, but they can insist on basic compartmentalization:
■ Employees receive access only to the systems and folders their job requires.
■ Backup deletion or modification requires separate credentials and, where supported, MFA.
■ Administrator access is named, limited, and reviewed when people change roles or leave.
■ Workstations, servers, point-of-sale systems, and guest Wi-Fi are separated where practical.
■ Old accounts, shared accounts, and vendor accounts are disabled or expired when no longer needed.
CISA summarizes the principle as least privilege: review accounts with administrative privileges and configure access so each person — and each service — gets only what is required.[8]
5. Write the recovery plan before adrenaline writes it for you
A one-page plan beats a binder nobody opens. It should answer, in order:
■ Who can authorize disconnecting systems from the network?
■ Who calls the IT provider, insurer, bank, attorney, and law enforcement?
■ Which systems come back first: phones, payment processing, accounting, scheduling, email?
■ Where is the contact list stored if email and the office network are unavailable?
■ How will customers be told what happened, in plain language, without guessing?
■ What evidence must be preserved before cleanup begins?
Then run a 30-minute tabletop once or twice a year. Read the plan aloud, find the missing phone number, discover that the backup credentials belong to someone who left, and fix it while the stakes are imaginary.
THE BACKUP QUESTION TO ASK THIS WEEK
Ask your IT provider for the date of the last successful restore test — and what was restored. The answer you need is not “backups are running.” It is: “On [date], we restored [system/data] to [location]; it took [time]; these items were missing; and this person can repeat it.” If nobody can answer, schedule the test before you discuss new security products.
Your 60-minute ransomware protection plan
You do not need an enterprise security program to improve your position this week. Set a timer and work through the following owner-level pass.
STEP 1
List the doors in
10 minutes
Write down every way someone can reach company systems from outside: VPN, remote desktop, vendor support tools, cloud apps, email, file sharing, and administrator portals. Mark the owner of each. Anything with no owner gets investigated first.
STEP 2
Get the backup evidence
10 minutes
Ask where backups live, whether one copy is offline or immutable, which account can delete them, when the last restore test happened, and how long restoration took. Write the answers down; “our provider handles it” is not an answer.
STEP 3
Verify MFA where it counts
10 minutes
Check email, VPN/remote access, banking, payroll, accounting, cloud administration, and backup consoles. Confirm former employees and old devices are removed.
STEP 4
Review administrator access
10 minutes
List every person and vendor with administrator rights. Remove anything unexplained. Make sure backup administration uses separate credentials.
STEP 5
Patch the overdue edge
10 minutes
Ask for the patch status of the firewall/VPN, remote-access tools, servers, and internet-facing applications. Critical known-exploited vulnerabilities go first; unsupported systems get isolated or replaced, not silently tolerated.
STEP 6
Write the first calls
10 minutes
Put the IT provider’s emergency number, insurer, bank, attorney, and owner contacts on one page. Save a paper copy and a copy outside the company network. Add the sentence staff need: “If you see a ransom note or mass file changes, disconnect from the network and call — do not try to fix it alone.”
At the end of the hour, you should have names, dates, and gaps — not a promise that you’re “secure.” Security is the work that follows: fix the gaps in the order you found them.
You see a ransom note. What should you do next?
Even good preparation cannot make ransomware a non-event. If employees see encrypted files, strange new extensions, or a ransom note, CISA’s response checklist starts with containment: determine which systems are affected and isolate them from the network. Power a device down only if it cannot be disconnected, because shutdown can destroy evidence investigators may need.[9]
The first calls should go to your IT provider or incident-response help, your cyber insurer, and law enforcement — locally and through the FBI’s Internet Crime Complaint Center. If banking information or payments are involved, call the bank as well. Preserve ransom notes, logs, and affected systems; do not wipe machines or restore over evidence until qualified help says the scope is understood.[9]
This is also where the pre-written plan earns its keep. Decide who is authorized to speak for the business, how customers will be updated, and which operations can continue manually. Do not let the loudest voice in the room make the payment decision. Get counsel and incident-response advice, understand whether data was stolen, and restore from known-clean backups only after the entry point is closed.
Your IT provider should be able to prove the basics exist
A provider does not need to drown you in reports. But “we take care of security” should translate into evidence an owner can read.
| Control | Evidence to request |
|---|---|
| Backup status | Copy locations, separation/immutability, separate credentials, date of last restore test |
| Restore evidence | What was restored, where, how long it took, and what failed or was missing |
| Remote access inventory | Every VPN / remote tool / exposed service, owner, and patch status |
| MFA verification | Account list showing MFA enforced for email, VPN, admin, banking, payroll, backup |
| Administrator access | Named admins, shared accounts removed, vendor access expiring and reviewed |
| Monitoring & patching | Who watches alerts, patch cadence, and escalation path when nobody responds |
Notice what is missing from that table: product names. A tool can help, but ransomware protection lives in configuration, patching, credentials, backups, monitoring, and rehearsal. If a provider cannot show those, the issue is not your lack of technical vocabulary. It is their lack of visible work.
The bottom line
Ransomware protection for a small business is not a product you buy once. It is a set of business decisions: know the doors in, keep them patched, make passwords insufficient by themselves, limit what one account can reach, and keep a clean copy of the business that criminals cannot touch.
The goal is not to be invulnerable. It is to make an attack survivable — a bad week with a recovery plan, not a ransom negotiation deciding whether you reopen.
Start with the backup question. If you can restore, in a tested time frame, with credentials the attacker cannot use, you have already changed the negotiation. Then close the remote-access doors the data says attackers are using. That is where Main Street ransomware protection begins.
Sources
Accessed October 1, 2026. Statistics describe the cited source’s dataset or reported complaints and should not be generalized beyond that scope.
1. Reported ransomware claim involving a family-owned pharmacy. QPulse/QuasarCyberTech brief, “Thegentlemen Ransomware Group Claims Attack on Custom Rx Shoppe” (September 30, 2026), summarizing Ransomware.live tracking. Attacker claim; not independently confirmed. Open source
2. Small-business breach and ransomware data. Verizon, 2026 Data Breach Investigations Report, SMB analysis (pp. 97–98) and ransomware payment findings. Open source
3. Insurer ransomware claims and VPN/edge findings; under-$25M severity. Business Wire release of At-Bay’s 2026 InsurSec Report (April 22, 2026): analysis of more than 6,500 claims and over 100,000 policy years. Insurer book only — not a census of all attacks. Open source
4. Breach-impact medians (all breach types, not ransomware-specific). Verizon, 2026 Breach Impact Study via HIPAA Journal coverage (2026): median impact around $38,000 in the SMB segment; response/recovery and business interruption leading loss categories. Open source
5. Official ransomware prevention/recovery guidance. CISA, FBI, NSA, and MS-ISAC, #StopRansomware Guide. Open source
6. Official small-business cyber guidance. CISA, “Cyber Guidance for Small Businesses” (MFA, patching, backup testing). Open source
7. Cyber Essentials for small organizations. CISA, Cyber Essentials (backup data; MFA for privileged/administrative/remote users; patch and update management). Open source
8. Official ransomware mitigations. CISA/FBI advisory AA24-109A, “#StopRansomware: Akira Ransomware” — MFA, offline backups, network segmentation, least privilege, patching. Open source
9. Official incident response checklist. CISA, “Ransomware Response Checklist.” Open source
10. 2025 Internet Crime Report (context). FBI Internet Crime Complaint Center, 2025 Internet Crime Report (April 2026). Open source