Ransomware protection for a business comes down to three jobs: make it hard for attackers to get in, make sure one bad click cannot spread across your network, and keep clean, tested backups so you can recover without paying. NIST frames it the same way: protect your data and devices, and be ready to respond when an attack gets through. This guide turns that into a plan a small or midsized company can run, with a defense plan you can write this month.
TL;DR
- Start with the basics federal agencies keep repeating: multi-factor authentication (MFA), fast patching, phishing training, and encrypted data.
- Treat backups as your real safety net: automatic, stored separately from your main systems, and restore-tested on a schedule.
- Write a short incident-response plan, name one person to run it, and rehearse it with leadership.
- In an attack, isolate affected systems first, then preserve evidence and restore in business-priority order.
- If you do not have in-house IT, a managed provider can run these controls for a predictable monthly fee.
Table of Contents
- Why small and midsized businesses are in scope
- The safeguards that do the most work
- Backups: your real recovery plan
- Build your ransomware defense plan
- Prioritize when budget and staff are thin
- What to do in the first hour of an attack
- Recovering without reinfection
- Our perspective
- How Axio Networks can run this for you
- FAQ
- Sources
Why small and midsized businesses are in scope
A common assumption is that attackers go after big enterprises. NIST’s small business guidance says to not assume you are too small to be targeted: ransomware can halt operations, make recovery expensive, and, if customer data is stolen, trigger state breach-notification laws.
That last point matters in Arizona. Under A.R.S. 18-552, a business that conducts business in the state and holds unencrypted personal information must investigate a security incident promptly. If it finds a breach, it has 45 days after that determination to notify affected individuals, with additional notices required when more than 1,000 people are affected. Encryption and good logging make that conversation much easier.
So the cost of an incident is not just the ransom demand. It is days of lost work, a legal clock, and customers wondering whether you can be trusted with their data.
The safeguards that do the most work
Government guidance is consistent on what to do first. CISA’s small business guidance lists these: train employees to recognize and report phishing, require strong passwords and MFA, update software, use logging, back up data, encrypt it, and keep an incident-response plan that you exercise.
Here is how each one looks in a real office.
Identity: MFA and least privilege
Most ransomware starts with a stolen or guessed login. CISA says to mandate MFA through technical controls, check compliance regularly, and turn it on for administrators first. It also recommends removing administrator privileges from user laptops. Where it is available, CISA specifically recommends phishing-resistant MFA.
NIST’s risk-management guide adds the principles behind this: unique accounts, least-privilege access, standard rather than administrator accounts where possible, and tightly controlled remote access. In practice, nobody shares a login, and the person who opens invoices all day does not have the keys to your servers.
Patching and vulnerabilities
Attackers reuse known flaws. CISA advises prioritizing fixes for vulnerabilities in its Known Exploited Vulnerabilities Catalog, which is a short, practical list of what is being used in the wild right now. NIST adds that computers should be fully patched, and that unnecessary services should be disabled and device configurations kept consistent.
Endpoint and email protection
NIST recommends always-on antivirus that scans email and removable media, controls that block known ransomware sites, and application allowlisting. It also recommends restricting personally owned devices used for remote access or on your network. Modern endpoint detection and response (EDR) tools go further than classic antivirus by watching behavior and containing a device when something looks wrong.
Segmentation
NIST’s guide recommends network segmentation to limit ransomware spread. If your accounting workstation, guest Wi-Fi, security cameras and file server all sit on one flat network, a single infected laptop can reach everything. Separate them, and an incident stays small.
People
Phishing is still the front door. Training works best when it is short, regular, and paired with an easy way to report a suspicious email without embarrassment. The goal is that the first person who notices tells IT within minutes, not after lunch.
Backups: your real recovery plan
Backups decide whether an attack is an inconvenience or a crisis. CISA states that recovery without backups can take weeks or months and may be impossible, while good backups reduce downtime and help you avoid paying a ransom.

