Chapter 16

Ransomware Response Playbook

3:12 AM. LockBit. 47 hosts. Payroll in six hours. Every minute of delay costs data and potentially costs recovery. This playbook covers the full ransomware response arc — from the first alert to the ransom decision to recovery — including the pre-deployment attacker behavior that nearly every victim missed before the encryption started.

Scenario

A financial services company's EDR console erupts at 3:12 AM: 400 file modification events per second on the finance VLAN. Forty-seven hosts are confirmed encrypting. The LockBit ransom note appears on every affected workstation desktop. The on-call SOC analyst pages the IR lead.

By the time the IR lead joins the call at 3:18, the team has already scoped: 47 hosts confirmed encrypted, 230 hosts on adjacent VLANs at risk, and the payroll processing servers — which run the automated payroll batch job at 9 AM — are in the at-risk group but not yet showing encryption activity. The business wants to know in the next 30 minutes whether payroll will process.

Worse: a review of EDR telemetry shows that the attacker was present in this environment for 23 days before encryption. They conducted reconnaissance, dumped credentials, mapped Active Directory, and staged the ransomware on a domain controller. The encryption was not day-one activity — it was the final step in a long operation that the security team missed entirely. This is now the rule for ransomware, not the exception.

What Happens Before the Encryption

Modern enterprise ransomware attacks — especially from RaaS (Ransomware-as-a-Service) groups like LockBit, BlackCat, Cl0p, and Royal — follow a predictable pre-encryption playbook that often spans days to weeks. By the time encryption starts, the attacker has already completed their primary objectives. Encryption is the ransom demand mechanism, not the intelligence collection phase. Understanding the pre-encryption playbook changes how you prioritize detection and response.

  Modern Enterprise Ransomware Attack Timeline
  ═══════════════════════════════════════════════════════════════════

  T - 23 days: Initial Access
  ─────────────────────────────────────────────────────────────────
  Entry via: phishing (VBA macro → Cobalt Strike), exploitation of
  internet-facing service (CVE in VPN, RDP, Exchange, Confluence),
  or purchased access (access broker selling initial foothold from
  prior compromise).
  At this point: one host, one user's credentials, no persistence yet.

  T - 21 days: Establish Persistence
  ─────────────────────────────────────────────────────────────────
  Install persistent C2: scheduled task, registry Run key, or DLL
  hijacking on a service. Test persistence by disconnecting and
  reconnecting. Goal: survive a host reboot.

  T - 18 days: Credential Harvesting
  ─────────────────────────────────────────────────────────────────
  Dump LSASS (comsvcs.dll MiniDump, Mimikatz, ProcDump).
  Extract credentials from NTDS.dit if possible.
  Harvest browser-saved passwords.
  Goal: collect credentials for domain-privileged accounts.

  T - 14 days: Active Directory Reconnaissance
  ─────────────────────────────────────────────────────────────────
  Run BloodHound/SharpHound to map AD attack paths.
  Enumerate: Domain Admins, Enterprise Admins, service accounts with
  delegation, GPO editors. Find the shortest path to Domain Admin.
  Goal: understand the environment and identify lateral movement targets.

  T - 7 days: Lateral Movement to Crown Jewels
  ─────────────────────────────────────────────────────────────────
  Move to: domain controllers, backup servers, file servers with
  sensitive data. Use compromised credentials + PsExec, WMI, or
  scheduled tasks for lateral movement.
  Goal: gain access to the data stores and infrastructure required
  for maximum impact.

  T - 3 days: Data Exfiltration (for double extortion)
  ─────────────────────────────────────────────────────────────────
  Exfiltrate sensitive data before encryption — customer PII,
  financial records, HR data, IP, credentials. Use Rclone, MEGAsync,
  FTP, or cloud storage APIs. Data uploaded to attacker-controlled
  infrastructure.
  Goal: establish second leverage point — "pay or we publish your data."

  T - 1 day: Stage Ransomware
  ─────────────────────────────────────────────────────────────────
  Copy ransomware binary to domain controller or network share.
  Create deployment mechanism: GPO, scheduled task, PSExec script
  that can deploy to all hosts simultaneously.
  Disable Windows Defender, VSS, backup agents.
  Delete shadow copies.

  T = 0: Deploy Ransomware
  ─────────────────────────────────────────────────────────────────
  Simultaneous deployment across environment.
  3:12 AM chosen because: IT staff not working, minimal monitoring,
  maximum time before business opens and response can begin.
  Encryption completes in 2-4 hours. Ransom note appears.
  ═══════════════════════════════════════════════════════════════════
  CRITICAL INSIGHT: Everything valuable to the attacker happened in
  T-23 days through T-0. By the time the EDR fires at 3:12 AM, the
  attacker has already achieved their goals. The encryption is their
  invoice.

