CIS Microsoft Azure Foundations Benchmark v1.4.0/Database Services/51 of 115
4.1.2Ensure that 'Data encryption' is set to 'On' on a SQL Database
Control family: Database Services
Control description
Enable Transparent Data Encryption on every SQL server.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Transparent data encryption encrypts a database's files, backups and logs at rest, so a copied file or backup can't be read. It is on by default for new Azure SQL databases, but older ones, or ones where someone switched it off, need checking.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that every Azure SQL database is encrypted at rest, and that turning encryption off needs an approved exception.
Evidence
- The database encryption standard
On Azure the tasks turn on transparent data encryption for each database, then keep it checked with the CIS standard.
Task 1Turn on transparent data encryption
- Sign in to the Azure portal at portal.azure.com and open SQL databases, then the database.
- Select Security > Transparent data encryption.
- Set Data encryption to On.
- Select Save.
- Check it: the page shows the encryption status as encrypted.
Task 2Keep 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.1.2.
- Open the assessment for Transparent Data Encryption on SQL databases should be enabled and fix the resources it lists as non-compliant.
- Check it: every resource under recommendation 4.1.2 shows as passing after the next evaluation.
Evidence
- Transparent data encryption of each database, showing it on
- The CIS v1.4.0 standard, with recommendation 4.1.2 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.