Study guide
5.4 Web Application Firewall for HTTP Workloads
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
5.4 Web Application Firewall for HTTP Workloads
Key Takeaways Explain This Topic AI
Azure Web Application Firewall protects web apps at layer 7 from common exploits such as SQL injection and cross-site scripting using managed rules plus custom rules.
Managed rules are based on the OWASP Core Rule Set (CRS); Azure's current managed ruleset is the Default Rule Set (DRS), and CRS/DRS use anomaly scoring (rules carry severities that accumulate to a threshold).
WAF deploys two ways: with Azure Application Gateway for regional protection and with Azure Front Door for globally distributed edge protection.
Detection mode logs without blocking; Prevention mode actively blocks. Tune in Detection first to remove false positives, then switch to Prevention. WAF (L7) complements DDoS Protection (L3/L4).
Last updated: June 2026
Protect Web Applications at the Application Layer
Web Application Firewall (WAF) is the Azure control to recognize whenever the stem talks about web application threats. Microsoft describes Azure WAF as protection for web applications from common exploits such as SQL injection , cross-site scripting (XSS) , and other web vulnerabilities. That makes WAF different from Azure Firewall (a managed network firewall) and from Azure DDoS Protection (network-layer availability). WAF operates at layer 7 , inspecting the content of HTTP and HTTPS requests — headers, query strings, body, and URI.
WAF works through policies . A WAF policy combines managed rules and custom rules . Managed rules provide out-of-the-box protection for common vulnerability patterns; custom rules let you define your own conditions, such as a source-IP allow/block list, a rate limit, or geo-filtering. You do not memorize every rule for SC-900, but you should understand that WAF protection is rule-based and that managed rules cover the well-known web risks.
OWASP Rule Sets, Modes, and Deployment Options
The managed rules derive from the OWASP Core Rule Set (CRS) . Azure's current recommended managed ruleset is the Default Rule Set (DRS) , which is built on a CRS baseline and adds Microsoft Threat Intelligence rules. When you use CRS/DRS, the WAF uses anomaly scoring : each matched rule has a severity (Critical, Error, Warning, Notice) that adds to a score, and the request is blocked only when the accumulated score crosses the threshold — a single match does not automatically block.
WAF runs in one of two modes , a classic exam distinction:
Mode Behavior When to use
Detection Logs and monitors rule matches but does not block Initial rollout; tune out false positives against real traffic
Prevention Actively blocks requests that breach the policy After tuning, for live protection
Best practice is to start in Detection , review the logs, build exclusions for false positives, then switch to Prevention .
Azure offers two WAF deployment patterns , and the exam may ask which fits:
WAF on Azure Application Gateway — a regional , dedicated layer-7 load balancer for protecting applications within a region.
WAF on Azure Front Door — a globally distributed edge service that inspects and filters traffic close to users before it reaches the origin, ideal for public, global endpoints.
WAF policies can also be associated with Azure CDN in some configurations, but Application Gateway and Front Door are the two you must know.
Layered Design and the Naming Trap
A layered design pairs WAF with DDoS Protection . DDoS Protection handles layer 3/4 volumetric floods; WAF handles layer 7 web exploits. If a question mentions both high-volume network attacks and web exploit attempts, the safe conceptual answer is that both layers have a role — DDoS Protection for the flood, WAF for the malicious requests.
Be careful with product names . Azure Firewall and Web Application Firewall both contain "firewall," but their exam roles differ:
Control Layer Protects Typical clue
Azure Firewall L3-L7 network Network/application connectivity for Azure workloads Central, stateful, FQDN, threat intel
- Web Application Firewall L7 web Web apps from OWASP exploits SQL injection, XSS, App Gateway, Front Door
- Azure DDoS Protection L3-L4 Public availability under floods Volumetric, denial of service
- Network security group L3-L4 Subnet/NIC traffic Allow/deny rules, 5-tuple
Quick selection cues:
Pick WAF for web application exploit protection (SQL injection, XSS, OWASP).
Pick Azure Firewall for central network firewalling and FQDN/threat-intel filtering.
Pick DDoS Protection for network-layer denial-of-service mitigation.
Pick NSGs for subnet or network-interface filtering.
What WAF Inspects, and Application Gateway vs Front Door
Because WAF works at layer 7 , it can read parts of a request that lower-layer controls never see: the URI , query string , request headers (including cookies and user-agent), the HTTP method , and the request body . Managed rules pattern-match these against known exploit signatures, while custom rules let you act on the same fields — for example, rate-limit by client IP, geo-filter by country, or block a specific header value.
This visibility is exactly why WAF, not Azure Firewall, is the answer for web-exploit questions: a network firewall sees IPs and ports, but WAF sees the content of the web request.
Choosing between the two deployment surfaces follows the traffic pattern:
- Factor WAF on Application Gateway WAF on Front Door
- Scope Regional (single region) Global edge (many points of presence)
Best for Apps served from one region; needs path-based routing/SSL offload Global, public, internet-facing endpoints needing edge filtering
- Where it filters At the regional gateway Close to the user, before traffic reaches the origin
- Pairs naturally with DDoS Protection on the VNet Front Door's built-in edge protections
For SC-900, you usually only need to recognize that both carry WAF and to map regional → Application Gateway and global edge → Front Door .
OWASP Top 10 Context and Common Traps
The exploits WAF defends against are drawn from the OWASP Top 10 — the industry list of the most critical web application risks, of which injection (including SQL injection) and cross-site scripting are perennial members. You do not need to memorize the full list, but knowing that "OWASP" in a stem signals web application risk and therefore WAF is high-value.
Two traps recur. First, candidates pick Azure Firewall because it also says "firewall" — but unless the stem mentions web exploits, HTTP content, Application Gateway, or Front Door, a network firewall is not a WAF. Second, candidates assume WAF blocks immediately on any rule match; with anomaly scoring , a single low-severity match may only contribute points, and blocking happens at the threshold — which is why Detection mode tuning matters before Prevention mode goes live.