OpenKCM (Open Key Chain Manager) vs QuintessenceLabs Trusted Security Foundation

OpenKCM (Open Key Chain Manager) is a free, open-source key management service for governing encryption keys and protecting data at rest. It supports BYOK key import and HYOK, which keeps master keys in a customer’s infrastructure. Its recursive L1–L4 hierarchy makes data keys dependent on higher-level keys. Governance and policy control are handled by CMK, while Krypton performs cryptographic execution; applications request key operations through the KMIP API.

The Gateway is designed to run near applications, such as in Kubernetes or a cloud VPC, and the same software can operate across AWS, Azure and on-premise environments. Customer root keys can remain in AWS, Azure or GCP key services, or on-premise HSMs, while OpenKCM holds a reference to the L1 key. A kill switch can halt downstream key use by removing that reference or revoking the root key. CMK connects to a corporate identity provider and sends audit logs to SIEM systems. The project’s CMK and Krypton components are actively being developed; encryption and decryption operations are in progress, while audit export, high availability and disaster recovery are planned for 2027.

QuintessenceLabs Trusted Security Foundation (TSF) is a centralized manager for cryptographic keys and policies across the key lifecycle. It is offered as a virtual machine or hardware appliance; TSF 100 virtual appliances can run locally or on AWS, Azure, and GCP. Product materials describe policies for objects and users, plus replication across up to 16 nodes. The TSF range supports OASIS KMIP and has been tested with products from IBM, HP, Oracle, and NetApp. Listed capabilities cover one-time pad, symmetric and asymmetric ciphers, key derivation, random objects, certificates, and selected cryptographic operations. Administrators can use web HTTPS or command-line SSH interfaces. The product sheet states support for thousands of end-client systems, tens of millions of keys, and 8,000 key requests per minute per node. The maker says TSF 400 contains an Entrust nShield XC FIPS 140-3 Level 3 validated HSM as a root of trust. TSF is under evaluation for Common Criteria NDcPP compliance. The maker also states that its key management application is compliant with NIST SP 800-57 where applicable. Pricing is available on request, with configurations tailored to different needs.