cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Different location awareness for ENS Firewall

Jump to solution

ePO 5.9.1

ENS 10.5.3

Hello.

We are migrating SEP to ENS, and in SEP Firewall we have location awarness group of rules for Corporate and NonCorporate networks.

I have no problem configuring the Corporate network, because in ENS there are an option to check the DNS Suffix, and if match the corporate DNS suffix, it aplies the asociate rlues.

But, when I tried to configure the Non Corporate group of rules, I dont see an equivalent option that I have in SEP, because in SEP I configure the following:

"If DNS Suffix is NOT corporate.dns.com, then aplies this rules"

Is there an alternative in ESN to detect that the client is NOT in the corporate network?

1 Solution

Accepted Solutions

Re: Different location awareness for ENS Firewall

Jump to solution

Hi mgamarra,

I'm currently in the middle of doing a Proof of Concept (PoC) with ENS Firewall, we're migrating from VSE 8.8 to ENS Threat Prevention and need to block some outbound ports (25 and mDNS), so we're testing the ENS Firewall at the moment.

What I discovered is the ENS firewall Location Awareness only seems to apply the rules under it if certain conditions are met, such as a Connection-Specific DNS suffix (i.e. abc.com). There isn't a way that I can see to do the opposite of this, such as identify a "public" network , etc. What it looks like you have to do is set a default "standard" firewall rules which apply everywhere that is considered public/private, and then create a Location Aware Group (LAG) with rules that apply when you are in domain. To simplify, think of it was Trusted vs Untrusted network. By default your firewall rules would be for "untrusted" networks, but if your system is on the domain, then the rules under the LAG apply and it appears as if you system is now in a "trusted" network.

1 Reply

Re: Different location awareness for ENS Firewall

Jump to solution

Hi mgamarra,

I'm currently in the middle of doing a Proof of Concept (PoC) with ENS Firewall, we're migrating from VSE 8.8 to ENS Threat Prevention and need to block some outbound ports (25 and mDNS), so we're testing the ENS Firewall at the moment.

What I discovered is the ENS firewall Location Awareness only seems to apply the rules under it if certain conditions are met, such as a Connection-Specific DNS suffix (i.e. abc.com). There isn't a way that I can see to do the opposite of this, such as identify a "public" network , etc. What it looks like you have to do is set a default "standard" firewall rules which apply everywhere that is considered public/private, and then create a Location Aware Group (LAG) with rules that apply when you are in domain. To simplify, think of it was Trusted vs Untrusted network. By default your firewall rules would be for "untrusted" networks, but if your system is on the domain, then the rules under the LAG apply and it appears as if you system is now in a "trusted" network.

ePO Support Center Plug-in
Check out the new ePO Support Center. Simply access the ePO Software Manager and follow the instructions in the Product Guide for the most commonly used utilities, top known issues announcements, search the knowledgebase for product documentation, and server status and statistics – all from within ePO.