Azure Compliance ControlsAzure HPC Cache
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.
What this control checks
HPC Cache must have a keyEncryptionKey keyUrl and sourceVault id set (CMK), else alarm.
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