--- name: building-incident-response-playbook-d64a19c6b6e6 description: 'Designs 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. ' domain: cybersecurity subdomain: incident-response tags: - IR-playbook - runbook - NIST-800-61 - SOAR-integration - response-procedures mitre_attack: - T1190 - T1566 - T1078 version: 1.0.0 author: Krishna Kumar (xalgord) 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. ## Common Misconfigurations & Verification - **Containment steps that destroy evidence:** a playbook that says "reimage" or "power off the host" before volatile capture wipes RAM, network connections, and `/tmp` artifacts. Order it correctly — isolate (network-contain, keep powered) → capture memory/volatile state → then eradicate. Power-off is a last resort for active destruction (ransomware encrypting). - **Containment that tips off the attacker:** blocking the C2 domain at DNS or disabling the account can trigger dead-man switches or push the actor to backup persistence. Stage simultaneous actions (block all C2 + rotate all creds + kill persistence at once) rather than piecemeal, and verify with the team before pulling triggers. - **Eradication that misses persistence:** removing the malware binary but leaving the cron job, systemd unit, scheduled task, or rogue SSH key guarantees reinfection. The playbook must enumerate persistence locations and require a clean-rebuild decision. - **Stale automation:** SOAR steps referencing decommissioned tools or expired API tokens fail silently mid-incident. **Verify the playbook actually holds:** run a tabletop *and* a live-fire test in a lab — confirm C2 is truly blocked (`dig` resolves to sinkhole, EDR shows no outbound), confirm rotated creds reject the old password, confirm persistence is gone after reboot, and confirm contact lists/escalation paths are current. Track MTTC/MTTR from the exercise, not assumptions. ## 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**: 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 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 ``` --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/incident-response/building-incident-response-playbook/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/incident-response/building-incident-response-playbook/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Operations Roles: Operations Manager, Security Engineer Specialties: Specialty not specified Tools: Soar Platforms Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 82f95889ab74d67443e8be5536579f28b19cd7330cde1dee297c32532e5eb882