Scenarios
The phase playbooks apply to every incident. Some kinds of incident add work at each step, and these pages list only the additions. Work the matching page next to the playbook for the step you are on.
The sector pages add the reporting clocks and terms of regulated organizations, and combine with any scenario. The kit builder puts a scenario, a sector and a cloud provider on one sheet.
| Scenario | Use it when | What it adds |
|---|---|---|
| Ransomware | Files are encrypted, a ransom note appears, or data theft is threatened | Exfiltration hunting, backup and hypervisor protection, restore order, the payment decision |
| Business email compromise | A mailbox is used to redirect payments or impersonate staff | Mailbox rules, OAuth grants, recovering the money with finance and the bank |
| Cloud | An attacker has cloud credentials, roles or tokens | Control-plane logs and their retention, the multi-cloud containment table, identity and access management (IAM) persistence. Provider commands are in the cloud playbooks |
| Insider threat | A current or former employee or contractor is the suspect | HR and counsel before any investigation, covert or overt handling, evidence fit for litigation |
| Supply chain | The compromise came through a supplier's software, hardware or service | Scoping by product and version, supplier coordination, customer notices |
| Operational technology | Industrial control systems or a physical process could be affected | Safety first, engineering sign-off before containment, manual operations, controller logic checks |
| Restricted data | Data under a residency, contract or government commitment was read or copied outside its boundary | Reading the commitment first, key usage logs, showing where the data did not go, notice to the parties the commitment names |
| SaaS and OAuth abuse | A connected app, integration token or consented OAuth app is used to pull data from a SaaS platform | Revoking tokens and connected apps, platform event logs, the vendor behind the integration, notifying data owners |
| Edge device exploitation | A VPN, firewall or remote access gateway is exploited, often before a patch exists | Vendor integrity checks, treating the appliance as untrusted, rotating every secret it stored, hunting from its internal address |
| Identity provider and help desk | An attacker resets multifactor authentication (MFA) through the help desk, registers a new factor, or takes an identity provider administrator | Help desk call records, factor and device enumeration, federation trust changes, tenant-wide session revocation |
| AI applications and agents | An AI application or agent leaks data, misuses its tools or credentials, or acts on poisoned content | Prompt and tool-call logs, revoking agent credentials, a kill switch, retrieval content review |
| Distributed denial of service | A flood takes an internet-facing service down, or a note threatens one unless the organization pays | Provider engagement and diversion, locking the origin, rate limits and WAF rules, extortion notes, outage reporting |
| Customer account takeover | Attackers take over customer accounts on your own product or website at scale, through credential stuffing, relayed MFA, SIM swap, stolen sessions or account recovery | Telling an attack from normal failed logins, bot and leaked credential defenses, session revocation, payout freezes, fraud and chargebacks, customer notice |
The ransomware, business email compromise, cloud, insider, supply chain and operational technology pages are built from Chapters 12, 13 and 17 to 19 of the book, and each cites the pages it draws on. The other five are additions to the book.