Bypass Categories - Console

Updated 3 hours ago by admin

Bypass Categories are similar to Custom URL Categories, except that they're used by agents to ignore something; for example, a domain, an IP range, a system process or SSL Interception. Bypasses are a powerful way to mitigate against applications that do not support proxying and to relax filtering where appropriate. Browse supports a large number of Bypass types, but there are variations between desktop agents and gateway agent support, which are described in this section.

Bypass Type

Behaviour

Agent support

Example

Bypass destination domain completely

Do not intercept HTTP or HTTPS traffic destined for the given domain

Windows, Mac, Gateway

domain.com

Bypass destination IP/CIDR completely

Do not intercept HTTP or HTTPS traffic destined for the given IP or CIDR

Windows, Mac, Gateway

10.0.0.5, 192.168.1.1/24

Bypass File Extension

Do not intercept HTTP or HTTPS traffic that has the specified file extension

Windows, Mac

.css, .js, .png

Bypass Executable/Process Name

Do not intercept HTTP or HTTPS traffic that is generated by the given executable or process (case sensitive, exact match)

Windows, Mac

DropBox.exe, itunes

Bypass destination domain for SSL Interception

Do not intercept HTTPS traffic destined for the given domain

Windows, Mac, Gateway

secureserver.com

Bypass destination IP/CIDR for SSL Interception

Do not intercept HTTPS traffic destined for the given IP or CIDR

Gateway

10.0.0.5, 192.168.1.1/24

Bypass source IP/CIDR completely

Do not intercept HTTP or HTTPS traffic originating from the given IP or CIDR

Gateway

10.0.0.5, 192.168.1.1/24

Bypass source IP/CIDR for SSL Interception

Do not intercept HTTPS traffic originating from the given IP or CIDR

Gateway

10.0.0.5, 192.168.1.1/24

Bypass source IP/CIDR for user authentication

Do not authenticate HTTP or HTTPS traffic originating from the given IP or CIDR

Gateway

10.0.0.5, 192.168.1.1/24

Bypass user authentication for destination domain

Do not authenticate HTTP or HTTPS requests destined for a particular domain

Gateway - explicit proxy

java.com

Bypass source MAC address for user authentication

Do not authenticate HTTP or HTTPS traffic originating from the given MAC address

Gateway (

70:85:C2:0E:E9:4E

Bypass HTTP Header

Do not intercept HTTP or HTTPS traffic if the specified HTTP header is matched

Windows, Mac

Content-Type: application/json

The key e.g. Content-Type can contain A-Z, a-z, 0-9, -, _

The value e.g. application/json can contain A-Z, a-z, _ :;.,/"'?!(){}[]@<>=-+*#$&`|~^%0-9

Bypass with Proxy Exception

Add the bypass pattern to the macOS proxy exceptions list

Mac

domain.com (without . prefix)- only bypass domain.com. Subdomains such as www.domain.com or app.domain.com will not be bypassed

.domain.com (with . prefix)- bypass all subdomains such as app.domain.com but not domain.com base domain

To bypass both the base domain and all sub-domains, add both patterns

You cannot exceed 70 patterns or 650 characters across all patterns, whichever limit is met first.
Bypass types and behaviour. In the console, each type appears in the Bypass Type list as: Domain – All, IP/CIDR – All, File Ext, Process, Domain – SSL, IP/CIDR – SSL, Src IP/CIDR, Src IP/CIDR – SSL, Src IP/CIDR – Auth, Auth – Domain, Auth – MAC, HTTP Header and Proxy Exception.

Managing Bypass Categories

In the console, go to Browse ⟶ Categories and open the Bypass tab.

The list shows each Bypass Category with its description, Bypass Mode and number of entries. Click the settings icon at the end of a row to see the bypass patterns in that category.

Searching

Use the search box above the list. Select Category to search category names, or Pattern to find the categories that contain a matching bypass pattern, then press Enter. Clear the search to return to the full list.

Adding a new Bypass Category

Click Add Category. In the new row, enter the details below and click the green + to save.

Name

A name for the new bypass category, plus an optional description.

Bypass Mode

The Bypass Mode decides how and when the bypass applies on a USS Gateway:

  • Direct Proxy: applies to direct connections to the proxy on port 8080 (for example via a browser configuration or WPAD).
  • Captive Portal: applies to transparently proxied connections (for example Captive/Guest portal, WCCP, gateway mode).
  • Hosted Gateway: applies to traffic through the Hosted (Mobile) Gateway, which supports the same bypasses as the USS Gateway.
  • Any: applies in all of the above modes.
  • None: the bypass is not applied to the USS Gateway.

Renaming and deleting Bypass Categories

Click the ⋯ menu at the end of the category's row and select Rename or Delete category.

Deleting a Bypass Category removes it from any Agent Configuration profiles that use it, and also deletes all the patterns in it.

Managing Patterns

In a Bypass Category, patterns are domains, IP addresses or ranges, processes and so on, as described in the bypass types table above.

Adding Bypass Patterns

  1. Click the settings icon at the end of the category's row. The Bypass Patterns panel opens, listing each pattern with its Bypass Type and description.
  2. Click Add Pattern, fill in the new row and click the green +.
Bypass Type

The bypass type to use, as described in the bypass types table above.

Pattern

The pattern to match against. Its format depends on the bypass type (see the table above).

Description

An optional comment or description for the pattern.

The Bypass Patterns panel has its own Toolbox button, so you can look up a URL while you edit the list.

Deleting Patterns

Hover over the pattern in the Bypass Patterns panel and click the delete (bin) icon at the end of its row.

Editing Patterns

Click a pattern in the Bypass Patterns panel to edit it in place, then press Enter to save it.

Using Bypasses in Agent Profiles

Bypass Categories are applied through Agent Configuration profiles to bypass filtering for particular domains, IP ranges or processes. Go to Browse ⟶ Agent Configuration, open the profile and select the Bypass Categories section. For example, you might add your company intranet to a bypass so that it is never filtered.


How did we do?