Security team in an operations center working on ransomware incident response

August 21, 2026 | Cybersecurity

Incident Response for Ransomware: A Step-by-Step Recovery Guide

Get a clear guide to ransomware incident response for the first 24 hours: contain, assess, protect backups, recover and meet notification duties.

The first sign is usually mundane. Files will not open, a shared drive is empty, or a note appears on a screen demanding payment. In the next few minutes, decisions made under pressure will shape how long the recovery takes and how much damage the business absorbs.

This guide walks through the first 24 hours of a ransomware incident, in order, and then covers the days that follow. It assumes you have some kind of plan and a few capable people, and it is meant to be printed and kept somewhere that does not depend on your own network. If you do not have a plan yet, the last section tells you how to build the minimum.

Hour 0 to 1: Contain and declare

Your first goal is to stop the spread without destroying evidence.

  • Declare an incident and name an incident commander. One person makes the calls. Everyone else supports.
  • Isolate affected systems from the network. Disconnect cables, disable wireless, or use your endpoint or network controls to quarantine hosts. Do not shut machines down unless you have no other way to stop encryption, because memory holds useful evidence.
  • Do not wipe or reimage yet. You need to understand how the attacker got in before you rebuild, or they will return.
  • Disable compromised accounts and, if you can, reset credentials for privileged accounts from a clean device.
  • Switch to out-of-band communication. Assume email and chat may be monitored by the attacker. Use phones, a separate messaging channel or a pre-agreed alternative.

Hour 1 to 4: Assemble the team and assess

Bring in the people you will need, and make sure each knows their role.

  1. Technical lead to direct investigation and containment.
  2. Legal counsel, ideally engaged early so that investigation work can be conducted under privilege where appropriate.
  3. Executive sponsor to approve major decisions and handle board communication.
  4. Communications lead for employees, customers and press.
  5. External specialists, such as an incident response firm and your cyber insurance carrier, if you have a policy. Many policies require notifying the carrier promptly and using approved responders, so check before spending money.

Start a written log. Record every action, who took it and when. This log becomes your evidence for insurers, regulators and any later legal process, and it keeps the team from repeating or contradicting itself.

Then scope the damage. Which systems are encrypted? Which are still healthy? Is there evidence that data was copied out before encryption? Modern ransomware commonly involves both encryption and theft of data, so treat any ransomware event as a potential data breach until you can show otherwise.

Hour 4 to 12: Protect the backups and find the way in

Your recovery depends on backups, and attackers know it. Check these first.

  • Are your backups intact, and are they isolated from the compromised network? Offline or immutable copies are the ones to trust.
  • Do the backup administration credentials still belong to you? If not, assume the backups are at risk.
  • Has anything been deleted, encrypted or tampered with?

In parallel, investigate how the attacker got in. Common routes include stolen credentials, exposed remote access services, unpatched internet-facing systems and phishing. You are looking for the entry point, the accounts used, any persistence mechanisms left behind, and signs of data staging or exfiltration. Eradication without this knowledge is guesswork. Regular penetration testing helps you find those same routes before an attacker does.

Hour 12 to 24: Decide on recovery and notifications

Decide the recovery approach

Prioritize systems by business need, using the tiers from your continuity planning if you have them. Rebuild from known-good images rather than cleaning infected machines. Restore data only after you are confident the environment is clean, and scan restored data before reconnecting it. Bring up identity services first, since almost everything depends on them, then critical applications, then the rest.

Think carefully about the ransom

Paying is a business, legal and ethical decision that belongs with executives and counsel, not with the technical team alone. Payment does not guarantee a working decryptor or that stolen data is deleted. In some cases, payments to sanctioned parties can create legal exposure. Law enforcement can sometimes provide help and context, so consider contacting them regardless of what you decide.

Map your notification duties

Which obligations apply depends on your industry, location and contracts, so get counsel's view early. Some well-known examples:

  • HIPAA: covered entities must notify affected individuals without unreasonable delay and no later than 60 days after discovery of a breach of unsecured protected health information. Ransomware involving protected health information is generally presumed to be a breach unless a risk assessment shows a low probability of compromise.
  • GDPR: a personal data breach must generally be reported to the supervisory authority within 72 hours of becoming aware of it, where it is likely to create a risk to individuals.
  • SEC rules: public companies must disclose a material cybersecurity incident on Form 8-K within four business days of determining that it is material.
  • State laws and contracts: state breach notification laws and customer agreements often set their own deadlines and content requirements.

Write down the clock for each obligation as soon as you know it applies, and track it on the incident log.

Days 2 to 14: Recover and learn

After the first day, the work shifts from emergency to disciplined restoration. Keep a single prioritized recovery list, update leadership on a fixed schedule, and keep communicating with employees and customers with accurate, plain information. Do not speculate about root cause or data loss in public until you have evidence.

Before returning to normal operation, close the entry point, rotate credentials across the environment, rebuild or verify domain and identity infrastructure, and add monitoring for the attacker's known methods. Then hold a blameless post-incident review. Document what worked, what failed, and what you will change, with owners and dates.

Where to start

The time to prepare is before the screen goes dark. Five steps give you a workable minimum:

  1. Write a one-page incident plan with roles, phone numbers, decision authority and an out-of-band communication method.
  2. Verify your backups. Keep at least one copy offline or immutable and test a full restore of a critical system.
  3. Line up outside help in advance: counsel, a response firm and your insurer's contact process.
  4. Run a tabletop exercise on a ransomware scenario, including the notification decisions.
  5. Close the common doors: multi-factor authentication on remote access and admin accounts, prompt patching of internet-facing systems, and limited standing privileges.

If you want help building or pressure-testing your response plan, our virtual CISO team can help, or get in touch.

Written By: Ken Pomella