PPhase playbook
Preparation
STARTS WHENNo incident running. This is the default state.
DONE WHENNever closes. Every debrief reopens it with named owners.
RECORDSThe signed authority matrix, the critical asset list and the contact list from this checklist, with containment tiers and risk levels agreed in Decide these before the incident.
Most of the team's hours belong here. Preparation is hardest to fund when it works, because nothing has gone wrong.
Make the case with measurements: time to detect, how fast the last drill contained, what the last tabletop exposed. The owners below are program roles. Replace them with names.
Organization
| # | Item | Owner |
|---|---|---|
| 1 | Write the policy that sets the mission, the priorities and when management is called in | CISO |
| 2 | Write the organization's position on paying a ransom and on communicating with attackers | CISO |
| 3 | Fill in and sign the authority matrix, including the containment tiers | CISO |
| 4 | Set recovery time objectives (RTO) and recovery point objectives (RPO) for each critical system | IT operations |
| 5 | Write the evidence retention and chain of custody procedures | IR lead |
| 6 | List the critical assets and set risk tolerance thresholds for all four risk levels | Risk management |
| 7 | Document the classification matrix and review it every year | IR lead |
| 8 | Set up primary and backup communication channels, secure them and test them | IR lead |
| 9 | Build the contact list: internal teams, law enforcement, regulators, insurer, retainer providers and cloud security contacts. Review it every quarter. | IR lead |
| 10 | Set reporting deadlines and distribution lists for each audience, using the templates | IR lead |
| 11 | Set notification triggers, the approval workflow and named spokespersons | Communications |
| 12 | Document the regulatory notification requirements for every applicable regime, starting from Notification deadlines | Legal |
| 13 | Publish security.txt as RFC 9116 describes, and route what it attracts to a named team | Security operations |
| 14 | Select and configure the incident tracking platform, and train the team on it | IR lead |
| 15 | Read the cyber insurance policy as a team, and store it offline with the carrier contacts, claims number and policy number | Legal |
| 16 | Negotiate your preferred responders onto the carrier's approved panel | Legal |
| 17 | Identify independent counsel, separate from the carrier's breach coach | Legal |
| 18 | Run awareness training with clear reporting channels and simulated phishing | Security awareness |
Team
| # | Item | Owner |
|---|---|---|
| 19 | Train the team on technical skills and on the skills that get skipped: documentation, decisions under pressure, negotiation | IR lead |
| 20 | Make backups immutable or air-gapped, with separate authentication and integrity monitoring | IT operations |
| 21 | Test restores against the RTO and RPO | IT operations |
| 22 | Agree who is responsible, accountable, consulted and informed (RACI) with IT operations, the security operations center (SOC), help desk, legal, HR, communications and business units | IR lead |
| 23 | Write playbooks for the incident types most likely to reach you, and update each one after every use | IR lead |
| 24 | Build and test forensic workstations, including cloud workstations where the estate is mostly cloud | IR lead |
| 25 | Provision evidence storage with enough capacity, test the collection tools and pack the jump bag | IR lead |
| 26 | Keep break-glass accounts in a vault or on hardware tokens, alert on their use, and test them | IT operations |
| 27 | Pre-authorize access where possible, and document the vendor and cloud support procedures | IR lead |
| 28 | Schedule exercises: monthly tabletop, quarterly technical drill, annual full-scale. A ready-to-run tabletop is in Incident Command. | IR lead |
Prevention and detection
| # | Item | Owner |
|---|---|---|
| 29 | Collect threat intelligence from commercial, Information Sharing and Analysis Center (ISAC), government and open sources, and turn it into detections using STIX 2.1 (Structured Threat Information Expression) | Threat intelligence |
| 30 | Patch by risk, with defined timelines and exception handling for systems that cannot be patched | Vulnerability management |
| 31 | Keep a software inventory with versions, software bill of materials (SBOM) data and end-of-life dates, and find shadow IT through billing reviews | IT operations |
| 32 | Apply hardening baselines from Center for Internet Security (CIS) Benchmarks or Defense Information Systems Agency Security Technical Implementation Guides (DISA STIGs), automate them in code, and monitor drift as a compromise indicator | IT operations |
| 33 | Deploy endpoint detection and response (EDR) on servers, workstations and cloud instances, tune it, and enable isolation and collection | Security operations |
| 34 | Add telemetry where EDR coverage is thin, and validate it with adversary simulation | Detection engineering |
| 35 | Monitor the network at egress and at segment boundaries, for north-south and east-west traffic | Security operations |
| 36 | Map detection rules to MITRE ATT&CK techniques, test them by simulation, track coverage and retire stale rules | Detection engineering |
| 37 | Run a hunting program with a hypothesis catalog, target data sources, a cadence per hypothesis, an audit table of runs, and findings promoted into rules | Threat hunting |
| 38 | Keep an asset inventory covering hardware, software, data, cloud and third-party connections, with offline copies | IT operations |
| 39 | Reconcile attack surface monitoring against the internal inventory | Vulnerability management |
| 40 | Prioritize remediation on Common Vulnerability Scoring System (CVSS) severity together with Exploit Prediction Scoring System (EPSS) probability, asset criticality, exposure and active exploitation intelligence | Vulnerability management |
Decisions and records
- Decide authority to isolate, containment tiers, risk levels, notification clocks and evidence handling in Decide these before the incident.
- Keep the signed authority matrix, the critical asset list and the contact list where responders can reach them offline.
- Add the preparation each scenario page lists for its incident type, such as offline backups for ransomware and HR agreements for insider cases.
Watch out
- Count a capability only if people use it. An intelligence feed nobody queries, a console nobody opens, and a playbook last edited by someone who has left will not help when the incident starts.