A curated repository of 1347 playbooks and scripts for security incident response, aimed to help security analysts and DFIR teams.
Vendor | Playbooks | Format | Link |
---|---|---|---|
Catalyst | 3 | YAML | /playbooks/catalyst |
Cortex XSOAR | 131 | YAML | /playbooks/xsoar |
Cisa IR playbooks | 81 | BPMN | /playbooks/cisa |
Palo Alto Demisto | 59 | YAML | /playbooks/demisto |
Fortinet FortiSOAR | 193 | JSON | /playbooks/fortinet |
Guardsight | 55 | /playbooks/guard_sight | |
IACD Automate | 9 | BPMN | /playbooks/iacd_automate |
LogicHub SOAR | 70 | JSON | /playbooks/logichub |
Microsoft | 4 | PNG | /playbooks/microsoft |
MS Azure Sentinel | 217 | JSON | /playbooks/ms_azure |
OasisOpen | 1 | JSON | /playbooks/oasis_open |
Rapid7 Insightconnect | 214 | ICON | /playbooks/rapid7 |
Resolve | 149 | XML | /playbooks/resolve |
Shuffle Automation | 18 | JSON | /playbooks/shuffle |
Chronicle Security | 4 | JSON | /playbooks/siemplify |
Splunk SOAR | 119 | JSON | /playbooks/splunk |
ThreatConnect | 83 | PBX(Z) | /playbooks/threat_connect |
Tines | 87 | JSON | /playbooks/tines |
Incident response "playbooks" are structured sets of operational procedures organizations use to instruct humans or machines on performing countermeasures against cybersecurity threats. These playbooks generally combine information about a given threat and organizational aspects relevant within the context of an organization. Both types of information are crucial for using, maintaining, and sharing playbooks across organizations as they ensure effectiveness and confidentiality. While practitioners show great interest in playbooks, their characteristics have not yet been thoroughly investigated from a research perspective. For this reason, we explore the topic by analyzing what is inside a playbook. Our approach consists of a comprehensive empirical assessment of available data (1217 playbooks), an online study with 147 participants, and final in-depth interviews with nine security professionals to consolidate and validate our findings. We notably find intrinsic ambiguities in the way practitioners and organizations define their playbooks. Furthermore, we notice that available playbooks cannot be used outright which might currently impair their wide use across different cybersecurity actors. As a result, we can conclude that organizations do "play it by the books" but individually define what is inside their playbooks and which areas of incident response they might address.
In addition, we provide a structural and content analysis of the playbooks and their steps. On the one hand, we look at the schemas of individual vendors and derive a meta-playbook from them (go to schemas). In addition, we analyze the content of the playbooks, compare the steps, and form categories (go to analysis).
We conducted expert interviews with nine experts and performed an online study with n=147 to gather information on a incident response processes. The data collected is not published to protect the privacy of the participants, but we publish the structure and content of both the interview and the questionnaire (go to factors).
We encourage contributions from the cybersecurity community to make this repository a valuable and up-to-date resource. If you have new incident response playbooks, incident analysis reports, or improvements to existing content, we welcome your contributions.
To contribute:
- Fork the repository and create your branch (
git checkout -b my-contribution
) - Make your changes and commit them (
git commit -m 'Added a new playbook'
) - Push the changes to your forked repository (
git push origin my-contribution
) - Open a pull request to the
main
branch of this repository.
Please consider citing our publication if you are using our Awesome-Playbooks for your research:
@InProceedings{Schlette2023,
author = {Daniel Schlette and
Philip Empl and
Marco Caselli and
Thomas Schreck and
G{\"u}nther Pernul},
title = {Do You Play It by the Books? A Study on Incident Response Playbooks and Influencing Factors},
booktitle = {Proceedings of the 45th IEEE Symposium on Security and Privacy, {SP} 2024, San Francisco, CA, USA, May 20-23, 2024},
pages = {1--19},
publisher = {{IEEE}},
year={2024}
}
Thank you for visiting our Incident Response Playbooks and Analysis Collection repository. We hope that this resource will empower you to handle cybersecurity incidents effectively and contribute to the collective security of our digital world.
If you have any questions or suggestions, feel free to reach out to us or create an issue in the repository.
Happy analyzing and responding!