Use playbooks to automate analyst workflows in Splunk SOAR (On-premises)

Create a playbook in Splunk SOAR (On-premises) 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 Splunk SOAR (On-premises). 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 Splunk SOAR (On-premises).

After you create and save a playbook in Splunk SOAR (On-premises), you can run playbooks when performing these tasks in Splunk SOAR (On-premises):

  • Triaging or investigating cases as an analyst
  • Creating or adding a case to Investigation
  • Configuring playbooks to run automatically directly from the playbook editor

You can see statistics for runs of your playbooks in the Visual Playbook Editor. See View Playbook Run Statistics for information on the kind of statistics and how to access them.

Note: The playbook editor requires a minimum screen width of 1200px.
CAUTION: 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.
Note: 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.