Skyhigh Security Client Proxy consists of server and client software, whose deployment details depend on the management platform you are using.
Client Proxy is managed with Skyhigh Security ePolicy Orchestrator® (Skyhigh Security ePO™) , Skyhigh Security ePolicy Orchestrator® Cloud (Skyhigh Security ePO™ Cloud) , or Skyhigh Security Trellix ePO. While Client Proxy is a managed product, the user or client computers in your organization can be managed or unmanaged.
The server software adds the Client Proxy server functionality to the Trellix ePO, Trellix ePO Cloud, or Trellix ePO. Because the server software extends the management platform functionality, it is called the extension software or extension. It is also called the manager.
Client computers can be managed with Trellix ePO, Trellix ePO Cloud, or Trellix ePO. Managed client computers are called endpoints. Unmanaged clients are called standalone computers.
The deployment of the client software to the client computers depends on whether they are managed or standalone. The deployment of the Client Proxy policy also depends on whether the client computers are managed or standalone.
|Client Proxy policy
|Checked in to the Master Repository on a Trellix ePO, Trellix ePO Cloud, or Trellix ePO server as a package, then deployed to the endpoints
|Configured in the interface, then deployed to the endpoints
|Separately installed on the client computers
|Configured in the interface, then exported to an .opg file for saving locally on the client computers
This table summarizes how the server and client software is deployed when Client Proxy is managed with Trellix ePO, Trellix ePO Cloud, or Trellix ePO.
|Server software (extension)
|Client software (package)
|You install the extension software on the Trellix ePO server.
|You check in the client package to the Master Repository and deploy the package to the endpoints.
|Trellix ePO Cloud or Trellix ePO
|The extension software is preinstalled on the Trellix ePO Cloud or Trellix ePO server
|The client package is already checked in to the Master Repository. You need to deploy only the package to the endpoints.