<?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: Clientless VPN inpection in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/clientless-vpn-inpection/m-p/554174#M4292</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/280217"&gt;@sbhingarde&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The NGFW already decrypts Clientless VPN because it is the tunnel endpoint.&amp;nbsp; If you look in Monitor &amp;gt; Logs &amp;gt; Traffic, you can filter on the destination IP address that matches the Application URL of one of your Clientless Apps.&amp;nbsp; You will see that the application is web-browsing because it is being decrypted.&amp;nbsp; In my case, the traffic matches the intrazone-default rule.&amp;nbsp; As long as you have security profiles applied to the rule, then you are performing Content-ID on the traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Thu, 17 Aug 2023 12:53:16 GMT</pubDate>
    <dc:creator>TomYoung</dc:creator>
    <dc:date>2023-08-17T12:53:16Z</dc:date>
    <item>
      <title>Clientless VPN inpection</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/clientless-vpn-inpection/m-p/554087#M4290</link>
      <description>&lt;P&gt;Hi, Can we do decryption for Clientless VPN traffic? If no, how is the traffic inspected? This is in regards to BYOD.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 04:40:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/clientless-vpn-inpection/m-p/554087#M4290</guid>
      <dc:creator>sbhingarde</dc:creator>
      <dc:date>2023-08-17T04:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: Clientless VPN inpection</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/clientless-vpn-inpection/m-p/554174#M4292</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/280217"&gt;@sbhingarde&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The NGFW already decrypts Clientless VPN because it is the tunnel endpoint.&amp;nbsp; If you look in Monitor &amp;gt; Logs &amp;gt; Traffic, you can filter on the destination IP address that matches the Application URL of one of your Clientless Apps.&amp;nbsp; You will see that the application is web-browsing because it is being decrypted.&amp;nbsp; In my case, the traffic matches the intrazone-default rule.&amp;nbsp; As long as you have security profiles applied to the rule, then you are performing Content-ID on the traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 12:53:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/clientless-vpn-inpection/m-p/554174#M4292</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2023-08-17T12:53:16Z</dc:date>
    </item>
  </channel>
</rss>

