Web Security Gateway (software-based)

Web Security Gateway (software-based)

Applies to

Web Security Gateway v7.6

In this topic

Overview

Deployment

Installation

Initial configuration

Overview

This section contains information and instructions for a software-based deployment of Websense® Web Security Gateway. In this deployment scenario, all Websense components are installed on servers in your network. Components are typically distributed across several machines. For information about a Websense-appliance-based deployment, see Web Security Gateway (appliance-based).

Websense Web Security Gateway software consists of components that work together to monitor Internet requests, log activity, apply Internet usage filters, and report on activity. Websense software is highly-distributable, providing the flexibility to scale a deployment to suit your needs. Components can be installed together on one machine for smaller organizations; or they can be distributed across mutliple machines, and multiple sites, to create a high-performing deployment for larger organizations. The appropriate deployment is determined by network size and configuration, Internet request volume, hardware performance, and filtering needs.

The following illustration is a high-level diagram of a basic software-based deployment of Web Security Gateway. Note that this illustration is intended to show the general distribution of components and does not include network details (such as segmenting, internal firewalls, routing, switching, and so forth).

Microsoft SQL Server is used to store Websense data (including log and reporting data). SQL Server must be obtained separately; it is not included as part of a Websense subscription. When installing Websense components, SQL Server must be installed and running, typically on its own machine as shown above. SQL Server Express (installed using the Websense installer) may be used in place of SQL Server. However, it is a best practice to use SQL Server Express only in non-production or evaluation environments.

TRITON management server is the term used to refer to the machine on whichTRITON Unified Security Center is installed. This machine is used to manage your Websense deployment. It includes TRITON™ Infrastructure and any or all of the TRITON Unified Security Center modules (Web Security, Data Security, and Email Security). Additional components may also be installed on this machine. For example, Web Security Log Server and Real-Time Monitor (note that these components may be installed on another machine; they are not required to be located on the TRITON management server).

Websense filtering components may be installed on the same machine or distributed across several machines. Additionally, you can install multiple instances (on different machines) of certain components to scale to your organization's needs.

Websense Content Gateway is a Web proxy that passes HTTP, HTTPS, FTP over HTTP, and native FTP traffic to Websense software for filtering. Content Gateway Manager—the Web-browser-based management UI for Content Gateway—runs on the Content Gateway machine, but is typically accessed from within TRITON Unified Security Center.

Websense Remote Filtering Server is typically installed on its own machine in the network DMZ. Remote Filtering Server is used, in conjunction with Remote Filtering Client, to filter off-site users that are outside the corporate network (e.g., traveling personnel or telecommuters).

Deployment

Network considerations

Component limits and ratios

Required external resources

Deploying transparent identification agents

Maximizing system performance

Hardware recommendations for stand-alone deployments of Web Filter or Web Security

Remote Filtering Server and Client

Deploying Network Agent

Integrating Web Security with Content Gateway

Integrating Web Security with Microsoft ISA Server or Forefront TMG

Integrating Web Security with Cisco

Integrating Web Security with Check Point

Integrating Web Security with Squid Web Proxy Cache

Integrating Web Security with Citrix

Other integrations for Web Security

Web Security Distributed Enterprise Deployments

Installation

Complete the following main steps (the links go to detailed procedures or information for each step).

1.	Preparing for Installation

2.	Obtaining SQL Server

3.	Installing Web Security components

Important: Be sure to install Policy Broker and Policy Server before creating a TRITON management server (in the next step).

4.	Websense Content Gateway

5.	Creating a TRITON Management Server

Important: When following the instructions under Creating a TRITON Management Server, choose to install only the Web Security module of the TRITON Unified Security Center. When you reach the Installation Type screen of the Websense installer, select only Web Security (under TRITON Unified Security Center).

You can choose to install the other modules of the TRITON Unified Security Center. However, they will be enabled only if the subscription key you enter includes those features.

Initial configuration

Ports

Antivirus configuration

Disable Enhanced Security Configuration in Internet Explorer

Accessing the TRITON Unified Security Center

Entering subscription key

SQL Server 2008 R2 Express

Getting Started Help

Windows Server 2008

Logon script for Logon Agent

Messenger Service for Network Agent block messages

Administrator privileges for User Service, DC Agent, or Logon Agent

Configuring Transparent Identification

Network Agent and multiple NICs

Remote Filtering

Identifying Filtering Service by IP address

Starting Content Gateway Manager

Entering a subscription key for Content Gateway

Enabling SSL Manager in Content Gateway

Enabling WCCP for Content Gateway

Web Security Gateway (software-based)