Azure Compliance ControlsMicrosoft Defender for Cloud
Azure subscriptions should have Microsoft Defender for Servers enabled
Azure Defender for servers provides real-time threat protection for server workloads and generates hardening recommendations as well as alerts about suspicious activities.
What this control checks
Microsoft Defender for Servers is turned on for the Azure subscription
Framework mappings
The clauses this control is mapped to in each framework.
- CC3.2 COSO Principle 7: The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managed
- CC4.2 COSO Principle 17: The entity evaluates and communicates internal control deficiencies in a timely manner to those parties responsible for taking corrective action, including senior management and the board of directors, as appropriate
- CC6.8: The entity implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software to meet the entity's objectives.
- CC7.1: To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities.
- A.5.25 Assessment and decision on information security events
- A.8.7 Protection against malware
- A.8.9 Configuration management
- 3 Incident handling
- 6 Security in network and information systems acquisition, development and maintenance
- AC-2(12) Account Monitoring for Atypical Usage
- AU-6 Audit Record Review, Analysis, and Reporting
- AU-6(4) Central Review And Analysis
- AU-6(5) Central Review And Analysis
- AU-12 Audit Record Generation
10 more clauses
- AU-12(1) System-Wide And Time-Correlated Audit Trial
- CM-7 Least Functionality
- IR-4 Incident Handling
- IR-5 Incident Monitoring
- RA-5 Vulnerability Monitoring and Scanning
- SC-3 Security Function Isolation
- SI-2 Flaw Remediation
- SI-3 Malicious Code Protection
- SI-4: System Monitoring
- SI-16 Memory Protection
NIST Cybersecurity Framework v2.0
- GV.RM-03: Cybersecurity risk management activities and outcomes are included in enterprise risk management processes.
- 3.3.1: Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity
- 3.3.2 Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions
- 3.3.4 Alert in the event of an audit logging process failure
- 3.3.5 Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity
- 3.4.6 Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities
8 more clauses
- 3.11.2 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified
- 3.11.3 Remediate vulnerabilities in accordance with risk assessments
- 3.14.1 Identify, report, and correct system flaws in a timely manner
- 3.14.2 Provide protection from malicious code at designated locations within organizational systems
- 3.14.3 Monitor system security alerts and advisories and take action in response
- 3.14.5 Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed
- 3.14.6 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks
- 3.14.7: Identify unauthorized use of organizational systems.
- 9.1.3.1 Ensure that Defender for Servers is set to 'On'
- 8.1.3.1 Ensure that Defender for Servers is set to 'On'
RBI Cyber Security Framework for UCBs
- Annex I (6)
- 3.1.f Maker-checker
- 3.1.g Trails
- OPS-04.01B Policies and instructions with specifications for protection against malware are documented, communicated, and provided in accordance with SP-01 with respect to the following aspects: - Use of system-specific protection mechanisms;- Operating protection programmes on system components...
- 2.1 Ensure that Azure Defender is set to On for Servers
- 2.1 Ensure that Microsoft Defender for Servers is set to 'On'
- 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On'
- 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On'
- 2.1.2 Ensure That Microsoft Defender for App Services Is Set To 'On'
- 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On'
- 3.1.3.1 Ensure That Microsoft Defender for Servers Is Set to 'On'
- AC-2(12) Account Monitoring
- AU-6 Audit Record Review, Analysis And Reporting
- AU-6(4) Central Review And Analysis
- AU-6(5) Integration / Scanning And Monitoring Capabilities
- AU-12 Audit Generation
11 more clauses
- AU-12(1) System-Wide / Time-Correlated Audit Trail
- CM-7 Least Functionality
- IR-4 Incident Handling
- IR-5 Incident Monitoring
- RA-5 Vulnerability Scanning
- SC-3 Security Function Isolation
- SI-2 Flaw Remediation
- SI-3 Malicious Code Protection
- SI-3(1) Central Management
- SI-4 Information System Monitoring
- SI-16 Memory Protection
- 164.308(a)(1)(ii)(A) Risk analysis
- 164.308(a)(5)(ii)(B): Administrative Safeguards
- 164.308(a)(6)(ii): Administrative Safeguards
Related controls
- Azure subscriptions should have Microsoft Defender for Key Vault enabled
- Azure subscriptions should have Microsoft Defender for Azure SQL Database servers enabled
- Microsoft Defender for Cloud should have Microsoft Defender for Cloud Apps (MCAS) integration selected
- Virtual machines should have system updates installed
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
securitycenter_azure_defender_on_for_server - Checkov Check:
CKV_AZURE_55 - Powerpipe Control:
azure_compliance.control.securitycenter_azure_defender_on_for_server - Prowler Check:
defender_ensure_defender_for_server_is_on - Azure Policy Definitions:
4da35fc9-c9e7-4960-aec9-797fe7d9051d,8e86a5b6-b9bd-49d1-8e21-4bb8a0862222
Last reviewed: 2026-10-15