<?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: Https inspection best practice in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227084#M37927</link>
    <description>&lt;P&gt;Its always like this...you bypass ALLOWED sites and inspect BLOCKED ones, thats it.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2024 13:09:39 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-09-18T13:09:39Z</dc:date>
    <item>
      <title>Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227083#M37926</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I have a question about HTTPS Inspection. We want to restrict some of our client machines to only access specific websites that is needed for their work. we have create two rules on the Firewall and APP/URL blades and also We've installed the HTTPS certificate on the user machines and created two rules in the HTTPS rule base: one for inspection and one for bypassing. I'm unsure which rule should be set to inspect and which should be set to bypass: the allowed sites or the blocked ones.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 12:53:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227083#M37926</guid>
      <dc:creator>Ihenock1011</dc:creator>
      <dc:date>2024-09-18T12:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227084#M37927</link>
      <description>&lt;P&gt;Its always like this...you bypass ALLOWED sites and inspect BLOCKED ones, thats it.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 13:09:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227084#M37927</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-09-18T13:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227085#M37928</link>
      <description>&lt;P&gt;There is a whole SecureKnowledge article dedicated to HTTPS Inspection Best Practices:&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk108202" target="_self"&gt;sk108202&lt;/A&gt;.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;However, I am sure there are other things you need to consider before moving forward with HTTPSi policy.&lt;/P&gt;
&lt;P&gt;HTTPS Inspection only allows you to see inside of TLS traffic. In most cases, you can effectively implement URL filtering (which you need to limit web access to specific sites only)&amp;nbsp; with something called HTTPSi Lite, a.k.a. HTTPS Filtering.&lt;BR /&gt;&lt;BR /&gt;I suggest you review&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk92743" target="_self"&gt;sk92743&lt;/A&gt; and specifically&amp;nbsp;HTTPS Filtering of the document before anything else.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 13:12:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227085#M37928</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-09-18T13:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227091#M37929</link>
      <description>&lt;P&gt;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/96626"&gt;@Ihenock1011&lt;/a&gt;&amp;nbsp;Let me know if you want to do remote, I have fully working ssl inspection lab on R81.20 jumbo 84.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 14:13:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227091#M37929</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-09-18T14:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227116#M37939</link>
      <description>&lt;P&gt;In order to bypass you need to inspect it. Unless you bypass made on IP address (that is almost never the case).&lt;/P&gt;
&lt;P&gt;You always want to whitelist an url because it is more easy or a complete category like finance.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But to know if you actually want to do the bypass firewall always has to do some inspection (not full).&lt;/P&gt;
&lt;P&gt;Most of the time checking the certificate for the name is enough.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 17:20:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227116#M37939</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-09-18T17:20:21Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227117#M37940</link>
      <description>&lt;P&gt;Not sure I understand your statement -&amp;gt; in order to bypass, you need to inspect it...sorry.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 17:30:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227117#M37940</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-09-18T17:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227124#M37941</link>
      <description>&lt;P&gt;It needs be able to check the certificate in order to see if it will hit a bypass rule. Unless you make the bypass based on IP. If you bypass based on URL it needs to do a check ithe cert n order to see if it will hit a bypass rule.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk177983" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk177983&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk122158" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk122158&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Cannot find the exact SK but these explain it also a bit&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 18:08:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227124#M37941</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-09-18T18:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: Https inspection best practice</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227125#M37942</link>
      <description>&lt;P&gt;Certificate, right, of course. I had not tested in some time without https inspection, but if not enabled, it might be tricky to make bypass work, though that 2nd option from 1st sk may be a good option.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 18:13:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Https-inspection-best-practice/m-p/227125#M37942</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-09-18T18:13:09Z</dc:date>
    </item>
  </channel>
</rss>

