All of our Splunk infrastructure utilises our in house PKI for Splunk to Splunk communication. Moving forward can we force the use of TLS v1.2?
I know about supportSSLV3Only = true/false
SSLV3 is getting old and obsolete . Please don't comment regarding SSLv3 is fine the question is in regards to TLS v1.2 and future proofing.
Perhaps it's on the road map for future versions of Splunk?
I suspect your question may have been pre-dated 6.1.5, but you can select tls1.2 as the sslVersion in the inputconf.
* Comma-separated list of SSL versions to support
* The versions available are "ssl2", "ssl3", "tls1.0", "tls1.1", and "tls1.2"
* The special version "" selects all supported versions. The version "tls"
selects all versions tls1.0 or newer
* If a version is prefixed with "-" it is removed from the list
* When configured in FIPS mode ssl2 and ssl3 are always disabled regardless of this configuration
* Defaults to ",-ssl2". (anything newer than SSLv2)
Just an FYI, as of PCI DSS 3.1, if your Splunk installation is in scope (and it probably is if you're forwarding logs from in-scope systems), you're required to use TLS 1.2 only.
I changed these settings ages ago, but my Security department wouldn't believe that it was disabled without proof.
I ran an openssl command from a forwarder to test:
openssl sclient -connect splunk-index-dev-01.example.com:9997 -tls12
and it worked as expected, giving me standard connection info.
Then I ran the same command for ssl3, and it gave me the same connection info:
openssl s_client -connect splunk-index-dev-01.example.com:9997 -ssl3
Doing the same command with ssl2 on the end showed that it was not enabled for ssl2.
I doublechecked my settings, and I had sslVersions = tls1.2 set in server.conf on the indexer and outputs.conf on the forwarder, and there was no change.
After a great deal of back-and-forth with Splunk tech support, we figured out that we needed to set sslVersions = tls1.2 in inputs.conf on the indexer, and nothing in the forwarder, not in outputs.conf, not in server.conf, nowhere at all on the forwarder, and also take it out of server.conf on the indexer.