How to Walk Through the Ransomware Recovery Process Hour by Hour

Ransomware rarely announces itself the moment it lands. Attackers often sit inside a network for days or weeks before triggering the encryption payload, which means the breach itself usually happens long before anyone notices a problem. By the time files start locking up, the clock on recovery has already started, and every decision made in the first few hours shapes how long the outage lasts and how much data comes back clean.

Recovery runs hour by hour from the moment you spot an active infection through the first three days, and the decisions that follow carry just as much weight: when to bring in outside IT support, what happens if backups fail, who you need to notify, and how you confirm the incident is actually closed.

What Recovery Looks Like Before You Start the Clock

Recovery is complete when your systems are verified clean and restored from a backup that predates the initial compromise, not just the point where files were encrypted. That distinction matters because ransomware can sit dormant for weeks before it activates, so a backup from yesterday might still contain the same hidden access the attacker used to get in.

Before anything else happens, you need three answers ready: where your backups actually live, whether they are offline or immutable rather than sitting on the same network as production systems, and who holds admin credentials to act on short notice. If nobody in the building can answer those three questions quickly, the first hours of recovery get spent hunting for information instead of acting on it. This is exactly where established small and midsized business IT support pays for itself, since those three answers should already be documented before an incident happens, not assembled during one.

The Hour by Hour Ransomware Recovery Process

Recovery moves through distinct blocks of time, each ending in a decision that determines what happens next. Isolation in the first thirty minutes leads into scope assessment over the following hours, which feeds the containment and business-continuity decisions made by hour eight, and those decisions set up the restoration work that runs from hour eight through hour seventy-two.

Hour 0 to 30 Minutes, Isolate Without Powering Off

The instinct when a screen lights up with a ransom note is to shut the machine down. Don’t. Live memory on an infected system can hold the encryption keys and forensic evidence investigators need later, and powering off erases both. Instead, disconnect the affected machines from the network: pull the network cable, disable the wireless connection, or if the system is virtual, disconnect the vNIC. The machine stays running and isolated rather than dark.

At the same time, notify whoever owns your incident response, whether that’s an internal IT lead or an outside IT partner. The goal in this window is containment, not diagnosis. You’re stopping the spread across shared drives and connected devices while preserving the evidence that later steps depend on.

Hour 1 to 3, Identify the Ransomware Variant and Check for Data Exfiltration

Once systems are isolated, the next question is what you’re actually dealing with. Ransomware notes and encrypted file extensions often match a known variant, and tools such as ID Ransomware can identify it from a sample file. Knowing the variant matters because some strains have free decryptors published by security researchers, while others do not.

This is also the window to check for data exfiltration, which is separate from encryption. According to the Sophos State of Ransomware 2025 report, cited by Adaptive Security, 50% of ransomware cyberattacks successfully encrypted data, and among those, 28% also involved data exfiltration. If attackers copied data out before locking it down, that changes your notification obligations well beyond just restoring files, so this check needs to happen alongside variant identification, not after it.

Hour 3 to 8, Decide on Backups and Keep the Business Running

With scope roughly understood, locate the most recent backup set and confirm whether the backup system itself was connected to the network during the attack. A backup that stayed connected may be compromised or encrypted right along with production data, which means you can’t assume the newest backup is safe just because it exists.

While that verification happens, your business still needs to function. Systems being offline for assessment doesn’t mean orders stop, invoices stop, or clients stop calling. This is the point to stand up manual workarounds, the same business-continuity step clinics use for paper charts during an EHR outage, applied to general office work instead: paper order forms, manual invoice logs, a phone tree for client updates. The goal is keeping the business moving on paper or by phone while the technical team works the problem without added pressure to rush a restoration.

Hour 8 to 24, Eliminate the Threat and Begin Prioritized Restoration

Once the scope is confirmed and you know which backup set is clean, the next job is removing the malware and closing whatever access point let it in, whether that was a phishing email, an exposed remote access tool, or a stolen credential. Leaving that door open means restoring clean systems only to have them reinfected.

Restoration itself needs to happen in order, not all at once. Domain controllers, DNS, and authentication infrastructure come back first, because every other system depends on them to function. End-user endpoints and applications come after. Mindcore’s ransomware recovery checklist states it directly: Restoring systems in the wrong order creates cascading operational failures that extend downtime. Skipping that sequence to get individual departments back online faster usually costs more time overall than it saves.

Hour 24 to 72, Rebuild Systems and Reset Credentials

