Online instance: https://opencybersecurityalliance.github.io/cacao-roaster/
CACAO Roaster is a sub-project of the Open Cybersecurity Alliance Community (OCA Community). It is a web application for generating, parsing, validating, editing, and visualizing CACAO v2.0 playbooks.
If you use CACAO Roaster in your work, please cite it as:
Zych, M., Mavroeidis, V., & Open Cybersecurity Alliance Community. (2025).
CACAO Roaster (Version 1.3.0) [Computer software]. Zenodo.
https://doi.org/10.5281/zenodo.20570338
Citation metadata is also available in CITATION.cff. On GitHub, you can use the Cite this repository button to export the citation in formats such as APA and BibTeX.
- CACAO Roaster
- Citation
- Introduction
- Getting Started
- Governance
- CLA and Non-assert signatures required
As cyber systems become increasingly complex and cybersecurity threats become more prominent, defenders must prepare, coordinate, automate, document, and share their response methodologies whenever possible. The CACAO standard was developed to address these requirements by providing a common, machine-readable framework and schema for documenting cybersecurity operations processes, including defensive tradecraft, tactics, techniques, and procedures.
To support wider adoption of the CACAO standard, it is important to simplify the creation, modification, and understanding of CACAO playbooks. CACAO Roaster addresses this need by providing a faster and easier way to create, edit, visualize, and share CACAO playbooks through a no-code graphical interface.
The CACAO Roaster web application fully complies with the CACAO Security Playbooks v2.0 Committee Specification 01.
CACAO Roaster is currently stable at version 1.3.0 and is under continuous maintenance.
The maintenance team tracks open issues and work items on the GitHub issues page.
CACAO Roaster includes a basic integration with the CACAO orchestrator/executor SOARCA.
To use this integration, you need a running instance of SOARCA. You can configure CACAO Roaster to use it by setting the SOARCA_URL environment variable to the SOARCA instance URL, or by providing the SOARCA URL directly in the SOARCA integration window in CACAO Roaster.
Integration with the CACAO executor SOARCA.
CACAO Roaster is aligned with CACAO and can be used alongside related OCA Community and OASIS cybersecurity automation efforts, including STIX and OpenC2.
Start screen of the application.
Example of a playbook view.
These instructions will help you run CACAO Roaster locally for development purposes. See the deployment section for notes on running the project on a live system.
- Node.js >= 20.5.0
- npm >= 9.8.0
Install the project dependencies:
npm iRun the project locally in development mode:
npm run startCACAO Roaster will be available locally at:
http://localhost:3000/
Build the project for production:
npm run buildInstall the serve package on the hosting machine:
npm install serveServe the production bundle:
serve distAlternatively, use Docker to build and run the application in a container:
docker build -t cacao-roaster .
docker run -it -p 3000:3000 cacao-roasterContributions are welcome. You can contribute by reporting issues, suggesting improvements, improving documentation, or submitting pull requests.
Before contributing, please review the repository guidelines in CONTRIBUTING.md. Technical contributions must also satisfy the CLA and non-assert requirements described below.
- Mateusz Zych: https://github.com/mateusdz
- Vasileios Mavroeidis: https://github.com/Vasileios-Mavroeidis
For support, questions, feature requests, or bug reports, please use the GitHub issues page or the community channels listed below.
Stay up to date on meetings, announcements, and other discussions with the CACAO Roaster mailing list. To subscribe, send an empty email to oca-cacao-roaster+subscribe@lists.oasis-open-projects.org.
CACAO Roaster has a Slack channel on the OCA Community Slack. Join here and say hi in #cacao-roaster.
This project is licensed under the Apache 2.0 License. See the LICENSE.md file for details.
CACAO Roaster operates as a sub-project of the Open Cybersecurity Alliance Community (OCA Community). Further details can be found in the OCA Community Governance document.
All technical contributions must be covered by a Contributor's License Agreement. This requirement allows our work to advance through OASIS standards development stages and potentially be submitted to de jure organizations such as ISO. You will get a prompt to sign this document when you submit your first pull request to a project repository, or you can sign here. If you are contributing on behalf of your employer, you must also sign the ECLA here.



