Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Forwarding traffic
Forwarding traffic
Getting Started Guide | Forcepoint Web Security Cloud
In order for Forcepoint Web Security Cloud to filter your traffic, web requests must be redirected to the cloud service. There are a number of methods available to redirect traffic.
During the initial stages of an evaluation or while testing a deployment, we recommend that you manually configure a number of web browsers to use the Forcepoint Web Security Cloud PAC file to forward traffic to the service. This is described in PAC file.
The following table outlines all the traffic redirection methods available, which may be suitable for different organizations and different network environments.
PAC file
A proxy auto-configuration (PAC) file defines how web browsers choose an appropriate proxy for fetching a given URL. The Forcepoint Web Security Cloud PAC file contains a number of global settings and includes any exclusions you add (for example, intranet sites) that should not use the cloud proxy.
All supported browsers have the ability to use PAC files. PAC files can be configured manually, or delivered via Windows GPO, or similar.
When configuring browsers to download the PAC file, you can specify either the standard PAC file URL or a policy-specific PAC file URL.
Example standard PAC file URL (HTTPS):
Example policy-specific PAC file URL (HTTPS):
(Where xxxxxx is a unique policy identifier.)
For more information on PAC files, see Proxy auto-configuration (PAC) in the Web Security Cloud help.
Forcepoint Endpoint clients run in the background on end user devices, providing a seamless browsing experience. Endpoint automatically authenticates users with the service, and provides policy enforcement and data security features. The endpoint client has been designed to consume minimal CPU, memory, and disk resources, and has tamper controls to prevent users disabling the software.
The endpoint client allows administrators to create policies that provide user-specific policy enforcement, with seamless authentication, full visibility of inbound and outbound traffic, and that don't restrict use of the device.
There are three versions of the endpoint client, each suited to different sets of end user needs:
Neo: this endpoint client can be used in either proxy connect mode or direct connect mode, and can automatically switch from one to the other when necessary.
Proxy Connect: also known as Classic Proxy Connect endpoint, this endpoint client redirects all traffic to the cloud proxy for analysis. Proxy Connect is recommended for most scenarios, and supports the widest set of security features.
Direct Connect: also known as Classic Direct Connect endpoint, this endpoint client contacts the cloud service for each request to determine whether to block or permit a website, but routes the web traffic itself directly to the Internet. Direct Connect also routes traffic to the cloud service to perform content analysis, if configured in your policy. Direct Connect is recommended for scenarios in which proxy connections may be problematic, and in some circumstances can improve content localization.
The following diagram illustrates the connectivity for Proxy Connect (through Neo or the Classic Proxy Connect endpoint) and Direct Connect (through Neo or the Cassic Direct Connect endpoint).
The diagram shows the two different endpoint versions servicing a web request:
If required, you can deploy a combination of Proxy Connect and Direct Connect endpoints in your organization. However, only one classic endpoint instance (Classic Proxy Connect or Classic Directory Connect) can be installed on a client machine at any one time. The Neo endpoint agent includes both proxy connect and direct connect modes.
For more information about Forcepoint Endpoint software, including deployment options and configuration settings, see Web endpoint overview in the Web Security Cloud help.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Forwarding traffic
Copyright 2022 Forcepoint. All rights reserved.