Popular topics

Explore all topics

Other helpful resources

Account usage

Your account page displays usage statistics of the Hopr sidecars you have deployed.

Frequently asked questions

Answers to the questions we hear most often.

Frequently asked questions

Can’t find the answer you’re looking for? Reach out to our customer support team.

Explore all FAQs

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).

Is the CHIPS™ algorithm dynamic enough to seed the key generator?

There is a significant amount of dynamism (variability) in the seed elements used in CHIPS algorithms. It begins with a vast number of URLs where dynamic information can be found, and increases with the many possible locations at an URL. It increases further because algorithms have many possible structures to alter or modify the dynamic elements. This includes nearly two-dozen variables, each of which has many possible values.

What is Hopr’s product security testing process?

Hopr employs continuous security testing from initial development and throughout the CE/CI lifetime of its product lines. In addition to GitLab’s state-of-the-art secure software development tools, GitLab’s code scanning processes, such as Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), Container Scanning, and Dependency Scanning can quickly identify the latest known security vulnerabilities in Hopr’s product code throughout the DevSecOps cycles.

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.