How to Respond to a Ransomware Attack: The First 24 Hours


Ransomware can appear as locked files, ransom notes, or unusual system behavior. The first 24 hours affect containment, evidence preservation, and recovery options. Plan how to respond to a ransomware attack before an incident. This guide explains key decisions for that first day; the response team must adapt the sequence to the facts.

Dive Deeper with Our Podcast!

Listen to the Episode: How to Respond to a Ransomware Attack: The First 24 Hours

Subscribe: YouTube | Spotify | Amazon

Before the Timeline Starts: Why Preparation Matters More Than Reaction

Prepare the response before an incident. A written plan, tested backups, and clear roles help teams act under pressure. Name the decision-makers and verify their contact details. If an attack is active, engage qualified responders while carrying out authorized containment steps.

Hour 0 to 1: Contain Without Destroying Evidence

The immediate priority is stopping the spread without destroying information that will matter for recovery and investigation.

  • Disconnect affected systems from the network rather than shutting them down. Unplug the network cable or disable Wi-Fi. Powering off a device can destroy evidence in memory that forensic investigators need. Some ransomware can also cause further damage on shutdown, depending on its design.
  • Isolate, don’t necessarily power off, affected network segments. If the attack appears to be spreading across multiple systems, disconnecting a switch or segment from the broader network can slow the spread while preserving the state of individual machines.
  • Do not pay the ransom at this stage, and do not communicate with the attacker yet. Any ransom decision should come later, with input from legal counsel, insurance, and incident response professionals — not as an immediate reaction in the first hour.
  • Preserve the ransom note and any visible attacker communication — photograph screens if needed rather than closing windows, since this information is useful for investigators and may be required for insurance claims.

Hour 1 to 4: Activate Your Response Team and Notify the Right People

  • Notify your IT or managed security provider immediately if they weren’t the ones who discovered the incident. If you don’t have a specialized incident response contact already, this is the moment to establish one rather than trying to handle a ransomware incident purely with general IT support.
  • Loop in leadership — ownership, executive team — so decisions about business continuity, communication, and potential ransom considerations have the right authority behind them.
  • Contact legal counsel early, particularly if the incident may involve customer or employee data. State and industry rules often set specific notification deadlines. Those deadlines may start at discovery, before the team knows the full scope.
  • Contact your cyber insurance carrier if you have a policy. Many policies set a notification window and specify which incident response or forensics vendors they approve.
  • Avoid broad internal communication over potentially compromised systems. If email or internal chat may be compromised, use an alternate communication channel (personal phones, a separate unaffected system) to coordinate the response.

Hour 4 to 12: Assess Scope Without Rushing to Conclusions

  • Identify affected and unaffected systems. Then assess whether unaffected systems can keep operating or need isolation as a precaution.
  • Identify how the attacker likely gained access — a phishing email, a compromised remote access credential, an exposed and unpatched service — since this affects both containment and how you prevent re-entry before restoring systems.
  • Check backup integrity carefully before assuming backups are clean. Some ransomware attacks sit undetected for days or weeks before triggering, meaning recent backups could potentially include a dormant copy of the malware. This is where having tested, versioned backups with some retention history becomes critical rather than theoretical.
  • Resist the urge to rebuild immediately before understanding how the attacker got in. Restoring systems without closing the original entry point often results in a second, faster-moving attack within days.

Hour 12 to 24: Begin Structured Recovery Planning

  • Prioritize systems for restoration based on business criticality — what absolutely must come back online first versus what can wait a few additional days without catastrophic impact.
  • Decide on the ransom question deliberately, not reactively. Law enforcement (FBI guidance in the United States) generally discourages paying ransoms, partly because payment doesn’t guarantee data recovery and funds further attacks. That said, this is ultimately a business decision made with legal, insurance, and incident response input — not something to decide alone under pressure in the first few hours.
  • Begin drafting external communication if the incident may involve customer or partner data. Work with legal counsel on timing and required disclosures rather than issuing ad-hoc messages.
  • Document everything — timeline of discovery, actions taken, systems affected — since this documentation matters for insurance claims, potential regulatory reporting, and post-incident review.

Who Should Be in the Room During the First 24 Hours

A ransomware incident requires decisions across the business. Include the IT or security lead, an executive with decision authority, legal counsel, and qualified incident responders. Smaller organizations should identify outside specialists in advance. Keep their contact details available outside the affected network.

Assign separate owners for employee, customer, partner, and media communications. Those owners should coordinate with legal counsel and the incident lead. Confirm facts before discussing the cause, scope, or recovery timeline. Record what the team communicated and when.

What Happens After the First 24 Hours

