HSM Integration for Devolutions Server PAM Encryption Keys
1 vote
Our organization is evaluating Devolutions Server PAM as a self-hosted Privileged Access Management solution. One of our security requirements is that the master encryption keys used to protect the PAM vault should not be stored locally on the Devolutions Server host.
Currently, vault encryption keys are stored in the encryption.config file and protected locally by the operating system. While backup and recovery material can be stored externally, active encryption operations still rely on locally stored key material.
Provide native support for external key management and Hardware Security Module (HSM) integration for Devolutions Server encryption keys.
Examples of supported platforms could include:
Azure Managed HSM
Azure Key Vault Premium
PKCS#11-compatible HSMs
YubiHSM 2
Other enterprise key management solutions
Store the master encryption key or key-encryption key outside of the Devolutions Server host.
Allow Devolutions Server to perform cryptographic operations using externally managed keys.
Support key rotation and lifecycle management through the external key management platform.
Support High Availability deployments where multiple Devolutions Server instances can securely access the same key material.
Ensure the root encryption material is never stored locally in plaintext on application servers.
Improved protection of PAM vault encryption keys.
Reduced risk if a PAM server is compromised.
Better alignment with enterprise security architectures and zero-trust principles.
Support for compliance requirements and security frameworks such as:
TISAX
ISO 27001
NIS2
PCI DSS
Easier adoption in organizations that already use centralized key management services.
We are considering using Azure Managed HSM, Azure Key Vault Premium, or dedicated HSM devices such as YubiHSM 2 to protect PAM encryption keys. Native integration with these platforms would allow us to meet our internal security requirements while simplifying operational management of the PAM infrastructure.
We've taken note of this feature request and will update this thread once the work is planned.
Cheers,
Luc Fauvel