building-incident-response-playbook

Featured

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.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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: ``` P...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category