Recovery may extend beyond the first day. Teams must restore systems, address the entry point, validate access, and review the incident. Timing depends on the systems and data involved. Early containment and evidence preservation support those decisions without guaranteeing a recovery time.

A Pre-Built Incident Response Checklist

Rather than building this list during an actual incident, prepare it in advance and keep it somewhere accessible even if primary systems are down (printed, or stored on a personal device):

  • Contact information for your IT/security provider, cyber insurance carrier, and legal counsel, kept somewhere accessible outside the primary network.
  • A clear decision-maker identified in advance for ransom-related decisions, rather than figuring out authority during the incident itself.
  • Confirmation that backups are tested regularly and retained with enough history to avoid restoring a dormant infected copy.
  • A documented, tested process for isolating network segments quickly without full shutdown.
  • A pre-identified alternate communication channel for the response team if primary systems are compromised.
  • A basic understanding, in advance, of what data your business holds that would trigger regulatory notification obligations if exposed.

Why Prevention Still Matters Most

Nothing in this guide is a substitute for preventing ransomware from succeeding in the first place. Multi-factor authentication on all remote access, actively monitored endpoint detection, regular patching, and ongoing security awareness training close the majority of common entry points attackers rely on. Businesses that invest in these fundamentals significantly reduce both the likelihood and severity of a ransomware incident compared to those relying solely on a response plan after the fact. Review our overview of cyber security services for the baseline protections every business should have in place well before an incident occurs. Businesses that prefer those fundamentals maintained for them can have them delivered through managed IT services in Irvine or managed IT services in Orange County.

Backup strategy deserves specific attention in the ransomware context, since recovery speed depends almost entirely on backup quality and testing — see our breakdown of data backup and recovery for what a properly tested, ransomware-resilient backup strategy should include, including offline or immutable copies that an attacker with network access can’t also encrypt or delete. Businesses wanting to validate whether their current defenses would actually catch an attack before it reaches the ransomware stage should also consider periodic penetration testing, which tests real-world exploitability rather than relying on assumptions about current security posture.

Frequently Asked Questions

Should we ever pay the ransom?

This is a case-by-case decision involving legal counsel, insurance, and incident response professionals, not something to decide reactively in the first hours. Law enforcement generally discourages payment since it doesn’t guarantee recovery and funds future attacks, but the decision ultimately depends on the specific circumstances, available backups, and business impact of continued downtime.

Why shouldn’t we just power off affected computers immediately?

Shutdown can destroy evidence held in memory, while leaving a compromised system connected can allow further damage. Isolate affected systems where practical and involve qualified responders. They should decide when shutdown is necessary based on the spread risk and evidence needs.

How do we know if our backups are safe to restore from?

Check backup integrity and timing carefully before restoring, since some ransomware sits dormant for days or weeks before triggering, meaning recent backups could include an infected copy. Backups with sufficient retention history and offline or immutable copies that couldn’t be encrypted alongside the rest of the network are the safest starting point for restoration.

Do we need to notify customers or regulators after a ransomware attack?

Notification duties depend on the data, applicable law, contracts, and confirmed facts. Different rules have different triggers and deadlines. Engage legal counsel early, record when the team learned relevant facts, and track each applicable requirement.

Who should be responsible for deciding what to communicate externally during an active incident?

Designate this in advance as part of your incident response plan — typically a single executive or communications lead working closely with legal counsel — rather than leaving it to whoever happens to be available when a customer or reporter asks a question. Premature or inconsistent public statements during an unfolding incident frequently create more lasting damage than the technical disruption itself.

Don’t wait for an active incident to find out your response plan has gaps. Get in touch to build or review an incident response plan before you need one.

A short planning session now, walking through exactly who does what in the first hours of an incident, is far cheaper and less stressful than discovering those gaps while systems are actually down and the business is losing revenue by the hour.

A Brief Word on Practicing the Plan

Test the written plan with a tabletop exercise. Walk through a realistic ransomware scenario with the people who would respond, without changing production systems. Check contact numbers, decision authority, backup assumptions, and communication paths. Record gaps, assign owners, and test the revised process after material changes.

Knowing how to respond to a ransomware attack is as much about preparation as reaction — the businesses that recover fastest are the ones who had a plan, tested backups, and clear decision-making authority established well before the first 24 hours ever started.

Ravi JainAuthor posts

Avatar for Ravi Jain

Technijian was founded in November of 2000 by Ravi Jain with the goal of providing technology support for small to midsize companies. As the company grew in size, it also expanded its services to address the growing needs of its loyal client base. From its humble beginnings as a one-man-IT-shop, Technijian now employs teams of support staff and engineers in domestic and international offices. Technijian’s US-based office provides the primary line of communication for customers, ensuring each customer enjoys the personalized service for which Technijian has become known.

Comments are disabled