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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...