Splunk® Enterprise Security

Install and Upgrade Splunk Enterprise Security

The documentation for Splunk Enterprise Security versions 8.0 and higher have been rearchitected from previous versions, causing some links to have redirect errors. For documentation on version 8.0, see Splunk Enterprise Security documentation homepage.
This documentation does not apply to the most recent version of Splunk® Enterprise Security. For documentation on the most recent version, go to the latest release.

Install Splunk Enterprise Security

Install Splunk Enterprise Security on an on-premises search head. Splunk Cloud Platform customers must work with Splunk Support to coordinate access to the Enterprise Security search head.

Splunk Enterprise platform considerations

Splunk Enterprise 7.2.0 uses Serialized Result Set (SRS) format by default. The exception is in searches that execute actions, for which we auto-detect whether to use CSV or SRS. This is handled in the alert_actions.conf file, but do not modify the forceCsvResults stanza without a thorough understanding of scripts or processes that access the results files directly.

A new install_apps capability is introduced in Splunk Enterprise v8. The change impacts the existing Enterprise Security edit_local_apps capability's functionality to install and upgrade apps. In ES, enable_install_apps is false by default. If you set enable_install_apps=True and you don't have the new install_apps and existing edit_local_apps capabilities, you will not be able to install and setup apps. This includes performing ES setup and installing other content packs or Technology Add-ons.

On the standalone search head or search peers and indexers, configure the setting enforce_auto_lookup_order = true in the [lookup] stanza of the limits.conf configuration file so that the lookup names in the props.conf file are looked up in ASCII order by name. For more information, see limits.conf configuration file in the Splunk Enterprise Administrator Manual.

Installation prerequisites

  • Review the Splunk platform requirements for Splunk Enterprise Security. See Deployment planning.
  • If a deployment server manages any of the apps or add-ons included with Splunk Enterprise Security, remove the deploymentclient.conf file that contains references to the deployment server and restart Splunk services. If you do not do this, the installation will not complete.
  • Your user account must have the admin role and the edit_local_apps capability. The admin role is assigned that capability by default.
  • Approximately 3 GB of free space is required in the /tmp/ directory for the installation or upgrade to complete. When installing or upgrading an app through either the CLI or Splunk Web UI, the /tmp/ directory is utilized during the process.

Step 1. Download Splunk Enterprise Security

  1. Log in to splunk.com with your Splunk.com user name and password.
  2. Download the latest Splunk Enterprise Security product.
  3. Click Download and save the Splunk Enterprise Security product file to your desktop.
  4. Log in to the search head as an administrator.

For more information on Splunk Enterprise Security licensing, see Licensing for Splunk Enterprise Security in the Use Splunk Enterprise Security manual.

Step 2. Install Splunk Enterprise Security

The installer dynamically detects if you're installing in a single search head environment or search head cluster environment. The installer is also bigger than the default upload limit for Splunk Web.

  1. Increase the Splunk Web upload limit to at least 2 GB by creating a file called $SPLUNK_HOME/etc/system/local/web.conf with the following stanza.
    [settings]
    max_upload_size = 2048
  2. To restart Splunk from the Splunk toolbar, select Settings > Server controls and click Restart Splunk.
  3. On the Splunk toolbar, select Apps > Manage Apps and click Install App from File.
  4. Click Choose File and select the Splunk Enterprise Security product file.
  5. Click Upload to begin the installation.
  6. Click Set up now to start setting up Splunk Enterprise Security

There are a few differences after installing on a deployer in a SHC environment. See Install Splunk Enterprise Security in a search head cluster environment.

Step 3. Set up Splunk Enterprise Security

Set up Splunk Enterprise Security in a single search head environment.

  1. Click Start.
  2. If you are not using Secure Sockets Layer (SSL) in your environment, do one of the following steps when you see the SSL Warning message:
    1. Click Enable SSL to turn on SSL and start using https:// for encrypted data transfer.
    2. Click Do Not Enable SSL to keep SSL turned off and continue using http:// for data transfer.
  3. The Splunk Enterprise Security Post-Install Configuration page indicates the status as it moves through the stages of installation.
  4. Choose to exclude selected add-ons from being installed, or install and disable them. When the setup is done, the page prompts you to restart Splunk platform services.
  5. If prompted to do so, click Restart Splunk to finish the installation.

