<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic HEC Invalid SSL Certificate in Security</title>
    <link>https://community.splunk.com/t5/Security/HEC-Invalid-SSL-Certificate/m-p/383666#M9407</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;
I'm using Splunk Cloud with an HEC configured via Settings --&amp;gt; Data Inputs --&amp;gt; HTTP Event Collector&lt;BR /&gt;
I can submit an event via &lt;CODE&gt;curl&lt;/CODE&gt;, but when attempting to send via AWS Firehose, it fails with an SSL error.&lt;BR /&gt;
It appears that the SSL cert installed on the HEC is a self-signed certificate.&lt;/P&gt;

&lt;P&gt;How can I get the Splunk Cloud HEC configured with a valid cert?&lt;/P&gt;</description>
    <pubDate>Thu, 02 Aug 2018 19:34:15 GMT</pubDate>
    <dc:creator>aaptiv_engineer</dc:creator>
    <dc:date>2018-08-02T19:34:15Z</dc:date>
    <item>
      <title>HEC Invalid SSL Certificate</title>
      <link>https://community.splunk.com/t5/Security/HEC-Invalid-SSL-Certificate/m-p/383666#M9407</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
I'm using Splunk Cloud with an HEC configured via Settings --&amp;gt; Data Inputs --&amp;gt; HTTP Event Collector&lt;BR /&gt;
I can submit an event via &lt;CODE&gt;curl&lt;/CODE&gt;, but when attempting to send via AWS Firehose, it fails with an SSL error.&lt;BR /&gt;
It appears that the SSL cert installed on the HEC is a self-signed certificate.&lt;/P&gt;

&lt;P&gt;How can I get the Splunk Cloud HEC configured with a valid cert?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2018 19:34:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/HEC-Invalid-SSL-Certificate/m-p/383666#M9407</guid>
      <dc:creator>aaptiv_engineer</dc:creator>
      <dc:date>2018-08-02T19:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: HEC Invalid SSL Certificate</title>
      <link>https://community.splunk.com/t5/Security/HEC-Invalid-SSL-Certificate/m-p/383667#M9408</link>
      <description>&lt;P&gt;Hi, &lt;BR /&gt;
I would recomend you use a Heavy Forwarder as your HEC endpoint, then send your data on to the Splunk Cloud via normal forwarder method.&lt;BR /&gt;
A ticket would need to be raised with the Splunk Cloud team, to get the Certificate fixed.&lt;BR /&gt;
If you do this via a heavy forwarder,  look through this section of the manual  &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.2/Security/AboutsecuringyourSplunkconfigurationwithSSL"&gt;"AboutsecuringyourSplunkconfigurationwithSSL"&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
If you would like a good presentation to talk you through setting up, this is a simple guide around the SSL certificate. &lt;A href="https://conf.splunk.com/session/2015/conf2015_DWaddle_DefensePointSecurity_deploying_SplunkSSLBestPractices.pdf"&gt;Best Practices Configuration for Splunk SSL&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.2/Security/AboutsecuringyourSplunkconfigurationwithSSL"&gt;https://docs.splunk.com/Documentation/Splunk/7.1.2/Security/AboutsecuringyourSplunkconfigurationwithSSL&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://conf.splunk.com/session/2015/conf2015_DWaddle_DefensePointSecurity_deploying_SplunkSSLBestPractices.pdf"&gt;https://conf.splunk.com/session/2015/conf2015_DWaddle_DefensePointSecurity_deploying_SplunkSSLBestPractices.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 10:52:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/HEC-Invalid-SSL-Certificate/m-p/383667#M9408</guid>
      <dc:creator>Albakercss</dc:creator>
      <dc:date>2018-08-28T10:52:34Z</dc:date>
    </item>
  </channel>
</rss>

