<?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 Enabling Protocol Signatures on a service: Does it affect Network Policies in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-Protocol-Signatures-on-a-service-Does-it-affect-Network/m-p/160425#M28276</link>
    <description>&lt;P&gt;Reading other community articles we got the impression enabling Protocol Signatures on a service will affect traffic going through Network Policy rules as well as in App Control rules.&lt;/P&gt;&lt;P&gt;We started to see strange things so I thought I would test in a lab.&lt;/P&gt;&lt;P&gt;I created a test using&lt;BR /&gt;1. The standard HTTPs service&lt;BR /&gt;2. Creating a new HTTPS service. TCP Port 443, HTTPs Protocol and enabled Protocol Signatures&lt;BR /&gt;3. Created an HTTP (not https) website listening on port 443.&lt;/P&gt;&lt;P&gt;Added 2 Network rules&lt;BR /&gt;1. Accept rule using custom HTTPs service with enabled Protocol Signatures.&lt;BR /&gt;2. Drop using the standard HTTPs service.&lt;/P&gt;&lt;P&gt;Test http traffic on port 443 is allowed on rule 1. i.e. using the custom HTTPS Service with enabled Protocol Signatures&lt;/P&gt;&lt;P&gt;Adding application control Rules&lt;BR /&gt;1. Accept rule using custom HTTPs service with enabled Protocol Signatures&lt;BR /&gt;2. Drop using the standard HTTPs service.&lt;/P&gt;&lt;P&gt;The traffic is dropped on Rule 2 bypassing rule 1 with the custom service.&lt;/P&gt;&lt;P&gt;Conclusions&lt;BR /&gt;The network rules only checked the port number and ignored Protocol Signatures.&lt;BR /&gt;In App Control the HTTP Traffic on 443 did not match the custom HTTPs service with enabled Protocol Signatures because it was not real HTTPS traffic. It&amp;nbsp;was then dropped in rule 2 because of the port number.&lt;/P&gt;&lt;P&gt;So to me this shows that enabling Protocol Signatures only works in the App Control rules and not Network rules would everyone concur?&lt;BR /&gt;Am I missing something in my tests?&lt;/P&gt;&lt;P&gt;The reason behind this is we want to enable Protocol Signatures on a few standard services but do not want the matching of network rules to change.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Oct 2022 07:08:11 GMT</pubDate>
    <dc:creator>spottex</dc:creator>
    <dc:date>2022-10-26T07:08:11Z</dc:date>
    <item>
      <title>Enabling Protocol Signatures on a service: Does it affect Network Policies</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-Protocol-Signatures-on-a-service-Does-it-affect-Network/m-p/160425#M28276</link>
      <description>&lt;P&gt;Reading other community articles we got the impression enabling Protocol Signatures on a service will affect traffic going through Network Policy rules as well as in App Control rules.&lt;/P&gt;&lt;P&gt;We started to see strange things so I thought I would test in a lab.&lt;/P&gt;&lt;P&gt;I created a test using&lt;BR /&gt;1. The standard HTTPs service&lt;BR /&gt;2. Creating a new HTTPS service. TCP Port 443, HTTPs Protocol and enabled Protocol Signatures&lt;BR /&gt;3. Created an HTTP (not https) website listening on port 443.&lt;/P&gt;&lt;P&gt;Added 2 Network rules&lt;BR /&gt;1. Accept rule using custom HTTPs service with enabled Protocol Signatures.&lt;BR /&gt;2. Drop using the standard HTTPs service.&lt;/P&gt;&lt;P&gt;Test http traffic on port 443 is allowed on rule 1. i.e. using the custom HTTPS Service with enabled Protocol Signatures&lt;/P&gt;&lt;P&gt;Adding application control Rules&lt;BR /&gt;1. Accept rule using custom HTTPs service with enabled Protocol Signatures&lt;BR /&gt;2. Drop using the standard HTTPs service.&lt;/P&gt;&lt;P&gt;The traffic is dropped on Rule 2 bypassing rule 1 with the custom service.&lt;/P&gt;&lt;P&gt;Conclusions&lt;BR /&gt;The network rules only checked the port number and ignored Protocol Signatures.&lt;BR /&gt;In App Control the HTTP Traffic on 443 did not match the custom HTTPs service with enabled Protocol Signatures because it was not real HTTPS traffic. It&amp;nbsp;was then dropped in rule 2 because of the port number.&lt;/P&gt;&lt;P&gt;So to me this shows that enabling Protocol Signatures only works in the App Control rules and not Network rules would everyone concur?&lt;BR /&gt;Am I missing something in my tests?&lt;/P&gt;&lt;P&gt;The reason behind this is we want to enable Protocol Signatures on a few standard services but do not want the matching of network rules to change.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 07:08:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-Protocol-Signatures-on-a-service-Does-it-affect-Network/m-p/160425#M28276</guid>
      <dc:creator>spottex</dc:creator>
      <dc:date>2022-10-26T07:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling Protocol Signatures on a service: Does it affect Network Policies</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-Protocol-Signatures-on-a-service-Does-it-affect-Network/m-p/160490#M28283</link>
      <description>&lt;P&gt;You are correct, and this is documented in the &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk111841&amp;amp;partition=Basic&amp;amp;product=All" target="_self"&gt;R80.10 Release SK&lt;/A&gt;&amp;nbsp;(where this was first added).&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Application Control enhancements:&lt;/LI&gt;
&lt;LI style="list-style-type: none;"&gt;
&lt;UL&gt;
&lt;LI&gt;Added Recommended Services to Applications for easier configuration of the unified policy.&lt;/LI&gt;
&lt;LI&gt;Applications matched on Recommended Services, customized set of services, or Any service.&lt;/LI&gt;
&lt;LI&gt;New Protocol Signature added to Service object, to enhance policy matching security and granularity.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Oct 2022 18:15:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Enabling-Protocol-Signatures-on-a-service-Does-it-affect-Network/m-p/160490#M28283</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-10-26T18:15:51Z</dc:date>
    </item>
  </channel>
</rss>

