Exclude all Zoom traffic from GlobalProtect VPN

[MarcelST]

We have been trying to exclude all Zoom-related traffic from the GlobalProtect VPN tunnel.

So far we have tried with: "*.zoom.us" exclusion configured directly on the GP gateway as a domain in:

Network --> GlobalProtect --> Gateways --> GW NAME --> Agent --> CLient Settings --> Split tunnel --> Domain and Application

But this seems to not completely do the trick as Zoom use some AWS default domains, not under *.zoom.us.

What approaches will work that does not involve having to manually exclude all the IP ranges as defined here?

https://support.zoom.us/hc/en-us/articles/201362683-Network-Firewall-or-Proxy-Server-Settings-for-Zo...

The Zoom binary path seems to be this one, but I'm not sure PA supports wildcards on the path like this:

C:\Users\*\AppData\Roaming\Zoom\bin\Zoom.exe

[BigPalo]

we have the correct ranges but its like the clients are not splitting the traffic and this traffic is still going through the tunnel.

Is it needed to restart the agent or any action in GP to refresh?

[MarcelST]

You need to do a GP connection refresh, and after connection is reestablished exit & access again Zoom, that should do it.

What version of GP are you using? My tests showed that begore GP v5.1.1 lots of things are not right with the split tunnel.

[BigPalo]

We configured the zoon split tunneling using domain and application but we see that sessions to zoom using port 8801. These 8801 sessions are going through the tunnel. Is there any way to split this traffic?

[BigPalo]

I have the same issue. Port 8801 is going through GP tunnel and some 443 zoom-base sessions.

How did you solve it? any idea?

[MarcelST]

What GP version are you using? TO me, deploying GP v5.1.1 solved the issue.Before we were using v4.something.

[BigPalo]

Hi,

I upgraded the clients to 5.1.3 GP version. but we still see traffic logs for zoom ips in port 443. Why? 

[AndrzejPiotrowski]

Hi, 

I have the same problem - GP 5.1.3 and exclude zoom app but some flows are still on gateway and in tunnel to the internal company network. Why? Somebody does know solid and stable solution how to exclude zoom traffic from tunnel on GP?

regards,

Andrzej

[BigPalo]

We still see connections in port 8801 in FW. someone worked split for zoom?

[AndrzejPiotrowski]

Split on gateway per user group domain zoom.us and zoom.com, split on gateway application zoom-base nad zoominfo (lack of application zoom-meeting which is main application!!!) or exclude process of zoom exe - all of them solutions don't work. Traffic still is sending via firewall and internal network despite of direct from client GP to the Internet/to the zoom cloud. Nobody resolved this issue?

[MarcelST]

Make sure you have the GlobalProtect license installed on that Gateway, as license is required for some advanced features like split tunneling.

[didel0815]

Hi just curious how you created the address group.

I'll tried in on PAN-OS 9.1x (Panorama and firewalls) and got a validation error, when I tried to push the changes to the firewall.

Which PAN-OS and GP versions are you using?

[PravinSingi]

Facing the same issue.

However, just 'allow listing' zoom.us and zoom.com along with /Applications/zoom.us.app/Contents/MacOS/zoom.us for MAC work. It's sad that I can't use the predefined application for video-conferencing to exclude in the spit-tunnelling.

[Brandonyawn]

Needs Global Protect license for optimized split tunnel to work correctly. 

[Brandon_Wertz]

Like @Brandonyawn mentioned here is the referenced link to that information:

https://docs.paloaltonetworks.com/globalprotect/8-1/globalprotect-admin/globalprotect-overview/about...

[HussainMohammed]

Also facing same issue,