Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Introducing Remote Filtering Software > Deployment information
Deployment information
Remote Filtering Software | Web Security Solutions | Versions 7.7, 7.8
Related topics:
*
System requirements
*
How remote filtering works
When you install remote filtering software, observe the following guidelines:
*
Install Remote Filtering Server:
*
Inside your organization's outermost network firewall
*
In the DMZ outside the firewall that protects the rest of the network
*
On its own, dedicated machine
This machine must be able to communicate with Websense Filtering Service and with the remote machines outside the network firewall. The Remote Filtering Server machine need not be joined to a domain.
*
Do not install Remote Filtering Server on the same machine as Filtering Service or Network Agent.
*
Make sure that Content Gateway, Network Agent, or your third-party integration product is configured to ignore (not filter) requests going to or from the Remote Filtering Server machine.
*
Make sure that Network Agent is not configured to "Log HTTP requests" (configured on the Settings > Network Agent > Local Settings > NIC Settings page in the Web Security manager).
*
Install only one primary Remote Filtering Server for each Filtering Service in your network.
*
To provide a failover option for the primary Remote Filtering Server, install optional secondary and tertiary Remote Filtering Server instances. Configure each of these Remote Filtering Server instances to communicate with the same Filtering Service.
*
Configure each Remote Filtering Client to connect to the backup servers in case of server failure. Remote Filtering Clients connect to only one Remote Filtering Server at a time.
Remote filtering software supports VPN connections, including split-tunneled VPN.
*
Remote Filtering Client manages all requests that go through a network adapter that is not connected to the internal network.
*
Websense software has tested split-tunneling for the following VPN clients: Cisco Anyconnect 2.5 and 3.0, Juniper/Netscreen, Microsoft PPTP.
The following diagram provides a rough sketch of a typical remote filtering software deployment, including port assignments (does not show all Websense components). See the Deployment and Installation Center (version 7.7 or version 7.8) for comprehensive deployment information for all Websense TRITON solutions.
 
* 
Important 
The heartbeat port, 8800, must be blocked at the external firewall.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Introducing Remote Filtering Software > Deployment information
Copyright 2016 Forcepoint LLC. All rights reserved.