We would like to restrict access to internal resources (service connection) for Prisma mobile users connected to other Global Protect gateways than our main one in the UK. Does anyone know how we could go about this? We will of course have policies to allow internet access but nothing more.
The Prisma IP pools include UK in emea/Europe so we can't restrict it easily by what subnet the user is in.
We see how to limit source traffic in policies to individual regions but in Prisma it seems once the user connects to the GP gateway of choice (testing manual atm), they are then in the emea mobile user IP pool, therefore negating the region restriction in traffic policies as it is counted as inter-fw traffic.
Can anyone point me in the right direction please?
once a user is connected they're considered as 'internal' so that limits your means of segregating them
for a different region you could use IP based access (as you can assign a different pool per region), but inside the same region you're limited to the same pool for everyone. eacht gateway will get a /24 (or multiple depending on the number of connected users) but I would't recommend using that as a reliable identification method
I'd suggest you create an AD group and limit which users are able to access the resource
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!