building-incident-response-playbook
FeaturedDesigns and documents structured incident response playbooks that define step-by-step procedures for specific incident types aligned with NIST SP 800-61r3 and SANS PICERL frameworks. Covers playbook structure, decision trees, escalation criteria, RACI matrices, and integration with SOAR platforms. Activates for requests involving IR playbook creation, incident response procedure documentation, response runbook development, or SOAR playbook design.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- adriannoes
- Repository
- adriannoes/awesome-agentic-ai
- Created
- 11 months ago
- Last Updated
- 1 weeks ago
- Language
- Jupyter Notebook
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ir-playbook
Use when writing a scenario-specific incident response playbook — ransomware, phishing, data breach, insider threat, or DDoS — with containment steps, exact commands, and decision trees per NIST SP 800-61, SANS PICERL, MITRE ATT&CK, and D3FEND. Triggers on "IR playbook", "runbook", "ransomware response", "containment steps", "PICERL".
soar-playbook-design
Design safe security automation playbooks for a SOAR platform (Microsoft Sentinel automation rules and Logic Apps, Splunk SOAR, Cortex XSOAR, Tines, Shuffle): triggers, enrichment, decision logic, containment behind human-approval gates, idempotency, rate limits, rollback, error handling, dry-run testing, and metrics, expressed in a vendor-agnostic JSON definition that a bundled linter checks. Use this whenever someone wants to "automate" an alert response, asks for a playbook, workflow, automation rule, Logic App, story, or runbook-as-code, wants to auto-block, auto-isolate, auto-disable, or auto-close anything, asks "is this automation safe", or wants an existing playbook reviewed or translated between platforms. Design and review only; it never executes actions.
playbook
Write a strategic operational playbook that coordinates a CLASS of situations (e.g. a Sev1 outage) across roles, decision points, and phases. Use for higher-altitude incident/operations coordination. Anti-trigger; for fixing one specific alert step-by-step use sre-runbook (tactical), not a playbook.