This yields an overall availability of 95%-99%.
Eliminating the Single Point of FailureUnbound Tech completely eliminates the single point of compromise for the most sensitive assets, ensuring keys and secrets are never kept whole (as they used to be protected inside HSMs in the past). Unbound implements multi-party computation (MPC) to create and use the fragmented secret without ever unifying it, in a method mathematically proven to be impossible to a breach or hack of any single location. The Unbound Key Control (UKC) system is comprised from one or more pairs of standard servers that are installed and managed by the user. Each of these pairs is comprised of an Entry Point and a Partner. Together, they form the secure boundary of the UKC. To satisfy the minimum high availability requirements two pairs must be used, comprised of four servers. Applications within the network connect to the entry point for consuming cryptographic services for the keys that are managed within the UKC. UKC provides a solution with high availability, meaning that no single server failure stops UKC functionality. An aspect of high availability is the existence of a Disaster Recovery (DR) or Continuity of Business (COB) site that takes over once the main site fails. While such a site is not required to be online as long as the main site is functional, it does need to stay connected and data synced with the online system, so that it can take over as needed with up-to-date key material. Measured UKC software server availability is 99.9%. Hence, the single pair UKC availability would be 99.8% (since Entry Point and Partner are operating in series). The following table demonstrates the availability of the UKC service per certain number of pairs running in parallel: With just 2 UKC pairs (a total of 4 servers) one can reach an availability level typically feasible only for telecom grade equipment (between five and six nines). With 3 UKC pairs (a total of 6 servers) availability level of IaaS/PaaS service is reached. UKC with 3 pair has 10.5 nines of availability (!), compared to AWS S3 with 11 nines.
Use CasesThe high-end level of key management and cryptographic keys availability is paramount for services serving a large number of end-users. Such cryptography consuming services include:
- Code signing for a SaaS / large enterprise
- Protecting SSL keys for hosted websites provider
- Document signing for a SaaS / large enterprise
- Securing payments transactions for a bank
- PGP within an organization
- IPsec for a telecom / SP network
- Smart metering for a water / gas / electrical utility
- File-level encryption for endpoint devices in an enterprise
Deployment Options Improving High AvailabilityThe location of the UKC cluster nodes is determined according to the application architecture, locations of the users consuming services and regulatory compliance aspects. The following figure depicts several possible topologies that allow to create an elaborate high availability scheme, such as locating the UKC nodes:
- On-prem – in the DC and the DR sites
- Hybrid – on prem and at the CSP
- Single CSP – across different regions / availability zones
- Different CSPs – a node per each CSP (at least)