HSM Vendors

HSM Vendors & Options — Buyer’s Guide

Compare on-prem and cloud HSM options with practical patterns for key custody, cloud HSM integration, enterprise PKI and cryptographic audits. Vendor-neutral advice; evidence-driven ceremonies.

We align to FIPS 140-3, PCI DSS 4.x, GDPR/UK GDPR and sector guidance. See US, Western Australia, and Europe region pages.

When should you use an HSM?

  • Root/issuing CA key custody for enterprise PKI (offline/online ceremonies, M-of-N).
  • Code/firmware signing, database TDE master keys, payment keys (PIN/EMV), and high-assurance cloud anchors.
  • Regulatory drivers demanding validated modules (e.g., FIPS 140-3).

On-prem HSM vendors (representative)

General purpose

Thales Luna HSM

General purpose

Entrust nShield

  • Network/PCIe; good developer tooling and code signing options.
  • Entrust nShield
General purpose

Utimaco SecurityServer

  • Network/PCIe; strong docs and payments options.
  • Utimaco HSM
Mainframe / payments

IBM Crypto Express (CEX)

We’re vendor-neutral; selection depends on APIs, throughput, residency, certification needs, existing tooling, and support model. Start with an environment audit.

Cloud HSM & KMS (managed)

  • AWS CloudHSM / KMS: dedicated HSM clusters and integrated KMS services — CloudHSMAWS KMS
  • Azure Key Vault & Managed HSM: multitenant Key Vault plus single-tenant Managed HSM — Managed HSMKey Vault
  • Google Cloud KMS / EKM: KMS with external key management options — Cloud KMSEKM
  • HashiCorp Vault (with HSM): Transit/PKI engines + HSM seal/integration — Vault

See our Cloud HSM Services and HSM Support Services for design, BYOK/KEK, rotations and ceremonies.

APIs & interoperability

  • PKCS#11 (OASIS): common crypto API across vendors — OASIS PKCS#11 TC
  • Microsoft CNG / KSP: Windows integration for key storage and ops — MS Docs
  • Java JCE/JCA: Java crypto providers and HSM adapters — Oracle JCE
  • OpenSSL engines/providers: app/library integration path — OpenSSL providers

We validate API support end-to-end (library versions, slot policies, mechanisms, key attributes, FIPS modes).

PQC considerations (planning ahead)

  • Assess vendor roadmaps for PQC (e.g., ML-KEM/ML-DSA) and firmware timelines; beware “one-click” claims — see our Quantum PKI Transition briefing.
  • Understand key forms (seed/expanded for ML-DSA) and PKCS#11 implications; see our explainer: Dual Private Keys & HSM Interoperability.
  • Run hybrid pilots, measure sizes/latency, check protocol/library readiness before committing.

Compliance & certifications

  • FIPS 140-3 validation: module assurance where policy requires — NIST FIPS 140-3
  • PCI DSS 4.x: keys for PAN data; rotations, DUKPT, evidence — PCI SSC
  • GDPR/UK GDPR: encryption & access control evidence — GDPRUK ICO

We don’t provide legal advice; we supply technical controls and artefacts so your compliance/legal teams can demonstrate conformity.

HSM vendors — FAQ

Do you recommend a single vendor?

No — we’re vendor-neutral. Selection depends on APIs, certification needs, workload patterns, residency and support.

Can you integrate HSMs with CLM and PKI?

Yes — Venafi, Keyfactor and EJBCA are common. See PKI architecture and audit services.

How do you handle ceremonies and evidence?

M-of-N, role segregation, tamper-evident artefacts, backup/restore validation — detailed in our HSM Services.