How can Splunk SOAR (On-premises) be installed?

Installing Splunk SOAR (On-premises) is the first step to realizing gains from security orchestration and automation. Splunk SOAR (On-premises) 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 Splunk SOAR (On-premises), this guide will help you understand how to get Splunk SOAR (On-premises), the system requirements for installing Splunk SOAR (On-premises), how to install Splunk SOAR (On-premises), as well as clustering, advanced setup, and upgrading Splunk SOAR (On-premises).

You can install Splunk SOAR (On-premises) in the following ways:

• Install Splunk SOAR (On-premises) using the Amazon Marketplace Image
• Install Splunk SOAR (On-premises) as an unprivileged user

There are several options to choose from when you deploy Splunk SOAR (On-premises). Work with your Splunk SOAR (On-premises) 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 Splunk SOAR (On-premises) clusters. Then follow the instructions in Create a Splunk SOAR (On-premises) cluster using an unprivileged installation
SOAR instance with one or more external services	Your Splunk SOAR (On-premises) 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. Set up an external PostgreSQL server Set up external file shares using GlusterFS Set up a load balancer with an HAProxy server Set up Splunk Enterprise
SOAR instance with Federal Information Processing Standard (FIPS) support	A new, unprivileged deployment of Splunk SOAR (On-premises) 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. Federal Standards and Regulations. 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 Splunk SOAR (On-premises) in the Administer Splunk SOAR (On-premises) manual to learn more about settings and user management.
• About Splunk SOAR (On-premises) in Use Splunk SOAR (On-premises).