topic Re: HIP Profile monitor only initially in General Topics

HIP Profile monitor only initially

FWPalolearner — Sun, 11 Oct 2020 21:23:51 GMT

Hello ,

We have got requirement to implement HIP profile for GP users ;

But first we want to run it in Monitor mode without any enforcement or without blocking any users

Below are the requirements

OS	Windows 10
AV	Mcafee
AV updates not older than	5 days
Patch management	/
Disk encryption	Enabled
Firewall	Enabled

So do i just have to create HIP Object with all these conditions ?

And how will i check which machines will not hit these HIP objects ?

Re: HIP Profile monitor only initially

BPry — Tue, 13 Oct 2020 01:01:21 GMT

@FWPalolearner,

So the thing to remember about HIP is that it never takes any action unless you've specifically told it to. By default, HIP is just going to be informational. What you would do here is just create a HIP Object matching your criteria and commit. The HIP Match logs on the firewall will tell you which connecting clients are matching your HIP Object.

If you want to quickly see what machines aren't meeting your defined HIP parameters, you could do that easily enough by creating two HIP Profiles. You would simply set it to match or NOT match your HIP Object you defined above, and then you could search for either HIP Profile in your logs.

So for an example, lets say that I created a HIP Object called "Secured-Clients" and had it match all the criteria you defined. I would then create two HIP Profiles, with the first being "Trusted-Clients" for example that would simply match on the "Secured-Clients" HIP object you created previously. You would then create another HIP Profile called "NonTrusted-Clients" and simply have the match criteria as NOT "Secured-Clients".

When it came to searching who was matching which profile, you can log into the firewall and search the HIP Match logs. To filter on the Trusted-Clients HIP Profile you would simply use the search ( matchname eq Trusted-Clients ) to find everyone who meets your HIP criteria and then ( matchname eq NonTrusted-Clients ) to find everyone who doesn't.

Just keep in mind that nothing will actually take into account your HIP Profiles until you actually configure it to do so. Simply creating new HIP Objects or HIP Profiles will never cause any issues to your existing profiles.

Re: HIP Profile monitor only initially

FWPalolearner — Fri, 23 Oct 2020 13:29:42 GMT

Hello @BPry

Thanks and apolgies for getting back to you late

I have configured HIP profiles but i have doubt in the syntax

I have created 4 HIP objects for checking AV , OS ,FW and Disk enc for machine in old domain . to check non compliant machines i have done below syntax for HIP profile

(not "GP-Internal-AV" or not "GP-Internal-OS" or not "GP-Internal-FW" or not "GP-Internal-DiskEncryption" ) and "GP-Internal-Domain-old"

or do i have to put parantheseis like below

((not "GP-Internal-AV" )or (not "GP-Internal-OS") or (not "GP-Internal-FW" )or (not "GP-Internal-DiskEncryption" ) )and "GP-Internal-Domain-old"

Similarly for external machines i have below

(not "GP-External-AV" or not "GP-External-OS" or not "GP-External-FW" or not "GP-External-DiskEncryption" ) and (not "GP-Internal-Domain-Old" )

or the syntax should be ?

((not "GP-External-AV") or (not "GP-External-OS") or (not "GP-External-FW") or (not "GP-External-DiskEncryption" )) and (not "GP-Internal-Domain-New" )

i am confused by paranthesis

Re: HIP Profile monitor only initially

BPry — Sat, 24 Oct 2020 17:19:57 GMT

@FWPalolearner,

The syntax for this is a little weird. You don't actually need to include brackets around things you don't want to group. So in your first example, the syntax that I would use would be:

not ("GP-Internal-AV" or "GP-Internal-OS" or "GP-Internal-FW" or "GP-Internal-DiskEncryption" ) and "GP-Internal-Domain-old"

Likewise your second example I would use:

not ("GP-External-AV" or "GP-External-OS" or "GP-External-FW" or "GP-External-DiskEncryption" ) and not "GP-Internal-Domain-Old"

Re: HIP Profile monitor only initially

FWPalolearner — Fri, 30 Oct 2020 11:35:13 GMT

@BPry Thanks . this works . Thanks for your help as always 🙂