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.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...