CrystalKey 360 vs OpenStack Barbican

CrystalKey 360 is an API-based control layer for managing cryptographic policy and automating key lifecycles across hybrid environments. It supports governance of ownership, approvals, and evidence, and automates key rotation through API integrations. Native data-protection capabilities include tokenization, MACing, data masking, code signing, database encryption, encryption, and decryption. Logging across supported environments is intended to improve visibility, accountability, and evidence collection. The product is designed to work alongside existing cryptographic infrastructure, with integrations listed for HSMs from Thales, Utimaco, Entrust, and Futurex, as well as AWS, Azure, GCP, other cloud platforms, and supported key stores. Identified use cases include cryptographic estate consolidation, shared trust infrastructure, payment-key management, and preparation for algorithm transitions and key migration. It supports AES, 3DES, RSA, EC, and HMAC keys, with external key control through BYOK. Platforms include API, Linux, self-hosted, web, and Windows. Pricing is on request; prospective customers can request a demo or use-case discussion.

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.