Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Storage Accounts/46 of 115

3.9Ensure Storage for Critical Data are Encrypted with Customer Managed Keys

Control family: Storage Accounts

Control description

Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Azure Storage encrypts all data with Microsoft-managed keys. For critical data, a customer-managed key in Key Vault adds control: you decide who can use the key, can see every use, and can cut off access by disabling it. The key vault must keep the key safe from deletion (8.6).

Before you start

The same on every cloud, before the steps in the tabs.

  • List the storage accounts that hold critical data and so need a customer-managed key.

Evidence

  • The list of storage accounts that need customer-managed keys

On Azure the tasks prepare a key in Key Vault, switch each critical storage account to it in its encryption settings, and keep it checked with the CIS standard.

Task 1Prepare a key vault and key

  1. Sign in to the Azure portal at portal.azure.com and open Key vaults; choose or create a vault with purge protection on (8.6).
  2. Select Objects > Keys > Generate/Import, create an RSA key, and give it a rotation policy.
  3. In the storage account, turn on a managed identity under Security + networking > Identity (or plan a user-assigned identity).
  4. In the key vault, grant that identity the Key Vault Crypto Service Encryption User role.

Task 2Switch the account to the customer-managed key

  1. In the storage account, select Security + networking > Encryption.
  2. Set Encryption type to Customer-managed keys.
  3. Choose Select from key vault, pick the vault and key, and select the identity.
  4. Select Save.
  5. Check it: the Encryption page shows the key vault and key in use.

Task 3Keep it checked with the CIS v1.4.0 standard in Defender for Cloud

  1. Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
  2. Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
  3. Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 3.9.
  4. Open the assessment for Storage accounts should use customer-managed key for encryption and switch any critical account it lists, or record why it doesn't need one.
  5. Check it: every resource under recommendation 3.9 shows as passing after the next evaluation.

Evidence

  • Encryption of each critical account, showing its customer-managed key
  • The key vault settings, with purge protection on

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.