<?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 HTTPS  Inspection - Limiting Traffic to prevent Remote access protocols in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163286#M29144</link>
    <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;My question is similar to "&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Gateway-as-HTTP-HTTPS-proxy/m-p/159888#M28128&amp;quot;" target="_blank" rel="noopener"&gt;https://community.checkpoint.com/t5/Security-Gateways/Gateway-as-HTTP-HTTPS-proxy/m-p/159888#M28128"&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;We want to setup an Internet facing Cluster to replace a non-transparent (HTTP/HTTPS) Proxy . We do NOT want to use the "non-transparent Proxy feature ( for many reasons, also mentioned in the other post) ! Should be a transparent forcing gateway/cluster.&lt;/P&gt;&lt;P&gt;Currently we do not have any&amp;nbsp; possibility for a setup to test this requirement.&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;One of these rules there at the current proxy is that e.g. MS RDP or Citrix protocol (or another remote access protocol, also SSH) are recognized (if tunneling via HTTPS) and thus these types of connections were rejected.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We want to implement a rulebase to do the same at the CheckPoint R81.10 cluster.&lt;/P&gt;&lt;P&gt;What is required to do this?&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;It's obvious that HTTPS inspection needs to be turned on&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;a) Do we have to enable "protocol signature" for HTTPS&amp;nbsp; and/or HTTP as a prerequisite ?&lt;/P&gt;&lt;P&gt;b) Could one approach be to use applications like "Microsoft Remote Desktop Connection","Citrix" or "SSH"&amp;nbsp; before any other HTTPS/HTTP allow rule to recognize and drop these applications ? Or is another step required: e.g. "drop non-Compliant HTTP" ?&lt;BR /&gt;&lt;BR /&gt;Appreciate any suggestions or ideas!&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Martin&lt;/P&gt;</description>
    <pubDate>Sun, 27 Nov 2022 15:51:59 GMT</pubDate>
    <dc:creator>Martin_Hofbauer</dc:creator>
    <dc:date>2022-11-27T15:51:59Z</dc:date>
    <item>
      <title>HTTPS  Inspection - Limiting Traffic to prevent Remote access protocols</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163286#M29144</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;My question is similar to "&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Gateway-as-HTTP-HTTPS-proxy/m-p/159888#M28128&amp;quot;" target="_blank" rel="noopener"&gt;https://community.checkpoint.com/t5/Security-Gateways/Gateway-as-HTTP-HTTPS-proxy/m-p/159888#M28128"&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;We want to setup an Internet facing Cluster to replace a non-transparent (HTTP/HTTPS) Proxy . We do NOT want to use the "non-transparent Proxy feature ( for many reasons, also mentioned in the other post) ! Should be a transparent forcing gateway/cluster.&lt;/P&gt;&lt;P&gt;Currently we do not have any&amp;nbsp; possibility for a setup to test this requirement.&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;One of these rules there at the current proxy is that e.g. MS RDP or Citrix protocol (or another remote access protocol, also SSH) are recognized (if tunneling via HTTPS) and thus these types of connections were rejected.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We want to implement a rulebase to do the same at the CheckPoint R81.10 cluster.&lt;/P&gt;&lt;P&gt;What is required to do this?&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;It's obvious that HTTPS inspection needs to be turned on&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;a) Do we have to enable "protocol signature" for HTTPS&amp;nbsp; and/or HTTP as a prerequisite ?&lt;/P&gt;&lt;P&gt;b) Could one approach be to use applications like "Microsoft Remote Desktop Connection","Citrix" or "SSH"&amp;nbsp; before any other HTTPS/HTTP allow rule to recognize and drop these applications ? Or is another step required: e.g. "drop non-Compliant HTTP" ?&lt;BR /&gt;&lt;BR /&gt;Appreciate any suggestions or ideas!&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Martin&lt;/P&gt;</description>
      <pubDate>Sun, 27 Nov 2022 15:51:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163286#M29144</guid>
      <dc:creator>Martin_Hofbauer</dc:creator>
      <dc:date>2022-11-27T15:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS  Inspection - Limiting Traffic to prevent Remote access protocols</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163317#M29145</link>
      <description>&lt;P&gt;Why are you posting to the AppSec category? This seems to be HTTPSi question for regular security GWs.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Nov 2022 08:15:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163317#M29145</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2022-11-28T08:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS  Inspection - Limiting Traffic to prevent Remote access protocols</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163496#M29199</link>
      <description>&lt;P&gt;Because this is a "Application Security" (...) question ... - &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;as I (unfortunately incorrectly) assumed that this is the category for GW application security&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&amp;nbsp;I never worked with "AppSec"&amp;nbsp;&amp;nbsp; -&amp;nbsp; this name is another example of a limited talent of your company choosing meaningfull names for products (look at the history of endless number for&amp;nbsp; names for a VPN client ...)&lt;BR /&gt;&lt;BR /&gt;Thanks for moving to the right category- still waiting for an answer ....&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 10:04:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163496#M29199</guid>
      <dc:creator>Martin_Hofbauer</dc:creator>
      <dc:date>2022-11-29T10:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS  Inspection - Limiting Traffic to prevent Remote access protocols</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163513#M29208</link>
      <description>&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/Management/Enable-Protocol-Signature-by-default/m-p/139285/highlight/true#M29469" target="_blank"&gt;Solved: Re: Enable Protocol Signature by default - Check Point CheckMates&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 10:41:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/HTTPS-Inspection-Limiting-Traffic-to-prevent-Remote-access/m-p/163513#M29208</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2022-11-29T10:41:29Z</dc:date>
    </item>
  </channel>
</rss>

