Deploying Remote Filtering Server and Client

For information about version compatibility, see the Version Equivalencies Between Forcepoint DLP and EIP Infrastructure/Web/Email Components.

With Forcepoint URL Filtering, you have the option to add the Remote Filter module to manage Internet activity for machines that reside or travel outside your network.
  • Remote Filtering Client is installed on each remote machine.
  • The client software communicates with Remote Filtering Server, which acts as a proxy to Filtering Service.

    Communication between the components is authenticated and encrypted. When you install remote filtering components:

  • Install Remote Filtering Server on a dedicated machine that can communicate with the Filtering Service machine.

    As a best practice, install Remote Filtering Server in the DMZ outside the firewall protecting the rest of the corporate network. This is strongly recommended.

  • Do not install Remote Filtering Server on the same machine as Filtering Service or Network Agent.
  • Each Filtering Service instance can have only one primary Remote Filtering Server.

    Remote Filtering Client system recommendations:

  • Pentium 4 or greater
  • Free disk space: 25 MB for installation; 15 MB to run the application
  • 512 MB RAM
Network Size Hardware Recommendations
1-500 clients

Windows or Linux

  • Quad-Core Intel Xeon 5420 or better processor, 2.5 GHz or greater
  • 2 GB RAM
  • 20 GB free disk space
500+ clients

Windows or Linux

  • Quad-Core Intel Xeon 5450 or better processor, 3.2 GHz or greater
  • 4 GB RAM
  • 20 GB free disk space

The following illustration provides an example of a Remote Filtering deployment. The illustration does not include all web protection components. For more information, see the Deploying the Remote Filter Module technical paper.