The Institute for Security and Technology reports that organizations with compromised backups face, on average, twice the ransom demand of those with secure backups, along with nearly eight times higher recovery costs. Attackers know to hunt for backups first, so where and how you store them matters.
A sound backup setup, per CISA, looks like this:
- Copies are stored separately from your primary systems.
- Backups run automatically and regularly, not when someone remembers.
- You keep both on-site and remote copies.
- You run scheduled recovery tests to verify integrity and refine your recovery-point and recovery-time objectives.
NIST adds that at least one frequently backed-up data set should be kept offline, and that you should test mean time to recovery. A backup you have never restored is a hope, not a control.
For a deeper walk-through, see our guide to building a backup and disaster recovery plan and the explainer on the difference between backup and disaster recovery.
Build your ransomware defense plan
A defense plan is a short document that answers: who decides, who does what, who gets called, and what comes back first. CISA’s #StopRansomware Guide splits the work into prevention practices and a response checklist covering preparation, containment, eradication and recovery. It also says to create and regularly exercise an incident-response and communications plan, have the CEO approve it, and make sure it is reviewed and understood across the chain of command.
What the plan should contain
| Section | What goes in it |
|---|---|
| Roles | One named coordinator and a backup, plus decision-makers from leadership, IT and legal |
| Critical assets | A ranked list of systems to restore first, tied to revenue and safety |
| Contacts | Internal and external contacts, including your insurer, legal counsel, IT provider and law enforcement |
| Communications | Who tells staff, customers and regulators, and by what channel if email is down |
| Recovery steps | Where clean backups live, who can restore them, and how you validate systems |
| Exercises | A scheduled tabletop run-through and a restore test |
The contents track what NIST recommends: defined roles and decision strategies, regular exercises, isolated backups, and an up-to-date contact list that includes law enforcement. CIS likewise suggests listing partners, insurers and vendors and testing the plan through tabletop exercises.
The Institute for Security and Technology recommends designating one person to coordinate and document response and recovery and setting up a standard reporting process. For a 25-person company, that one person is often the owner or operations manager, with your IT provider as the technical lead.
Separate incident response from disaster recovery
The Canadian Centre for Cyber Security makes a distinction worth borrowing: incident response detects and contains, while disaster recovery restores critical business functions. It also advises documenting what is recovered, by whom, when and where. Keep these as two sections of your plan, since they involve different people and different clocks.
For a ready-made outline, our own 5-step proactive ransomware defense plan covers the proactive side.
Prioritize when budget and staff are thin
You do not need every control on day one. The Institute for Security and Technology describes its Blueprint for Ransomware Defense as 40 safeguards aligned with NIST’s framework, and says smaller organizations with limited resources should put Identify, Protect, Respond and Recover safeguards first.
A workable order for a small company:
- MFA everywhere it is offered, starting with email, remote access and admin accounts.
- Backups with a copy ransomware cannot reach, and one successful test restore.
- Patching on a schedule, starting with internet-facing systems.
- Endpoint protection with monitoring, so someone sees an alert at 2 a.m.
- A one-page response plan with phone numbers on paper.
The same logic applies whatever you sell; this overview of cybersecurity priorities for e-commerce shows how to rank high-impact safeguards against staffing and budget limits.
What to do in the first hour of an attack
Write this on a card and put it where your team will find it. CISA’s guidance for anyone who has been hit says IT should identify impacted systems and isolate them, use out-of-band communications, and power devices down only if they cannot otherwise be disconnected.
- Isolate. CISA’s response checklist says to take the network offline at the switch level if multiple systems or subnets are affected. Otherwise, disconnect affected devices from Ethernet or Wi-Fi.
- Triage. Check systems against your critical-asset list and prioritize those tied to health and safety, revenue and critical services. Write down what you know so far.
- Preserve evidence. CISA recommends keeping system images, memory captures, relevant logs and malware samples where possible, and examining antivirus, EDR and logs for earlier-stage malware.
- Hunt for the access route. Look for suspicious privileged accounts, VPN logins, backup tampering, remote-management tools, credential theft and data exfiltration.
- Inform and report. Keep management updated and report the incident to the appropriate authorities. Call your insurer and counsel per your plan.
Our step-by-step ransomware recovery plan for the first hour goes deeper on this, and how to minimize ransomware damage covers what to do while the incident is still unfolding.
Recovering without reinfection
CISA’s recovery steps in the #StopRansomware Guide are a good template. Contain the incident, preserve evidence, identify persistence and the initial access route, and prioritize critical services. Then rebuild or restore on a clean environment, using offline, encrypted backups verified as clean.
After that:
- Restore in business-priority order.
- Validate each system before reconnecting it.
- Rotate compromised credentials.
- Monitor for reinfection.
- Document lessons learned and update the plan.
The credential step is the one most often skipped. If attackers stole passwords, restoring clean files into the same compromised accounts invites a second round.
Our perspective
We see the same pattern in Phoenix-area businesses of 10 to 200 people: the company has antivirus and a backup, and assumes that is protection. Then an attack shows that the backup sat on the same network as everything else, nobody had restored from it, and no one knew who was in charge.
That is why we build security into every managed service rather than selling it as a separate add-on. Patching, endpoint protection, email filtering, backup and monitoring should be designed together, because ransomware moves across all of them. Our SOC monitoring watches for the early signs, and our average response time is under 30 minutes, because speed in the first hour changes how much you have to restore.
We also believe small businesses should not need an in-house IT department to get this level of protection. Flat-rate pricing means the cost of keeping your defenses current is known in advance, and a local team means the people who answer the phone know your environment and the Arizona business landscape.
Jim O’Connell
How Axio Networks can run this for you
If you would rather not manage MFA rollouts, patch cycles and restore tests yourself, that is what our managed IT services are for. We deliver managed IT and cybersecurity to small and midsized businesses across the Phoenix metro area with a security-first design and flat-rate pricing.
The pieces that map to this guide are endpoint security and EDR, SOC monitoring and MDR, and backup and disaster recovery. If an incident has already happened, our ransomware and malware recovery service is the place to start. To talk through your situation, visit Axio Networks.
FAQ
How much does ransomware protection for a business cost?
It depends on your headcount, devices and what you already have in place. With a managed provider, the cost is typically a fixed monthly fee covering monitoring, endpoint protection, backup and support. Axio Networks does not publish prices, so contact us for a quote based on your environment.
Is antivirus enough to stop ransomware?
No single tool is enough. NIST recommends always-on antivirus as one layer alongside patching, allowlisting, blocking known ransomware sites and restrictions on personal devices. Add MFA, tested backups and monitored endpoint detection so that a missed threat is still contained.
Should we pay the ransom?
The best position is not to need to. The Institute for Security and Technology reports that organizations with secure backups are less likely to pay and face lower recovery costs. If you are attacked, contact your counsel, insurer and law enforcement before making any decision, and report the incident to the appropriate authorities.
How often should we test backups and our response plan?
CISA calls for scheduled recovery tests to verify backup integrity and refine recovery objectives. Pick a regular schedule, such as a restore test each quarter and a tabletop exercise each year, and run an extra one after major changes to your systems or staff.
Sources
- Ransomware | NIST
- Arizona Revised Statutes 18-552
- Cyber Guidance for Small Businesses | CISA
- Secure Your Business | CISA
- NIST Tips and Tactics: Preparing Your Organization for Ransomware Attacks
- Getting Started with Cybersecurity Risk Management: Ransomware | NIST
- Back Up Business Data | CISA
- Prepare, Don’t Pay: A Quick-Start Guide to Defending Against Ransomware
- #StopRansomware Guide | CISA
- Steps to Help Prevent & Limit the Impact of Ransomware | CIS
- Ransomware Playbook (ITSM.00.099) | Canadian Centre for Cyber Security
- I’ve Been Hit By Ransomware! | CISA
- Ransomware Response Checklist | CISA
- 7 Key Reasons Cybersecurity Matters for E-Commerce Success
