PIVTR-D

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.

ScenarioUse it whenWhat it adds
RansomwareFiles are encrypted, a ransom note appears, or data theft is threatenedExfiltration hunting, backup and hypervisor protection, restore order, the payment decision
Business email compromiseA mailbox is used to redirect payments or impersonate staffMailbox rules, OAuth grants, recovering the money with finance and the bank
CloudAn attacker has cloud credentials, roles or tokensControl-plane logs and their retention, the multi-cloud containment table, identity and access management (IAM) persistence. Provider commands are in the cloud playbooks
Insider threatA current or former employee or contractor is the suspectHR and counsel before any investigation, covert or overt handling, evidence fit for litigation
Supply chainThe compromise came through a supplier's software, hardware or serviceScoping by product and version, supplier coordination, customer notices
Operational technologyIndustrial control systems or a physical process could be affectedSafety first, engineering sign-off before containment, manual operations, controller logic checks
Restricted dataData under a residency, contract or government commitment was read or copied outside its boundaryReading the commitment first, key usage logs, showing where the data did not go, notice to the parties the commitment names
SaaS and OAuth abuseA connected app, integration token or consented OAuth app is used to pull data from a SaaS platformRevoking tokens and connected apps, platform event logs, the vendor behind the integration, notifying data owners
Edge device exploitationA VPN, firewall or remote access gateway is exploited, often before a patch existsVendor integrity checks, treating the appliance as untrusted, rotating every secret it stored, hunting from its internal address
Identity provider and help deskAn attacker resets multifactor authentication (MFA) through the help desk, registers a new factor, or takes an identity provider administratorHelp desk call records, factor and device enumeration, federation trust changes, tenant-wide session revocation
AI applications and agentsAn AI application or agent leaks data, misuses its tools or credentials, or acts on poisoned contentPrompt and tool-call logs, revoking agent credentials, a kill switch, retrieval content review
Distributed denial of serviceA flood takes an internet-facing service down, or a note threatens one unless the organization paysProvider engagement and diversion, locking the origin, rate limits and WAF rules, extortion notes, outage reporting
Customer account takeoverAttackers take over customer accounts on your own product or website at scale, through credential stuffing, relayed MFA, SIM swap, stolen sessions or account recoveryTelling 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.