<?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 Why does VA scan identify that Splunk uses default certificate on port 8089? in Security</title>
    <link>https://community.splunk.com/t5/Security/Why-does-VA-scan-identify-that-Splunk-uses-default-certificate/m-p/609756#M16286</link>
    <description>&lt;P&gt;Hello folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our Nessus scanner detects that Splunk servers are using default certificate on port 8089. Basically it tells the SSL certificate for this service is for a different host.&lt;/P&gt;
&lt;P&gt;I have tried to update server.conf file with proper SSL certificate, but it still the same.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kvm_0-1660716305780.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/21064i881D026EF9081800/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kvm_0-1660716305780.png" alt="kvm_0-1660716305780.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have anyone come across this and have a workaround available for this issue?&lt;/P&gt;</description>
    <pubDate>Wed, 17 Aug 2022 14:40:35 GMT</pubDate>
    <dc:creator>kvm</dc:creator>
    <dc:date>2022-08-17T14:40:35Z</dc:date>
    <item>
      <title>Why does VA scan identify that Splunk uses default certificate on port 8089?</title>
      <link>https://community.splunk.com/t5/Security/Why-does-VA-scan-identify-that-Splunk-uses-default-certificate/m-p/609756#M16286</link>
      <description>&lt;P&gt;Hello folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our Nessus scanner detects that Splunk servers are using default certificate on port 8089. Basically it tells the SSL certificate for this service is for a different host.&lt;/P&gt;
&lt;P&gt;I have tried to update server.conf file with proper SSL certificate, but it still the same.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kvm_0-1660716305780.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/21064i881D026EF9081800/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kvm_0-1660716305780.png" alt="kvm_0-1660716305780.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have anyone come across this and have a workaround available for this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 14:40:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Why-does-VA-scan-identify-that-Splunk-uses-default-certificate/m-p/609756#M16286</guid>
      <dc:creator>kvm</dc:creator>
      <dc:date>2022-08-17T14:40:35Z</dc:date>
    </item>
  </channel>
</rss>

