Integrating Web Security with Content Gateway

Applies to

Web Security Gateway v7.6

Integrating Web Security with Content Gateway

Websense Content Gateway™ is a central gateway for controlling Web content that offers:

u	The advantages of a proxy cache, improving bandwidth usage and network performance by storing requested Web pages and, if the page is still considered "fresh," serving the Web page to the requesting client.

Real-time content categorization. This feature examines the content of uncategorized sites and sites that include rapidly changing content, and then returns a recommended category to Filtering Service.

Websense Content Gateway can run in explicit or transparent proxy mode.

u	In explicit proxy mode, client browsers must be configured to point to Content Gateway.

u	In transparent proxy mode, the client request is intercepted and redirected to the proxy. Traffic is redirected through a router or a Layer 4 switch and the ARM (Adaptive Redirection Module) feature of Content Gateway.

Content Gateway can participate in flexible cache hierarchies, where Internet requests not fulfilled in one cache can be routed to other regional caches. Content Gateway also scales from a single node into multiple nodes to form a cluster, improving system performance and reliability.

Content Gateway is installed on a Linux machine, separate from other Websense components. See Websense Content Gateway for more information.

The following illustration shows Websense Content Gateway and Websense Data Security deployed with Websense Web filtering components (including Policy Broker, Policy Server, Filtering Service, User Service, and a transparent identification agent).

Data Security, Content Gateway, and Websense filtering component machines access network traffic through a router.

Network Agent is installed on a separate machine, attached to the span port on a switch.

The diagram provides a general overview and best practice location for your integration product, but does not show all Websense components. Larger networks require Websense components to be distributed across several dedicated machines.