Splunk® Enterprise

Securing the Splunk Platform

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Configure Splunk forwarding to use the default certificate

The default root certificate that ships with Splunk software is the same root certificate in every download. Splunk software uses these certificates by default. You do not need to configure them unless they have been removed or corrupted.

Default certificates are not considered highly secure. Anyone who has downloaded Splunk Enterprise has server certificates signed by the same root certificate and are able to authenticate to your certificates. To ensure that no one can easily snoop on your traffic or wrongfully send data to your indexers, replace the default certificates with certificates that you sign.

The default certificates expire three years after their generation and you must then create and configure new certificates using one of the methods described in Appendix A of this manual.

To configure your forwarders to use certificates that you have signed with your own root certificate authority (CA) or through a third-party CA, see Configure Splunk forwarding to use your own certificates.

Procedure for configuring Splunk forwarders to use the default certificates that come with Splunk software

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

Set up the indexer to use the default server certificate

  1. In the $SPLUNK_HOME/etc/system/local/inputs.conf configuration file (or the appropriate directory of any app you are using to distribute your forwarding configuration), set up the following stanzas:
    [splunktcp-ssl:9997]
    disabled = 0
    
    [SSL]
    serverCert = Absolute path to the certificate. The default certificate is $SPLUNK_HOME/etc/auth/server.pem<br>
    sslPassword = password
    requireClientCert=false (There is no need validate the default server certificate)<br>
    
  2. (Not required on Windows) In the $SPLUNK_HOME/etc/system/local/server.conf file, add the following:
    [sslConfig]
    
    sslRootCAPath = /opt/splunk/etc/auth/cacert.pem
    
  3. Restart the splunkd process on the indexer:
    $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.

  1. Define the following stanzas in the $SPLUNK_HOME/etc/system/local/outputs.conf configuration file (or in the appropriate directory of any app you are using to distribute your forwarding configuration):
    [tcpout:group1]
    
    server = 10.1.12.112:9997
    
    clientCert = $SPLUNK_HOME/etc/auth/server.pem
    
    sslPassword = password
    
    sslVerifyServerCert = false
    
  2. In the $SPLUNK_HOME/etc/system/local/server.conf file, add the following:
    Linux:
    [sslConfig]
    
    sslRootCAPath = /opt/splunkforwarder/etc/auth/cacert.pem
    

    Windows:

    [sslConfig]
    
    caCertFile = cacert.pem
    caPath = $SPLUNK_HOME\etc\auth
    
  3. Restart the forwarder:
    # $SPLUNK_HOME/bin/splunk restart splunkd

Next steps

Check the connection between the forwarder and the indexer to confirm that the configuration works. See "Validate your configuration" for more information.

Last modified on 19 December, 2020
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: 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.2.0, 8.2.1


Was this documentation topic helpful?

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