Ransomware Response: What to Do in the First HourĀ
RansomwareĀ rarelyĀ arrivesĀ atĀ aĀ convenientĀ time.Ā ItĀ mightĀ startĀ withĀ anĀ employeeĀ reportingĀ thatĀ theyĀ cannotĀ openĀ aĀ file, a server suddenly becoming unavailable, orĀ aĀ ransomĀ noteĀ appearingĀ onĀ multipleĀ computersĀ atĀ once.Ā WithinĀ minutes,Ā theĀ situationĀ canĀ moveĀ fromĀ āsomethingĀ isĀ wrongĀ withĀ ITāĀ toĀ aĀ business-wide incident affectingĀ employees,Ā customers,Ā systems,Ā andĀ criticalĀ operations.Ā
TheĀ firstĀ hourĀ mattersĀ becauseĀ ransomwareĀ canĀ spreadĀ quickly,Ā andĀ theĀ actionsĀ takenĀ duringĀ thoseĀ firstĀ momentsĀ canĀ eitherĀ helpĀ containĀ theĀ incidentĀ orĀ makeĀ theĀ eventualĀ investigationĀ andĀ recoveryĀ moreĀ difficult.Ā ThatĀ doesĀ notĀ meanĀ yourĀ teamĀ needsĀ toĀ solveĀ theĀ attackĀ inĀ 60Ā minutes.Ā ItĀ meansĀ youĀ needĀ toĀ knowĀ whatĀ toĀ doĀ beforeĀ panicĀ takesĀ over.Ā Ā
Here is a practical first-hour response plan for a business facing a suspected ransomware attack.Ā
1. Confirm that you are dealing with an incident.Ā
The first step is to establish what you are seeing without spending too much time trying to diagnose the entire attack.Ā
Signs of ransomware can include files becoming inaccessible or renamed, unusual file extensions, ransom notes, widespread system outages, unexpected account activity, or multiple employees reporting similar problems.Ā
Do not assume that one locked computer is an isolated IT issue if other systems are showing unusual behavior. Look for patterns.Ā
At the same time, avoid letting everyone start investigating independently. Someone should take responsibility for coordinating the response and keeping track of what is happening.Ā
The goal at this stage is not to identify the attacker or ransomware variant. The goal is to determine whether you have a potentially active security incident and move into containment.Ā
2. Isolate affected systems immediately.Ā
This is one of the most important actions in the first hour. CISA recommendsĀ immediately isolating systems known or suspected to be affected. If several systems or network segments appear compromised, the organization may need to take the affected network offline at the switch level. For individual devices, disconnecting the Ethernet cable or removing the device from Wi-Fi can help contain the infection.Ā
The important distinction is betweenĀ isolating a system and simply turning it off. If you can disconnect an affected device from the network, do that first rather than automatically shutting it down. CISA notes that powering down systems can cause the loss of potentially valuable evidence stored in volatile memory, and recommends doing so only when other methods of disconnecting the device are not possible.Ā Ā
This is also why employees should not start randomly unplugging servers or rebooting machines, unless the incident response process calls for it.Ā Ā
The objective is to stop the attacker from moving further through the environment while preserving information that may help determine what happened.Ā

3. Stop normal communication if it could expose your response.Ā
During an active attack, assume that compromised systems and accounts may no longer be trustworthy.Ā
CISA specifically recommends using out-of-band communication methods, such as phone calls, when coordinating an incident. This can reduce the risk of communicating through systems that may be monitored or compromised by the attacker.Ā
In practical terms, that may mean moving the response team to phone calls or another safe communication channel rather than continuing the conversation through potentially compromised corporate email or collaboration tools.Ā
This is also the moment to establish one clear communication path. Employees should know where to report suspicious activity and who is making decisions. Otherwise, an incident can quickly turn into dozens of people making independent decisions, restarting systems, clicking through ransom notes, or contacting customers before the business understands what has happened.Ā
4. Protect your backups. Ā
One of the biggest mistakes during a ransomware incident is treating backups as automatically safe. If the backup environment is connected to the compromised network, attackers may be able to reach it as well.Ā NIST recommendsĀ maintaining backups that are isolated so ransomware cannot readily spread to them.Ā
Do not start restoring systems simply because backups exist. First, determine whether the backups are intact, when they were created, and whether they could have been exposed to the same compromise. You need to know what your clean recovery point actually is before beginning restoration.Ā
This is where preparation pays off. A company that has tested its backups and knows exactly how recovery works is in a very different position from one that discovers during an attack that its ābackupā is a folder sitting on the same network as everything else. Ā

