Blog Cybersecurity

Ransomware Hit Your Business? What to Do in the First Hour

By Evolution IT Services 8 min read

If you are reading this because ransomware just hit your business, slow down for 60 seconds before you do anything. The first hour decides whether the incident costs you a few thousand dollars and a week of pain, or whether it costs you tens of thousands and months of recovery. The actions you take right now matter.

This article is a practical response guide for the first hour of a ransomware incident at a Central Oregon small business. We will cover the steps in order, what not to do, who to call, and how to think about the decisions ahead. Save this page. If something looks like ransomware, come back here.

Ransomware warning on business computer screen

How to tell if what you have is actually ransomware

Common signs of a ransomware incident:

  • Files on your computer or server have strange extensions you do not recognize (.locked.encrypted.enc, random strings).
  • You cannot open documents, images or spreadsheets that opened fine yesterday.
  • Desktop wallpaper is replaced with a ransom message.
  • A text file titled something like README, DECRYPT or HELP sits in multiple folders.
  • Microsoft 365 OneDrive or SharePoint files show mass changes to encrypted versions.
  • Line-of-business software fails to open database files.
  • Servers are unresponsive or showing error messages about missing files.
  • Antivirus has popped up alerts you have not seen before.

Not every "my computer is weird" moment is ransomware. But if you see the first three signs above together, strange file extensions, files not opening, a ransom note, assume it is ransomware and respond accordingly.

The First Hour: Step by Step

Step 1 (minute 0): Stop what you are doing

Do not run antivirus scans, do not try to delete suspicious files, do not restart the computer. Each of these can make recovery harder. Pause. Breathe. Read these steps.

Step 2 (Minute 2): Isolate the Infected Device

Unplug the ethernet cable from the device. Turn off Wi-Fi. Do not shut down: many ransomware families destroy more data on shutdown. Just disconnect from the network. This stops the infection from spreading to other devices.

Step 3 (Minute 5): Isolate the Network

If you can, physically disconnect the server from the network as well. Disconnect any device that could be infected. If you have a dedicated backup server, unplug it immediately: you need those backups intact.

Step 4 (minute 10): Alert staff and stop everyone from using systems

Send a message to all staff: "Do not open emails or files right now. Do not log into any shared systems. Will update soon." You want to prevent anyone else from spreading the infection or logging in and getting themselves compromised.

Step 5 (minute 15): Call your cyber insurance carrier

Most cyber insurance policies require you to notify the carrier as soon as practicable, and many will provide incident response resources. Many policies include a hotline for exactly this moment. Call before you hire an incident response firm: many policies require you to use the carrier's panel vendors. Even if you are not sure the policy covers it, call.

Step 6 (Minute 20): Call Your IT Provider

If you have managed IT services, call them now. Say "ransomware" and whatever details you have. They have tools and training for incident response.

