Hello,
I have issues understanding what is an Application Filter for and how to use it. What I understand:
- Web Policies: Allow you to block or allow traffic to users (based on categories/file types, etc.). Only one web policy is meant to be used for a group of users through a firewall rule. If you have multiple rules with multiple web policies, only the first firewall rule/web policy that matches the traffic, will be applied (the subsequent ones will be ignored). Source: https://community.sophos.com/xg-firewall/f/discussions/83833/web-policy-and-filtering-not-working-at-all/
- Application Filters: Offers the flexibility of matching traffic by identifying the application related to it (i.e. you can create an application to match anything where SmartFilter = "Netflix", regardless of knowing or not what servers or ip address ranges Netflix uses).
My scenario:
I want to configure a Web Policy to block users from getting to certain websites at all times, but have the flexibility to enable/disable a firewall rule configured with an Application Filter that matches "Netflix". If the rule is enabled, Netflix will be allowed, otherwise it will be blocked. I don't try to configure this as part of the Web Policy, because I want to be able to turn on/off the "Netflix" application firewall rule manually as needed through the XG's REST API.
What I've tried:
Firewall Rule 1 - Application Filter Allowing Netflix (Smart Filter = "Netflix").
Firewall Rule 2 - Web Policy Filter Blocking "Video Hosting" category at all times.
Issues with this configuration:
- If Rule 1 is enabled, not only Netflix, but ALL traffic is allowed. Why? (I thought the Application Filter would only match the configured criteria, and let the traffic be matched by the next rule).
- If I somehow incorporate the Netflix block as part of the Web Policy (provided it is not too difficult to match this type of traffic with the options available), there's not easy way to turn on/off this block from the REST API. Even if I did it manually, I would have to turn on/off a web policy rule (and modifying a web policy) frequently, which is less than desirable.
Should I be doing things differently? (Somehow I think if would be easier if we could turn off a Web Policy's "default action", and let the packet match the next rule available. Eventually, it would reach to the "Drop All" (last) firewall rule, if traffic is not matched by anything. (To give some background, I come from using Microsoft TMG 2010, and that's how TMG used to work).
Thanks!
This thread was automatically locked due to age.