OpenStack Barbican vs QuintessenceLabs Trusted Security Foundation

OpenStack Barbican is the OpenStack Key Manager service for storing, provisioning, and managing secrets such as keys, certificates, passwords, and raw binary data. Its barbican-api component provides an OpenStack-native REST API for managing secrets; barbican-worker and barbican-keystone-listener are also part of the service. The listener manages Barbican’s database records for Keystone projects when those projects are deleted. A plugin architecture lets operators connect software secret stores or hardware such as HSMs. Documented options include KMIP, Dogtag, and Vault secret-store plugins, as well as PKCS#11 crypto plugins. With PKCS#11, master encryption and HMAC keys can reside in an HSM. Operators can develop plugins for storage, generation, and event handling, though support status may be stable, experimental, or out-of-tree. The default Simple Crypto plugin stores its single encryption key in plaintext in barbican.conf, so service-node access must be restricted carefully. Container ACL settings do not carry over to associated secrets, and ACL functionality requires Keystone integration. Barbican is free under Apache 2.0; installation guidance assumes a working OpenStack deployment.

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.