Ransomware remediation: what to do in the first 24 hours
Key takeaways
- Isolate affected devices from the network right away, but avoid routine shutdowns because disconnecting preserves evidence that powering off would destroy, unless isolation is impossible.
- Assign an incident lead with authority and keep a decision log recording what happened, who authorized each action, and what remains uncertain.
- Protect backups before reconnecting them, reset exposed credentials, and close the attacker's entry route before restoring any system into production.
- Removing the malware does not reverse encryption, and the FBI does not support paying ransom because payment does not guarantee data recovery.
Ransomware remediation starts with containing the attack, preserving evidence, and establishing a controlled path to recovery—not immediately wiping computers. During the first 24 hours, prioritize stopping further damage while determining which systems, accounts, and data are affected. This practical sequence follows government and incident-response guidance; use it alongside your organization’s approved response plan and specialist support. (cisa.gov)
What should you do immediately after discovering ransomware?
Immediately isolate affected devices from networks, activate your incident response team, and coordinate through a trusted communication channel. Avoid routine shutdowns or restarts: disconnecting systems can preserve evidence that powering them off would destroy. CISA recommends powering down affected devices when network isolation is not possible to prevent further spread. (cisa.gov)
For an employee, that means disconnecting Ethernet and Wi-Fi, reporting the warning or ransom note, and waiting for instructions. For authorized administrators, containment may involve endpoint isolation or disconnecting affected network segments. Coordinate broader outages with operational owners, especially where interruptions could affect safety or critical services. Isolation limits remote access and spread, but may not stop malicious processes already running locally; seek specialist advice on that trade-off. (cisa.gov)
Use this immediate checklist:
- Isolate affected devices: Remove network connectivity without reconnecting them for convenience.
- Protect unaffected infrastructure: Prioritize critical services and systems attackers could reach next.
- Use separate communications: Choose trusted phone calls or another channel outside the potentially compromised environment.
- Record the discovery: Capture the detection time, affected device names, observed symptoms, and actions taken. (cisa.gov)
Hours 1–4: Establish incident ownership and operating priorities
Assign an incident lead with authority to coordinate technical response, business continuity, and communications. Effective security incident management requires clear decision-making—not several teams independently changing systems. Bring together IT, security, operations, executive leadership, and legal support as appropriate. (ncsc.gov.uk)
As a working arrangement, designate a technical lead to direct containment and investigation, an operations lead to identify essential services and workarounds, and a communications owner to approve updates. Assign someone to maintain a decision log. Record what happened, who authorized each action, and what remains uncertain so the next shift can continue without reconstructing the incident. (ncsc.gov.uk)
Engage an incident-response provider if internal capabilities are insufficient. If you have cyber insurance, review the policy’s response arrangements and contact the insurer about available assistance. Agree on responsibilities before outside responders begin work, including who can isolate infrastructure, collect evidence, and authorize recovery. (cyber.gc.ca)
Treat the time windows in this article as planning aids, not waiting periods. Containment, investigation, and coordination should overlap wherever practical. (learn.microsoft.com)
Hours 1–8: Preserve evidence and determine the scope
Do not assume the first encrypted laptop marks the beginning or full extent of the attack. Ransomware can follow an earlier compromise involving stolen credentials, additional malware, and data theft. Investigators should establish both what is affected now and how attackers reached those systems. (learn.microsoft.com)
Ask qualified responders to preserve relevant system images, memory captures, logs, and malware samples before destructive cleanup where feasible. Prioritize volatile evidence and logs with short retention periods. Preserve ransom notes and encrypted-file details, but do not delay urgent containment to complete forensic collection. (cisa.gov)
Build a working scope assessment around these questions:
- Devices: Which endpoints, servers, and cloud resources show related activity?
- Identities: Which user, administrator, or service accounts may be compromised?
- Applications: Which business services are unavailable, and what dependencies do they require?
- Attacker activity: Is there evidence of ongoing access, malicious communications, or movement between systems?
- Data: What information could attackers access, and is there evidence of theft? (learn.microsoft.com)
Use endpoint, authentication, VPN, firewall, and application records to test your assumptions. Keep “confirmed affected,” “under investigation,” and “not currently showing evidence” separate in the incident log. A device without encrypted files still needs assessment if its accounts or network activity connect it to the intrusion. (learn.microsoft.com)
Hours 4–12: Protect backups and remove attacker access
Protect recovery options before connecting backup storage to affected systems. Consider disconnecting online backup infrastructure until containment is established, and pause synchronization where infected devices could overwrite cloud files. Confirm which backup copies remain available and whether their integrity has been tested. (learn.microsoft.com)
Address compromised identities alongside infected machines. Responders should suspend accounts involved in the attack, reset exposed credentials, and require affected users to authenticate again. Coordinate privileged-account changes carefully so you retain trusted administrative access and do not lock the recovery team out of essential systems. (learn.microsoft.com)
Threat mitigation must also address the entry route. Identify exploited vulnerabilities, exposed remote access, or other weaknesses and correct them before reconnecting restored systems. Rebuilding computers without closing the attacker’s access path risks another compromise. (cyber.gc.ca)
Make the ransomware remediation plan specific: assign an owner, status, dependency, and approval requirement to each task. For example, “restore accounting” should identify the required application, database, authentication service, and validated backup—not simply name the server to restart. (learn.microsoft.com)
Can malware removal alone restore encrypted files?
No. Malware removal addresses malicious software; recovering encrypted files requires a usable backup or an appropriate decryption method. Removing the ransomware does not itself reverse encryption, and a decryptor may not be available for the variant involved. (cyber.gc.ca)
Separate three workstreams when evaluating ransomware solutions:
- Eradication: Remove malicious software and unauthorized access, rebuilding affected devices where appropriate.
- Data recovery: Validate backups or assess a legitimate, variant-specific decryption option.
- Secure restoration: Correct the entry point, patch systems, and restore into a clean, isolated environment. (cyber.gc.ca)
Have specialists assess the ransomware using the ransom note, file extensions, and technical evidence. Ask law enforcement or qualified responders about legitimate recovery options rather than testing unverified tools on your only copies. Preserve recovery material while the team determines the safest approach. (cyber.gc.ca)
The FBI does not support paying ransom, and payment does not guarantee that data will be recovered. Do not let an attacker’s deadline replace coordinated decision-making. Escalate any payment discussion to leadership, legal counsel, and law enforcement rather than treating it as an ordinary IT purchase. (ic3.gov)
Hours 8–24: Prepare a controlled recovery
Begin ransomware recovery only when the response team has established suitable conditions—not because a full day has passed. Verify backups using an uncompromised system, restore into an isolated environment, and address the initial access route before reconnecting services. Prioritize critical business functions and the systems they depend on. (cyber.gc.ca)
Use an approval checklist before returning a service to production:
- Evidence preserved: Necessary collection is complete before wiping or rebuilding.
- Access controlled: Known compromised accounts and entry routes have been addressed.
- Recovery data checked: Backup content has been scanned and its suitability assessed.
- Systems prepared: Restored infrastructure has appropriate patches and security controls.
- Business validation assigned: A service owner can confirm that essential workflows function. (cyber.gc.ca)
For example, restoring a billing database is not enough if staff cannot authenticate or the application configuration is missing. Document dependencies and test the service as a business process, not merely as a powered-on machine. Keep investigation and recovery coordinated so new findings can change restoration decisions. (learn.microsoft.com)
Report the incident and communicate verified facts
In the United States, report ransomware to the FBI through IC3. Preserve details such as the ransom demand, attacker contact information, encrypted-file extensions, and ransomware name if known. Share confirmed information rather than guessing at attribution or scope. (ic3.gov)
Have legal counsel assess applicable notification duties rather than assuming every incident follows one deadline. For healthcare organizations, HHS explains that ransomware affecting protected health information requires a fact-specific breach assessment. Operational restoration does not eliminate the need to investigate possible data exposure. (hhs.gov)
The first-day takeaway
Aim to finish the first day with containment, accountable ownership, preserved evidence, and a documented recovery path—not an unsupported declaration that everything is clean. Keep unresolved questions visible and carry them into the next response period. A controlled recovery is more valuable than a rushed restart that leaves the original compromise unresolved. (ncsc.gov.uk)
Related guides
Sources
- #StopRansomware Guide | CISA
- Disruptive cyber attacks – reducing their impact, reducing the risk | Recovering from a highly disruptive cyber attack | 1. Immediate activities | National Cyber Security Centre
- Ransomware playbook (ITSM.00.099) - Canadian Centre for Cyber Security
- Responding to ransomware attacks - Microsoft Defender XDR | Microsoft Learn
- Microsoft Incident Response ransomware approach and best practices | Microsoft Learn
- Ransomware: How to prevent and recover (ITSAP.00.099) - Canadian Centre for Cyber Security
- Ransomware - Internet Crime Complaint Center (IC3)
- hhs.gov: Index