Study guide
5.3 Web Application Firewall (WAF) & Azure Front Door
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
5.3 Web Application Firewall (WAF) & Azure Front Door
Key Takeaways Explain This Topic AI
Azure Web Application Firewall (WAF) provides Layer 7 protection for web applications deployed globally on Azure Front Door or regionally on Azure Application Gateway.
Core Rule Sets (CRS 3.2 / DRS 2.1) automatically defend against OWASP Top 10 vulnerabilities including SQL Injection, Cross-Site Scripting, and Remote Command Execution.
WAF policies operate in either Detection mode (logging threats for false-positive tuning) or Prevention mode (actively blocking malicious requests with HTTP 403).
False positives are remediated without compromising security by creating precise WAF Exclusion lists or custom rules rather than disabling entire rule groups.
Integrated Bot Protection leverages Microsoft Threat Intelligence feeds to identify, classify, and mitigate malicious botnet traffic and vulnerability scanners.
Last updated: August 2026
4.3 Web Application Firewall (WAF) & Azure Front Door
Azure Web Application Firewall (WAF) provides centralized, Layer 7 protection for web applications against common web exploits, vulnerabilities, and malicious bot traffic. WAF policies can be attached to two distinct Azure delivery services: Azure Application Gateway (for regional HTTP/HTTPS load balancing) and Azure Front Door (for global edge content acceleration and routing).
Architectural Comparison: Application Gateway WAF vs. Azure Front Door WAF
Selecting the correct WAF deployment model depends on application distribution and traffic entry points:
Feature / Dimension Application Gateway WAF Azure Front Door WAF
Deployment Scope Regional (Deployed inside dedicated subnet in a specific VNet) Global (Deployed at Microsoft's global Point of Presence edge locations)
Inspection Location Within the Azure Region prior to backend application pools At the Edge network prior to entering the Azure backbone
Managed Rulesets OWASP Core Rule Set (CRS 3.0, 3.1, 3.2) Default Rule Set (DRS 1.1, 2.0, 2.1) aligned with OWASP
Bot Protection Microsoft Threat Intelligence Bot Ruleset Managed Bot Protection Ruleset with IP Reputation
Custom Rule Match Criteria IP address, Geo-location, HTTP parameters, Request Headers IP address, Geo-location, HTTP parameters, Request Headers, Rate Limiting
Rate Limiting Rules Supported (Per IP / matching criteria over 1 or 5 min) Supported (Per IP / matching criteria over 1 or 5 min)
Backend Target Types Azure VMs, Virtual Machine Scale Sets, App Services, AKS Public IPs, Azure App Services, Storage static sites, On-premises
OWASP Top 10 Protection & Core Rule Sets (CRS / DRS)
Azure WAF includes pre-configured, managed rule sets maintained by Microsoft security researchers to guard against the Open Web Application Security Project (OWASP) Top 10 web vulnerabilities.
Primary Threat Categories Defended
SQL Injection (SQLi): Detects malicious SQL syntax in query parameters, forms, or headers intended to manipulate backend databases.
Cross-Site Scripting (XSS): Blocks injected client-side scripts in request parameters that execute in end-user browsers.
Local File Inclusion (LFI) & Remote File Inclusion (RFI): Prevents attackers from forcing web applications to read local server files ( /etc/passwd ) or execute remote scripts.
Remote Code Execution (RCE): Blocks system command injection strings targeting operating system shells.
Protocol Violations & Anomalies: Detects malformed HTTP headers, missing user agents, or HTTP request smuggling patterns.
Operational Modes: Detection vs. Prevention
WAF policies run in one of two modes, controlled at the policy level:
1. Detection Mode
WAF evaluates requests against all active rules and logs detected threats to a Log Analytics workspace.
Does NOT block traffic. All requests are forwarded to the backend application regardless of rule matches.
Mandatory Use Case: Always deploy new WAF policies in Detection mode during initial onboarding. Analyze log telemetry over a 1–2 week baseline to identify legitimate application traffic flagged as false positives before switching to Prevention mode.
2. Prevention Mode
WAF evaluates requests against active rules.
When a request triggers a rule match, WAF immediately drops the request and returns an HTTP 403 (Forbidden) status code to the client.
The block action and matching rule ID are logged to diagnostic streams.
False Positive Tuning & WAF Exclusion Lists
In production web applications, legitimate complex requests (e.g., rich text editor inputs containing HTML tags or JSON payloads containing SQL-like keywords) may trigger WAF rule false positives.
Anti-Pattern to Avoid
Do NOT disable an entire rule group (such as SQLI or XSS ) to fix a single false positive. Disabling entire rule groups creates severe security vulnerabilities.
Recommended Remediation Methods
WAF Exclusion Lists: Exclude specific request attributes from rule evaluation while maintaining protection across all other parameters.
Supported Match Targets: Request Header names, Request Cookie names, Query String parameter names, Request Body attribute names.
Example: If an admin portal sends HTML content in a request body field named articleContent , create an exclusion for Request Body Attribute Name Equals articleContent . WAF will ignore articleContent while continuing to inspect all other body fields.
Custom Rules with Allow Actions: Create high-priority custom rules that permit traffic from trusted IP ranges or specific API endpoints before Core Rule Sets are evaluated.
- Custom Rules & Bot Protection Engine
- Custom WAF Rules
Custom rules are evaluated prior to managed Core Rule Sets. Common custom rules include:
Geo-Filtering Rules: Allow or block incoming traffic based on two-letter country codes (e.g., block inbound web traffic originating outside corporate operating regions).
IP Match Rules: Create explicit Allow CIDR lists for administrative endpoints or Deny CIDR lists for known malicious networks.
Rate Limiting Rules: Prevent Denial of Service (DoS) and brute-force attacks by limiting the number of requests allowed from a single client IP address within a 1-minute or 5-minute window.
Bot Protection Engine
The managed Bot Protection engine integrates with Microsoft Threat Intelligence feeds to categorize incoming request traffic:
Good Bots: Search engine crawlers (Google, Bing) allowed through without friction.
Bad Bots: Malicious web scrapers, credential-stuffing tools, vulnerability scanners, and known command-and-control IPs automatically blocked or challenged.
Unknown Bots: Uncategorized automated traffic evaluated against standard rate-limiting and custom rules.
TLS Termination & End-to-End Encryption
WAF appliances serve as the primary entry point for HTTPS traffic and manage transport layer security policies:
TLS Termination: WAF decrypts incoming HTTPS client traffic, performs deep packet payload inspection against WAF rule sets, and routes plain HTTP or re-encrypted HTTPS traffic to backend pools.
End-to-End TLS Encryption: For high-compliance environments, WAF inspects traffic at Layer 7 and re-encrypts the request using a new TLS session to the backend web servers, validating backend server certificates against approved Root CA pools.
TLS Protocol Enforcement: WAF policies can enforce minimum TLS protocol versions (disabling deprecated TLS 1.0/1.1 and requiring TLS 1.2 or TLS 1.3) and restrict cipher suites to modern forward-secrecy standards.