If you do not have an IT provider, call an incident response firm (your insurer's panel firm, if your policy has one). In Central Oregon, you can also text us at (541) 239-3338. We'll tell you what to do next.

Step 7 (Minute 25): Document What You Know

Grab paper and pen (do not type into the compromised device). Write down:

  • When you first noticed the issue.
  • What computer or server shows the problem.
  • What file extensions you see.
  • Any ransom message content (copy it word for word).
  • Who was logged in when it happened.
  • What they were doing just before.
  • Any email attachments or links clicked in the last 48 hours.

Step 8 (Minute 35): Check Backups

From a known-clean device outside the compromised network, log into your backup system's console using separate credentials (not your regular network or domain login). Do not restore anything yet. Verify that recent backups exist and have not been encrypted. Many modern ransomware variants target backups, so this check is critical.

Step 9 (minute 45): Decide who else to call

  • Your attorney, especially if you handle regulated data (healthcare, legal, financial).
  • Your bank, if there is any suspicion of financial impact.
  • Law enforcement: the FBI Portland Field Office or ic3.gov, CISA (report@cisa.gov), and your local sheriff. They often cannot help immediately but file reports help future investigations and may be required for insurance.
  • Your line-of-business software vendor if their software appears affected.

Step 10 (minute 55): Set up communication from a clean device

From a known-clean phone or laptop not connected to the business network, create a text thread or Slack channel for the response team. The compromised network is not safe for incident coordination.

Business computer locked with ransomware emergency

What NOT to Do in the First Hour

  • Do not pay the ransom. Not until you have talked to your insurer and attorney. Payment often does not recover data, may violate sanctions regulations, and marks you as a target for future attacks.
  • Do not try to decrypt files yourself. You will almost certainly make it worse.
  • Do not reboot the infected device. Many ransomware strains do destructive things on reboot.
  • Do not reconnect devices to the network to check if things work. You will spread the infection.
  • Do not delete the ransom note or encrypted files. Your incident response team needs them.
  • Do not post about it on social media. Attackers monitor; so do your clients.
  • Do not promise anyone a timeline. You do not know yet.
  • Do not log into the compromised network, even from a known-clean device. Your credentials could be captured. Reach the backup console only as described in Step 8: from outside the compromised network, with separate credentials.

What Happens in Hours 2 Through 24

Once the first hour of containment is done, the response moves into assessment and planning:

  • Scope the infection. How many devices? Which servers? What data? Your IT team or incident response firm does this.
  • Identify the variant. Different ransomware families have different behaviors, decryption availability, and insurance implications.
  • Preserve forensic evidence. Insurance and legal need it.
  • Verify backups. Confirm you can restore clean data.
  • Decide on the recovery path. Restore from backup, pay the ransom (last resort), or rebuild from scratch.
  • Notify stakeholders. Owner, insurer, legal, affected clients (if required).
  • Begin the recovery plan. Rebuild infected machines, restore data from clean backups, change all credentials.

The Real Timeline for Ransomware Recovery

Honest expectations for a Central Oregon small business:

  • 24 to 48 hours: Containment. The spread is stopped. Scope is understood.
  • Days 2 to 5: Recovery of critical systems. Email, line-of-business software, point-of-sale. Business can operate again, with pain.
  • Days 5 to 14: Recovery of secondary systems. Full file restoration. Rebuild of infected workstations.
  • Weeks 2 to 4: Cleanup, documentation, insurance claim processing, client notification if required.
  • Months 1 to 6: Monitoring for any lingering compromise. Security improvements to prevent recurrence. Legal and compliance follow-up.

For a 15 to 25 person business, expect weeks of partial disruption and recovery costs that often run well into the tens of thousands of dollars. Costs are highest when backups are not working, encryption is complete, and clients or regulators are involved.

IT professional analyzing security incident on laptop

The Ransom Payment Question

If recovery from backups is not possible, you will face the ransom payment question. Honest guidance:

  • Paying does not guarantee recovery; surveys such as Sophos's State of Ransomware report payers typically get back only part of their data.
  • Payment can trigger US Treasury sanctions compliance issues if the ransomware is attributed to a sanctioned entity.
  • Payment marks you as a target. Businesses that pay are more likely to be attacked again.
  • Insurance may or may not cover payment. Many policies now exclude it or require specific approvals.
  • Negotiation sometimes reduces the ransom amount significantly. Specialist incident response firms handle this.
  • Payment should only be considered when recovery from backup is confirmed impossible and after insurance and legal consultation.

Why Most Ransomware Incidents Happen

In small businesses, the overwhelming majority of ransomware incidents trace back to one of a few initial access methods:

  1. Phishing email. A staff member clicked a link, entered credentials, or opened an attachment.
  2. Exploited internet-facing devices. Unpatched vulnerabilities in firewalls, VPN appliances and other remote access gear are one of the top ways attackers get in.
  3. Compromised remote access. Weak VPN or Remote Desktop configurations exposed to the internet.
  4. Compromised third-party vendor. A connected service was breached and used to reach your network.

All of these are preventable with routine controls: multi-factor authentication, modern endpoint protection, no exposed RDP, patching, phishing training, backup. The vast majority of ransomware incidents at small businesses happen to organizations missing at least one of these.

What to Do Before the Next Incident

If you have been through a ransomware incident or want to make sure you survive the next one:

  • Enable multi-factor authentication on everything that supports it.
  • Deploy modern endpoint detection and response: SentinelOne, CrowdStrike, Microsoft Defender for Business.
  • Keep Windows, macOS, firewalls, Wi-Fi gear and line-of-business software patched.
  • Run phishing training several times a year.
  • Back up to immutable storage (ransomware cannot encrypt it). Include Microsoft 365 and Google Workspace in your backup.
  • Test restore of backups quarterly.
  • Remove exposed Remote Desktop and tighten VPN access.
  • Review and tighten administrative privileges: most staff do not need admin access.
  • Document an incident response plan so the first hour has a playbook.
  • Review cyber insurance coverage and make sure you meet all required controls.
Hard drive and data recovery tools on technician desk

Short Version

If ransomware just hit your business: isolate the infected devices from the network, call your cyber insurance carrier, call your IT provider, document what you know, check that backups are intact, and do not reboot, decrypt, pay the ransom or try to clean the infected device. The first hour determines whether the incident becomes a bad week or a bad quarter.

If you are in the middle of a ransomware incident at a Central Oregon business and need help right now, text (541) 239-3338 or call (541) 239-3338. We'll tell you what to do next. If you want to put the preventive controls in place before an incident, book a free 30-minute security consultation.