If you enable SSL, you must change the Splunk Web URL to use https to access the search head after installing ES.

After the installation completes, review the installation log in: $SPLUNK_HOME/var/log/splunk/essinstaller2.log.

Step 4. Configure Splunk Enterprise Security

To continue configuring Splunk Enterprise Security, see the following:

  1. Deploy add-ons included with Splunk Enterprise Security
  2. Configure and deploy Indexes
  3. Configure users and roles
  4. Configure data models

For an overview of the data sources and collection considerations for Enterprise Security, see Data source planning.

Install Splunk Enterprise Security from the command line

Install Splunk Enterprise Security using the Splunk software command line. See About the CLI for more about the Splunk software command line.

  1. Follow Step 1: Download Splunk Enterprise Security to download Splunk Enterprise Security and place it on the search head.
  2. Start the installation process on the search head. Install with the ./splunk install app <filename> command or perform a REST call to start the installation from the server command line.
    For example:
    curl -k -u admin:password https://localhost:8089/services/apps/local -d filename="true" -d name="<file name and directory>" -d update="true" -v 

    Using the -d option in the command might cause errors in case of a new installation of Splunk Enterprise Security.

    For information on upgrading Splunk Enterprise Security, see Upgrade Splunk Enterprise Security. You can upgrade the Splunk Enterprise Security app on the CLI using the same process as other Splunk apps or add-ons. For information on upgrading Splunk platform apps, see Manage apps and add-ons. After the Splunk Enterprise Security app is installed, run the essinstall command with the appropriate flags as shown in the next step.

  3. On the search head, use the Splunk software command line to run the following command:
    splunk search '| essinstall' -auth admin:password

    You can also run this search command from Splunk Web and view the installation progress as search results.

    | essinstall

    When installing from the command line, ssl_enablement defaults to "strict." If you don't have SSL enabled, the installer will exit with an error.

    If you run the search command to install Enterprise Security in Splunk Web, you can review the progress of the installation as search results. If you run the search command from the command line, you can review the installation log in: $SPLUNK_HOME/var/log/splunk/essinstaller2.log.

Test installation and setup of Splunk Enterprise Security

Follow these steps to test the installation and setup of Splunk Enterprise Security:

  1. Follow Step 1: Download Splunk Enterprise Security to download Splunk Enterprise Security and place it on the search head.
  2. Start the installation process on the search head. Install with the ./splunk install app <filename> command or perform a REST call to start the installation from the server command line.
    For example:
    curl -k -u admin:password https://localhost:8089/services/apps/local -d filename="true" -d name="<file name and directory>" -d update="true" -v
  3. From Splunk Web, open the Search and Reporting app.
  4. Type the following search to perform a dry run of the installation and setup.

    |essinstall --dry-run

Uninstall Splunk Enterprise Security

You can uninstall the Splunk ES app by removing the Splunk Enterprise Security Suite from the $SPLUNK_HOME/etc/apps folder by recursively deleting the directory or moving it to $SPLUNK_HOME/etc/disabled-apps and restarting Splunk. When you restart Splunk, the KV Store data is also removed. You can temporarily test the uninstallation of the Splunk ES app by moving the Splunk Enterprise Security Suite to the disabled-apps folder and then move it back.

ES is a collection of apps, so removing a single app folder will not uninstall it. You need to remove or move all applicable apps in the Splunk Enterprise Security Suite.

Last modified on 22 May, 2023
Data source planning for Splunk Enterprise Security   Install Splunk Enterprise Security in a search head cluster environment

This documentation applies to the following versions of Splunk® Enterprise Security: 7.0.1, 7.0.2, 7.1.0, 7.1.1, 7.1.2, 7.2.0, 7.3.0, 7.3.1, 7.3.2


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters