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 in the following ways:
- Install using the Amazon Marketplace Image
- Install as a privileged user
- Install as an unprivileged user
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, privileged||Start with the clustering overview.
Then based on your chosen deployment type, use the specific documentation to build your cluster.
|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, a load balancer, or a Splunk Enterprise or Splunk Cloud deployment.
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 7.x or CentOS 7.x in Federal Information Processing Standard (FIPS) mode can be found on the Red Hat Security Guide in Chapter 9.
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.
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.1, 5.3.2, 5.3.3, 5.3.4