For machines that were actually infected, decrypting files in place isn’t enough. Given how long attackers can sit inside a network before activating ransomware, there’s a real chance they planted backdoors beyond the files that got encrypted. Rebuilding from a known-clean image removes both the encrypted files and anything else the attacker left behind, which in-place decryption can’t guarantee.

This is also when every administrative and user credential gets reset, not just the ones tied to obviously affected accounts. Enforce multi-factor authentication across the board before any rebuilt system reconnects to the network. Credentials are one of the most common root causes behind how ransomware gets in to begin with, so this step closes a door that IT security practices should have flagged long before the attack started.

When to Bring In Outside IT Support

A business running with ten to two hundred employees usually doesn’t have an internal security operations team, and that gap shows up fastest at the assessment stage, where forensic tooling and variant identification require skills most in-house IT staff don’t use often enough to stay sharp. Trying to build that expertise mid-incident costs hours you don’t have. This is one of the reasons small and medium business IT support exists as its own category of service, built around exactly this kind of gap.

An outside IT partner is most useful when looped in as early as the isolation step, not called in after internal attempts have already stalled. Brought in early, a co-managed or fully managed IT services partner can guide the first isolation decisions, then take over variant identification, backup verification, and restoration sequencing as the incident moves through its hours. Vintage IT Services works with Austin small and midsized businesses, government agencies, and nonprofits on exactly this kind of co-managed support. Whichever partner you work with, ask how quickly they can engage during an incident, and treat any figure you are given as a measured service benchmark rather than a guaranteed response time.

What to Do If Backups Fail or the Ransom Demand Changes the Situation

When backups turn out to be missing, incomplete, or encrypted right alongside production data, the decision changes. At that point you’re choosing between a free public decryption tool matched to the identified variant, or negotiating the ransom itself as the only remaining path back to your data.

Paying doesn’t guarantee a working decryption key, and it doesn’t end the risk. Roughly 80 percent of organizations that pay a ransom get targeted again, according to a 2024 Cybereason report. If backups have failed and payment becomes the only option on the table, skilled negotiation typically reduces the initial demand by 40 to 60 percent, so that negotiation step is worth pursuing even in a bad situation. Public decryption tool databases have also helped more than 6 million ransomware victims avoid paying at all, which is worth checking before assuming payment is the only route.

Reporting the Attack to Law Enforcement and Your Insurance Carrier

Once scope and variant are confirmed, file a report with the FBI’s Internet Crime Complaint Center, and where appropriate, with CISA or your local FBI field office. This isn’t just a formality. Law enforcement tracks ransomware variants and payment addresses across cases, and your report contributes to that picture even when it doesn’t lead to an immediate recovery of your own data.

Notify your cyber insurance carrier early in the process as well. Many policies require notification within a defined window after discovery, and some require you to use a forensic or negotiation vendor from their approved list before coverage applies. Waiting until restoration is underway to make that call can put coverage at risk over a timing technicality that had nothing to do with the actual incident.

Post-Incident Review and Backup Hardening

Once systems are back up, the work isn’t finished until you know how the attacker got in. Root cause analysis traces the original access point, whether that was a phishing email, an unpatched internet-facing service, or a compromised credential. Exploited vulnerabilities and compromised credentials remain the two most common root causes behind successful ransomware attacks, so those are the first two places to check. This is also the point where ongoing IT security work, patching, credential hygiene, and monitoring, earns its keep, since closing the same gap the attacker used matters more than any single tool you add afterward.

The backup gap that let connected backups get compromised during the attack gets closed by moving to a 3-2-1-1-0 strategy: three copies of your data, on two different types of media, with one copy offsite, one copy offline or immutable, and zero errors confirmed on verification. Immutable backup copies should be retained for at least six months, giving you a clean recovery point even if an infection sits undetected for weeks before it activates. This kind of backup and disaster recovery planning is worth reviewing with your IT provider on a regular schedule, not just after an incident forces the conversation.

How to Confirm the Ransomware Recovery Process Is Complete

Recovery isn’t done just because systems are back online. Each restored system needs to be tested individually before it reconnects to the network, confirming it’s clean rather than assuming the rebuild worked. Data completeness gets checked against the pre-attack state, not just against what the backup happened to contain.

From there, monitoring needs to run for a sustained window with no signs of reinfection before you consider the incident closed. Credentials and multi-factor authentication should be reset network-wide, not just for the accounts directly tied to the attack. The recovery process is genuinely finished only when all four conditions hold: tested systems, validated data, clean monitoring, and reset credentials. That is also a reasonable point to schedule the post-incident review with your managed IT services provider, turning this experience into stronger backup and security practices going forward.

References