5. Bring the right people into the room. Ā
Ransomware is not only an IT problem. Once an incident is confirmed or strongly suspected, the response may involve IT or security staff, leadership, an MSP or security provider, legal counsel, cyber insurance representatives, and law enforcement.Ā
CISA recommends engaging relevant internal and external teams and keeping senior leaders informed as the situation develops. NIST likewise recommends maintaining an up-to-date list of internal and external contacts as part of ransomware preparedness. That means you should not be searching for your cyber insurance contact, outside counsel, or security provider after the attack has already started.Ā
Ideally, those contacts should already be part of your incident response plan. Leadership also needs to understand what is known, what is not known, what systems are affected, and what decisions need to be made. The technical team should not be left alone to make business decisions about customer communication, regulatory obligations, downtime, or ransom demands.Ā
6. Preserve evidence.Ā
Once the immediate spread has been contained as much as possible, preserve what may help investigators understand the incident. CISA’s ransomware guidance recommends collecting relevant logs and other indicators of compromise and preserving evidence such as system images, memory captures, suspicious files, communications with attackers, and copies of ransom notes.Ā
That means you should resist the temptation to wipe every affected machine and start from scratch simply because that feels like the fastest way forward. A clean rebuild may ultimately be part of recovery, but investigation and remediation should happen with an understanding of how the attacker got in, what they accessed, and whether they still have access. Otherwise, you risk fixing the visible damage while leaving the original problem behind. Ā
7. Document what is happening. Ā
WhenĀ peopleĀ areĀ underĀ pressure,Ā detailsĀ disappearĀ quickly.Ā StartĀ keepingĀ aĀ timelineĀ fromĀ theĀ beginningĀ ofĀ theĀ incident. Record when the first problem was reported, which systems were affected, which systems were isolated, who made key decisions, what evidence was collected, which external parties were contacted, and what communications were sent. Ā
Keep copies of ransom notes and attacker communications. Record relevant timestamps and preserve logs where possible. This information can become important later for forensic investigation, insurance claims, legal advice, regulatory requirements, and recovery planning. It also helps prevent the response team from relying on memory when the incident stretches from hours into days.Ā
8. Do not rush into paying the ransom.Ā
A ransom demand creates enormous pressure because the business may be unable to operate normally, and the attackers may claim that payment is the fastest way out.Ā
However, a ransom note is not a recovery plan. TheĀ FBI does not support paying ransom. It specifically warns that payment does not guarantee that an organization will regain access to its data, and paying does not necessarily prevent stolen information from being exposed. The FBI also encourages ransomware victims to report incidents to law enforcement.Ā
That does not mean the decision can be reduced to a simple ānever payā rule. A real incident can involve legal, operational, financial, insurance, and regulatory considerations, and those decisions should be made with the appropriate professional advice.Ā Ā
TheĀ importantĀ pointĀ forĀ theĀ firstĀ hourĀ isĀ simpler:Ā DoĀ notĀ letĀ theĀ ransomĀ Ā demandĀ dictateĀ yourĀ responseĀ beforeĀ youĀ understandĀ theĀ situation. First contain the attack, preserve evidence, establish what has been affected, assess your recovery options, and bring the right people into the decision-making process. Ā

9. Prioritize recovery instead of trying to restore everything at once.Ā
Once the immediate threat is contained, the next question is not necessarily, āHow do we get every computer back online?āĀ
ItĀ is:Ā WhatĀ doesĀ theĀ businessĀ needĀ toĀ recoverĀ first? CISA recommends identifying and prioritizing critical systems for restoration based on factors such as health and safety, revenue generation, and critical business services. Ā
For one company, that might mean restoring the system that handles customer orders. For another, it could be a case management platform, production environment, financial system, or communications infrastructure.Ā
This is why a ransomware recovery plan should be connected to the business itself, not just an IT asset list.Ā
You need to know which systems are truly critical, what they depend on, where the clean backups are, and how long the business can operate without them.Ā
What Not to Do During the First HourĀ
A ransomware incident creates a natural urge to act immediately, but some actions can make the situation worse.Ā
Avoid taking these actions:Ā
- Rebooting or shutting down affected systems without understanding the implications.Ā
- Continuing to use potentially compromised accounts or devices for incident coordination.Ā
- Deleting ransom notes, suspicious files, emails, or other evidence.Ā
- Restoring from backups before confirming that the backups are clean.Ā
- Giving employees permission to investigate or āfixā affected machines independently.Ā
- Contacting the attacker or negotiating a ransom without the appropriate experts involved.Ā
- Assuming that encrypted files are the only problem.Ā
- Announcing publicly what happened before the organization understands the facts and its obligations.Ā
The first hour is about creating control in a situation where control has suddenly disappeared.Ā
How Klik Solutions Can HelpĀ
Ransomware response is not the time to discover that nobody knows who owns the backup system, which devices are critical, or how to reach the person responsible for cybersecurity.Ā
If your ransomware response plan starts with ācall someone and figure it out,ā it may be time to build a better plan. Contact Klik Solutions to assess your current security and recovery readiness.Ā
Frequently Asked QuestionsĀ
What should I do first if I suspect a ransomware attack?Ā
Start by treating it as a potential security incident. Identify the affected systems and isolate them from the network as quickly and safely as possible. Avoid shutting systems down unless disconnecting them is not possible. This may cause volatile evidence to be lost. Then activate your incident response process and bring in the appropriate technical and leadership teams.Ā
Should I turn off a computer infected with ransomware?Ā
Not automatically. If you can disconnect the affected device from the network, CISA recommends doing that first. Powering down a device may destroy volatile evidence that could help investigators understand the attack. If disconnecting the device is not possible, shutting it down may be necessary to prevent further spread.Ā
Should a business pay the ransom?Ā
The FBI does not support paying ransomware demands and warns that payment does not guarantee that data will be recovered. Any decision involving a ransom should be handled carefully with appropriate legal, cybersecurity, insurance, and leadership input rather than made impulsively during the first minutes of an attack.Ā
How can a company prepare for ransomware before it happens?Ā
Start with the basics. Maintain secure and isolated backups, test restoration, keep systems and software up to date, establish an incident response plan, define responsibilities, maintain emergency contacts, and identify the systems that are most important to business operations. NIST specifically recommends planning and regularly testing recovery procedures rather than waiting until an incident occurs to determine whether they work.Ā
