Your IT lead just told you the file servers are encrypted and there's a ransom note on every screen. Email may or may not be compromised. Nobody's sure what's still working. The next 48 hours will determine whether your company recovers cleanly or bleeds cash and credibility for months.
Ransomware attacks have become the dominant cyber threat facing mid-sized companies. They strike fast, encrypt the systems you need to operate, and present you with an ugly choice. But the outcome depends far more on your response than on the attack itself.
Phase 1: Discovery and Immediate Containment
The first hours after discovering ransomware are critical. What you do and don't do in this window determines whether the attack spreads or stays contained.
What Actually Happens in the First Hour
Here's what the first hour typically looks like in practice, because it's never as orderly as the playbooks suggest:
Someone notices they can't open files. They call IT. IT checks and sees ransom notes across a file share. Adrenaline spikes. There's usually a 10-15 minute period of confusion where people are trying to figure out if this is real or a false alarm. Meanwhile, the encryption may still be spreading.
Your immediate priorities, in order:
-
Isolate affected systems from the network. Disconnect infected machines from the network but keep them powered on. This prevents lateral movement while preserving forensic evidence. Don't shut them down -- powering off can destroy evidence forensics teams need.
-
Switch to out-of-band communication. Your corporate email and Slack may be compromised, and the attacker may be reading them. Move your response coordination to personal phones, a WhatsApp group, or whatever you can set up fast. CISA's #StopRansomware Guide specifically warns that after an initial compromise, malicious actors may monitor an organization's activity and communications. Using compromised channels to discuss response strategy can cause attackers to move laterally or deploy ransomware more broadly before networks are taken offline.
-
Activate your incident response team. If you have one. If you don't, this is where having a retainer with a cybersecurity firm pays for itself immediately. If you have neither, your cyber insurance carrier's hotline is your next call -- they'll connect you with an IR firm.
-
Preserve evidence. Don't attempt to clean or restore systems yet. Forensic investigators need to understand how the attack happened.
Warning: Never communicate with the attacker using your corporate email or systems. They may be monitoring your communications. Use out-of-band channels like personal phones or a separate communication platform.
The CEO's role in this first hour isn't technical. It's making sure the right people are in the room, that someone is taking notes, and that nobody makes a panicked decision like wiping servers or replying to the ransom note.
What NOT to Do
Don't Pay Immediately
Rushing to pay the ransom before understanding your options often leads to poor outcomes. Take time to assess your backups, consult experts, and understand what data was actually compromised.
Don't Contact the Attacker Directly
If you do decide to negotiate, use experienced ransomware negotiators. Attackers are skilled at manipulation, and amateur negotiation often increases the ransom demand.
Don't Hide the Incident
Attempting to cover up a ransomware attack almost always backfires. You have legal notification obligations, and discovery of a cover-up destroys trust far more than the attack itself.
Phase 2: Assembling Your Response Team
Ransomware recovery is not an IT problem. It's a business crisis that requires coordinated response across multiple functions.
1Executive Leadership
- CEO for strategic decisions and external communication
- CFO for financial impact assessment and payment decisions
- COO for operational continuity planning
- General Counsel for legal obligations and liability
2Technical Team
- Internal IT/Security lead for system knowledge
- Forensic investigators (usually external)
- Incident response specialists
- Backup and recovery specialists
3External Advisors
- Cyber insurance carrier (notify immediately)
- Breach counsel (specialized cyber attorneys)
- Ransomware negotiation specialists if needed
- Crisis communications firm
4Communications Team
- PR/Communications lead for messaging
- HR for employee communications
- Customer success for client outreach
- Designated spokesperson for media
Industry data consistently shows that the biggest gap here isn't technical -- it's that organizations lack pre-established relationships with breach counsel or forensics firms. According to the IBM Cost of a Data Breach Report (2024), organizations with an incident response team and regularly tested IR plan experience breach costs approximately 35% lower than those without. You don't want to be searching for an incident response company while your systems are encrypted. Get these relationships in place before you need them.
Phase 3: The Communication Plan
How you communicate during a ransomware attack shapes your reputation for years to come. Silence breeds speculation. Transparency builds trust.
Internal Communications
Your employees will know something is wrong. If they don't hear from leadership, they'll fill the void with rumors.
- Within hours: Send a company-wide message acknowledging the incident, confirming leadership is engaged, and providing guidance on what employees should and shouldn't do.
- Daily updates: Even if there's no new information, confirm that work continues and provide a timeline for the next update.
- Clear instructions: Tell employees which systems they can use, how to report suspicious activity, and whom to contact with questions.
External Communications
Stakeholder communication priorities:
✓ Notify cyber insurance carrier within policy timeframes
✓ Alert critical customers proactively before they hear elsewhere
✓ Prepare holding statement for media inquiries
✓ Document everything for regulatory notification requirements
Phase 4: The Pay or Not Pay Decision
This is the question that keeps CEOs awake at night. There's no universally right answer, but there is a framework for making the decision.
The FBI recommends against paying ransoms because payment funds criminal enterprises and doesn't guarantee data recovery. However, they also acknowledge that each organization must make its own decision based on its circumstances.
Factors That Favor NOT Paying
- You have verified, tested backups that can restore operations
- The encrypted data is not critical or can be reconstructed
- The ransom demand exceeds your ability to pay
- The attacker is on a sanctions list (paying would be illegal)
- You have strong reason to believe payment won't result in decryption
Factors That May Favor Paying
- Backups are unavailable, compromised, or too old to be useful
- Extended downtime would cause greater financial harm than the ransom
- Patient safety or critical services are at risk
- The attacker has demonstrated reliability in past incidents
- Legal counsel and insurance carrier support the decision
Data point: According to Coveware research, only 8% of organizations that pay ransoms recover all of their data. The average recovery rate after payment is around 65%. -Coveware Quarterly Ransomware Report
If You Decide to Pay
- Use professional negotiators. They often reduce the ransom demand by 40-60% and know how to verify the attacker can actually decrypt your data.
- Get proof of life. Before any payment, require the attacker to decrypt a few files to prove they have working decryption keys.
- Understand the logistics. Cryptocurrency purchases, wallet setup, and payment execution take time and expertise.
- Plan for failure. Even after payment, decryption tools may not work perfectly. Have a backup plan.
Phase 5: Working with Law Enforcement
Many companies hesitate to involve law enforcement, fearing publicity or complications. This is usually a mistake.
Why You Should Report
- No obligation to disclose publicly: Reporting to the FBI or Secret Service doesn't mean your incident becomes public.
- Access to intelligence: Law enforcement may have decryption keys or intelligence about your specific attacker.
- Potential for recovery: In some cases, law enforcement has helped recover ransom payments.
- It's often required: Many regulations and cyber insurance policies require reporting to authorities.
How to Report
- FBI Internet Crime Complaint Center (IC3): ic3.gov
- CISA: Report through cisa.gov/report
- FBI local field office: For direct engagement on significant incidents
- Secret Service: Particularly for financial sector incidents
"Reporting ransomware attacks to law enforcement is one of the most important things a victim organization can do. It helps us track and disrupt these criminal enterprises, and it may help you recover."
Phase 6: Recovery and Restoration
Recovery from ransomware takes weeks, not days. Set expectations accordingly with your board, your customers, and your employees.
Days 1-3: Triage
- Complete forensic investigation
- Identify all affected systems
- Verify backup integrity
- Establish clean environment
Days 4-14: Rebuild
- Rebuild critical systems first
- Restore data from clean backups
- Implement emergency security controls
- Resume essential operations
Days 15-30+: Harden
- Close vulnerability that enabled attack
- Implement enhanced monitoring
- Update incident response plans
- Conduct lessons learned review
One thing these timelines don't capture: the operational chaos in between. Your sales team can't access their CRM. Finance can't run payroll. Customer-facing teams are fielding calls with no information. Someone has to manage all of that while the technical recovery happens, and it's usually the COO or a senior operations person who ends up running a parallel track of manual workarounds and customer communication.
Phase 7: Post-Incident Improvements
Every ransomware attack reveals gaps in your security posture. The companies that recover best are the ones that use the painful clarity of the moment to fix what they should have fixed before.
Immediate Security Enhancements
Priority improvements post-incident:
✓ Implement MFA on all accounts if not already in place
✓ Deploy endpoint detection and response (EDR)
✓ Segment network to limit lateral movement
✓ Implement immutable, air-gapped backups
✓ Enhance email security and phishing defenses
✓ Establish 24/7 security monitoring
Organizational Changes
Beyond technical controls, consider what organizational changes will prevent recurrence:
- Executive accountability: Assign clear ownership for cybersecurity at the C-level
- Budget reallocation: Redirect resources to prevention based on lessons learned
- Culture shift: Use the incident to drive security awareness throughout the organization
- Vendor review: Assess whether third-party relationships contributed to the attack
Prepare Before You Need This Guide
If you're reading this before an attack, you're in a better position than most. The single most valuable thing you can do right now is establish an incident response retainer with a reputable cybersecurity firm and make sure your backups are tested and immutable. Everything else can be figured out under pressure, but those two things cannot.
For a complete framework on building ransomware resilience, see Cybersecurity for CEOs.