Skip to main content
skill CX Codex

building-incident-response-playbook — Claude Code skill

building-incident-response-playbook designs structured incident response playbooks aligned with NIST SP 800-61r3 and SANS PICERL. Helps teams draft response procedures, decision trees, and SOAR workflows.

Apache-2.0 324 installs ★ 36,511 updated 2026-08-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-incident-response-playbook -a claude-code
Open on GitHub

What building-incident-response-playbook does

This skill builds standardized incident response runbooks based on the NIST SP 800-61r3 and SANS PICERL frameworks. It scopes each playbook to a single threat scenario, such as ransomware or credential compromise. The logic requires clear trigger conditions before any response sequence begins.

Output files follow a nine-part template. The skill drafts RACI matrices, triage severity levels, and specific containment steps. It also generates explicit tool commands, such as endpoint isolation in CrowdStrike Falcon or domain blocking in BIND DNS.

For security orchestration, response steps translate into actions for Cortex XSOAR or Splunk SOAR. Playbooks focus entirely on reusable documentation rather than one-off forensic investigations. Without an asset inventory and defined team roles, these procedures cannot function effectively.

What it helps with

  • Document response procedures for ransomware or credential compromise
  • Establish a RACI matrix and clear escalation triggers for CISO alerts
  • Translate manual containment actions into automated SOAR workflows
  • Prepare structured security procedures for SOC 2 or PCI-DSS audits

Example prompts for the agent

  • Draft a ransomware incident response playbook aligned with NIST SP 800-61r3 including a RACI matrix.
  • Create a containment procedure for credential compromise with endpoint isolation steps in CrowdStrike.
  • Design a triage decision tree with escalation triggers for confirmed data exfiltration.

How to install building-incident-response-playbook

1Skills CLI (Vercel)

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-incident-response-playbook -a claude-code

2Manually: put the files in place

~/.claude/skills/building-incident-response-playbook/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/building-incident-response-playbook/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about building-incident-response-playbook

How to install building-incident-response-playbook in Claude Code?

Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-incident-response-playbook -a claude-code in your terminal.

What does building-incident-response-playbook do?

It generates standardized incident handling runbooks, sets RACI responsibilities, and structures containment procedures across security tools.

Can this skill be used to investigate an active security incident?

No, this skill creates reusable procedure templates and automation workflows rather than investigating ad-hoc incident cases.

Source text

SKILL.md · Apache-2.0
---
name: building-incident-response-playbook
description: Designs and documents structured incident response playbooks with step-by-step
  procedures per incident type, decision trees, escalation criteria, RACI matrices,
  and SOAR platform integration, aligned to NIST SP 800-61r3 and SANS PICERL. Use
  when creating or maturing an IR program, documenting response runbooks for a new
  incident type, or designing SOAR playbooks.
domain: cybersecurity
subdomain: incident-response
tags:
- IR-playbook
- runbook
- NIST-800-61
- SOAR-integration
- response-procedures
mitre_attack:
- T1486
- T1566
- T1190
- T1041
- T1078
version: 1.0.0
author: mahipal
license: Apache-2.0
nist_csf:
- RS.MA-01
- RS.MA-02
- RS.AN-03
- RC.RP-01
---

# Building Incident Response Playbooks

## When to Use

- Establishing or maturing an incident response program from scratch
- Documenting procedures for a new incident type after a novel attack
- Automating response workflows in a SOAR platform (Cortex XSOAR, Splunk SOAR)
- Preparing for compliance audits requiring documented IR procedures (SOC 2, PCI-DSS, HIPAA)
- Conducting a gap analysis of existing IR capabilities against specific threat scenarios

**Do not use** for one-time ad hoc investigations; playbooks are reusable procedure documents, not case-specific reports.

## Prerequisites

- Organizational risk assessment identifying top incident scenarios by likelihood and impact
- NIST SP 800-61r3 or SANS PICERL framework adopted as the organizational IR standard
- Asset inventory with business criticality ratings and data classification
- RACI chart defining roles: Incident Commander, SOC analysts, system administrators, legal, communications
- Existing detection capabilities inventory (SIEM rules, EDR detections, IDS signatures)
- SOAR platform access if building automated playbooks

## Workflow

### Step 1: Select and Scope the Incident Type

Define the specific scenario the playbook will address:

- Identify the top incident types based on organizational risk assessment and historical data
- Scope each playbook to a single incident type for clarity (do not combine unrelated scenarios)
- Define trigger conditions that activate the playbook

Common playbook types:
```
Priority Playbooks (build first):
1. Ransomware incident response
2. Phishing/credential compromise
3. Business email compromise
4. Malware infection
5. Data breach/exfiltration
6. DDoS attack
7. Insider threat
8. Account takeover
9. Web application compromise
10. Cloud infrastructure compromise
```

