How to configure multiple global protect portals and gateways

[Mlhras0]

We have several Palo alto firewalls in production now. We currently have client vpn going to Cisco ASAs. We are looking to move the VPN to the Palo Alto. I have been able to get a single vpn profile working. Before we can move to the Palo Alto, i need to figure out how to get the Global protect vpn working similar to the ASA anyconnect vpns.

On the ASA we have two profiles that allow our users to connect. A user can connect to either profile. Users can only connect to one of the profiles if they are using a domain joined computer. this check is done with Azure Saml login. A user can log in at https://ourrouter/vpn1 or https://ourrouter/vpn2. If the user has a domain joined computer they will be allowed to log in to vpn1 and they will have full access to our network. If the users chooses to log in to vpn2 or does not have a domain joined computer, once they log in, the computer has only RDP and DNS access to devices on our network.

We also have a vendor vpn at https://ourrouter/vendor. We have a couple of AD groups for the vendors. If an acccount is a member of vendor1 group, they get allowed access to a couple of devices based on ACL. if the vendor is in vendor2group they get another ACL. we can add more vendor groups and add an acl for each of those groups.

How would we go about creating a similar configuration on the Palo Alto?

[TomYoung · Accepted solution]

Hi @Mlhras0 ,

You can create 3 portals and gateways on your NGFW as long as you have 3 public IP addresses attached to 3 interfaces.  They can be loopbacks.

You can control access through the security policy:

1. VPN1 gateway tunnel tied to zone1.  Authentication is Azure.  The matching security policy rule:
   1. Zone1/Source device = match HIP object for domain
2. VPN2 gateway tunnel tied to zone2.  Authentication is Azure.  The matching security policy rule:
   1. Zone2
   2. Can optionally include Zone1 in the same rule if fallback to this rule is needed for non-domain PCs.
3. Vendor gateway tied to zone3.  Authentication is AD.  LDAP is also setup to query group membership.  The matching security policy rules:
   1. Zone3 - source user vendor1 group.
   2. Zone3 - source user vendor2 group.
   3. Etc.

Since the separation is done in the security policy you could combine gateways 1 and 2.  You could even combine all 3 into 1 portal and gateway, but that would require extra configuration.

Thanks,

Tom

[TomYoung]

Thanks, @Mlhras0 !

I forgot to mention that HIP Profiles require a GP license.