Splunk® Enterprise

Securing Splunk Enterprise

Download manual as PDF

Splunk Enterprise version 5.0 reached its End of Life on December 1, 2017. Please see the migration information.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Configure Splunk forwarding to use the default certificate

The default root certificate that ships with Splunk is the same root certificate in every download. That means that anyone who has downloaded Splunk has server certificates that have been signed by the same root certificate and would be able to authenticate to your certificates. To ensure that no one can easily snoop on your traffic or wrongfully send data to your indexers, we recommend that you replace them with signed certificates.

Important: The default certificates are set to expire three years after they are generated. For any version prior to 6.3, your default certificates must immediately be replaced.

To configure your forwarders to use certificates signed by your own root CA or a third-party CA see "Configure Splunk forwarding to use your own certificates."

In this topic we describe how to:

  • Configure the indexer to use the default certificates that ship with Splunk
  • Configure the forwarder to use the default certificates that ship with Splunk

Note: When configuring multiple forwarders, configure each forwarder to use the default certificate separately.

Set up the indexer to use the default server certificate

1. In $SPLUNK_HOME/etc/system/local/inputs.conf (or the appropriate directory of any app you are using to distribute your forwarding configuration), set up the following stanzas:

For this example, we are using port 9997 to receive data from forwarders.

[SSL]
rootCA = $SPLUNK_HOME/etc/auth/cacert.pem
serverCert = $SPLUNK_HOME/etc/auth/server.pem
password = password

[splunktcp-ssl:9997]
disabled=0

Where rootCA is the path to the CA public key and serverCert is the path to the default server certificate.

The default certificate can be found at $SPLUNK_HOME/etc/auth/server.pem.

Note: When using the default certificate it is not necessary to set requireClientCert = true since we do not need to check the validity of the default server certificate.

2. Restart splunkd:

$SPLUNK_HOME/bin/splunk restart splunkd

Configure the forwarder

Set up your forwarder to use the same default certificates as your indexer and configure the forwarder to send data to the configured listening port.

In the following example, the indexer IP address is 10.1.12.112.

1. Define the following stanzas in $SPLUNK_HOME/etc/system/local/outputs.conf (or in the appropriate directory of any app you are using to distribute your forwarding configuration):

[tcpout]
defaultGroup = splunkssl
[tcpout:splunkssl]
server = 10.1.12.112:9997
sslVerifyServerCert = false
sslRootCAPath = $SPLUNK_HOME/etc/auth/cacert.pem
sslCertPath = $SPLUNK_HOME/etc/auth/server.pem
sslPassword = password

Where rootCA is the path to the CA public key and serverCert is the path to the default server certificate.

Note again that you do not need to set sslVerifyServerCert = true. It is not necessary to ask the forwarders to check the validity of the default server certificate.

2. Restart splunkd:

# $SPLUNK_HOME/bin/splunk restart splunkd

Next steps

Next, you should check your connection to make sure your configuration works. See "Validate your configuration" for more information.

PREVIOUS
About securing data from forwarders
  NEXT
Configure Splunk forwarding to use your own certificates

This documentation applies to the following versions of Splunk® Enterprise: 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.14, 5.0.15, 5.0.16, 5.0.17, 5.0.18, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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