### Step 2: Define the Playbook Structure

Every playbook should follow a consistent structure:

```
PLAYBOOK TEMPLATE
━━━━━━━━━━━━━━━━
1. Playbook Metadata
   - Name, version, owner, last review date
   - Trigger conditions
   - Severity criteria

2. RACI Matrix
   - Who is Responsible, Accountable, Consulted, Informed for each step

3. Detection & Triage
   - How the incident is detected
   - Initial triage checklist
   - Severity classification criteria

4. Containment
   - Short-term containment actions
   - Long-term containment actions
   - Evidence preservation requirements

5. Eradication
   - Root cause identification
   - Malware/threat removal steps
   - Verification procedures

6. Recovery
   - System restoration steps
   - Validation criteria
   - Monitoring requirements post-recovery

7. Post-Incident
   - Lessons learned meeting trigger
   - Report template
   - Detection improvement actions

8. Communication
   - Internal notification matrix
   - External notification requirements (regulators, customers, law enforcement)
   - Status update cadence

9. Appendices
   - Tool-specific procedures
   - Contact lists
   - Evidence collection checklists
```

### Step 3: Write Decision Trees and Escalation Criteria

Define clear decision points with binary outcomes:

```
Detection Alert Received
├── Is the alert a true positive?
│   ├── YES → Classify severity
│   │   ├── P1 (Critical) → Page incident commander, begin containment immediately
│   │   ├── P2 (High) → Notify IR lead, begin investigation within 30 min
│   │   ├── P3 (Medium) → Queue for investigation within 4 hours
│   │   └── P4 (Low) → Document and investigate within 24 hours
│   └── NO → Document as false positive, tune detection rule
└── Cannot determine → Escalate to Tier 2 for deeper analysis
```

Escalation triggers:
- Any P1 incident: Immediate escalation to IR lead and CISO
- Data exfiltration confirmed: Legal counsel and privacy officer notified
- Customer data involved: Customer notification process activated
- Third-party involvement: Vendor security contact engaged
- Law enforcement needed: General counsel authorizes before contact

### Step 4: Define Specific Technical Procedures

Write tool-specific instructions for each step (not generic guidance):

```
CONTAINMENT - Endpoint Isolation via CrowdStrike:
1. Open Falcon Console > Hosts > Search for affected hostname
2. Click on the host > Host Details
3. Click "Contain Host" button in upper right
4. Confirm isolation (host will only communicate with CrowdStrike cloud)
5. Document containment action in incident ticket with timestamp
6. Verify containment: Host should show "Contained" status badge

CONTAINMENT - Block C2 Domain at DNS:
1. SSH to DNS server: ssh [email protected]
2. Add to block zone: echo "zone evil.com { type master; file /etc/bind/db.sinkhole; };" >> /etc/bind/named.conf.local
3. Reload DNS: rndc reload
4. Verify: dig @dns-primary evil.com (should resolve to sinkhole IP 10.0.0.99)
5. Document blocked domain in incident ticket
```

### Step 5: Integrate with SOAR Platform

Convert manual playbook steps into automated workflows:

- Map each playbook step to a SOAR action (API call, script, human decision point)
- Define automation boundaries (what runs automatically vs. what requires analyst approval)
- Build enrichment automations for the triage phase
- Create containment automations with approval gates for high-impact actions
- Configure notification automations for stakeholder communication

### Step 6: Test and Maintain the Playbook

Validate the playbook through exercises and maintain currency:

- Conduct tabletop exercises with the IR team walking through the playbook
- Perform live-fire exercises simulating the incident type in a test environment
- Review and update after every real incident that uses the playbook
- Schedule quarterly reviews for accuracy of contact lists, tool procedures, and escalation paths
- Track playbook metrics: mean time to contain, mean time to resolve, false positive rate

## Key Concepts

| Term | Definition |
|------|------------|
| **Playbook** | Documented, repeatable set of procedures for responding to a specific incident type |
| **Runbook** | More granular than a playbook; step-by-step technical instructions for a specific task within a playbook |
| **RACI Matrix** | Responsibility assignment chart defining who is Responsible, Accountable, Consulted, and Informed for each activity |
| **Decision Tree** | Flowchart-based logic defining the response path based on binary conditions at each decision point |
| **Escalation Criteria** | Predefined conditions that trigger notification of higher-level personnel or external parties |
| **SOAR Playbook** | Automated workflow in a Security Orchestration, Automation, and Response platform executing playbook steps |

## Tools & Systems