Phase 1: Immediate Actions (T+0 to T+30 min)

The first 30 minutes of ransomware response are the highest-stakes window. Active encryption is running. Every minute of delay costs additional encrypted files and potentially additional encrypted hosts. The two competing priorities — containment speed and scope accuracy — must be resolved with a clear decision framework.

  30-Minute Decision Tree
  ═══════════════════════════════════════════════════════════════════

  T+0: Alert fires
       │
       ▼
  Step 1: Is encryption ACTIVELY RUNNING right now?
  ─────────────────────────────────────────────────
  Check: EDR shows active file modification events at high velocity?
  Files being changed right now? EDR alert type: encryption activity?
       │
       ├── YES → ISOLATE IMMEDIATELY
       │         Do not wait for scoping. Isolate every host with
       │         active encryption events via EDR bulk contain.
       │         Scoping happens AFTER isolation.
       │         Rationale: active encryption is data destruction.
       │         Cost of wrong isolation: one system offline.
       │         Cost of wrong delay: hundreds of additional files encrypted.
       │
       └── NO (encryption appears stopped) →
             Step 2: Is attacker still in the network?
             ─────────────────────────────────────────
             Check EDR for: active C2 beaconing on any host?
             Active command execution? Active lateral movement?
                  │
                  ├── YES → ISOLATE now — attacker can re-deploy ransomware
                  │         Don't give them time to deploy again.
                  │
                  └── NO →
                        Step 3: Scope before contain
                        ────────────────────────────
                        30 minutes to scope:
                        - Which hosts are confirmed encrypted?
                        - Which hosts show C2 beaconing?
                        - Which hosts were accessed by compromised accounts?
                        Then: SIMULTANEOUS isolation of all confirmed +
                              suspected hosts.
                        Goal: one cut, not a rolling series of isolations
                        that tips off the attacker.
Common mistake: isolating hosts one at a time

Rolling isolation — containing hosts one by one as they're confirmed — is the most common mistake in early ransomware response. If the attacker still has an active C2 connection (which they almost certainly do in the first 30 minutes), they can see host isolation events happening and accelerate deployment to remaining uncontained hosts. The correct approach: scope, then execute simultaneous bulk isolation. Accept that some hosts you isolate may not actually be compromised — that's recoverable. The alternative is giving the attacker time to encrypt additional hosts while you're carefully verifying each one.

Full Response Playbook

TimeActionOwnerNotes
T+0:00Confirm ransomware; P1 declared; IR lead pagedSOC on-callConfirm: file extension change, ransom note, high-velocity file modification
T+0:05Switch all incident communications to out-of-band channel (Signal, phone)IR leadMandatory. Attacker may have email/Slack access. Do not discuss containment plans on monitored channels.
T+0:08Page CISO; call cyber insurance hotline; call external IR retainerIR leadInsurance may have 24-hour notification SLA; external IR may need hours to spin up.
T+0:15Execute containment (see 30-minute decision tree above)EDR teamSimultaneous isolation via bulk contain. Save host list for scope documentation.
T+0:30Scope confirmation: how many hosts? What data was on them?IR leadUse asset inventory. Map to business processes: what is down? What is at risk?
T+1:00Identify ransomware family (ransom note, file extension, behavior)Threat intelSubmit sample to ID Ransomware (id-ransomware.malwarehunterteam.com). Check nomoreransom.org for free decryptors.
T+1:00OFAC check: is this group sanctioned?Legal + Threat intelCheck OFAC SDN list. Ransomware groups subject to sanctions: Conti affiliates, Evil Corp, Sandworm. Paying sanctioned entities is a federal violation.
T+1:30Begin forensic triage on a confirmed-infected hostIR forensicsGoal: identify initial access vector, earliest attacker activity, and persistence mechanisms. This drives eradication plan.
T+2:00Assess backup status: are clean backups available? What is recovery point?IT + IRCheck: are backups intact? Were backup systems in scope? Are backup servers encrypted? Offline/immutable backups are the answer here.
T+2:00First SITREP to leadership (written, through out-of-band channel)IR leadInclude: confirmed impact, current status, key decisions needed, timeline estimate
T+4:00Ransom payment decision meetingCISO + CEO + Legal + InsuranceIR team provides input (see ransom decision framework). Business makes the call.
T+6:00Eradication: full persistence hunt across all affected hostsIR forensicsDon't start recovery before eradication. Attacker may have persistence on recovered hosts.
T+12:00Recovery planning: define sequence, timeline, validation criteriaIR + IT + BusinessSee Chapter 13 for full recovery planning detail
T+24:00Begin Phase 1 restoration (infrastructure, security tools first)IT / InfraRestore security monitoring capability before restoring business systems

