← Back to Splunk Enterprise 7.x for Windows Security Technical Implementation Guide

V-221600

CAT I (High)

Splunk Enterprise must be installed with FIPS mode enabled, to implement NIST FIPS 140-2 approved ciphers for all cryptographic functions.

Rule ID

SV-221600r961857_rule

STIG

Splunk Enterprise 7.x for Windows Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-002450

Discussion

FIPS 140-2 precludes the use of unvalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as providing no protection to the information or data. In effect, the data would be considered unprotected plaintext. If the agency specifies that the information or data be cryptographically protected, then FIPS 140-2 is applicable. In essence, if cryptography is required, it must be validated. Cryptographic modules that have been approved for classified use may be used in lieu of modules that have been validated against the FIPS 140-2 standard.

Check Content

Select the Search and Reporting App.

Execute a search query using the following:

| rest splunk_server=local /services/server/info | fields fips_mode

Verify that the report returns fips_mode = 1.

If the query returns 0, this is a finding.

Fix Text

FIPS 140-2 mode MUST be enabled during installation. If not enabled, it requires a reinstall or upgrade of the application.

The installer must be executed from the command line so that it can be passed the LAUNCHSPLUNK=0 parameter.

This allows Splunk to install and not automatically start up after install.

Example: msiexec /i <splunkinstaller.msi> LAUNCHSPLUNK=0

Using a text editor, edit $SPLUNK_HOME/etc/splunk-launch.conf file, add the line SPLUNK_FIPS=1 to it, restart the server, and then recheck this requirement.