Skip to main content

Signing & Integrity

This guide explains how Breeze Agent verifies installer authenticity, mutual authentication, transport security, signed operations, and update integrity

Software Authenticity​

  • Breeze Agent installers are signed using a code‑signing certificate so operating systems and security tools can verify their origin.
  • Always download installers from Cloudaware Admin to ensure you receive signed, verified artifacts.
  • Customers can review the installer and agent source code; Cloudaware avoids shipping opaque binaries where possible.

Mutual Authentication​

  • Breeze Agent presents a client certificate issued by Breeze Server.
  • Breeze Server presents its own server certificate, which is validated by the agent against the certificate bundled with (or trusted by) the installer.
  • Only when both sides validate each other successfully does the agent proceed to exchange data.

Transport Security​

  • All agent ↔ server traffic is sent over HTTPS with FIPS‑compliant encryption and signing algorithms.
  • If a proxy performs TLS interception, install the proxy CA root as trusted in the OS or via HTTP_CA_FILE, so the agent can validate the intercepted certificate chain (see Environment & proxy).

Cryptographic Operations & Updates​

  • Breeze cryptographically signs operations between the agent and the server to ensure:
    • Requests and responses are authentic.
    • Plugin payloads or results have not been modified in transit.
  • Plugins and agent updates are signed before distribution; Breeze Server validates signatures before making them available to agents.