cancel
Showing results for 
Search instead for 
Did you mean: 
wouterr
Level 11
Report Inappropriate Content
Message 1 of 3

getting the SYSTEM process into ENS FW rules

We are currently migrating from HIPS FW to ENS FW;

However during migration we notice the executable object <SYSTEM> is not migrated properly to ENS.

The object looks correct when looked at from ePo, however it's never applied on the endpoint (FW rule is active without the application filtering on the SYSTEM process)

Also in ENS we seem to be unable to recreate this executable object (each attempt results in code looking like **\SYSTEM or **\<SYSTEM> and which the FW module on the client is unable to match to the actual system process.

Any suggestions on how to make FW rules in ENS which only apply to the system process?

2 Replies
McAfee Employee ktankink
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: getting the SYSTEM process into ENS FW rules

You should be able to just use SYSTEM.  See screenshot below.

 

 system.jpg

 

system2.jpg

McAfee Employee ktankink
McAfee Employee
Report Inappropriate Content
Message 3 of 3

Re: getting the SYSTEM process into ENS FW rules

Also, **\SYSTEM is an equivalent value that should match SYSTEMSYSTEM will be what's in the policy, but the ENS Firewall client will interpret that as **\SYSTEM.  It should still match System traffic properly though.

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator