<?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 What should I enable in the firewall to allow communication collector-SplunkServer in Security</title>
    <link>https://community.splunk.com/t5/Security/What-should-I-enable-in-the-firewall-to-allow-communication/m-p/421728#M13271</link>
    <description>&lt;P&gt;Hi team!&lt;/P&gt;

&lt;P&gt;What ports do I need to open and in what direction, I do not know if I leave any.&lt;/P&gt;

&lt;P&gt;Is there any communications table?&lt;/P&gt;

&lt;P&gt;Thank you a lot.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Mar 2019 10:53:48 GMT</pubDate>
    <dc:creator>christianubeda</dc:creator>
    <dc:date>2019-03-05T10:53:48Z</dc:date>
    <item>
      <title>What should I enable in the firewall to allow communication collector-SplunkServer</title>
      <link>https://community.splunk.com/t5/Security/What-should-I-enable-in-the-firewall-to-allow-communication/m-p/421728#M13271</link>
      <description>&lt;P&gt;Hi team!&lt;/P&gt;

&lt;P&gt;What ports do I need to open and in what direction, I do not know if I leave any.&lt;/P&gt;

&lt;P&gt;Is there any communications table?&lt;/P&gt;

&lt;P&gt;Thank you a lot.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 10:53:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-should-I-enable-in-the-firewall-to-allow-communication/m-p/421728#M13271</guid>
      <dc:creator>christianubeda</dc:creator>
      <dc:date>2019-03-05T10:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: What should I enable in the firewall to allow communication collector-SplunkServer</title>
      <link>https://community.splunk.com/t5/Security/What-should-I-enable-in-the-firewall-to-allow-communication/m-p/421729#M13272</link>
      <description>&lt;P&gt;Splunk does not dictate which ports event forwarding uses, however there is a 'convention'.&lt;BR /&gt;
Splunk management port defaults to 8089, but this also is configurable.&lt;/P&gt;

&lt;P&gt;As a basic start (and using defaults) the following should allow your Universal Forwarders to communicate with a deployment server and forward events to indexers/intermediate tiers.&lt;/P&gt;

&lt;P&gt;UF -&amp;gt; Splunk TCP:9997 (unencrypted event forwarding)&lt;BR /&gt;
UF -&amp;gt; Splunk TCP:9998 (TLS encrypted event forwarding)&lt;BR /&gt;
UF -&amp;gt; Deployment Server TCP:8089 (TLS)&lt;/P&gt;

&lt;P&gt;There is a great post with diagrams here which does an awesome job of illustrating all the communications ports&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/58888/what-are-the-ports-that-i-need-to-open.html"&gt;https://answers.splunk.com/answers/58888/what-are-the-ports-that-i-need-to-open.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 11:00:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-should-I-enable-in-the-firewall-to-allow-communication/m-p/421729#M13272</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2019-03-05T11:00:05Z</dc:date>
    </item>
  </channel>
</rss>

