topic HIP Profile Windows 11 in General Topics

HIP Profile Windows 11

etoribio — Tue, 04 Jan 2022 14:10:24 GMT

As stated in Where Can I Install the GlobalProtect App? (paloaltonetworks.com) the official client for W11 is > 5.2.10

Personally, I've used version ~5.2.7 without issues, the only thing I noticed was that detected host for HIP Profile was Microsoft Windows 10 Pro. Now that I've updated to version 5.2.10-6, detected host is Microsoft Windows 11 Pro.

This now comes with an issue. We have in our HIP Profile to allow connection for W10 versions only, but W11 versions are not appearing. One workaround would be to deny all versions listed, except W10 (and indirectly W11).

The list of OSs in HIP profile depends on PAN OS? We have version 10.0.0.8-h8

Regards

Re: HIP Profile Windows 11

aleksandar.astardzhiev — Tue, 04 Jan 2022 15:56:27 GMT

Hi @etoribio ,

I believe the OS list and any other setting you can use in the HIP profile are defined by the GlobalProtect Data File

Which basically means that Palo Alto push updates once in while. Unfortunately it seems the latest update was 07.11.2020 and it looks it applies for all PanOS versions (at least from my environment).

There are two possible workarounds:

- For OS vendor choose "Other" and just type "Microsoft Windows 11 Pro". Basically the same string you see from GlobalProtect application under the OS.

I am not 100% if it will work, and cannot test it right now, but in theory at the end it just string comperison between what GlobalProtect app is reporting and what FW config is using.

- The other way would be to use custom check and look for registry key that contains the OS version.

Re: HIP Profile Windows 11

BPry — Wed, 05 Jan 2022 19:46:02 GMT

@etoribio,

I really recommend actually using custom checks to control what builds can connect to your environment. If your saying that Windows 10 devices can just connect, your allowing all builds of Windows 10 including extremely outdated builds that are no longer getting updates.

I personally like getting

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion as a custom check and pulling the CurrentBuildNumber registry value. Then build out custom hip-objects for each build of Windows that you want to allow to connect (ideally just the supported builds) and you can use a HIP-Profile to group supported operating systems.

This helps to ensure that you aren't allowing outdated Windows 10 builds (or Windows 11 builds going forward).