<?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 Re: Securing Splunk HEC with LetsEncrypt in Security</title>
    <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518651#M11776</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/129407"&gt;@thambisetty&lt;/a&gt;&amp;nbsp;, this looks like a great reference! My question is if I can create this with the Let'sEncrypt generated certificates, that way my HEC will be trusted by everyone? I don't want to have to also manage certificates if possible.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Sep 2020 11:20:43 GMT</pubDate>
    <dc:creator>AxelPersinger</dc:creator>
    <dc:date>2020-09-09T11:20:43Z</dc:date>
    <item>
      <title>Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518582#M11774</link>
      <description>&lt;P&gt;Hi all! I'm trying to enable SSL for my HEC ingestor on a small, centralized Splunk Enterprise deployment. I used Let'sEncrypt to generate the certificates for the Splunk Web interface, as it's trusted by everyone. I'm tying to configure HEC to use the same certificates, but I'm having no luck in doing so. I tried following all the guides/questions on this board for securing HEC using certs, but I'm not sure which .pem files to use, if I have to encrypt them with an additional password, etc.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 01:15:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518582#M11774</guid>
      <dc:creator>AxelPersinger</dc:creator>
      <dc:date>2020-09-09T01:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518600#M11775</link>
      <description>&lt;P&gt;Splunk web doesn't support CSR which is signed with secret key (secret should be removed from key before creating CSR), you might have signed CSR without secret key.&amp;nbsp;&lt;/P&gt;&lt;P&gt;where as HEC requires key. to create cert follow below thread: and follow steps used to create server cert:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Security/Tcp-data-input-and-ssl/m-p/518529#M11769" target="_blank"&gt;https://community.splunk.com/t5/Security/Tcp-data-input-and-ssl/m-p/518529#M11769&lt;/A&gt;&lt;/P&gt;&lt;P&gt;you should follow below create pem file ( this is also there in the above thread)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;server.pem: is combination of below

server_signed_cert.pem
server.key
internmediate.pem (if any)
root.pem&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf for hec:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[http]
enableSSL=1
disabled=0
serverCert = $path/server.pem
sslPassword= passwordwhichisusedwhilecreatingprivatekey&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 09 Sep 2020 06:10:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518600#M11775</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-09T06:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518651#M11776</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/129407"&gt;@thambisetty&lt;/a&gt;&amp;nbsp;, this looks like a great reference! My question is if I can create this with the Let'sEncrypt generated certificates, that way my HEC will be trusted by everyone? I don't want to have to also manage certificates if possible.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 11:20:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518651#M11776</guid>
      <dc:creator>AxelPersinger</dc:creator>
      <dc:date>2020-09-09T11:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518654#M11777</link>
      <description>&lt;P&gt;I got it to work with LetsEncrypt!&amp;nbsp;&lt;/P&gt;&lt;P&gt;From inside the LetsEncrypt directory (probably something like &lt;FONT face="courier new,courier"&gt;/etc/letsencrypt/live/&amp;lt;site&amp;gt;/&lt;/FONT&gt;)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;openssl pkcs8 -topk8 -inform PEM -outform PEM -in privkey.pem -out privkey.enc.pem # Will prompt for password

cat cert.pem &amp;gt;&amp;gt; hec.pem

cat privkey.enc.pem &amp;gt;&amp;gt; hec.pem

cat chain.pem &amp;gt;&amp;gt; hec.pem&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then copy the &lt;FONT face="courier new,courier"&gt;hec.pem&lt;/FONT&gt; to your desired location, and change the &lt;FONT face="courier new,courier"&gt;inputs.conf&lt;/FONT&gt; like you said earlier!&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 11:44:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518654#M11777</guid>
      <dc:creator>AxelPersinger</dc:creator>
      <dc:date>2020-09-09T11:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518657#M11778</link>
      <description>&lt;P&gt;fantastic. I was checking on let's encrypt to provide guide on how you can sign your own CSR.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 12:00:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518657#M11778</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-09T12:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Splunk HEC with LetsEncrypt</title>
      <link>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518658#M11779</link>
      <description>&lt;P&gt;fantastic, I was checking how you can sign your own CSR in let's encrypt so that you will only have private key.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 12:02:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Securing-Splunk-HEC-with-LetsEncrypt/m-p/518658#M11779</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-09T12:02:43Z</dc:date>
    </item>
  </channel>
</rss>

