Hit by a Ransomware Attack? 7 Steps to Take in the First 72 Hours 

A ransomware attack can disrupt business operations, lock you out of important files and expose sensitive information. What your organisation does in the first few hours can decide how well the incident is contained and how quickly operations recover. 

The first 72 hours should focus on limiting the impact, understanding what happened, protecting evidence and coordinating recovery. Not every incident follows the same timeline, so actions should be guided by how severe the attack is and the advice of qualified cybersecurity professionals. 

Here are seven steps businesses should prioritise after discovering a ransomware attack. They line up closely with the incident response checklist in the #StopRansomware Guide from the US Cybersecurity and Infrastructure Security Agency, one of the most widely used references on ransomware response. 

1. Isolate Affected Systems Immediately

The first priority is to stop the incident from spreading to other devices and systems. 

If a laptop, server or other endpoint shows signs of ransomware, follow your incident response procedures to disconnect the affected device from wired and wireless networks. Your IT or cybersecurity team should then assess whether other systems also need to be isolated. 

Avoid making broad changes to the network without understanding their impact, especially where critical business services are involved. Controls such as network access control make it easier to isolate specific devices without taking down the whole network. 

Your response team should identify which devices are affected, which services are still running and whether there are signs of further suspicious activity. 

Why it matters: Containing affected systems limits further disruption while the investigation begins. 

2. Activate Your Incident Response Team

A ransomware incident should never be handled like an ordinary IT support ticket. 

Notify the relevant internal stakeholders, which may include IT, cybersecurity, management, legal, compliance and communications teams. If your business uses an external IT support provider or a managed Security Operation Centre (SOC), trigger the agreed escalation process. 

Assign clear responsibilities for technical investigation, business decisions, recovery coordination and external communications. 

If critical services are affected, management should also decide which business operations take priority. 

Why it matters: A coordinated response reduces confusion and makes sure important decisions are made by the right people. 

3. Preserve Evidence and Establish What Happened

Once the incident is contained as far as reasonably possible, your response team needs to understand its scope. 

Preserve relevant security logs, system records, endpoint alerts, suspicious emails and any other available evidence. Record when the incident was discovered, which systems were affected and what actions have already been taken. 

Where possible, have qualified incident responders collect and analyse evidence before systems are rebuilt or heavily modified. 

The investigation should establish key facts, including: 

  • Which systems and accounts may be affected. 
  • When suspicious activity may have started. 
  • Whether unauthorised access is still occurring. 
  • Whether sensitive data may have been accessed or taken. 
  • Which business services are disrupted. 

For a closer look at how a structured investigation works, see our guide on how a Security Operation Centre responds to a cyber crisis. 

Why it matters: Understanding the incident helps the business choose the right containment and recovery measures instead of working from assumptions. 

4. Check Whether Business Data Has Been Exposed

Ransomware incidents are not always just about encrypted files. Some attackers also steal data and threaten to publish it. 

Your investigation should therefore check whether personal data, customer records, employee information, financial information or confidential business documents may have been accessed or copied out. 

If personal data may have been compromised, bring in your legal or compliance team quickly to assess notification duties under Malaysia’s personal data protection framework or other applicable laws. The Commissioner’s guidelines on data breach notification explain when a breach must be reported. 

Designated National Critical Information Infrastructure (NCII) entities and regulated organisations may have additional reporting duties. Requirements and deadlines depend on the organisation and the circumstances of the incident. 

Why it matters: Restoring systems does not remove the risks linked to exposed data or outstanding legal obligations. 

5. Verify Backups Before Starting Recovery

Backups may be essential to getting the business running again, but they must be checked before use. 

Your IT team or recovery specialists should confirm which backups are still available, whether they have been affected and whether they contain the data needed to restore critical services. 

Before restoring systems, make sure the underlying security issue has been dealt with well enough to reduce the risk of reinfection. Prioritise recovery based on business importance, system dependencies and your recovery objectives. 

The recovery process should include: 

  • Identifying clean and usable backup copies. 
  • Checking backup integrity and recovery points. 
  • Prioritising critical systems and business data. 
  • Restoring systems in a controlled environment where appropriate. 
  • Testing recovered systems before returning them to normal operations. 

Why it matters: A rushed restoration can bring infected systems back online before the threat has been removed. 

6. Assess Reporting Requirements and Get Specialist Support

During the first 72 hours, the business should work out whether the incident triggers any reporting obligations and whether specialist help is needed. 

