Forcepoint Endpoint Context Agent packages made via the package builder
Windows packages created with the package builder contain a single executable file: FORCEPOINT-ONE-ENDPOINTx64. exe. To deploy the Forcepoint ECA installation package in your environment, you must complete the following procedures:
- Authenticate Forcepoint ECA using client certificates
The Forcepoint NGFW Engine uses a client certificate to authenticate endpoint machines running Forcepoint ECA. In this procedure, you must establish a certificate authority (CA) for Forcepoint ECA, create the client certificate template, then deploy a unique client certificate to each endpoint machine.
- Configure Forcepoint ECA settings in the Security Management Center (SMC)
In this procedure, you must configure the initial Forcepoint ECA settings in the SMC to create a configuration file. This configuration file is added to the installation package through the package builder.
- Deploy Forcepoint ECA to the endpoint machine
In this procedure, manually install Forcepoint ECA on the endpoint machine.
- Copy the executable file to the endpoint machine.
- Double-click the executable file and step through the installation wizard
Forcepoint ECA Evaluation
Forcepoint ECA can also be deployed to a limited set of endpoint machines using the ECA Evaluation deployment option. This deployment option is beneficial for customers who wish to evaluate Forcepoint ECA without deploying the Forcepoint ECA software enterprise-wide.
With ECA Evaluation, all of the required certificates for communication between endpoint machines and the NGFW Engine are created automatically. After enabling the ECA Evaluation feature, a web app is hosted on the management server. On each endpoint machine, users can browse to the web app, then download and install the Forcepoint ECA software and the necessary certificates. Windows administrator rights are required for installing Forcepoint ECA on the endpoint machine.
For instructions about deploying Forcepoint ECA for evaluation purposes, see Knowledge Base article 16193.