What LockBit Actually Does: Encryption Mechanics

Understanding how ransomware encrypts files is operationally important — it affects how you scope the impact, how you identify it on a live system, and what your recovery options are. Modern ransomware uses hybrid encryption: a fast symmetric cipher (AES-256) for the file contents, protected by asymmetric encryption (RSA-2048 or ECDH) for the key. The attacker holds the private key; you cannot decrypt without it.

  LockBit Encryption Mechanism
  ═══════════════════════════════════════════════════════════════════

  1. LockBit generates a unique AES-256 key for each file
  2. File content is encrypted with this AES key
  3. The AES key is encrypted with the attacker's RSA-2048 public key
     (this public key is embedded in the ransomware binary)
  4. The encrypted AES key is appended to the encrypted file
  5. Original file is overwritten or deleted (depending on variant)
  6. File extension changed to .lockbit (or custom victim-specific ext)

  Result structure of each encrypted file:
  ┌─────────────────────────────────────────┐
  │ [Encrypted file content]                │
  │ [Encrypted AES key (RSA-encrypted)]     │
  │ [Ransom note pointer / metadata]        │
  └─────────────────────────────────────────┘

  Why you cannot brute-force decrypt:
  RSA-2048 keyspace is 2^2048. Even at 10^18 operations per second
  (faster than any hardware), cracking RSA-2048 would take longer
  than the age of the universe. Without the private key, decryption
  is mathematically infeasible.

  What "buying the decryptor" means:
  Attacker provides a tool containing their RSA private key. Tool
  reads the encrypted AES key from each file, decrypts it with the
  RSA private key, then decrypts the file content with the AES key.

Double Extortion: The Exfiltration Dimension

Since approximately 2019, most enterprise ransomware attacks include a data exfiltration component before encryption. The exfiltration creates a second leverage point: even if the victim can restore from backups without paying, the attacker threatens to publish the stolen data on their "leak site" unless a ransom is paid. This tactic is called double extortion.

Extortion typeLeverageCounter
Single extortion (encryption only) "Pay or your files stay encrypted" Restore from backup — no payment needed if backup is clean and available
Double extortion (encryption + exfiltration) "Pay or we publish your customer data / IP / HR records on our leak site" No backup counter — data is already gone. Decision: weigh ransom cost against breach disclosure cost, regulatory fines, reputational damage
Triple extortion (+ DDoS threat) "Pay or we encrypt your files AND publish your data AND DDoS your remaining online services" DDoS mitigation service; legal threats; limited practical counter
Why double extortion changes the ransom decision fundamentally

Before double extortion was common, the backup-based counter to ransomware was nearly complete: restore from backups, don't pay, attacker gets nothing. Double extortion breaks this calculus because the stolen data exists outside your control regardless of what you do with your backups. Now even organizations with perfect backup hygiene face a genuine decision about whether paying is worth reducing the data leak risk. Note: paying does not guarantee the attacker deletes the data. They have made this promise to many victims and broken it. There is no enforceable contract with a criminal organization. The ransom payment buys a probabilistic reduction in data leak risk — not a guarantee.

Ransomware Family Identification

Identifying the ransomware family quickly matters for two reasons: it determines whether a free decryptor is available, and it provides TTP intelligence about the actor's typical behavior (persistence mechanisms, exfiltration methods, C2 infrastructure) that informs scope assessment.

Identification methodWhat to look forTool/resource
File extension Encrypted files: .lockbit (LockBit), .BlackCat/.alphv (BlackCat), .cl0p (Cl0p), .ryuk (old Ryuk). Some families use victim-specific extensions. Check extension against known families
Ransom note filename/content LockBit: Restore-My-Files.txt; Conti: CONTI_README.txt; BlackCat: RECOVER-UNIQUE-ID-FILES.txt. Content includes Tor payment site URL. Search for ransom note filename patterns
Binary hash Submit ransomware binary to VirusTotal or Malware Bazaar for family identification VirusTotal, MalwareBazaar
File header magic bytes Some families have identifying bytes prepended or appended to encrypted files. Useful when file extension was changed to generic name. ID Ransomware (upload sample file)
C2 infrastructure Identify C2 IP/domain from EDR telemetry, check against threat intel for actor association Shodan, VirusTotal, threat intel platform