Depending on the circumstances, this may involve cybersecurity authorities, law enforcement, regulators, insurers or legal advisers. 

For Malaysian organisations, the requirements can differ depending on whether the incident involves personal data, designated NCII, a regulated financial institution or suspected criminal activity. 

Do not assume every ransomware incident has the same notification deadline. Identify the relevant legal and regulatory requirements as early as possible. 

If your internal team lacks the necessary expertise, bring in qualified incident response specialists to help with containment, forensic investigation and recovery planning. 

Why it matters: Specialist support helps the organisation make informed decisions while meeting its technical, operational and compliance responsibilities. 

7. Build a Recovery Plan and Prevent Another Attack

By the end of the first 72 hours, the organisation should have a clearer picture of the incident and a coordinated plan for the next stage. 

Full recovery may take longer, especially if many systems are affected. The immediate goal is to set priorities, identify remaining risks and agree on next actions. 

The recovery plan should address: 

  • Which systems need to be restored first. 
  • Which security weaknesses need fixing. 
  • How compromised accounts and access credentials will be secured. 
  • How restored systems will be checked and monitored. 
  • Who is responsible for each recovery action. 
  • How business operations and stakeholders will be kept updated. 

Once the immediate incident is over, review what happened and identify improvements to endpoint protection, network security, access controls, backup arrangements and incident response procedures. An independent review is one of the reasons businesses bring in outside security expertise after a serious incident. 

Why it matters: Recovery should not stop at getting systems running again. The business also needs to reduce the chance and impact of another attack. 

What About Paying the Ransom? 

Paying a ransom does not guarantee that files will be restored, that stolen information will be deleted or that the attackers will not come back. 

Any decision about a ransom demand should be escalated to senior management and the appropriate legal, cybersecurity and law enforcement advisers. Organisations should also consider applicable sanctions and other legal restrictions. 

The immediate priorities stay the same: containment, evidence preservation, understanding the impact and setting up a safe recovery process. 

How ACEiT Supports Ransomware Readiness and Response 

ACEiT provides cybersecurity capabilities through AceTeam Connect, the group’s managed cybersecurity arm, including Security Operation Centre services, threat intelligence, managed security services and network security solutions. 

These capabilities help businesses strengthen security visibility, spot suspicious activity and improve how they monitor and respond to threats. The support available during an active ransomware attack depends on the agreed service scope and the response capabilities required. 

Businesses should also agree clear escalation arrangements with their IT and cybersecurity providers before an incident happens. Knowing who to contact and what support is available reduces delays during a crisis. 

Concerned about your business’s ransomware exposure? Talk to ACEiT and explore how its cybersecurity services can support your security monitoring, protection and incident response readiness. 

Frequently Asked Questions (FAQ)

1. What should a business do first during a ransomware attack?

The first priority is to contain the incident by isolating affected systems in line with your incident response plan. Notify the relevant IT and cybersecurity teams, and avoid actions that could spread the incident or destroy important evidence. 

2. Can a ransomware attack be resolved within 72 hours?

Some incidents can be contained within this period, but full investigation and recovery may take longer. The timeline depends on the number of affected systems, the extent of the compromise, whether clean backups are available and how complex the recovery is. 

3. Should a business shut down its entire network after a ransomware attack?

Not automatically. The right response depends on the scope and severity of the incident. Qualified responders should decide whether specific devices, network segments or wider services need to be isolated. 

4.Should a business report a ransomware attack in Malaysia?

It depends on the circumstances and the laws that apply to the organisation. An incident may trigger reporting duties if it involves a reportable personal data breach, designated NCII, regulated services or other applicable requirements. Organisations should assess these obligations promptly. 

5. Can backups protect a business from ransomware?

Backups support recovery, but they are not a complete defence. Their value depends on whether they are intact, accessible, recent enough and protected from the incident. Businesses should test their recovery procedures regularly. 

Conclusion

The first 72 hours after a ransomware attack are critical for containing the incident, understanding its impact and planning recovery. Businesses should isolate affected systems, coordinate the response, preserve evidence, check for data exposure, verify backups, review reporting obligations and set up a controlled recovery plan. 

Preparation matters too. Clear incident response procedures, tested backups and effective cybersecurity monitoring help organisations respond with more confidence when an attack happens. 

For businesses looking to strengthen their defences, ACEiT offers cybersecurity capabilities that support a more structured approach to security monitoring and incident response readiness.