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).
How do Hopr's products meet Zero Trust principles?
Zero Trust requires verification of trust. Hopr rotates workload identity and secret credentials at a high frequency with our CHIPS™ technology and the SEE™ protocol. Hopr verifies both credentials at the start of each session to guarantee the authenticity and trust of both workloads in a communication session. Hopr's products meet 6 of the 7 NIST principles for zero trust. We intentionally do not monitor data traffic (principle #7) because we believe this increases cyber risk to PII and other sensitive data.
What is Hopr’s overall security strategy and approach?
Hopr is dedicated to ensuring that security is a paramount priority from corporate operations to product development to customer services and support. Hopr’s overall strategy for security is to make significant use of outsourced SaaS such as Google Workspace for sensitive corporate business applications and GitLab for all of Hopr’s SW product development. These SaaS services provide secure applications and storage, maintained by the SaaS providers. That said, Hopr still maintains and follows an overall Security Framework that includes our outsourced SaaS approach as well the rest of our company and employee’s work environments, tools, and work processes.
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.
