GlobalProtect HIP check issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

GlobalProtect HIP check issue

L4 Transporter

 

HIP object is correctly setup.

 

We are testing the missing patches HIP check object and noticed that an VPN endpoint is showing 3 missing patches (on the HIP report).
However the machine is showing it's installed these patches already.
How does Palo detect the missing patches as Windows is showing them as installed?

 

Using ver: 8.1.10

1 accepted solution

Accepted Solutions

TAC Team has advised it is a bug in GP version GP client version 5.0.7-2. It is being tracked as GPC-10176 and currently PA is planning to release the fix in the upcoming GlobalProtect client version 5.0.9. Alternatively we can use GlobalProtect client version 5.1.0 or later.

View solution in original post

3 REPLIES 3

Community Team Member

Hi @FarzanaMustafa ,

 

That is indeed very strange.

 

Maybe the GP agent didn't detect the host information properly or the GP agent didn't pass on the report to the gateway...

 

Here is explained how HIP mechanism works in GlobalProtect: 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLSYCA4

 

Anytime you see the HIP Match issues I would recommend following this document and gather the information explained in the article.  It will help with the investigation of the issue and will get the information necessary to engage support.

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000boP1CAI

 

Hope it helps,

-Kiwi.

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

TAC Team has advised it is a bug in GP version GP client version 5.0.7-2. It is being tracked as GPC-10176 and currently PA is planning to release the fix in the upcoming GlobalProtect client version 5.0.9. Alternatively we can use GlobalProtect client version 5.1.0 or later.

TAC Team has advised it is a bug in GP client version 5.0.7-2. It is being tracked as GPC-10176 and currently PA is planning to release the fix in the upcoming GlobalProtect client version 5.0.9. Alternatively we can use GlobalProtect client version 5.1.0 or later.

  • 1 accepted solution
  • 6583 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!