Fornetix Key Orchestration Platform vs OpenStack Barbican

Fornetix Key Orchestration Platform centers on VaultCore, which automates enterprise encryption key management and lifecycle work across an organization. It supports policy-driven key rotation and enforcement, with access controls that combine attribute-based and role-based rules. Fornetix says VaultCore supports over one hundred million keys. It connects to KMIP-compatible systems, while Orchestration Gateway plugins translate non-KMIP integrations including AWS, Azure, and F5. VaultCore is available as a hardware, virtual, or cloud appliance. The gateway runs on Windows Server or Linux and provides REST API integrations. VaultCore provides Common Event Format logging and can respond to SIEM alerts, including Splunk alerts, with rapid rekeying. Fornetix describes support for compliance work involving GDPR, CCPA, HIPAA, PCI-DSS, and NIST 800, and integrations with HSMs such as nCipher; it cites FIPS 140-2 Level 3 certification for that combination. Pricing is by quote, and a full-featured 30-day trial is available. The company is headquartered in Frederick, Maryland.

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.