topic Re: User-ID rule to bypass HIP check not matching. in General Topics

User-ID rule to bypass HIP check not matching.

adrianflux — Wed, 23 Sep 2020 14:08:48 GMT

Hi all,

I have a rule to allow certain Global Protect users DNS and RDP traffic by matching the user-id. However, even though it looks like the traffic should match when I view the traffic log it's not?! For some users the rule works fine but others it doesn't match and I can't work it out.

Any help would be greatly appreciated 🙂

Kevin.

Re: User-ID rule to bypass HIP check not matching.

BPry — Thu, 24 Sep 2020 02:04:15 GMT

@adrianflux,

Would really need to look at the logs to figure this out. You've verified that the user-id is recorded in the denied traffic logs and the rulebase entry properly passes when you do a test security-policy-match? Can you give us an output of the security entry and an example of one of the logs that isn't currently working?

Re: User-ID rule to bypass HIP check not matching.

GeorgiosFakis — Thu, 24 Sep 2020 06:57:39 GMT

Hi ,

Check the user-id how is formatted in the logs like : domain\bob

Then check the traffic logs that you interested and check there the user , it should be something else and that is the reason why

Then check the security policy to see if you have domain\bob like the user ID .

The HIP collection is taking the username and domain.

Re: User-ID rule to bypass HIP check not matching.

BigPalo — Fri, 04 Jun 2021 08:36:45 GMT

Hi all,

I have a similar problem. I have some users connect by global protect with HIP Profile that sometimes they have match in one rule and othertimes they have match in another rules.

I still have two rules, one with HIP and one without HIP profile for this reason.

I want to delete the rule without HIP profile but not for the moment because I have the doubt that if I don't have it... the traffic can go down as it is still maching on both rules

Can anyone help me?

Re: User-ID rule to bypass HIP check not matching.

Remo — Wed, 02 Jun 2021 15:41:20 GMT

@BigPalo are there different HIP profiles specified in the two security policy rules?

Re: User-ID rule to bypass HIP check not matching.

BigPalo — Wed, 02 Jun 2021 15:43:11 GMT

No, We have only one HIP profiles specified in the one security policy rule

The other rule does not have HIP profile applied

Re: User-ID rule to bypass HIP check not matching.

Remo — Wed, 02 Jun 2021 15:44:49 GMT

Then it looks like the HIP profile does not match all the time. What do you check with that HIP profile?

Re: User-ID rule to bypass HIP check not matching.

BigPalo — Thu, 03 Jun 2021 06:54:06 GMT

Hi,

Thanks for your answer...but I think that it is not the problem because users sometimes match in correct rule If we had HIP profile wrong it never work fine , no?

Re: User-ID rule to bypass HIP check not matching.

Remo — Thu, 03 Jun 2021 08:03:38 GMT

I was thinking about the HIP profile because of the topic here where you posted this comment. And also because in the screenshot everything is exactly the same. Another possibility would be an URL category in the rule which makes sometime match one and then again the other rule.

Re: User-ID rule to bypass HIP check not matching.

GeorgiosFakis — Thu, 03 Jun 2021 08:56:45 GMT

When the user disconnects from GP there are session that will expire, therefore there is no HIP data at the moment . I have seen in my logs that is matching a "catch" rule DENY for those HIP profiles are not working.

Re: User-ID rule to bypass HIP check not matching.

BigPalo — Thu, 03 Jun 2021 15:10:41 GMT

Hi, thanks for your response, I have checked in my logs but I have not found rule DENY

I only see that user change your match for another rule but it is allow rule

Regards

Re: User-ID rule to bypass HIP check not matching.

GeorgiosFakis — Fri, 04 Jun 2021 06:42:52 GMT

Hi ,

Are they RDP with the same account like the login username of GP ?

Have you defined AD groups in the ACL ?

What username is not matching the RDP and the DNS and have you compared that to the username login ?

I had the same issue and I deleted the source user AD group because I had users like domain\bob and the RDP was done by domain\admbob.