CIS Microsoft Azure Foundations Benchmark v1.4.0/Database Services/69 of 115
4.6Ensure SQL server's TDE protector is encrypted with Customer-managed key
Control family: Database Services
Control description
TDE with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties.
With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security.
Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key).
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Transparent data encryption protects each database's encryption key with a TDE protector. Making that protector a customer-managed key in Key Vault means you control and audit its use, and can make the databases unreadable by revoking it. The protector is set at the server and every database inherits it.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which SQL servers need a customer-managed TDE protector, and who administers the keys, separately from database administrators.
- Agree how the key is rotated and what happens if it is lost or revoked.
Evidence
- The key management decision for SQL servers
On Azure the tasks prepare the key vault and key, set the server's TDE protector to that key, and keep it checked with the CIS standard.
Task 1Prepare the key vault and key
- Sign in to the Azure portal at portal.azure.com and open Key vaults; choose a vault with soft delete and purge protection on.
- Make sure the vault firewall allows trusted Microsoft services.
- Create or import an RSA key to use as the TDE protector.
- Give the SQL server's managed identity the Key Vault Crypto Service Encryption User role on the vault (or get, wrapKey and unwrapKey in an access policy).
Task 2Set the TDE protector to the key
- Open SQL servers, then the server, and select Security > Transparent data encryption.
- Choose Customer-managed key and select the key vault and key.
- Select Save.
- Check it: the page shows the customer-managed key as the TDE protector.
Task 3Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 4.6.
- Open the assessment for SQL servers should use customer-managed keys to encrypt data at rest and fix the resources it lists as non-compliant.
- Check it: every resource under recommendation 4.6 shows as passing after the next evaluation.
Evidence
- The Transparent data encryption page of each SQL server, showing the customer-managed key
- The CIS v1.4.0 standard, with recommendation 4.6 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
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.