HPC Cache accounts should use customer-managed keys for encryption
Manage encryption at rest of Azure HPC Cache with customer-managed keys. By default, customer data is encrypted with service-managed keys. Customer-managed keys enable the data to be encrypted with an Azure Key Vault key created and owned by you.
By default, customer data is encrypted with service-managed keys, but customer-managed keys are commonly required to meet regulatory compliance standards. Customer-managed keys enable the data to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management.
What this control checks
HPC Cache must have a keyEncryptionKey keyUrl and sourceVault id set (CMK), else alarm.
Common pitfalls
Default is service-managed keys
By default, customer data is encrypted with service-managed keys.
Identity type must also exist
The policy applies its effect when identity.type does not exist. It also applies its effect when Microsoft.StorageCache/caches/encryptionSettings.keyEncryptionKey.sourceVault.Id does not exist.
Audit evidence
Evidence that deployed resources meet this control: Azure Policy compliance results for the built-in policy definition "HPC Cache accounts should use customer-managed key for encryption" (970f84d8-71b6-4091-9979-ace7e3fb6dbb); PowerPipe control azure_compliance.control.hpc_cache_encrypted_with_cmk.
Framework-specific interpretation
NIST SP 800-53 Rev 5: Mapped to SC-12 (Cryptographic Key Establishment and Management).
FedRAMP Moderate Baseline Rev 4: Mapped to SC-12 (Cryptographic Key Establishment And Management).
Framework mappings
The clauses this control is mapped to in each framework.
- Cryptographic Key Establishment And Management (SC-12)
FedRAMP Moderate Baseline Rev 4
- SC-12 Cryptographic Key Establishment And Management
- 3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems
- 2.1.1.2.1 Ensure Critical Data is Encrypted with Customer Managed Keys (CMK)
- SC.L2-3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems
- SC-12 Cryptographic Key Establishment And Management
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
hpc_cache_encrypted_with_cmk - Powerpipe Control:
azure_compliance.control.hpc_cache_encrypted_with_cmk - Azure Policy Definition:
970f84d8-71b6-4091-9979-ace7e3fb6dbb
Last reviewed: 2026-10-13