Use playbooks to automate analyst workflows in
Create a playbook in to automate security workflows so that analysts can spend more time performing analysis and investigation. The playbook editor provides a visual platform for creating playbooks without having to write code.
To define a workflow that you want to automate, link together a series of actions that are provided by apps. An app is third-party software integrated with . For example, you can integrate MaxMind as an app, which provides a
geolocate ip action, or integrate Okta as app to provide actions such as
set password or
enable user. The actions available for use in your playbooks are determined by the apps integrated with .
After you create and save a playbook in , you can run playbooks when performing these tasks in :
- Triaging or investigating cases as an analyst
- Creating or adding a case to Investigation
- Configuring playbooks to run automatically directly from the playbook editor
The playbook editor has a minimum supported screen size of 1200px.
Python 3.9 impacts on apps:
You must upgrade all custom apps to be compatible with with Python 3.9. If you don't, those apps might not run in the Python 3.9 environment.
Existing Python 3.6 playbooks continue to work in the new Python 3.9 environment.
If you use the terms "async" or "await" as names of variables, functions, or other pieces of code in your playbooks, a SyntaxError results. Rename anything named "async" or "await" in your playbooks.
If your system restarts while a playbook is running, the playbook run is cancelled. Any changes made by the playbook before the restart remain, and are not rolled back.
Debug playbooks in
Choose between playbooks and classic playbooks in
This documentation applies to the following versions of Splunk® SOAR (Cloud): current
Feedback submitted, thanks!