Ransomware just locked your files. Don't pay yet.
What to do in the first hour, from a USAF veteran with CompTIA Security+. Read the steps below in order. If you're mid-incident right now, call (208) 918-0636 first and read while I triage with you. The first 60 minutes determine whether your business recovers in days or weeks.
This page is general guidance, not a substitute for engagement with your cyber-insurance carrier's incident-response vendor or breach counsel.
First 60 minutes: do these in order
If you read nothing else on this page, read this list.
- Disconnect affected machines from the network. Unplug the ethernet cable. Turn off Wi-Fi. Do not power them off. Powering off destroys volatile memory that helps identify the strain and trace the attacker. Pulling the network cable stops the spread without losing forensic evidence.
- Photograph the ransom screen with your phone. Get a clear shot of the entire screen including any countdown timer, ransom amount, contact details, and the file extension being used. Timestamp matters. The exact wording of the ransom note matters because it identifies the strain.
- Call your cyber-insurance carrier BEFORE anything else. Most policies have specific incident-response vendors and required workflows. Paying the ransom (or even bringing in a non-approved IR firm) without their consent often voids coverage entirely. Get them on the line first.
- Call me: (208) 918-0636. I triage with you. If your insurance carrier has a designated IR firm, I coordinate with them instead of competing. If they don't, I step in. Either way, I keep you from making the next 12 hours worse.
Don't do this
Each one of these turns a recoverable incident into a much worse one.
- Don't pay the ransom yet. No decryption is guaranteed. Paying marks you as a paying target, and repeat attacks are common. Your insurance may refuse to cover an unauthorized payment.
- Don't reboot or power off affected machines. You lose volatile evidence and may trigger a second wave of encryption on next boot.
- Don't restore from backup yet. If the attacker is still in your environment, restoring just gives them fresh data to encrypt again. Restore comes after containment, not before.
- Don't delete files. Even encrypted files. Some strains are decryptable later when keys are seized; others contain forensic timestamps you'll need.
- Don't post about it publicly. That includes social media, community forums, and customer emails. The attacker may be watching, your insurance carrier has communication protocols, and you may have legal disclosure obligations that come first.
- Don't try to "clean up" yourself. Antivirus scans and registry cleaners destroy forensic evidence and rarely remove the persistence the attacker left behind.
What I do for you
Incident scoping
Which machines are encrypted. Which user accounts were compromised. What data may have been exfiltrated. What persistence mechanisms are still in place. I document it all with timestamps.
Evidence preservation
Disk images of affected systems, log captures, ransom note copies, and chain-of-custody documentation. If law enforcement or your insurance carrier needs the evidence later, it exists.
Insurance coordination
I work with your cyber-insurance carrier's preferred IR firm or stand alone if they don't have one. Communication, scoping, and reporting all kept to the carrier's required format.
Isolated restore from clean backups
Once your environment is verified clean of attacker persistence, I restore from offline / immutable backups into an isolated network segment first. This minimizes re-infection risk. Everything verified before going back to production.
Written incident report
What happened, when, how, and what was done about it. Suitable for handing to clients, your insurance carrier, the AG's office, or a regulator. Written in plain English.
Stay-out hardening
The patches, configurations, and policy changes that keep them from coming back. Detailed in the next section.
Why ransomware happens to small businesses
Industry-wide data. These are not Idaho Proper IT client outcomes.
Verizon's 2024 Data Breach Investigations Report (DBIR) found that ransomware was involved in roughly one-third of all breaches, and the human element (phishing, pretexting, and credential misuse) was a factor in approximately 68% of breaches across all industries. The most common initial access vectors at small businesses haven't changed in years: phishing emails, exposed Remote Desktop (RDP), and unpatched software.
IBM's Cost of a Data Breach Report 2024 placed the global average cost of a data breach at $4.88M, with smaller organizations disproportionately affected by recovery time and lost revenue rather than direct ransom payments. The same report noted that organizations with security AI and automation deployed extensively saved an average of $2.22M per breach.
The pattern is consistent: businesses without MFA on every account, without EDR on every endpoint, and without immutable, tested backups are the ones with the worst outcomes. Businesses that have those three controls in place have a much better chance of recovering without paying.
Sources: Verizon, "2024 Data Breach Investigations Report." IBM Security, "Cost of a Data Breach Report 2024."
What changes so they don't come back
I can stand up a proper defense in 14 to 21 days.
MFA enforcement
Phishing-resistant multi-factor authentication on every M365, VPN, banking, and admin account. No exceptions.
EDR on every endpoint
Behavioral endpoint detection & response replaces basic antivirus. Catches ransomware staging behavior, not just known signatures.
Immutable backups
Daily encrypted backups with immutability. The attacker cannot delete or encrypt the snapshots even with full domain admin access.
Written incident response runbook
The plan you wish you'd had this week. Who to call, in what order, with what scripts. Tested with tabletop exercises.
Staff training
Practical phishing simulation and short, role-relevant training. Most attacks start with a click, so the human attack surface needs fixing too.
Patch & configuration management
Routine patching, vulnerability scanning, and configuration hardening. The hygiene that keeps the front door locked in the first place.
Emergency pricing
$250/hr
emergency rate after hours · 1-hour minimum · scope quote usually same day
Final scope and pricing depend on environment size and incident severity. I aim to give you a written quote the same day as the triage call.