After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
How can be installed?
Installing is the first step to realizing gains from security orchestration and automation. allows you to combine security infrastructure orchestration, playbook automation, and case management capabilities to integrate your team, processes, and tools together.
If you are a system administrator who is responsible for setting up , this guide will help you understand how to get , the system requirements for installing , how to install , as well as clustering, advanced setup, and upgrading .
You can install as an unprivileged application under its own user account. See Install as an unprivileged user.
The application can be installed on local hardware controlled by your organization, or using the same installation package, in an Amazon Web Services EC2 instance.
There are several options to choose from when you deploy . Work with your Delivery Team representative to choose the right method and options for your organization.
The following table lists your options with links to relevant portions of this manual:
| Installation option | Additional information |
|---|---|
| Clustered, unprivileged | Start with the clustering overview in About clusters.
Then follow the instructions in Create a cluster using an unprivileged installation |
| SOAR instance with one or more external services | Your deployment can externalize services such as the PostgreSQL database, file shares, or a load balancer.
For each of the options, see the relevant documentation. |
| SOAR instance with Federal Information Processing Standard (FIPS) support | A new, unprivileged deployment of can be created in a FIPS-compliant mode.
The underlying operating system kernel must be in FIPS mode. Information about setting up RHEL 8.x in Federal Information Processing Standard (FIPS) mode can be found in the Red Hat Security Guide in Chapter 2. You can only deploy a new, unprivileged instance of Splunk SOAR (On-premises) in FIPS-compliant mode. This choice cannot be undone and cannot be changed after deployment. |
See also
- Administer in the Administer manual to learn more about settings and user management.
- About in Use .
| Get |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.3.0, 6.3.1
Download manual
Feedback submitted, thanks!