Azure Compliance ControlsAzure Batch
Batch accounts should use customer-managed keys to encrypt data
Use customer-managed keys to manage the encryption at rest of your Batch account's data. Customer-managed keys enable the data to be encrypted with an Azure Key Vault key created and owned by you. You have full control of the key lifecycle.
What this control checks
Checks whether Batch accounts are set up to encrypt data with customer-managed keys
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:
batch_account_encrypted_with_cmk - Powerpipe Control:
azure_compliance.control.batch_account_encrypted_with_cmk - Azure Policy Definition:
99e9ccd8-3db9-4592-b0d1-14b1715a4d8a
Last reviewed: 2026-10-11