Key Management with HSM, cloud KMS, and PKCS#11

The AIC Enterprise Privilege Suite™ from Analog Informatics Corporation encrypts every stored secret and lets you choose where the keys live: in software, in a hardware security module (HSM) through PKCS#11, or in a cloud Key Management service (KMS) key that you own. The same model works on premises, in the cloud, and in hybrid deployments. AIC Server uses AWS-LC as its default cryptographic library. AWS-LC holds a Federal Information Processing Standards (FIPS) 140-3 certificate.

These features are built into AIC Enterprise Privilege Suite™.

Short answers

What cryptographic module does AIC use?

AWS-LC, which holds a FIPS 140-3 certificate. We share the certificate on request. FIPS mode is fixed at build time and cannot be turned off. If you use an HSM or a cloud KMS key, that device or service carries its own FIPS certification, and you confirm the certification of each one you configure.

Where can the keys live?

In the platform secret store (software), on an HSM through PKCS#11, or in a customer-owned key in AWS KMS, Azure Key Vault Managed HSM, or Google Cloud KMS.

Can different zones of systems use different keys?

Yes. Each system group can have its own encryption key set, separate from the server default. A CUI enclave, a lab network, and business systems can each be protected by a different key, and each can be rekeyed on its own.

Can you rekey data that is already encrypted?

Yes. Rotate a key set, preview the change, and re-encrypt. Each stored value records which key protects it, so older data stays readable until re-encryption finishes. You can also move keys from software to an HSM, or from one HSM to a replacement, without downtime.

Which HSMs are supported?

Any HSM with a PKCS#11 library. The console includes profiles for Thales, SafeNet, Entrust nShield, Utimaco, Futurex, AWS CloudHSM, Azure Dedicated HSM, IBM Cloud HSM, YubiHSM, and open-source tokens.

Does AIC hold our cloud key?

No. You own the cloud KMS key and its access policy. AIC Server asks the key service to protect its data keys. If the cloud key cannot be reached or access is denied, AIC Server does not use it and raises a warning.

Deployment options

Deployment Key custody
On premises Network or PCIe HSM through PKCS#11
Cloud AWS CloudHSM or Azure Dedicated HSM through PKCS#11
Cloud Customer-owned AWS KMS, Azure Key Vault Managed HSM, or Google Cloud KMS key
Hybrid Software and HSM engines live together while keys move between them, with no downtime
Hybrid On-premises enclaves on an HSM and cloud enclaves on a cloud KMS key, with the same key model
Air-gapped Local PKCS#11 HSM with no cloud connection
Any Software key in the platform secret store, as the simple default

Key sets, rotation, and re-encryption

  • Server default key set plus named key sets per system group
  • Rotate a key set
  • Preview re-encryption (dry run)
  • Re-encrypt all data, or one group's data
  • Rewrap all secrets after an engine change, without re-encrypting content
  • Move encryption keys from software to an HSM
  • Replace an HSM token from a wrap-only backup
  • Maximum key age with a rotation warning
  • Two-person approval for sensitive key actions
  • Smart card (PIV/CAC) sign-in required for key administrators
  • Every key action audited to the audit log, Windows Event Log, and syslog

Supported HSM vendors

Vendor Products
Thales Luna Network HSM, CipherTrust Cloud HSM
Thales (SafeNet) SafeNet Network HSM, Data Protection On Demand
Entrust nShield (formerly nCipher), KeyControl Cloud
Utimaco CryptoServer, CloudHSM
Futurex KMES, VirtuCrypt Cloud HSM
Amazon Web Services AWS CloudHSM, AWS KMS
Microsoft Azure Dedicated HSM, Azure Key Vault Managed HSM
Google Google Cloud KMS
IBM IBM Cloud HSM
Yubico YubiHSM, through its PKCS#11 library
Open source OpenSC, OpenHSM, and SoftHSM2 for testing

Any other HSM that provides a PKCS#11 library can be registered as a new vendor.

Hardware Security Module (HSM) vendors

ThalesEntrustUtimacoFuturexIBM Cloud HSMYubico YubiKeyPKCS#11Amazon Web ServicesMicrosoft AzureGoogle Cloud

All logos and trademarks are the property of their respective owners. Their use does not imply endorsement.

FIPS 140-3

Where the cryptography runs Validation
Inside AIC Server AWS-LC, which holds a FIPS 140-3 certificate. We share the certificate on request
On an HSM The HSM's own FIPS certificate for its model and firmware. You confirm it for your configuration
In a cloud KMS The provider's certificate for the service tier and region. You confirm it for your configuration

Screenshots

Screenshots come from a demonstration system. Host names, account names, and network addresses are replaced with sample values.

Encryption runs in AWS-LC and can move to an HSM.
Each key set can be rotated, and stored data re-encrypted after a preview.
A separate key set can be created for each zone of systems and assigned to its system group.
Built-in PKCS#11 profiles cover on-premises and cloud HSMs from the major vendors.

Validate Your Key-Custody Requirements

  1. Choose the software, hardware security module, or cloud key service for a test deployment.
  2. Review the assigned key set and preview a rotation or re-encryption operation.
  3. Verify access to the protected data and inspect the recorded key-management activity.

See These Controls in Action

Request a personal demonstration focused on your systems, requirements, and the tasks your team needs to perform.

Request a Demo