Getting Data In

How to disable SSL 2.0 and 3.0. Use TLS 1.1 (with approved cipher suites) or higher instead.

sureshsala
Explorer

Description

The remote service accepts connections encrypted using SSL 2.0 and/or SSL 3.0. These versions of SSL are affected by several cryptographic flaws. An attacker can exploit these flaws to conduct man-in-the-middle attacks or to decrypt communications between the affected service and clients.

NIST has determined that SSL 3.0 is no longer acceptable for secure communications. As of the date of enforcement found in PCI DSS v3.1, any version of SSL will not meet the PCI SSC'S definition of 'strong cryptography'.

0 Karma

mtranchita
Communicator

It is configurable in multiple conf files.
for example in web.conf you can set cipherSuite and sslVersions in the [settings] stanza or sslCipher in outputs.conf.

You should review minimally:
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Serverconf
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Webconf
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Outputsconf

0 Karma

sureshsala
Explorer

I have added in inputs.conf and outputs.conf but still the same error.
[default]
sslVersions=tls1.2

0 Karma
Get Updates on the Splunk Community!

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...