<?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 Bypass - checkpoint capsule connect in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86222#M30</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we use the Checkpoint Caspusle Connect Client (Cloud Firewall) with HTTPS Inspection enabled and wanted to call the URL &lt;A href="https://www.xing.com" target="_blank"&gt;https://www.xing.com&lt;/A&gt;. However when the cloud client is connected, we can't call this URL. We only get the notification, that the site is not available. When we disconnect the cloud client, we can call this URL without any problem.&lt;/P&gt;&lt;P&gt;So we tried to bypass this site from the HTTPS inspection (*.xing.com in the cloud portal) however this also doesn't work. So we tried to analyse the traffic with "Fiddler" and there we see that the HTTPS handshake to &lt;A href="http://www.xing.com" target="_blank"&gt;www.xing.com&lt;/A&gt;&amp;nbsp;failed, because the stream was closed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that the https bypass not really works. Does anybody know how we can bypass the traffic to xing?&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Mon, 25 May 2020 13:18:24 GMT</pubDate>
    <dc:creator>hw</dc:creator>
    <dc:date>2020-05-25T13:18:24Z</dc:date>
    <item>
      <title>Https Inspection Bypass - checkpoint capsule connect</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86222#M30</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we use the Checkpoint Caspusle Connect Client (Cloud Firewall) with HTTPS Inspection enabled and wanted to call the URL &lt;A href="https://www.xing.com" target="_blank"&gt;https://www.xing.com&lt;/A&gt;. However when the cloud client is connected, we can't call this URL. We only get the notification, that the site is not available. When we disconnect the cloud client, we can call this URL without any problem.&lt;/P&gt;&lt;P&gt;So we tried to bypass this site from the HTTPS inspection (*.xing.com in the cloud portal) however this also doesn't work. So we tried to analyse the traffic with "Fiddler" and there we see that the HTTPS handshake to &lt;A href="http://www.xing.com" target="_blank"&gt;www.xing.com&lt;/A&gt;&amp;nbsp;failed, because the stream was closed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that the https bypass not really works. Does anybody know how we can bypass the traffic to xing?&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2020 13:18:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86222#M30</guid>
      <dc:creator>hw</dc:creator>
      <dc:date>2020-05-25T13:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: Https Inspection Bypass - checkpoint capsule connect</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86267#M31</link>
      <description>Recommend a TAC case.&lt;BR /&gt;I suspect (without having done the troubleshooting) that there is an incompatibility with TLS ciphers between this site and what is supported by the Capsule Cloud infrastructure.&lt;BR /&gt;In this case, the only way a bypass would work is if you bypass the site by IP address.</description>
      <pubDate>Mon, 25 May 2020 20:31:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86267#M31</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-05-25T20:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: Https Inspection Bypass - checkpoint capsule connect</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86279#M32</link>
      <description>&lt;P&gt;Thanks for the answer. I will open a checkpoint case.&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 04:38:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/86279#M32</guid>
      <dc:creator>hw</dc:creator>
      <dc:date>2020-05-26T04:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Https Inspection Bypass - checkpoint capsule connect</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/89586#M33</link>
      <description>&lt;P&gt;Not sure if you solved the issue already but for others who may come across the same problem, Check Point Capsule Connect doesn't support IP addresses in https inspection bypass rules. The quickest way to solve this is to exclude the IP / URL from web management interface (cloud.checkpoint.com)&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 17:35:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Https-Inspection-Bypass-checkpoint-capsule-connect/m-p/89586#M33</guid>
      <dc:creator>Bekir_Aldemir2</dc:creator>
      <dc:date>2020-06-23T17:35:40Z</dc:date>
    </item>
  </channel>
</rss>

