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 admin@dns-primary.corp.local
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:
- Interview SOC analysts to document their current ad hoc process
- Define the trigger: user reports phishing email via abuse@ mailbox or phishing button
- Write triage steps: extract email headers, check sender reputation, analyze URLs/attachments in sandbox
- Define containment: quarantine email from all mailboxes, block sender domain, reset passwords if credentials entered
- Build SOAR automation: auto-extract IOCs from reported email, enrich via VirusTotal, create case in TheHive
- 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 abuse@corp.com 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
1---2name: building-incident-response-playbook3description: >4 Designs and documents structured incident response playbooks that define step-by-step5 procedures for specific incident types aligned with NIST SP 800-61r3 and SANS PICERL6 frameworks. Covers playbook structure, decision trees, escalation criteria, RACI matrices,7 and integration with SOAR platforms. Activates for requests involving IR playbook creation,8 incident response procedure documentation, response runbook development, or SOAR playbook9 design.10domain: cybersecurity11subdomain: incident-response12tags: [IR-playbook, runbook, NIST-800-61, SOAR-integration, response-procedures]13version: 1.0.014author: mahipal15license: MIT16metadata:17 source: https://skillmd.com/skills/njones17/building-incident-response-playbook18---1920# Building Incident Response Playbooks2122## When to Use2324- Establishing or maturing an incident response program from scratch25- Documenting procedures for a new incident type after a novel attack26- Automating response workflows in a SOAR platform (Cortex XSOAR, Splunk SOAR)27- Preparing for compliance audits requiring documented IR procedures (SOC 2, PCI-DSS, HIPAA)28- Conducting a gap analysis of existing IR capabilities against specific threat scenarios2930**Do not use** for one-time ad hoc investigations; playbooks are reusable procedure documents, not case-specific reports.3132## Prerequisites3334- Organizational risk assessment identifying top incident scenarios by likelihood and impact35- NIST SP 800-61r3 or SANS PICERL framework adopted as the organizational IR standard36- Asset inventory with business criticality ratings and data classification37- RACI chart defining roles: Incident Commander, SOC analysts, system administrators, legal, communications38- Existing detection capabilities inventory (SIEM rules, EDR detections, IDS signatures)39- SOAR platform access if building automated playbooks4041## Workflow4243### Step 1: Select and Scope the Incident Type4445Define the specific scenario the playbook will address:4647- Identify the top incident types based on organizational risk assessment and historical data48- Scope each playbook to a single incident type for clarity (do not combine unrelated scenarios)49- Define trigger conditions that activate the playbook5051Common playbook types:52```53Priority Playbooks (build first):541. Ransomware incident response552. Phishing/credential compromise563. Business email compromise574. Malware infection585. Data breach/exfiltration596. DDoS attack607. Insider threat618. Account takeover629. Web application compromise6310. Cloud infrastructure compromise64```6566### Step 2: Define the Playbook Structure6768Every playbook should follow a consistent structure:6970```71PLAYBOOK TEMPLATE72━━━━━━━━━━━━━━━━731. Playbook Metadata74 - Name, version, owner, last review date75 - Trigger conditions76 - Severity criteria77782. RACI Matrix79 - Who is Responsible, Accountable, Consulted, Informed for each step80813. Detection & Triage82 - How the incident is detected83 - Initial triage checklist84 - Severity classification criteria85864. Containment87 - Short-term containment actions88 - Long-term containment actions89 - Evidence preservation requirements90915. Eradication92 - Root cause identification93 - Malware/threat removal steps94 - Verification procedures95966. Recovery97 - System restoration steps98 - Validation criteria99 - Monitoring requirements post-recovery1001017. Post-Incident102 - Lessons learned meeting trigger103 - Report template104 - Detection improvement actions1051068. Communication107 - Internal notification matrix108 - External notification requirements (regulators, customers, law enforcement)109 - Status update cadence1101119. Appendices112 - Tool-specific procedures113 - Contact lists114 - Evidence collection checklists115```116117### Step 3: Write Decision Trees and Escalation Criteria118119Define clear decision points with binary outcomes:120121```122Detection Alert Received123├── Is the alert a true positive?124│ ├── YES → Classify severity125│ │ ├── P1 (Critical) → Page incident commander, begin containment immediately126│ │ ├── P2 (High) → Notify IR lead, begin investigation within 30 min127│ │ ├── P3 (Medium) → Queue for investigation within 4 hours128│ │ └── P4 (Low) → Document and investigate within 24 hours129│ └── NO → Document as false positive, tune detection rule130└── Cannot determine → Escalate to Tier 2 for deeper analysis131```132133Escalation triggers:134- Any P1 incident: Immediate escalation to IR lead and CISO135- Data exfiltration confirmed: Legal counsel and privacy officer notified136- Customer data involved: Customer notification process activated137- Third-party involvement: Vendor security contact engaged138- Law enforcement needed: General counsel authorizes before contact139140### Step 4: Define Specific Technical Procedures141142Write tool-specific instructions for each step (not generic guidance):143144```145CONTAINMENT - Endpoint Isolation via CrowdStrike:1461. Open Falcon Console > Hosts > Search for affected hostname1472. Click on the host > Host Details1483. Click "Contain Host" button in upper right1494. Confirm isolation (host will only communicate with CrowdStrike cloud)1505. Document containment action in incident ticket with timestamp1516. Verify containment: Host should show "Contained" status badge152153CONTAINMENT - Block C2 Domain at DNS:1541. SSH to DNS server: ssh admin@dns-primary.corp.local1552. Add to block zone: echo "zone evil.com { type master; file /etc/bind/db.sinkhole; };" >> /etc/bind/named.conf.local1563. Reload DNS: rndc reload1574. Verify: dig @dns-primary evil.com (should resolve to sinkhole IP 10.0.0.99)1585. Document blocked domain in incident ticket159```160161### Step 5: Integrate with SOAR Platform162163Convert manual playbook steps into automated workflows:164165- Map each playbook step to a SOAR action (API call, script, human decision point)166- Define automation boundaries (what runs automatically vs. what requires analyst approval)167- Build enrichment automations for the triage phase168- Create containment automations with approval gates for high-impact actions169- Configure notification automations for stakeholder communication170171### Step 6: Test and Maintain the Playbook172173Validate the playbook through exercises and maintain currency:174175- Conduct tabletop exercises with the IR team walking through the playbook176- Perform live-fire exercises simulating the incident type in a test environment177- Review and update after every real incident that uses the playbook178- Schedule quarterly reviews for accuracy of contact lists, tool procedures, and escalation paths179- Track playbook metrics: mean time to contain, mean time to resolve, false positive rate180181## Key Concepts182183| Term | Definition |184|------|------------|185| **Playbook** | Documented, repeatable set of procedures for responding to a specific incident type |186| **Runbook** | More granular than a playbook; step-by-step technical instructions for a specific task within a playbook |187| **RACI Matrix** | Responsibility assignment chart defining who is Responsible, Accountable, Consulted, and Informed for each activity |188| **Decision Tree** | Flowchart-based logic defining the response path based on binary conditions at each decision point |189| **Escalation Criteria** | Predefined conditions that trigger notification of higher-level personnel or external parties |190| **SOAR Playbook** | Automated workflow in a Security Orchestration, Automation, and Response platform executing playbook steps |191192## Tools & Systems193194- **Cortex XSOAR**: SOAR platform with visual playbook editor, 700+ integrations, and collaborative War Room195- **Splunk SOAR**: SOAR platform integrated with Splunk ES, drag-and-drop playbook builder with 2,800+ automated actions196- **TheHive**: Open-source incident response platform with case templates that function as playbook frameworks197- **Confluence / GitLab Wiki**: Documentation platforms for maintaining human-readable playbook documents with version control198- **Tines**: No-code security automation platform for building playbook workflows without programming199200## Common Scenarios201202### Scenario: Building a Phishing Response Playbook from Scratch203204**Context**: An organization with a 5-person SOC has no documented phishing response procedure. Analysts handle phishing reports inconsistently.205206**Approach**:2071. Interview SOC analysts to document their current ad hoc process2082. Define the trigger: user reports phishing email via abuse@ mailbox or phishing button2093. Write triage steps: extract email headers, check sender reputation, analyze URLs/attachments in sandbox2104. Define containment: quarantine email from all mailboxes, block sender domain, reset passwords if credentials entered2115. Build SOAR automation: auto-extract IOCs from reported email, enrich via VirusTotal, create case in TheHive2126. Test with simulated phishing email and measure response time improvement213214**Pitfalls**:215- Writing overly generic procedures that don't reference specific tool interfaces or commands216- Not including the communication plan for notifying users who received the phishing email217- Forgetting to define the criteria for when a phishing report becomes a full incident investigation218- Not versioning the playbook or scheduling regular review cycles219220## Output Format221222```223INCIDENT RESPONSE PLAYBOOK224============================225Playbook Name: Phishing Incident Response226Version: 2.1227Owner: SOC Manager228Last Reviewed: 2025-11-01229Next Review: 2026-02-01230Trigger: Phishing email reported via abuse@corp.com or phish button231232RACI MATRIX233Activity | SOC L1 | SOC L2 | IR Lead | Legal | Comms234Initial Triage | R | C | I | |235Email Analysis | R | A | I | |236Containment | | R | A | I |237Credential Reset | | R | A | |238User Notification | | C | A | | R239Regulatory Notification | | | C | R | A240Lessons Learned | C | C | R | I | I241242PROCEDURE STEPS243[Detailed steps with tool-specific instructions]244245DECISION TREE246[Flowchart logic]247248ESCALATION MATRIX249[Conditions and contacts]250251METRICS252Target MTTA: 15 minutes253Target MTTC: 1 hour254Target MTTR: 4 hours255```