← All posts
Mitigating Ransomware RisksNovember 15, 2026 · 5 min read

Ransomware just hit. What you do in the first hour matters most

Do not panic, do not pay yet, and do not plug things back in. A calm first hour limits the damage — here is the checklist to follow.

Ransomware is the moment every small business hopes never comes: you open a file and it will not open, or a screen appears demanding payment to unlock your own computers. The first instinct is panic. The second is to pay and make it go away. Neither is the right first move.

What you do in the first hour matters more than anything you do later. A calm, ordered response limits how far the attack spreads, protects the copies of your data you will need to recover, and keeps a bad day from becoming a business-ending one. This is the checklist to follow — and the reason to write it down and keep it somewhere everyone can find it before you ever need it.

Step one: disconnect, do not shut down

The moment you suspect ransomware, disconnect the affected machines from the network — unplug the network cable or turn off the Wi-Fi. Ransomware spreads across a network, from one computer to the next, and every minute connected gives it more to reach. Disconnecting stops the spread.

Do not turn the machines off unless you have to. Turning a machine off can make recovery harder, because the evidence of what happened — what the attack touched, and in what order — lives in its memory. Leave the machines on, disconnected, until someone who knows what they are doing tells you otherwise.

Do the same for any shared drives and cloud folders: disconnect them so the attack cannot reach them through a synced connection.

Step two: do not pay yet

Paying the ransom feels like the fastest way out, and sometimes people pay because they cannot see another option. But paying is not a fix. It does not guarantee your files come back — the people who locked them are criminals, and there is no customer service desk to complain to. It also marks your business as one that pays, which makes a second attack more likely.

There are also legal considerations in some places around paying attackers, depending on who they are. Do not pay in the first hour. Paying is a decision to make with advice, after you know what your backups can do — not a reflex in the first ten minutes.

Step three: check your backups — from a clean machine

This is the moment your backups either save you or they do not. Check them from a machine you know is clean — not from an infected one, where the attack may be able to see what you are doing.

What you need to know: when was the last good backup, and is it complete? If you have a recent, clean backup that the attack could not reach, you have a way back that does not involve paying anyone. If your backups were connected to the same network and got encrypted too, that is important to know now, not later.

This is also why the backups post in this blog matters: a backup that lives on the same network, always connected, is not a safety net. It is another thing the attack can reach. Backups should be separate — offline, or in a place the attack cannot touch.

Step four: call for help

Call whoever handles IT for you — your IT person, your managed service provider, or a local computer security firm. If you do not have one, call a reputable local IT company and say the words "ransomware" and "small business." They have heard it before and they will know what to do first.

Tell them exactly what happened and when, what you have disconnected, and what your backups look like. Do not try to fix it yourself by running scans or deleting files. Well-meaning cleanup in the first hour can destroy the evidence that would have told you what was taken and how it got in.

Step five: tell your team, and keep notes

Tell your team what is happening, plainly: we have a ransomware attack, do not open attachments, do not plug anything in, do not use the affected machines, and bring anything strange to me immediately. People cannot help if they do not know.

Then start a written note — time, what you saw, what you disconnected, who you called, what they said. This matters for two reasons. First, the people helping you will ask for it. Second, if customer data was involved, you may have obligations to report the incident, and a clear record makes that far easier. Keep the note factual: times, actions, names.

Step six: do not restore until it is clean

The temptation after a backup is found is to restore everything immediately and get back to work. Wait. Restoring onto machines that are still compromised just locks the files again. The attack has to be understood and removed first — how it got in, what it touched, and whether anything was left behind. Your IT help will tell you when it is safe.

Only then do you restore, change every password that mattered, and check the restored systems carefully before going back to normal work.

After it is over

Once you are back up, do the unglamorous work that prevents the next one: find how it got in and close that door, make sure the backups are genuinely separate from the network, turn on multi-factor authentication everywhere it was missing, and update everything. Then write down what happened and what you changed, and keep the first-hour checklist somewhere the whole team can reach it.

Ransomware is frightening because it takes away the thing a business runs on — its own files. But the businesses that get through it are rarely the ones with the most expensive security. They are the ones that stayed calm for an hour, disconnected fast, knew their backups, and called for help instead of paying in a panic. Have the checklist ready before you need it.

Want a second pair of eyes on what your business exposes online? Our done-for-you website security scan starts at $297.

Book a security scan →