Respond is for when it is already happening. Each playbook is a timed sequence with the reason for every step, a “How far has it got?” question list for triage, and a matching TheHive case template. Open the one that matches what you are seeing; the longer playbooks split by scenario, so you can switch branch as you learn more.
Read the first steps before you touch anything: the early actions decide how much you can recover, and several of them (isolating instead of powering off, revoking sessions before resetting passwords) are easy to get backwards under pressure. Getting ready beforehand is under Prevent, and finding it sooner is under Detect.
Respond
Incident Response Playbooks
It is happening now. Timed steps with the reason for each, a "How far has it got?" question list for triage, and a matching TheHive case template.
Ransomware Response
The first 72 hours, by scenario: encryption in progress, discovered before encryption, data theft without encryption, hypervisor/NAS, backups destroyed, cloud data held hostage. Isolate, don't power off; protect the way back; the board's pay/don't-pay facts.
BEC Response
Compromised mailbox, payment in flight. Money first, then mailbox: bank recall, capture-then-purge rules, tenant sweep, and who to warn.
Identity Breach Response
You're already compromised — what to do in the next 15 minutes, 4 hours, 30 days. T+0 containment commands, 8 incident-type variations (account takeover, device-code, OAuth abuse, NHI, privileged). Password reset is not remediation.
Device Code Abuse Response
Device-code phishing confirmed or suspected. The 12-step containment checklist: revoke before reset, kill device registrations, audit OAuth consent, hunt tenant-wide.
Supply Chain Incident Response
A vendor disclosed a breach, or a package or update you install shipped malicious code. Vendor track: validate, suspend data flows, revoke every credential they hold. Package track: find everywhere it was installed, pin, and rotate every secret it could read.
Cloud Incident Response
An attacker in AWS, Azure or GCP. Keep the logs running, revoke the credential and the sessions it already minted, quarantine the account when the scope is unknown, and hunt every key, role and trust they created. Leaked keys, cryptomining, storage theft or hostage, compromised workloads and pipelines, root or tenant admin.
ClickFix Response
A user pasted a fake-CAPTCHA command. Isolate, capture the command from RunMRU or the PowerShell history, revoke every session the stealer took, and decide whether it is a stealer or a foothold.