Populating the endpoint content in the compliance page

The PowerSC GUI server and PowerSC GUI agent communicate with the endpoint to discover the compliance level.

Upon startup, and intermittently until successful, the agent attempts to initiate contact with the PowerSC GUI server. When contact is established, a one-time agent-server security handshake is performed. After the agent-to-server security handshake is successfully negotiated the first time, the server creates a domain element with a Unique Identifier (UID) for internal representation of the endpoint, and passes the UID back to the endpoint. The UID is then included with all communication from the agent to the server. This action completes the discovery process. The PowerSC GUI server and the endpoint can communicate securely in either direction.

After completion of the initial discovery handshake, or after the PowerSC GUI agent is restarted, the PowerSC GUI agent attempts to determine the current compliance status information for its endpoint and updates the PowerSC GUI server. The existence of the endpoint and the current compliance information is used to populate the compliance status page of the PowerSC GUI. If no compliance status information can be determined, the entry is not available in the compliance status page.

The PowerSC GUI server contains a representation of all known endpoints, which are automatically created as a result of the initial agent-server connection and communication. As the endpoint agents track changes in the compliance status of the endpoint, the changes are passed to the server and retained. All user interaction from the PowerSC GUI with an endpoint is performed through the PowerSC GUI server. The user interface does not interact directly with any endpoint or endpoint agent.