topic Re: GlobalProtect HIP Check when connecting to external gateway in GlobalProtect Discussions

GlobalProtect HIP Check when connecting to external gateway

TomKisiel — Thu, 17 Dec 2020 14:55:15 GMT

I have GlobalProtect portal/gateway configured and working in my environment. External users can connect to the GP portal/gateway and receive network access.

I have set up a HIP profile to check for domain joined and AV updated in the last 3 days. What I'd like to do is have the HIP check run during the initial connection to GP portal/gateway, so basically if HIP check passes, user is allowed to connect to GP, if HIP check fails, user is not allowed to connect to GP.

I do not want to set the HIP check profile for SSLVPN zone on every single firewall rule (we have a huge ruleset). I only want the HIP check enforced on connection to the GP portal/gateway.

I tried applying the HIP check profile to the firewall rule that allows GP connection from WAN, but that did not do the trick.

Re: GlobalProtect HIP Check when connecting to external gateway

Mick_Ball — Fri, 18 Dec 2020 12:22:56 GMT

No I don't think this is possible as HIP info is collected and sent after the GW connection is established.

You could add a deny policy at the top of your ruleset to deny all from sslvpn zone if HIP is "Not" a match.

this would save you adding to all other policies but you will then need to move up any policies that you may have that would allow traffic with a no match (If you have any).

Re: GlobalProtect HIP Check when connecting to external gateway

TomKisiel — Fri, 18 Dec 2020 16:20:49 GMT

I understand what you're saying, but trying to figure out how I would design that rule.

Zone- SSLVPN

Source- User, Address- Any

HIP Profile- HIP-Checks

Destination- Zone, User, Address- Any

Action- Deny?

Re: GlobalProtect HIP Check when connecting to external gateway

Mick_Ball — Fri, 18 Dec 2020 16:44:18 GMT

OK I will try to keep it simple and us an OS as the example.

what we are trying to achieve is to allow all win10 devices access via the policies.

But we do not want to add this to all of the policies as there is hundreds of them.

so...

objects/hip object add name win10-check general/host info/OS contains msoft windows 10.

then..

objects/hip profiles add name not-win10 match add NOT win10-check

then..

policy add from sslvpn to private hip not-win10 any any any deny

i hope i got that correct as popping out...

so... if you only allow a certain level in, AV etc. then block those that do not meet the requirement with a NOT hip profile.

Re: GlobalProtect HIP Check when connecting to external gateway

Mick_Ball — Fri, 18 Dec 2020 16:48:08 GMT

Re: GlobalProtect HIP Check when connecting to external gateway

TomKisiel — Fri, 18 Dec 2020 17:01:22 GMT

Perfect, this works!!