Bloombase KeyCastle vs Oracle Cloud Infrastructure Secret Management

Bloombase KeyCastle manages cryptographic keys and certificate authority certificates, including private signing keys, public verification keys, authentication keys, and data encryption keys. It supports key creation, import, protected storage, verification, validation, inquiry, and deletion. Bloombase says keys stored in KeyCastle cannot technically be retrieved in plain form; its specifications say capacity is limited by available system storage, not a preset key count. Listed algorithms include AES, RSA, SHA hashes, Camellia, SEED, ARIA, and post-quantum options such as CRYSTALS-Kyber and CRYSTALS-Dilithium. KeyCastle supports PKCS#11 hardware security modules, OASIS KMIP, and a listed FIPS 140-2 compliant Bloombase Cryptographic Module. It connects with key services from AWS, Google, IBM, Microsoft Azure, and Oracle. Certificate functions include X.509 and PKCS#12 import and export, validity checks, retrieval, and revocation checks. Administration includes web and command-line consoles, central configuration, SNMP, and syslog. Optional high availability supports active-active or active-standby operation; recovery options include configuration backup and restore and recovery quorums. Pricing is on request, and Bloombase says customers may request a 30-day evaluation kit.

Oracle Cloud Infrastructure Secret Management stores, retrieves, rotates, and manages credentials used by applications and cloud environments. It supports database passwords, access tokens, third-party API keys, SSH private keys, application configuration secrets, and OAuth2 or JWT signing credentials. Administrators and applications can access secrets through APIs, SDKs, the CLI, and OCI Console. OCI Vault keys encrypt secrets, while OCI manages encryption, decryption, access control, and audit logging; OCI IAM policies provide granular permissions. Automatic rotation can run at intervals from one to 12 months and integrates with Autonomous AI Database and OCI Functions. Secrets can be replicated to as many as three destination regions, where replicas are read-only and inherit changes from the source. A tenancy can contain up to 5,000 secrets, with up to 30 active versions and 30 versions pending deletion per secret. The service is aimed at applications and cloud environments that need centrally managed secrets rather than credentials embedded in source code or configuration files. It is listed as free, though no price is provided.