The Ransom Payment Decision Framework

Whether to pay a ransom is not an IT decision — it is a business, legal, and risk management decision with potentially severe legal consequences (OFAC sanctions, SEC disclosure obligations) and operational consequences either way. The IR team's role is to provide structured input to the business decision-makers, not to make the decision unilaterally.

  Ransom Decision Input Framework
  ═══════════════════════════════════════════════════════════════════

  INPUT 1: Backup Assessment
  ─────────────────────────────────────────────────────────────────
  Q: Are clean backups available?
  Q: What is the recovery point (data loss in time)?
  Q: What is the recovery time estimate (hours to restore)?
  Q: Are backup systems also encrypted?
  Q: Are offline/immutable backups available?

  If clean backups exist → ransom payment leverage drops significantly.
  If all backups are encrypted → ransom payment leverage is high.

  INPUT 2: Decryptor Assessment
  ─────────────────────────────────────────────────────────────────
  Q: Is a free decryptor available? (nomoreransom.org)
  Q: What is this family's decryptor reliability?
  Q: What is typical decryption time for this family per host?
  Q: Does this family have a history of providing decryptors after payment?

  Free decryptor available → don't pay.
  Family known for unreliable decryptors → payment risk is higher.

  INPUT 3: Legal Assessment
  ─────────────────────────────────────────────────────────────────
  Q: Is this group on the OFAC SDN (Specially Designated Nationals) list?
  Q: Is there a pattern indicating nation-state affiliation (Sandworm, Lazarus)?
  Q: What are our regulatory notification obligations regardless of payment?

  OFAC-sanctioned group → payment may be federal violation. Consult
  legal counsel before any payment decision.

  INPUT 4: Insurance Assessment
  ─────────────────────────────────────────────────────────────────
  Q: Does our cyber insurance policy cover ransom payments?
  Q: Is pre-payment authorization required from the insurer?
  Q: Are there insurer-required IR steps before payment is covered?

  Many insurers require: IR firm engagement, documented recovery attempts,
  OFAC check, and specific payment process to cover the claim.

  INPUT 5: Data Exfiltration Assessment
  ─────────────────────────────────────────────────────────────────
  Q: Did the attacker exfiltrate data before encrypting?
  Q: What data was likely exfiltrated based on the systems accessed?
  Q: What are the regulatory notification requirements for this data?
  Q: Has the attacker published a portion of the data as proof of exfiltration?

  Data exfiltration present → payment reduces (but does not eliminate)
  leak risk. Factor in: cost of breach notification, regulatory fines,
  reputational damage vs. ransom payment amount.
Real scenario: OFAC violation during crisis response

In 2021, a healthcare organization paid a ransomware demand under extreme pressure — patient systems were down and lives were at risk. After payment, it was discovered that the group they paid had significant overlap with an OFAC-sanctioned entity. The organization faced potential civil penalties even though they acted in good faith. OFAC has a "safe harbor" provision for ransomware payments reported promptly to OFAC, but the organization still spent six months with legal teams navigating the regulatory response. The lesson: OFAC check is not optional even when the pressure to pay immediately is extreme. A 30-minute delay to complete the check is worth it to avoid a multi-year regulatory investigation.

Q & A

Q: How do you know if the attacker exfiltrated data before encrypting?

Several indicators: (1) Network egress telemetry from proxy or firewall logs showing large outbound transfers to unusual destinations in the days/weeks before the incident. Look for: unusually large uploads to cloud storage services (Mega, Dropbox, GoFile), FTP connections to unfamiliar IPs, connections to known data staging services (Rclone typically makes distinctive API calls). (2) EDR process telemetry showing rclone.exe, MEGAsync, or WinRAR/7-Zip creating archives in unexpected locations followed by network connections. (3) Attacker's own communications on their leak site — they often pre-announce victims before publishing, giving the victim a "pay in 72 hours or we publish" deadline. If the attacker has data, they will tell you. (4) User behavior anomalies in DLP logs — unusual access to large volumes of sensitive documents in the week before the attack.

Q: The attacker's decryptor is working but so slowly that it would take 10 days to decrypt all 300 affected hosts. The business wants systems restored faster. What are the options?

