Web Exceptions

Web Exceptions apply block, allow and bypass, or continue actions for URL requests that match specified Web Categories and URL Lists. Exceptions can be applied to specified traffic sources.

Exceptions can be used to grant permission to access specific resources for certain users within your organization (based on source IP address). For example, if the Social Networking category is blocked by your policy, you can create an exception that allows access to this category for specific source addresses.

Exceptions always override Web Category rules. Web exceptions are applied in order, with the highest priority rule applied first. The first matching rule is applied, and no further rules are used.

A web exception rule consists of the following elements:

Web Category/URL List: Web Categories and URL Lists to which the exception will apply. By default, the exception applies to requests to any website for requests to which the exception applies.
Applies To: defines the source for the web request to which the exception will apply. By default, the exception applies to web requests from any source to which the policy applies.
Action: the action applied to matching traffic. Rule actions are:
- Allow and bypass: allows traffic and bypasses further inspection. Traffic is not decrypted, and no further policy processing stages are applied.
- Block: blocks matching traffic by terminating the session. No further policy processing is performed.
- Continue inspection: this action allows matching traffic, and applies all further policy processing stages.
Web Exceptions are applied in order, with the highest priority rule (priority 1) applied first. The first matching rule is applied, and no further rules are used.

Web Exceptions are applied in the priority order in which they appear in the list.

Web Exceptions are matched before Web Category rules.