# 2.3 Ensure that Azure Defender is set to On for Azure SQL database servers

- Source: https://support.icompaas.com/support/solutions/articles/62000219746-2-3-ensure-that-azure-defender-is-set-to-on-for-azure-sql-database-servers
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Azure CIS Benchmark Level 1 & Level 2](https://support.icompaas.com/support/solutions/62000112163) › [2. Security Center](https://support.icompaas.com/support/solutions/folders/62000167545)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

Microsoft Defender for Azure SQL Databases provides advanced threat protection for Azure SQL Database workloads. When enabled, it adds a layer of intelligent, cloud-native security that continuously monitors database activity, identifies potential attacks or anomalous behaviors, and detects vulnerabilities or misconfigurations.

  

Rationale:

Enabling Microsoft Defender for Azure SQL Databases is a critical security control because it:

-   Provides continuous threat monitoring to detect malicious or suspicious activity in real time.
    
-   Identifies vulnerabilities and misconfigurations that could expose data or weaken security posture.
    
-   Supports regulatory requirements by offering continuous monitoring aligned with frameworks such as ISO 27001, SOC 2, PCI DSS, and GDPR.
    

  

Impact:

Turning on Microsoft Defender for Azure SQL Databases will:

-   Increase visibility into potential threats, security risks, and anomalous activity.
    
-   Generate alerts for suspicious behavior, unauthorized access attempts, and database vulnerabilities.
    
-   Enhance compliance readiness by ensuring databases are continuously monitored and aligned with security best practices.
    

The main impact is cost, as Microsoft Defender is a paid security feature charged per database or per server tier. There is no performance impact on SQL workloads.

  

Default Value:

By default, Microsoft Defender for Azure SQL Databases is not enabled.

  

Pre-requisites:

-   Azure subscription with Microsoft Defender for Cloud enabled.
    
-   Global Administrator or Security Administrator permissions to enable and configure Microsoft Defender for Azure SQL Database.
    

  

Test Plan:

1.  Sign in to the Azure Portal.
    
2.  Search for Microsoft Defender for Cloud.
    
3.  Under the management section, select the Environment settings, then choose the subscription where your Azure SQL Database is located.
    
4.  In Cloud Workload Protection (CWPP), in  Databases, click Select types, and check whether it is turned on or off for SQL servers on machines.
    

![](https://support.icompaas.com/assets/kb/2787a5276549b80e.png)

5.  If it is OFF, follow the implementation plan.
    

  

Implementation Steps:

1.  Sign in to the Azure Portal.
    
2.  Search for Microsoft Defender for Cloud.
    
3.  Under the management section, select the Environment settings, then choose the subscription where your Azure SQL Database is located.
    

  

  ![](https://support.icompaas.com/assets/kb/b77ba4f21f224bb7.png)

  

4.  In Cloud Workload Protection (CWPP), in  Databases, click Select types, and turn ON for the Azure SQL Database.
    

      ![](https://support.icompaas.com/assets/kb/39d5fd4a4c64ff19.png)

5.  Save it.
    

Backout Plan:

1.  Sign in to the Azure Portal.
    
2.  Search for Microsoft Defender for Cloud.
    
3.  Under the management section, select the Environment settings, then choose the subscription where your Azure SQL Database is located.
    
4.  In Cloud Workload Protection (CWPP), in  Databases, click Select types, and turn OFF for the Azure SQL Database.
    
5.  save it
    

References:

-   [https://learn.microsoft.com/en-us/azure/defender-for-cloud/enable-sql-database-plan](https://learn.microsoft.com/en-us/azure/defender-for-cloud/enable-sql-database-plan)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
