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?
Also, **\SYSTEM is an equivalent value that should match SYSTEM. SYSTEM 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.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.