<?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 Zscaler Traffic Pattern in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/zscaler-traffic-pattern/m-p/595069#M3598</link>
    <description>&lt;P&gt;My company users are using ZCC on their laptops. Recently, there has been an issue where Zscaler traffic is being denied by the Palo Alto Firewall.&lt;BR /&gt;&lt;BR /&gt;Upon checking the logs, it appears that the ZCC traffic pattern changed into web browsing and HTTP Proxy, which is being denied by the firewall. We have configured the firewall to allow Zscaler Private Access and Zscaler Internet Access as applications but have not allowed web browsing and HTTP Proxy.&lt;BR /&gt;&lt;BR /&gt;Previously, this setup worked with Zscaler Private Access and Zscaler Internet Access. Please confirm why the traffic pattern has changed to web browsing and HTTP Proxy. Additionally, please validate the logs attached to the case and the firewall screenshot provided for your reference.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Long story into short and to be more granular, please check was there any change in the ZCC traffic pattern (or) any changes in the encryption/TLS?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2024 03:37:49 GMT</pubDate>
    <dc:creator>madu2609</dc:creator>
    <dc:date>2024-08-16T03:37:49Z</dc:date>
    <item>
      <title>Zscaler Traffic Pattern</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/zscaler-traffic-pattern/m-p/595069#M3598</link>
      <description>&lt;P&gt;My company users are using ZCC on their laptops. Recently, there has been an issue where Zscaler traffic is being denied by the Palo Alto Firewall.&lt;BR /&gt;&lt;BR /&gt;Upon checking the logs, it appears that the ZCC traffic pattern changed into web browsing and HTTP Proxy, which is being denied by the firewall. We have configured the firewall to allow Zscaler Private Access and Zscaler Internet Access as applications but have not allowed web browsing and HTTP Proxy.&lt;BR /&gt;&lt;BR /&gt;Previously, this setup worked with Zscaler Private Access and Zscaler Internet Access. Please confirm why the traffic pattern has changed to web browsing and HTTP Proxy. Additionally, please validate the logs attached to the case and the firewall screenshot provided for your reference.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Long story into short and to be more granular, please check was there any change in the ZCC traffic pattern (or) any changes in the encryption/TLS?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2024 03:37:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/zscaler-traffic-pattern/m-p/595069#M3598</guid>
      <dc:creator>madu2609</dc:creator>
      <dc:date>2024-08-16T03:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: Zscaler Traffic Pattern</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/zscaler-traffic-pattern/m-p/595307#M3606</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/655710467"&gt;@madu2609&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks for post!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have checked ZCC traffic logs in my environment and I can confirm that traffic across all Firewalls is identified correctly as&amp;nbsp;zscaler-internet-access and&amp;nbsp;zscaler-private-access. Regarding your case what comes to my mind is Z-Tunnel 1.0 vs Z-Tunnel 2.0:&amp;nbsp;&lt;A href="https://help.zscaler.com/client-connector/about-z-tunnel-1.0-z-tunnel-2.0" target="_self"&gt;z-tunnel-1.0-z-tunnel-2.0&lt;/A&gt;. If your clients are using Z-Tunnel 1.0, then this could be an reason why Firewall is identifying traffic as proxy. Was there any change in forwarding profile?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2024 04:16:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/zscaler-traffic-pattern/m-p/595307#M3606</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2024-08-20T04:16:33Z</dc:date>
    </item>
  </channel>
</rss>

