<?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: DOS traffic from External IP going port 18264 (Implied Rule) in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/230973#M44479</link>
    <description>&lt;P&gt;Quoting from&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk52421" target="_self"&gt;sk52421&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE id="filterportTable" border="1" width="100%" cellspacing="2" cellpadding="4"&gt;
&lt;TBODY&gt;
&lt;TR class="SubTitle" bgcolor="#d6dff0"&gt;
&lt;TD width="10%"&gt;&lt;STRONG&gt;Protocol&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="10%"&gt;&lt;STRONG&gt;Port number&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="30%"&gt;&lt;STRONG&gt;Service Name and Comment&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="50%"&gt;&lt;STRONG&gt;Usage&lt;/STRONG&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR class="SubTitle" align="center" bgcolor="#d6dff0"&gt;
&lt;TD colspan="4"&gt;Infrastructure&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;TCP&lt;/TD&gt;
&lt;TD&gt;18264&lt;/TD&gt;
&lt;TD&gt;&lt;EM&gt;FW1_ica_services&lt;/EM&gt;&amp;nbsp;- Check Point Internal CA Fetch CRL and User Registration Services&lt;/TD&gt;
&lt;TD&gt;Connections to Management Server for Certificate Revocation Lists (CRLs) and registering users when using the Endpoint Policy Server (for Endpoint Security clients)&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See what which destinations are listed for this traffic. In a large environment, with many endpoint clients, it is possible that there is a lot of chatter on this port&lt;/P&gt;</description>
    <pubDate>Mon, 28 Oct 2024 12:29:41 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2024-10-28T12:29:41Z</dc:date>
    <item>
      <title>DOS traffic from External IP going port 18264 (Implied Rule)</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/230651#M44385</link>
      <description>&lt;P&gt;Hello Mates,&lt;/P&gt;&lt;P&gt;I'm new to Checkpoint, so please bear with me.&lt;/P&gt;&lt;P&gt;I noticed an alert for high traffic (potential DoS) in our SIEM coming from an external IP to our public-facing server via port 18264. I’m curious why this traffic is allowed. After some research, I found that this port might be governed by an implied rule, meaning the traffic is permitted by default, and some sources advise against blocking it.&lt;/P&gt;&lt;P&gt;My questions are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Could this traffic have any negative impact on our server?&lt;/LI&gt;&lt;LI&gt;Is port 18264 vulnerable to exploitation?&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 24 Oct 2024 02:30:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/230651#M44385</guid>
      <dc:creator>unavita</dc:creator>
      <dc:date>2024-10-24T02:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: DOS traffic from External IP going port 18264 (Implied Rule)</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/230973#M44479</link>
      <description>&lt;P&gt;Quoting from&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk52421" target="_self"&gt;sk52421&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE id="filterportTable" border="1" width="100%" cellspacing="2" cellpadding="4"&gt;
&lt;TBODY&gt;
&lt;TR class="SubTitle" bgcolor="#d6dff0"&gt;
&lt;TD width="10%"&gt;&lt;STRONG&gt;Protocol&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="10%"&gt;&lt;STRONG&gt;Port number&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="30%"&gt;&lt;STRONG&gt;Service Name and Comment&lt;/STRONG&gt;&lt;/TD&gt;
&lt;TD width="50%"&gt;&lt;STRONG&gt;Usage&lt;/STRONG&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR class="SubTitle" align="center" bgcolor="#d6dff0"&gt;
&lt;TD colspan="4"&gt;Infrastructure&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;TCP&lt;/TD&gt;
&lt;TD&gt;18264&lt;/TD&gt;
&lt;TD&gt;&lt;EM&gt;FW1_ica_services&lt;/EM&gt;&amp;nbsp;- Check Point Internal CA Fetch CRL and User Registration Services&lt;/TD&gt;
&lt;TD&gt;Connections to Management Server for Certificate Revocation Lists (CRLs) and registering users when using the Endpoint Policy Server (for Endpoint Security clients)&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See what which destinations are listed for this traffic. In a large environment, with many endpoint clients, it is possible that there is a lot of chatter on this port&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 12:29:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/230973#M44479</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-10-28T12:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: DOS traffic from External IP going port 18264 (Implied Rule)</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/231214#M44540</link>
      <description>&lt;P&gt;Thanks mate. Appriciate it.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 07:01:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DOS-traffic-from-External-IP-going-port-18264-Implied-Rule/m-p/231214#M44540</guid>
      <dc:creator>unavita</dc:creator>
      <dc:date>2024-10-30T07:01:33Z</dc:date>
    </item>
  </channel>
</rss>

