Hashicorp Vault and Barbican (Openstack security API) are probably the two best-known options. Linux administrators are probably familiar with a basic example in the form of KeyBox, which manages SSH keys. If you stand up a KMS whose purpose is to store, track and make available encryption keys for your own internal-use applications, it is easier to secure access such that you can trust the KMS and its keys. Key management on a global scale is hard, but it's easier within the scope of a single organization. Applications such as web browsers and components within operating systems have lists of certification authorities they trust. SSL certificates are tied to a certification authority that vouches for their authenticity to varying degrees. In one sense, the entire SSL certificate authority mechanism is key management. It's impossible to do without involving both trust and adherence to some form of standards at some point, limiting the real-world uses of large-scale key management. This isn't because it's difficult to encrypt an email, it's because key management – keeping everyone's keys sorted, verifying keys are still current, belong to the right individual or application, etc – is difficult to organize. You'll note that PGP encryption of email isn't exactly popular. Microsoft has an enterprise licensing management system they call KMS, and the early versions of it were pretty buggy. The undeserved portion comes largely from Microsoft. Some of the frustrations with KMSes is deserved, and some isn't. This has led to the growing popularity of key management as a service (KMaaS). Key management of public key infrastructure (PKI) is an option for privacy, but key management servers (KMSes) are notoriously miserable to set up and maintain. It has used zero knowledge encryption as the basis for its cloud storage platform. The service is designed so that Sync (the company) couldn't crack open your Sync account and root around inside, even if they wanted to. Another option is Canadian Dropbox alternative.
0 Comments
Leave a Reply. |