<?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: Block unknown protocol in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86033#M11135</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Protocol signatures are used in part of PSL/PXL.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Packets may arrive out of order or may be legitimate retransmissions of packets that have not yet received an acknowledgment. In some cases a retransmission may also be a deliberate attempt to evade IPS detection by sending the malicious payload in the retransmission. Security Gateway ensures that only valid packets are allowed to proceed to destinations. It does this with Passive Streaming Library (PSL) technology.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you set the protocol it will be analyzed by PSL/PXL&amp;nbsp;to specify the protocol type such as http, ftp, imap, etc.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;More read here:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.checkpoint.com/t5/General-Topics/R80-x-Security-Gateway-Architecture-Content-Inspection/td-p/41665" target="_self"&gt;R80.x Security Gateway Architecture (Content Inspection)&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 22 May 2020 06:08:47 GMT</pubDate>
    <dc:creator>HeikoAnkenbrand</dc:creator>
    <dc:date>2020-05-22T06:08:47Z</dc:date>
    <item>
      <title>Block unknown protocol</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86002#M11133</link>
      <description>&lt;P&gt;Forgive me the probably idiotic question but what is the best way to block this:&lt;/P&gt;
&lt;DIV id="tinyMceEditorHristoGrigorov_1" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV id="tinyMceEditorHristoGrigorov_2" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="unknproto.PNG" style="width: 265px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6188i300FDA752E5C7395/image-size/large?v=v2&amp;amp;px=999" role="button" title="unknproto.PNG" alt="unknproto.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2020 15:51:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86002#M11133</guid>
      <dc:creator>HristoGrigorov</dc:creator>
      <dc:date>2020-05-21T15:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: Block unknown protocol</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86031#M11134</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Depending on the specifics you may wish to explore TCP service advanced options further e.g.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Protocol Signature&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;- A unique signature created by&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="Other_Varstp_cp"&gt;Check Point&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;for each protocol and stored on the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="Other_Varstp_gw"&gt;gateway&lt;/SPAN&gt;&lt;SPAN&gt;. The signature identifies the protocol as genuine. Select this option to limit the port to the specified protocol.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Refer:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/General-Topics/Protocol-Signatures/m-p/54945" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Protocol-Signatures/m-p/54945&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2020 05:44:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86031#M11134</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2020-05-22T05:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: Block unknown protocol</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86033#M11135</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Protocol signatures are used in part of PSL/PXL.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Packets may arrive out of order or may be legitimate retransmissions of packets that have not yet received an acknowledgment. In some cases a retransmission may also be a deliberate attempt to evade IPS detection by sending the malicious payload in the retransmission. Security Gateway ensures that only valid packets are allowed to proceed to destinations. It does this with Passive Streaming Library (PSL) technology.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you set the protocol it will be analyzed by PSL/PXL&amp;nbsp;to specify the protocol type such as http, ftp, imap, etc.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;More read here:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.checkpoint.com/t5/General-Topics/R80-x-Security-Gateway-Architecture-Content-Inspection/td-p/41665" target="_self"&gt;R80.x Security Gateway Architecture (Content Inspection)&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2020 06:08:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86033#M11135</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2020-05-22T06:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: Block unknown protocol</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86181#M11136</link>
      <description>What about using the Application Control signature "Unknown Traffic" in a drop rule?</description>
      <pubDate>Mon, 25 May 2020 04:33:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86181#M11136</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-05-25T04:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: Block unknown protocol</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86182#M11137</link>
      <description>&lt;P&gt;Yeah, I am sorry I forgot to follow up.&lt;/P&gt;
&lt;P&gt;I added both Unknown Traffic application signature and Unknown Traffic application category to a drop rule and that sorted out this issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you all for your recommendations.&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2020 04:39:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Block-unknown-protocol/m-p/86182#M11137</guid>
      <dc:creator>HristoGrigorov</dc:creator>
      <dc:date>2020-05-25T04:39:52Z</dc:date>
    </item>
  </channel>
</rss>

