Ransomware:
Understanding and Defeating Digital Extortion
From the $189 AIDS Trojan to multi-million dollar criminal enterprises. This guide covers the full ransomware landscape -- attack lifecycle, defense strategies, incident response playbooks, and compliance obligations -- sourced from CISA, FBI, NIST, and industry research.
What Is Ransomware?
Ransomware is a category of malware that encrypts files, locks systems, or steals data -- then demands payment for restoration or non-disclosure. What started as a $189 demand distributed on floppy disks has evolved into a multi-billion dollar criminal enterprise with affiliate programs, negotiation teams, and dedicated leak sites.
Modern ransomware operations target businesses, critical infrastructure, and healthcare systems for maximum leverage. Attackers spend days to weeks inside a network before deploying encryption, exfiltrating data, deleting backups, and issuing ransom demands that routinely exceed millions of dollars.
Who Needs This
59% of organizations were hit by ransomware in 2024. The average total cost of recovery reached $1.85M, while average ransom demands climbed to $2.73M. Ransomware groups now operate as professional criminal enterprises with RaaS (Ransomware-as-a-Service) models, supply chain attacks, and encryption-less extortion tactics that bypass traditional defenses entirely.
Key Concepts
Ransomware defense spans backup architecture (immutable, air-gapped), endpoint detection and response (EDR), network segmentation, email security, patch management, and incident response planning. This page covers each domain with practitioner-level depth, from the attack lifecycle to compliance reporting obligations.
The Ransomware Threat Landscape
The Evolution of Ransomware
Created by biologist Joseph Popp, the AIDS Trojan (also called PC Cyborg) used simple symmetric cryptography to hide file names and demand payment. The encryption was weak enough to reverse, but the concept of holding data hostage for payment was born. It would take over two decades for the model to become commercially viable for criminals.
Reveton pioneered the affiliate distribution model that would later define the ransomware economy. Operators provided the malware and infrastructure while affiliates handled distribution, splitting profits. The social engineering component -- fake FBI or Interpol warnings -- exploited fear and shame to drive payment without actually encrypting files.
CryptoLocker represented a fundamental shift: strong asymmetric encryption meant victims could no longer reverse-engineer the decryption key. Combined with Bitcoin for anonymous payment, it created a reliable criminal revenue model. The Gameover ZeuS botnet provided the distribution infrastructure, reaching hundreds of thousands of victims before law enforcement disruption.
Instead of casting wide nets for small ransoms, groups like Ryuk and SamSam began researching targets, identifying organizations with high revenue and low security maturity. Attackers spent weeks inside networks, mapping infrastructure, escalating privileges, and positioning for maximum impact before deploying encryption. Ransom demands jumped from hundreds to millions of dollars.
Double extortion eliminated the backup defense. Even organizations with perfect backup strategies faced public data exposure, regulatory penalties, and reputational damage. Maze created the first dedicated leak site to publish victim data, and the tactic was immediately adopted across the ransomware ecosystem. It fundamentally changed the calculus of whether to pay.
Modern ransomware operations use supply chain compromises to reach hundreds of victims simultaneously. Some groups have abandoned encryption entirely, relying solely on data theft and extortion threats. Zero-day exploits provide initial access before patches are available. Criminal organizations maintain HR departments, bug bounty programs, and customer service portals for ransom negotiations.
Ransomware Types
Ransomware Attack Lifecycle
Phishing remains the most common delivery mechanism, but RDP brute-force and exploitation of unpatched vulnerabilities (especially VPNs and edge devices) are increasingly used. Initial Access Brokers (IABs) sell pre-established footholds into corporate networks, allowing ransomware affiliates to skip this step entirely.
Attackers install remote access trojans (RATs), create new privileged accounts, and establish encrypted C2 communications. Persistence mechanisms include scheduled tasks, registry modifications, and deployment of legitimate remote management tools (e.g., AnyDesk, TeamViewer) to blend with normal IT operations.
Attackers use tools like Mimikatz for credential dumping, BloodHound for Active Directory mapping, and legitimate admin tools for reconnaissance. Lateral movement through RDP and SMB connections allows access to file servers, database servers, and backup infrastructure. Domain controller compromise provides the keys to the entire environment.
Attackers identify and exfiltrate high-value data: financial records, customer PII, intellectual property, legal documents, and healthcare records. Data is typically staged in a central location, compressed, and exfiltrated via cloud storage services, FTP, or custom tools. This stage can take days to weeks depending on data volume.
Before encryption begins, attackers delete Volume Shadow Copies (vssadmin delete shadows), disable Windows Recovery, and target backup servers and NAS devices. Encryption is then deployed simultaneously across all compromised endpoints, often during off-hours or weekends. Ransom notes provide instructions for Tor-based communication and cryptocurrency payment.
Modern ransomware groups operate professional negotiation portals. They may offer discounts for quick payment, provide proof-of-life decryption of sample files, and set deadlines before publishing data. Some groups contact journalists, customers, or regulators directly to increase pressure. Payment is typically demanded in cryptocurrency, with amounts adjusted based on the victim's perceived revenue.
Key Ransomware Terms
Defense & Prevention
Ransomware Incident Response Playbook
Network isolation prevents further lateral movement and encryption spread. Do not shut down infected systems -- volatile memory contains forensic evidence (encryption keys, process traces, network connections) that is lost on power-off. Disable compromised accounts, block C2 IP addresses at the firewall, and quarantine affected network segments.
Identify the ransomware family using ransom notes, encrypted file extensions, and threat intelligence databases (ID Ransomware, No More Ransom). Determine how many systems are affected, whether backups are intact, and whether data was exfiltrated before encryption. This assessment drives every subsequent decision, including whether recovery is possible without paying.
Legal counsel should be engaged immediately to establish attorney-client privilege over investigation communications. File reports with FBI IC3 and CISA -- they may have decryption keys or intelligence on the threat actor. Notification timelines vary: CIRCIA requires 72 hours for significant incidents, SEC requires 4 business days for material incidents, and state breach laws have varying requirements.
Restore from immutable or air-gapped backups only -- backups on the compromised network may also be encrypted or contain backdoors. Rebuild domain controllers and critical infrastructure from scratch if compromise is suspected. Verify backup integrity before restoration. Reconnect recovered systems to a clean network segment and monitor closely for signs of re-infection or persisted backdoors.
Create a detailed incident timeline from initial access to containment. Identify root cause, dwell time, and gaps in detection. Update incident response plans, security controls, and monitoring rules based on findings. Share indicators of compromise (IoCs) with ISACs and law enforcement. The post-incident report drives the security improvements that prevent recurrence.
To Pay or Not to Pay
The FBI and CISA strongly advise against paying ransoms. Paying does not guarantee data recovery, funds criminal operations, and encourages further attacks against the paying organization and others. Law enforcement has observed victims who pay being targeted again.
Some jurisdictions may impose legal penalties for paying ransoms to sanctioned entities (OFAC). Organizations must conduct sanctions screening before any payment. Payments to groups affiliated with sanctioned nations or designated terrorist organizations can result in federal penalties regardless of the circumstances.
Cyber insurance policies increasingly require demonstrated security posture before covering ransom payments. Insurers may require evidence of MFA deployment, endpoint protection, backup testing, and incident response planning. Some policies exclude ransomware entirely or cap coverage at levels below typical demands.
While 97% of organizations ultimately recovered their data, only 68% recovered after paying the ransom. The remainder recovered through backups, decryption tools from law enforcement, or other means. Organizations with tested, immutable backups consistently recover faster and at lower cost than those who pay.
Notable Ransomware Incidents
Compliance & Reporting Obligations
- 72-hour reporting for significant cyber incidents
- 24-hour reporting for ransom payments
- Applies to critical infrastructure sectors
- Reports submitted to CISA
- 4 business days to disclose material incidents (Form 8-K)
- Materiality determination required
- Annual cybersecurity risk management disclosure
- Board oversight of cybersecurity risk
- 72-hour notification to supervisory authority
- Notification to affected individuals if high risk
- Document all breaches in internal register
- Fines up to 4% of global annual revenue
- Varying notification timelines (30-90 days typical)
- Different definitions of "personal information"
- Some require notification to state AG
- Multi-state incidents require parallel compliance
PR.DS: Data security — backup encryption, immutable storage.
DE.CM: Continuous monitoring — EDR, network traffic analysis.
RS.MA: Incident management — ransomware-specific response procedures.
Requirement 10: Log and monitor all access — detection and forensic readiness.
Requirement 11: Test security regularly — vulnerability scanning, penetration testing.
Requirement 12.10: Incident response plan — ransomware scenario must be covered.
A.8.13: Information backup — 3-2-1-1-0 backup strategy.
A.5.24: Information security incident management planning — IR playbook.
A.5.26: Response to information security incidents — containment and recovery.
CC7.2: Monitor system components for anomalies — ransomware detection.
CC7.3: Evaluate detected events — triage and escalation procedures.
A1.2: Recovery testing — backup restoration verification (the "0" in 3-2-1-1-0).
Ransomware Articles
Build Your Ransomware Defense
Explore incident response playbooks, security frameworks, and practitioner resources across the Cybersecurity Hub. Defense starts with preparation.