Technical Library
|
Support
Installing Web Security solutions
> Installation overview: Web Security Gateway
Installation overview: Web Security Gateway
Deployment and Installation Center | Web Security Solutions | Version 7.7.x
Applies to:
In this topic
Web Security Gateway v7.7.x
Deployment
Installation
Initial configuration
This section contains information and about installing Websense Web Security Gateway software components. If your deployment also includes one or more V-Series appliances, additionally refer to
Installing appliance-based Websense solutions
.
Websense Web Security Gateway is highly-distributable, providing the flexibility to scale a deployment to suit your needs. 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 Web Security Gateway reporting data. When you install Websense Log Server (the main reporting component), SQL Server must be installed and running. (In very small deployments, or for evaluation, SQL Server Express, installed using the Websense installer, may be used.)
The TRITON management server hosts the Web-based management console (the TRITON Unified Security Center), including both infrastructure and TRITON - Web Security components. The TRITON Unified Security Center (TRITON console) is used to configure, manage, and report on your Websense software.
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. It resides on a Linux server or a V-Series appliance. Content Gateway Manager—the management console for Content Gateway—runs on the Content Gateway machine, but can be accessed from the TRITON console.
Deployment
Deploying Web Security core components
Extending your Web Security deployment
Web Security required external resources
Maximizing Web Security system performance
Deploying transparent identification agents
Hardware recommendations for standalone Web Security deployments
Deploying Remote Filtering Server and Client
Deploying Web Security for a distributed enterprise
Installation
Complete the following main steps (the links go to detailed procedures or information for each step).
1.
Preparing for installation
2.
Obtaining Microsoft SQL Server
3.
Installing filtering components on one or more machines
For Windows, see
Installing Web Security components
.
For Linux, see
Installing Web Security Components on Linux
.
For V-Series appliances, see
Installing appliance-based Websense solutions
.
Important
: Install Policy Broker, Policy Server, and Filtering Service or the full policy source appliance before installing other components.
During Filtering Service software installation (if applicable), be sure to specify that Filtering Service will be integrated with Websense Content Gateway.
4.
Installing Websense Content Gateway
5.
Creating a TRITON Management Server
Important
: When you reach the
Installation Type
screen, select only
Web Security
under TRITON Unified Security Center.
Initial configuration
Websense TRITON Enterprise default ports
Excluding Websense files from antivirus scans
Initial Configuration for All Websense Modules
Web Security initial configuration
Using BCP for log record insertion with SQL Server 2008
Content Gateway initial configuration
Installing Web Security solutions
> Installation overview: Web Security Gateway
Copyright 2016 Forcepoint LLC. All rights reserved.