Azure subscriptions should have Microsoft Defender for App Service enabled
Azure Defender for App Service leverages the scale of the cloud, and the visibility that Azure has as a cloud provider, to monitor for common web app attacks.
Without this coverage, malicious traffic and runtime anomalies may go unseen, enabling:
Confidentiality loss via data exfiltration. Integrity compromise through web shells or code tampering. Availability impact from takeover and resource abuse.
What this control checks
The AppServices pricing tier at subscription scope must be Standard (Defender for App Service.
Common pitfalls
Only the Standard tier passes
The existence condition requires Microsoft.Security/pricings/pricingTier to equal Standard.
Check applies to AppServices pricing only
The check passes when resource_type is not AppServices or tier equals Standard.
Audit evidence
Evidence that deployed resources meet this control: Azure Policy compliance results for the built-in policy definitions "Azure Defender for App Service should be enabled" (2913021d-f2fd-4f3d-b958-22354e2bdbcb) and "Configure Azure Defender for App Service to be enabled" (b40e7bcd-a1e5-47fe-b9cf-2f534d0bfb7d); Prowler check defender_ensure_defender_for_app_services_is_on (prowler azure --checks defender_ensure_defender_for_app_services_is_on); PowerPipe control azure_compliance.control.securitycenter_azure_defender_on_for_appservice.
Scans of the Terraform code that flag the same setting before deployment: Checkov check CKV_AZURE_61.
Framework-specific interpretation
SOC 2: Mapped to CC6.8 (The entity implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software...) and CC7.1 (To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations...).
ISO/IEC 27001:2022: Mapped to A.5.25 (Assessment And Decision On Information Security Events) and A.8.7 (Protection Against Malware).
NIS2 Directive (EU 2022/2555): Mapped to 3.6.2 (The relevant entities shall ensure that post-incident reviews contribute to improving their approach to network and...) and 6.9.2 (For that purpose, the relevant entities shall in particular implement measures that detect or prevent the use of...).
NIST SP 800-53 Rev 5: Mapped to AC-2(12) (Account Monitoring for Atypical Usage), AU-12 (Audit Record Generation), AU-12(1) (System-wide and Time-correlated Audit Trail) and 8 more clauses.
NIST Cybersecurity Framework v2.0: Mapped to GV.RM-03 (Cybersecurity risk management activities and outcomes are included in enterprise risk management processes.).
Framework mappings
The clauses this control is mapped to in each framework.
- 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
- 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
6 more clauses
- AU-12(1) System-Wide And Time-Correlated Audit Trial
- IR-4 Incident Handling
- IR-5 Incident Monitoring
- RA-5 Vulnerability Monitoring and Scanning
- SI-2 Flaw Remediation
- SI-4: System Monitoring
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.11.2 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified
6 more clauses
- 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.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.6.1 Ensure That Microsoft Defender for App Services Is Set To 'On'
- 8.1.2.1 Ensure Microsoft Defender for APIs is set to 'On'
- 8.1.6.1 Ensure That Microsoft Defender for App Services Is Set To 'On'
RBI Cyber Security Framework for UCBs
- Annex I (6)
- 3.1.f Maker-checker
- 3.1.g Trails
- 4.4.a IT Operations
- 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.2 Ensure that Azure Defender is set to On for App Service
- 2.2 Ensure that Microsoft Defender for App Service is set to 'On'
- 2.1.2 Ensure That Microsoft Defender for App Services Is Set To 'On'
- 2.1.2 Ensure That Microsoft Defender for App Services Is Set To 'On'
- 2.1.2 Ensure That Microsoft Defender for App Services Is Set To 'On'
- 3.1.6.1 Ensure That Microsoft Defender for App Services 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
6 more clauses
- AU-12(1) System-Wide / Time-Correlated Audit Trail
- IR-4 Incident Handling
- IR-5 Incident Monitoring
- RA-5 Vulnerability Scanning
- SI-2 Flaw Remediation
- SI-4 Information System Monitoring
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
securitycenter_azure_defender_on_for_appservice - Checkov Check:
CKV_AZURE_61 - Powerpipe Control:
azure_compliance.control.securitycenter_azure_defender_on_for_appservice - Prowler Check:
defender_ensure_defender_for_app_services_is_on - Azure Policy Definitions:
2913021d-f2fd-4f3d-b958-22354e2bdbcb,b40e7bcd-a1e5-47fe-b9cf-2f534d0bfb7d
Last reviewed: 2026-10-14