<?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: Splunk Certificate 8089 Port in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508563#M2557</link>
    <description>What problem are you trying to solve?&lt;BR /&gt;What "vulnerability" are you talking about?&lt;BR /&gt;Port 8089 is not "SplunkWeb". It's the Splunk management port used by Splunk instances to talk to each other. Change the security on that post and you could break your Splunk installation.&lt;BR /&gt;"SplunkWeb" is port 8000.</description>
    <pubDate>Sat, 11 Jul 2020 00:27:10 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-07-11T00:27:10Z</dc:date>
    <item>
      <title>Splunk Certificate 8089 Port</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508551#M2554</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I'm trying to install a web certificate for port 8089, I don't know what I'm doing wrong.&lt;BR /&gt;There are already 3 scans and the vulnerability continues to appear.&lt;/P&gt;&lt;P&gt;Someone who has already solved it&lt;/P&gt;&lt;P&gt;This is the stanza I have in the web.conf file&lt;/P&gt;&lt;P&gt;[settings]&lt;BR /&gt;enableSplunkWebSSL = true&lt;BR /&gt;privKeyPath = /opt/splunk/etc/auth/mycerts/certificate.key&lt;BR /&gt;serverCert = /opt/splunk/etc/auth/mycerts/certificate.pem&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jul 2020 22:11:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508551#M2554</guid>
      <dc:creator>edgarsilva01</dc:creator>
      <dc:date>2020-07-10T22:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Certificate 8089 Port</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508563#M2557</link>
      <description>What problem are you trying to solve?&lt;BR /&gt;What "vulnerability" are you talking about?&lt;BR /&gt;Port 8089 is not "SplunkWeb". It's the Splunk management port used by Splunk instances to talk to each other. Change the security on that post and you could break your Splunk installation.&lt;BR /&gt;"SplunkWeb" is port 8000.</description>
      <pubDate>Sat, 11 Jul 2020 00:27:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508563#M2557</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-07-11T00:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Certificate 8089 Port</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508579#M2558</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;richgalloway&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The problem I have is that a scan was performed to one of the servers where a universal forwarder is installed and a vulnerability in port 8089 of the splunk service was detected.&lt;/P&gt;&lt;P&gt;To solve this problem, a digital certificate was requested, upload it to the deployment server, in a second scan the vulnerability is still active&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jul 2020 04:53:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508579#M2558</guid>
      <dc:creator>edgarsilva01</dc:creator>
      <dc:date>2020-07-11T04:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Certificate 8089 Port</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508609#M2560</link>
      <description>You don't say what vulnerability was reported, but perhaps this answer will solve your problem: &lt;A href="https://community.splunk.com/t5/Security/Splunk-Enterprise-8089-Vulnerability-Scan-Results-Resolve-these/td-p/493478" target="_blank"&gt;https://community.splunk.com/t5/Security/Splunk-Enterprise-8089-Vulnerability-Scan-Results-Resolve-these/td-p/493478&lt;/A&gt;&lt;BR /&gt;It's not enough to put a certificate on the DS - it must be installed on the UF to protect the UF's management port.</description>
      <pubDate>Sat, 11 Jul 2020 12:39:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Certificate-8089-Port/m-p/508609#M2560</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-07-11T12:39:48Z</dc:date>
    </item>
  </channel>
</rss>

