A ransomware incident requires disciplined decisions before complete answers are available. This checklist gives IT teams a practical sequence for isolating affected systems, preserving evidence, protecting backups, coordinating communications, and restoring services without destroying useful forensic information or allowing the intrusion to continue.
Overview
Ransomware response is both an emergency operation and an investigation. The immediate goal is to stop unauthorized activity and protect people, systems, and recoverable data. The parallel goal is to document what happened well enough to support containment, legal review, insurance requirements, regulatory decisions, and a safe recovery.
Do not treat the appearance of an encrypted file or ransom note as proof that the incident began at that moment. Attackers may have entered earlier, created additional accounts, stolen credentials, copied data, disabled security tools, or reached backup infrastructure before encrypting files. Assume the scope is uncertain until the investigation establishes otherwise.
Activate the organization’s incident response plan and identify one incident lead. That person should maintain the decision log, assign technical work, set update intervals, and prevent conflicting instructions. Involve security, infrastructure, identity, communications, legal, privacy, business continuity, and executive stakeholders according to the organization’s plan. If cyber insurance or contractual response requirements apply, check those obligations early; deadlines and approved contacts can vary.
First priorities
- Protect life, safety, and essential operations, especially in healthcare, manufacturing, utilities, and other environments where an outage can create physical risk.
- Contain the intrusion without taking actions that unnecessarily destroy logs, memory, malware samples, or other evidence.
- Preserve clean backups and prevent the attacker from reaching them.
- Establish a reliable record of decisions, observations, and communications.
- Restore only after the organization understands the likely entry path, persistence mechanisms, and affected systems.
What to track
Use a shared incident record with controlled access. Record the time zone and use synchronized timestamps where possible. Each entry should identify the observer, source of the information, action taken, result, and confidence level. Separate confirmed facts from working hypotheses.
Containment and system status
- Hostnames, users, IP addresses, network segments, cloud resources, and applications showing encryption, suspicious commands, or unusual authentication.
- Systems isolated, powered down, blocked at the firewall, removed from identity services, or placed in a recovery state.
- Known ransom notes, file extensions, attacker messages, suspicious processes, scheduled tasks, services, accounts, and remote-access tools.
- Changes to privileged accounts, multifactor authentication, endpoint protection, logging, domain policies, virtualization platforms, and backup consoles.
- Evidence of lateral movement, credential theft, data staging, archiving, exfiltration, or deletion of logs.
Evidence preservation
Before reimaging or deleting anything, consult the organization’s forensic process and legal contacts. Preserve relevant endpoint, identity, email, VPN, firewall, DNS, proxy, cloud, backup, and application logs. Export copies to a protected location that the suspected attacker cannot alter. Document collection times, systems, tools, and custodians.
For high-value or actively compromised systems, consider collecting volatile information such as running processes, network connections, logged-in users, and memory before shutdown, provided doing so is safe and authorized. Do not open suspicious files casually, execute samples on production systems, or email potentially sensitive evidence without controls. Preserve ransom notes, encrypted samples, phishing messages, malicious attachments, and relevant URLs in a restricted evidence repository.
Patient zero and attack path
Build a timeline that begins before encryption. Review the earliest unusual login, endpoint alert, newly created account, remote-access session, mailbox rule, vulnerability exploit, or abnormal data transfer. Compare identity logs with endpoint and network records. Ask:
- Which account or service was first abused?
- Was multifactor authentication bypassed, unavailable, or misconfigured?
- How did the attacker move from the first system to administrative access?
- Which systems were accessed but not encrypted?
- Could sensitive data have been copied before the ransomware deployment?
Backups and recovery assets
Track every backup tier, including offline, immutable, cloud, snapshot, SaaS, configuration, and database backups. Verify whether backup credentials, management servers, replication targets, and recovery documentation were exposed. Protect known-good copies by restricting access and separating them from compromised identity infrastructure. Do not assume a backup is clean because it completed successfully; validate its age, integrity, malware risk, and ability to support a usable restoration.
For related preparation, review the Breach Response Playbook for SMBs and use a quarterly cybersecurity tabletop exercise to test roles and dependencies.
Cadence and checkpoints
The following sequence is a starting framework. Adjust it for operational risk, system architecture, and the organization’s incident response plan.
| Time window | Primary checkpoint | Decision focus |
|---|---|---|
| First hour | Confirm the signal, appoint an incident lead, protect safety, isolate affected segments, and preserve initial evidence. | Is the activity still spreading, and which actions can stop it with the least evidence loss? |
| First four hours | Secure privileged access, review identity and remote-access activity, protect backups, and identify critical business dependencies. | What is affected, what remains trustworthy, and which services must be kept running or deliberately shut down? |
| First day | Build a preliminary timeline, determine likely entry points, scope possible data access, and establish internal updates. | Can the organization contain the threat, or is additional network isolation required? |
| Recovery planning | Validate clean recovery sources, rebuild compromised identity and management systems, and define restoration order. | Can systems be restored without reintroducing the attacker or relying on unverified credentials? |
| After stabilization | Complete root-cause analysis, review communications and reporting decisions, and capture corrective actions. | What control, process, or dependency allowed the incident, and how will the change be tested? |
Shutdown, isolation, or recovery?
| Choice | Use when | Main trade-off |
|---|---|---|
| Shutdown | A system presents immediate risk, is unsafe to leave connected, or cannot be isolated reliably. | It may stop active behavior but can remove volatile evidence and interrupt critical operations. |
| Isolation | The host or segment can be contained while investigators need access to logs or volatile information. | It preserves more investigative value but may not stop an attacker with alternate access paths. |
| Recovery | The environment is contained, recovery sources are verified, and rebuilding has addressed persistence and identity risks. | It restores operations but can spread the intrusion if systems or credentials are not clean. |
Communicate using a verified channel that was not dependent on the suspected environment. Tell employees what systems to avoid, how to report suspicious activity, and where legitimate updates will appear. Avoid sharing unverified theories or detailed technical information that could help an attacker. Keep customer, regulator, and partner communications coordinated with the appropriate legal and privacy review. The cyber incident communications matrix can help map audiences, owners, and approval steps.
How to interpret changes
New evidence should change the response plan, not merely expand the incident report. A second wave of encryption, new privileged accounts, unexplained outbound traffic, or activity in backup systems suggests containment is incomplete. Pause restoration and reassess trust boundaries.
A quiet network does not necessarily mean the attacker is gone. Silence may reflect a damaged command channel, a pause in activity, or a shift to persistence that is less visible. Treat systems as untrusted until relevant accounts, remote-access paths, endpoint controls, administrative tools, and scheduled tasks have been reviewed.
When evidence conflicts, preserve both records and state the uncertainty explicitly. For example, an endpoint may show a local login while identity logs show no corresponding authentication. That discrepancy could reflect logging gaps, cached credentials, a compromised collector, or a different access route. Do not force a single narrative before validating the sources.
Restoration readiness improves when these conditions are met:
- The likely entry path and persistence mechanisms have been addressed or isolated.
- Privileged credentials and recovery secrets have been reviewed and rotated through a trusted process.
- Recovery sources have been checked for integrity and tested in a controlled environment.
- Logging, monitoring, endpoint protection, and alert routing are working before production services return.
- Restoration order reflects business impact and dependencies rather than convenience.
- An owner is assigned to monitor each restored service for renewed suspicious activity.
Use the third-party incident response checklist when a supplier, managed service, cloud platform, or software provider may be involved. If the initial access involved an exploited vulnerability, the CVE and patch decision guide provides a useful framework for validating affected versions and remediation.
When to revisit
Revisit this ransomware incident checklist at least quarterly, during backup reviews, and after meaningful changes to identity, remote access, cloud infrastructure, network segmentation, or critical vendors. A short review should confirm:
- Incident contacts and escalation paths are current.
- Backup ownership, retention, isolation, and restoration tests are documented.
- Logs are available for the systems needed to build an attack timeline.
- Emergency communication channels work if email or collaboration platforms are unavailable.
- Recovery priorities and service dependencies match current operations.
- Tabletop exercises have tested decisions about shutdown, isolation, evidence, and restoration.
Update the playbook after every exercise and incident, not only after a confirmed ransomware event. Also review it when trusted security advisories describe a technique relevant to your environment, when a backup or monitoring product changes, or when reporting and contractual requirements are updated. Before the next incident, print or securely store an offline copy of essential contacts, recovery steps, network diagrams, and evidence-preservation instructions. A plan that cannot be reached during an outage is not yet a dependable recovery plan.