Getting Data In

Why do I receive SSL alert number 40 with selfsigned certificates?


Dear all,

We are on process of ingesting Check Point EDR logs in our Splunk Cloud Platform. This should be done through a Heavy Forwarder. Checkpoint sends encrypted data to HFW.

For that purpose, we used the following guide provided by CheckPoint for generating and configure the certificates which contains specific instructions for Splunk:

As summary, there are two certificates that needs to be configured on the Splunk side: 

- splunk.pem It is a combination of SyslogServer.crt + SyslogServer.key + RootCa.pem configured in /opt/splunk/etc/apps/CheckPointAPP/local/inputs.conf
- ca.pem configured in /opt/splunk/etc/system/local/server.conf

This configuration is not working because the certificate splunk.pem is giving a handshake error "SSL alert number 40".

The following setting in server.conf as the CheckPoint guide specifies, returns an error in Splunk: "Invalid key in stanza [SSL]".



cipherSuite = TLSv1+HIGH:TLSv1.2+HIGH:@STRENGTH


We also have tried with this configuration with the same result:






In Splunk internal wereceive the following error:


Received fatal SSL3 alert. ssl_state='SSLv3 read client certificate A', alert_description='unknown CA'.


Do you know which could be the point of failure? Why the certificate is returning an error 40 or if the configuration should be set in a different way?

Best regards

Tags (1)
0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...