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:
Install as an unprivileged user
Tar file distributions of are available for installations where runs as an unprivileged user.
If you install a stand-alone instance as an unprivileged user, underlying services such as the PostgreSQL database are installed in the user space for that user.
Prerequisites
Contact support to get this installation file.
Supported Operating Systems for this method:
- Red Hat Enterprise Linux 7.6 through 7.9.
- CentOS 7.6 through 7.9.
Federal Information Processing Standard (FIPS) support
can be deployed in a FIPS compliant mode, if the operating system kernel is in FIPS mode.
- Your operating system, either RHEL or CentOS must be in FIPS mode.
- You must create a new, unprivileged deployment of , either as a single instance or as a cluster.
Information about setting up RHEL 7.x or CentOS 7.x in Federal Information Processing Standard (FIPS) mode can be found in the Red Hat Security Guide in Chapter 9.
Prepare the system
Before you install as an unprivileged user, the root user or a user with sudo access must prepare the system.
Do all these tasks with root permissions, either by logging in as root or as a user with sudo permission.
Install the operating system dependencies
- Edit
/etc/selinux/config
to disable SELinux. Enabling SELinux is not officially supported. Change theSELINUX=
entry to:SELINUX=disabled
- Clear yum caches.
yum clean all
- Update installed packages.
yum update
- Restart the operating system.
shutdown -r now
- Install dependencies.
yum install -y libevent libicu c-ares bind-utils java-1.8.0-openjdk-headless mailcap fontconfig ntpdate perl rsync xmlsec1 xmlsec1-openssl libxslt ntp zip net-tools policycoreutils-python libxml2 libcurl gnutls
- If you are using an external file share using GlusterFS, download the GlusterFS packages.
mkdir gfinstall cd gfsinstall curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-api-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-cli-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-client-xlators-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-coreutils-0.2.0-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-devel-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-events-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-fuse-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-libs-7.5-1.el7.x86_64.rpm curl -O https://repo.phantom.us/phantom/5.2/base/7/x86_64/glusterfs-server-7.5-1.el7.x86_64.rpm
- If you are using an external file share using GlusterFS, install the GlusterFS packages.
yum install *.rpm
- Set firewall rules to allow the required ports listed in required ports.
- Synchronize the system clock.
ntpdate -v -u 0.centos.pool.ntp.org systemctl enable ntpd
Create the user account that will run
An unprivileged install of will run in the user space of a specific user.
When you create the user account that will run Splunk SOAR (On-premises), do not use special characters other than a hyphen or underscore. A hyphen or underscore must not be the first character in the username. Other special characters are not supported.
- Create the user account that will be used to run .
adduser -c "Splunk SOAR User" <username> passwd <username>
- Create a directory for .
su - <username> -c "mkdir /home/<username>/<directory_name>"
- Create a file called
/etc/security/limits.d/25-phantom-limits.conf
. This file sets resource limits for the user that will run .touch /etc/security/limits.d/25-phantom-limits.conf - Edit the file /etc/security/limits.d/25-phantom-limits.conf to add these settings:
<username> hard nofile 64000 <username> soft nofile 64000 <username> hard nproc 64000 <username> soft nproc 64000
- Save the file.
- Apply the new security settings.
sysctl --system
Install from the tar file
- Log in as the user that will run . Do not perform these steps as the root user.
- Copy the installation tar file to the directory /home/<username>/<directory_name> created earlier.
- Verify your downloaded file's SHA256 hash against the SHA256 hash displayed on the Community site.
sha256sum phantom-<version>.tgz
- Extract the tar file. tar -xvzf phantom-<version>.tgz
- Copy the new kernel settings file 50-phantom.conf from the the extracted files to /etc/sysctl.d. This step requires sudo permissions. cp /home/<username>/<directory_name>/etc/sysctl.d/50-phantom.conf /etc/sysctl.d/
- Apply the new kernel settings. This step requires sudo permissions. sysctl --system
- Run the installation script. Make sure to specify the ports for to use for HTTPS traffic. The HTTPS port cannot be a port which is already in use. This port must be a port greater than 1023. ./phantom_tar_install.sh install --https-port=<port>
For more installation command line options, see phantom_tar_install.sh options.
Next step: log in to verify the installation
You can log in to the web interface after the setup script completes to configure user accounts and additional settings. See Log in to the web interface.
Install on a system with limited internet access | Log in to the web interface |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.2.1
Feedback submitted, thanks!