General Deployment Recommendations for Web Security > Remote Filtering Server and Client
|
For all Web Filter and Web Security solutions, you can monitor computers outside your network using remote filtering components. The Remote Filtering Client must be installed on each remote machine.The remote clients communicate with a Remote Filtering Server, which acts as a proxy to Filtering Service. This communication is authenticated and encrypted.
If you have Websense Web Security Gateway Anywhere, you can also use the hybrid service to monitor users outside your network. This does not require software installation on remote machines. See Web Security Gateway Anywhere (software-based) or Web Security Gateway Anywhere (appliance-based) for more information.
The Remote Filtering Server should be installed on a dedicated machine that can communicate with the Filtering Service machine.
Do not install any Websense component on a domain controller.
As a best practice, the Remote Filtering Server should be installed inside the outermost firewall, in the DMZ outside the firewall protecting the rest of the corporate network. This is strongly recommended.
See System Requirements, for operating system requirements for Remote Filtering Server.
Windows or Linux
Quad-Core Intel Xeon 5420 or better processor, 2.5 GHz or greater
2 GB RAM
20 GB free disk space Windows or Linux
Quad-Core Intel Xeon 5450 or better processor, 3.2 GHz or greater
4 GB RAM
20 GB free disk space
Free disk space: 25 MB for installation; 15 MB to run the application
512 MB RAMThe following illustration provides an example of a Remote Filtering deployment. The illustration does not include all Websense components. For more information, see the Websense Remote Filtering Software technical paper.
General Deployment Recommendations for Web Security > Remote Filtering Server and Client
|