Endpoint General

The Endpoint General page provides installation settings for the Forcepoint Web Security Endpoint, which is built using the Forcepoint One Endpoint package builder.

The Forcepoint Web Security Endpoint can be deployed to your end users' workstations in order to direct web (HTTP/HTTPS) traffic to the Dynamic Edge Protection proxy service. Endpoint deployment supports roaming users, and remote offices that do not have a tunnel connection to the service.

Forcepoint Dynamic Edge Protection supports the Forcepoint Web Security Endpoint in a proxy connect deployment: all proxied web traffic is directed through the proxy service for inspection and policy enforcement.

The endpoint client identifies your account and the specific user, allowing policies to be applied to users, and user activity to be logged in reports. For example, you can create a policy for each site, and a separate policy for roaming users.

Note: For users with the endpoint client installed who connect to the service via a site connection (over an IPsec or GRE tunnel), the endpoint will enter "fallback" mode. This applies, for example, to users who are typically roaming, but who sometimes connect their device at a site location. Fallback mode temporarily bypasses the endpoint. Traffic is directed through the site's tunnel connection, and policies applied to traffic from the site will apply.

The following items are displayed on the Endpoint General page, which are required during Endpoint installation:

Table 1. Endpoint deployment settings
Field Description
Account token The account token code is unique to your account, and is used by the endpoint client to identify network requests from your organization's users. Use this token when deploying the client manually, or via a Windows Group Policy Object (GPO) or similar deployment method.
Configuration file template The HWSConfig.xml configuration file is used during endpoint installation to define installation settings for the client. This file must be placed in the same folder as the installation package.
As part of endpoint configuration, you must manually edit the following entries in the configuration file template to configure the appropriate settings for your account:
  • Hosted PAC file URL: this defines the location that will be used to retrieve the PAC file used by the endpoint client.
  • Account token: the account token identifies your account to the service.
  • Application bypass list (if required): a list of applications whose web traffic should be exempted from forwarding and inspection. Application executable file names are added as a pipe-separated list, using regular expressions.
  • Endpoint user control option (if required): defines whether users can temporarily disable the endpoint client, using the context options in the notification area.