- **Cortex XSOAR**: SOAR platform with visual playbook editor, 700+ integrations, and collaborative War Room
- **Splunk SOAR**: SOAR platform integrated with Splunk ES, drag-and-drop playbook builder with 2,800+ automated actions
- **TheHive**: Open-source incident response platform with case templates that function as playbook frameworks
- **Confluence / GitLab Wiki**: Documentation platforms for maintaining human-readable playbook documents with version control
- **Tines**: No-code security automation platform for building playbook workflows without programming

## Common Scenarios

### Scenario: Building a Phishing Response Playbook from Scratch

**Context**: An organization with a 5-person SOC has no documented phishing response procedure. Analysts handle phishing reports inconsistently.

**Approach**:
1. Interview SOC analysts to document their current ad hoc process
2. Define the trigger: user reports phishing email via abuse@ mailbox or phishing button
3. Write triage steps: extract email headers, check sender reputation, analyze URLs/attachments in sandbox
4. Define containment: quarantine email from all mailboxes, block sender domain, reset passwords if credentials entered
5. Build SOAR automation: auto-extract IOCs from reported email, enrich via VirusTotal, create case in TheHive
6. Test with simulated phishing email and measure response time improvement

**Pitfalls**:
- Writing overly generic procedures that don't reference specific tool interfaces or commands
- Not including the communication plan for notifying users who received the phishing email
- Forgetting to define the criteria for when a phishing report becomes a full incident investigation
- Not versioning the playbook or scheduling regular review cycles

## Output Format

```
INCIDENT RESPONSE PLAYBOOK
============================
Playbook Name:    Phishing Incident Response
Version:          2.1
Owner:            SOC Manager
Last Reviewed:    2025-11-01
Next Review:      2026-02-01
Trigger:          Phishing email reported via [email protected] or phish button

RACI MATRIX
Activity                    | SOC L1 | SOC L2 | IR Lead | Legal | Comms
Initial Triage              |   R    |   C    |   I     |       |
Email Analysis              |   R    |   A    |   I     |       |
Containment                 |        |   R    |   A     |   I   |
Credential Reset            |        |   R    |   A     |       |
User Notification           |        |   C    |   A     |       |   R
Regulatory Notification     |        |        |   C     |   R   |   A
Lessons Learned             |   C    |   C    |   R     |   I   |   I

PROCEDURE STEPS
[Detailed steps with tool-specific instructions]

DECISION TREE
[Flowchart logic]

ESCALATION MATRIX
[Conditions and contacts]

METRICS
Target MTTA: 15 minutes
Target MTTC: 1 hour
Target MTTR: 4 hours
```

© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills

Similar skills

All skills for Security →

From the same set152

The whole set →
analyzing-pdf-malware-with-pdfid analyzing-pdf-malware-with-pdfid walks an agent through a suspicious PDF's structure to find embedded JavaScript, shellcode and exploits before anyone opens the file. CX Codex +1 328installs analyzing-memory-forensics-with-lime-and-volatility analyzing-memory-forensics-with-lime-and-volatility is a Claude Code skill for acquiring Linux memory images with LiME and analyzing artifacts in Volatility 3 during incident investigations. CX Codex +1 328installs analyzing-threat-intelligence-feeds analyzing-threat-intelligence-feeds turns commercial and open-source threat intel feeds into actionable indicators, adversary tactics and campaign context, normalized to STIX 2.1. CX Codex +1 327installs conducting-network-penetration-test The conducting-network-penetration-test skill guides authorized network penetration tests, covering host discovery, service checks, vulnerability review, controlled exploitation, and reporting. CX Codex +1 325installs analyzing-ransomware-network-indicators analyzing-ransomware-network-indicators parses Zeek conn.log and NetFlow to spot periodic C2 callbacks, TOR exit node connections and large outbound transfers. CX Codex +1 324installs analyzing-threat-actor-ttps-with-mitre-attack analyzing-threat-actor-ttps-with-mitre-attack maps threat actor behavior and observed IOCs to MITRE ATT&CK, creates ATT&CK Navigator layers, and helps assess detection gaps. CX Codex +1 323installs abusing-shadow-credentials-for-privesc abusing-shadow-credentials-for-privesc is a Claude Code skill that guides Active Directory account takeover via Shadow Credentials, from writing a public key to msDS-KeyCredentialLink to recovering the target NT hash with PKINIT. CX Codex +1 322installs exploiting-websocket-vulnerabilities exploiting-websocket-vulnerabilities is a Claude Code skill for checking WebSocket authentication, cross-site hijacking, injection, and message handling. It runs during authorized security assessments of applications that use WebSockets. CX Codex +1 316installs

Project sponsors

Companies that keep this analytics open