More Info:

Ensure that your Azure virtual machine disk volumes are using customer-managed keys (also known as Bring Your Own Keys - BYOKs) instead of service-managed keys (default keys used by Microsoft Azure for disk encryption), in order to have a more granular control over your VM data encryption/decryption process.

Risk Level

High

Address

Security

Compliance Standards

HITRUST, SOC2, NISTCSF, PCIDSS

Triage and Remediation

Remediation

To remediate the misconfiguration of not using BYOK for disk volume encryption in Azure, follow these steps:

  1. Log in to the Azure portal (https://portal.azure.com/).
  2. Navigate to the “Key Vaults” menu and create a new Key Vault if you do not have an existing one.
  3. In the “Key Vaults” menu, select the Key Vault that you want to use for BYOK.
  4. In the Key Vault, select the “Keys” menu and create a new key.
  5. Provide a name for the key, select “RSA” as the key type, and provide a key size of at least 2048 bits.
  6. Select the “BYOK” option under “Key Options” and provide the URI of your on-premises key management service (KMS).
  7. Save the key and take note of the key identifier (URI) for later use.
  8. Navigate to the “Disks” menu and select the disk that you want to encrypt using BYOK.
  9. Under the “Encryption” tab, select “Disk encryption set” and click “Create new”.
  10. Provide a name for the disk encryption set and select the Key Vault that you created in step 2.
  11. In the “Key management” section, select “Bring your own key (BYOK)” and provide the key identifier (URI) that you noted in step 7.
  12. Save the disk encryption set and wait for the encryption process to complete.

By following these steps, you have successfully remediated the misconfiguration by using BYOK for disk volume encryption in Azure.