The system allows the application of several content filter profiles in the same connection context (Source, Destination, User). That is, when detecting a policy where a specific type of HTTP or HTTPS traffic is applicable, the system considers the URL in the policy's search parameters (Lookup).
In Content Filter profiles it is possible to Allow, Block and Disable categories. A policy that has a Web Filter enabled takes into account only the URLs whose categories have been allowed or blocked in the Profile, if the URL is disabled, the service will move on to the next policy where the HTTP connection context matches, if there is no policy that applies, the URL will be blocked, the same is true for web-type applications if the application control is active.
page.
For more information on application control, see this
This table shows the behavior if the request matches webfilter and application control categories:
Application Control | Webfilter Category | Behavior |
---|---|---|
Without inspection control | Without inspection control | Allow access |
Without inspection control | Disabled | Next policy |
Without inspection control | Refuse | Block access |
Without inspection control | Allow | Allow access |
Allow | Without inspection control | Allow access |
Block | Without inspection control | Block access |
Disabled | Without inspection control | Next policy |
Disabled | Disabled | Next policy |
Disabled | Allow | Allow access |
Disabled | Refuse | Block access |
Allow | Disabled | Allow access |
Allow | Allow | Allow access |
Allow | Refuse | Block access |
Block | Disabled | Block access |
Block | Allow | Block access |
Block | Refuse | Block access |
Do not match any policy | Block access |
If the tab is not selected, click on "Profiles".
Profiles tab
The “Profiles” screen of Web Filter will appear, as shown by the image below:
Web Filter - Profiles
This session will cover how to register, edit and remove Web Filter profiles;
Next, we'll look at the functions located at the top of this panel.