Do both workloads (client and server) in a connection need a Hopr Sidecar?
Yes. A Hopr Sidecar must be configured and deployed with each workload for a Synchronous Ephemeral Encryption (SEE) communication channel to be built in point-to-point communication sessions.
How is key generation for SEE™ synchronized?
Sidecars self-synchronize during secrets construction using their CHIPS™ algorithm. The client (the initiating workload) in a communication session builds its symmetric key first and the server (the workload receiving the encrypted client message) builds its symmetric key when the encrypted message is received (at nearly the same time as the client built its key).
What is a "workload"?
"Workloads" is a general term for machines and devices that operate throughout the cloud. It includes VMs, containerized infrastructure, mobile devices, and IoT. When Hopr uses the term in the context of "protecting workloads, APIs, and data" we are referring to containerized workloads in systems such as Kubernetes or Docker. But our products are not limited to those systems only.
Stay in touch with us
Sign up for our awesome newsletter! No spam ever.
Thank you! Your subscription is confirmed.
Oops! Something went wrong while submitting the form.