Multiple paths: (1) Prioritize critical systems in decryption queue — most ransomware families' decryptors accept a directory or host as input; decrypt the highest-business-value systems first. (2) Parallel decryption — if the decryptor allows multiple simultaneous instances, run it on different host segments in parallel. (3) Restore highest-priority systems from backup in parallel — accept the data loss from backup age for those specific systems rather than waiting for decryption. The priority systems may be worth restoring from a 30-day-old backup to get them online in hours rather than waiting days for decryption. (4) Contact the ransom operator's support channel — this is distasteful but common practice. Many RaaS operators have a "support" function and will provide technical assistance or a faster decryptor when recovery is proceeding slowly. External IR firms that specialize in ransomware response typically manage this communication.

Q: Forty-eight hours into the incident, a threat intel feed reports that the specific LockBit affiliate responsible for your attack has been arrested by law enforcement. Does this change anything?

Tactically: review your decryption status. Law enforcement operations against ransomware groups have sometimes resulted in decryption keys being released publicly (as happened with some Hive victims after the FBI seized Hive's infrastructure in 2023). Check whether law enforcement is distributing decryptors. Strategically: the affiliate arrest does not necessarily mean the RaaS group (LockBit in this case) is dismantled — LockBit has operated through multiple law enforcement actions by simply replacing arrested affiliates. Your eradication and recovery process does not change. The affiliate's arrest does reduce the likelihood of them actively monitoring your environment for re-compromise in the near term, which is a minor positive for monitored recovery. Do not reduce monitored recovery intensity based on this — other affiliates may be aware of your environment.

Q: The CISO wants to pay the ransom to recover faster. The IR team believes backups can restore everything in 5 days. How do you present this to the business?

Present both options with full cost and risk analysis: "Option 1: Restore from backup. Timeline: 5 days to full recovery. Cost: [IT overtime + productivity loss during outage]. Risk: backup age is [N] days, so [N] days of data may be irrecoverable; confirm with business units which data loss is acceptable. Upside: no payment, no attacker contact, no OFAC risk. Option 2: Pay ransom. Timeline: 2-3 days to receive decryptor + [X] days to decrypt 300 hosts in parallel = estimated 4-7 days. Cost: ransom demand ($[X]) + IR fees + legal review. Risk: decryptor reliability is [%] based on threat intel; OFAC check is [clear/pending]; attacker retains exfiltrated data regardless of payment. Net recommendation: with backups available and OFAC risk present, Option 1 is preferable on risk-adjusted cost. But I want the business to make this decision with complete information." Let the business decide — your job is to give them the information, not to make the call for them.

Q: Twenty-four hours into recovery, you discover that the attacker deleted all shadow copies. Backups are your only recovery option. The backup tapes require a tape reader that's at an offsite facility. What do you do?

Immediate parallel tracks: (1) Dispatch someone to retrieve the tape reader (or arrange emergency shipping if the facility is distant). (2) Call your external IR retainer — experienced IR firms often have relationships with recovery specialists who may have alternative backup media readers. (3) Negotiate with the ransomware operator while the backup retrieval is underway — not to pay, but to buy time. Keep the channel open and indicate you're "evaluating payment options." This buys 24-48 hours of negotiation time during which you may be able to recover tape backups. (4) Review whether any specific critical systems might have cloud backup copies (O365 retention, OneDrive version history, Azure VM snapshots) that weren't deleted. Even partial data from cloud backups may allow critical systems to function while tape recovery proceeds. (5) Consider whether payment is now the right call — if the backup retrieval timeline is 3-5 days and the business cannot tolerate that, the calculus shifts.

Q: After the ransomware incident, leadership asks whether the company should build a "ransomware response team" that specializes in this type of incident. What do you recommend?

This is a reasonable request and the answer depends on two factors: incident frequency and organization size. For most organizations, a dedicated ransomware team is overkill — the better investment is a general IR capability with ransomware-specific playbooks (like this one), relationships with external IR retainers who specialize in ransomware, a well-maintained backup program, and the detection capabilities to catch pre-ransomware attacker activity early. Catching the attacker during credential harvesting (T-21 days in the scenario above) is worth more than having a specialized team that responds faster after encryption. For large organizations in high-target industries (healthcare, financial services, critical infrastructure), a dedicated function or specialized IR team with ransomware expertise can be justified. The business case: ransomware incidents at these organizations commonly cost $5-50M; a specialized team that reduces response time by 50% pays for itself in the first incident.