We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

DDoS Protection vs WAF: Which Layer Stops Which Attack

For IT heads with public sites on AWS or Azure: network DDoS protection and a web application firewall compared on five points, from the attacks each stops and where each sits to who tunes it and the gap left when one runs alone. The AWS and Azure service is named for each layer, with the AWS WAF rate-based rule window and the Azure Front Door rate limit explained. It takes no side and quotes no prices.

DDoS protection vs WAF is a question of layers: network DDoS protection absorbs volumetric and protocol floods at layers 3 and 4, while a web application firewall filters HTTP floods and bad requests at layer 7. However, each stops attacks the other does not.


Last reviewed 2026-11-16 by Manish Sharma.

This article is for IT heads and security leads whose websites, portals and APIs run on AWS or Azure. Overall, it settles which layer stops which attack, and how Signisys sets up flood defense for public sites puts the two layers into one design.

DDoS Protection vs WAF Compared on Five Points

The comparison below covers five points, with the AWS and Azure service named in each cell.

Point Network DDoS protection WAF
Attacks stopped Volumetric and protocol floods at layers 3 and 4. AWS Shield; Azure DDoS Protection HTTP floods, bad requests and exploits at layer 7. AWS WAF; Azure Web Application Firewall
Where it sits AWS Shield at the perimeter of the AWS network, with added benefit at Amazon Route 53 and Amazon CloudFront. Azure DDoS Protection on resources in a virtual network AWS WAF on CloudFront or other AWS web entry points. Azure WAF policy on Front Door or on Application Gateway
Who tunes it Tunes itself on Azure; applies automatically on AWS The team writes and adjusts the rules
In a layer 7 flood Layer 7 mitigation on AWS is a Shield Advanced option you configure. Azure DDoS Protection does not cover layer 7 AWS WAF rate-based rules and Azure rate limiting rules act on the requests
Gap when used alone Valid-looking HTTP floods and exploits pass through A volumetric flood can fill the link in front of it

Advantages
Network DDoS protection tunes itself on Azure and applies automatically on AWS.


Limitations
A WAF alone sits behind a link that a volumetric flood can fill.

Read each row across before reading the next, and match it to the service in front of your site.

DDoS protection vs WAF: network protection at layers 3 and 4 beside a WAF at layer 7, each with its AWS and Azure service
Two layers, each with an AWS and an Azure service.

Attacks Each Layer Stops in DDoS Protection vs WAF

The two layers answer different kinds of traffic, so the attack type decides which one applies.

Volumetric and Protocol Floods at Layers 3 and 4

Volumetric floods fill the network link until real visitors are locked out. Protocol floods use up the state that servers and network devices keep for each connection.

AWS lists a TCP SYN flood as able to exhaust connection state on servers, load balancers or firewalls, as its documentation on how Shield works explains. A firewall can therefore be the target of an attack, not only the defense against one.

Network DDoS protection is the layer built for these floods, and a rule set or a rate limit is the wrong tool here.

HTTP Floods and Bad Requests at Layer 7

However, layer 7 attacks arrive as web requests. Microsoft’s list of attack types includes HTTP protocol violations, SQL injection, cross-site scripting and other layer 7 attacks.

Is a WAF a layer 7 firewall? Yes: AWS WAF inspects HTTP(S) requests, and Azure states that layer 7 protection needs a WAF. See how a WAF reads each request for the term itself.

A request flood looks like normal traffic until a rule judges it. For that reason, filtering happens at this layer.

Layer 4 vs Layer 7 DDoS: Where AWS and Azure Draw the Line

The line between a layer 4 and a layer 7 DDoS attack falls in different places on each cloud’s documents.

On AWS, the Shield Standard page covers network and transport layer attacks, Shield Advanced adds layer 7 detection and optional automatic mitigation, and AWS WAF does the layer 7 filtering.

On Azure, DDoS Protection covers layers 3 and 4 only, and layer 7 needs a WAF.

Where DDoS Protection vs WAF Sit in Front of a Site

Position also decides what each layer sees first. Network protection works on the path to the site, and the WAF works on the requests that arrive.

AWS WAF vs Shield on One Traffic Path

Shield Standard applies automatically to AWS customers, with added benefit at Amazon Route 53 hosted zones and Amazon CloudFront distributions. Also, no setup step turns it on.

You attach AWS WAF to CloudFront or to other AWS web entry points, and it then inspects the requests that reach that resource. In the AWS WAF vs Shield pairing, then, Shield sits on the path and AWS WAF sits on the request.

Azure DDoS Protection on the Network, Azure WAF at the Edge or the App

First, Azure DDoS Protection covers resources in a virtual network. Second, Azure WAF can run on Azure Front Door, at the network edge, or on Azure Application Gateway, which delivers the web application.

Front Door also gives platform protection against network level floods. That platform protection does not replace the network layer for resources inside a virtual network.

Who Tunes DDoS Protection vs WAF

Network protection tunes itself, and the WAF rules belong to the team that runs the site.

Rate-Based Rules in AWS WAF for Request Floods

How can AWS WAF be used against a flood? Through rate-based rules. A rate-based rule counts requests by an aggregation key and acts once the count passes a set rate. In addition, the evaluation window is 60, 120, 300 or 600 seconds, and 300 is the default.

Key Takeaway Use the AWS WAF rate-based rule against request floods, and set it from known normal traffic.

Rate-Based Window

AWS WAF evaluation window: 60, 120, 300 or 600 seconds. The default is 300.

Per the AWS page on rate-based rule settings, AWS WAF applies the limit near the setting and does not promise an exact match, so a limit is a guide, not a wall.

Rate Limiting and Managed Rules in Azure WAF

Azure WAF on Front Door has rate limiting rules that count requests from each client IP address over a one minute or five minute duration. Then the team sets the threshold.

Azure WAF also offers managed rule sets for common exploits, and custom rules that run before the managed rule set. Also, the team that owns the site tunes both.

Gaps When DDoS Protection vs WAF Runs Alone

However, network protection alone lets valid-looking HTTP floods and exploits through, as Microsoft’s page on attack types states for layer 7. A WAF alone sits behind a link that a volumetric flood can fill.

In a layer 7 flood on AWS, mitigation comes from the rate-based rules the team writes in the web ACL, or from Shield Advanced automatic mitigation if you turn it on. Each layer leaves a gap, and neither covers the whole path alone.

Key Takeaway Network protection stops floods at layers 3 and 4, the WAF filters requests at layer 7, and each leaves a gap the other covers.

Signisys’s working view is that the two layers are one path in front of the site, not a choice between them. The first signs that traffic has turned hostile show which layer is under pressure when a site slows down.

Planning DDoS Protection vs WAF Cover Together Across Both Clouds

Overall, Microsoft Learn recommends Azure DDoS Protection and a WAF together for web workloads. On AWS, Shield Advanced can be set to respond automatically to layer 7 floods, and it then manages a rule group in the web ACL. For Shield Advanced customers, the AWS Shield Response Team can, with your approval, change the web ACL to block an attack.

Three questions help the team plan: Which public service sits behind which layer? Who owns each rule set and each rate limit? Who calls the provider, and when?

Name the Owner

Name the owner of every rate limit before an event, not during it.

Likewise, Signisys’s working view is the same. The eight actions to take before, during and after an attack cover what happens in the event, and the readiness items to settle for each public site cover what to settle beforehand.

Signisys works with AWS and Microsoft, and offers its cybersecurity practice and a network and endpoint security offering to clients. In a working session, we pair each public site, portal and API with the layer in front of it. Then the output is a list of gaps and their owners, nothing more. No charge, with a fixed scope.

Planning both layers for each public site, portal and API: layer in front, rule owner, rate limit owner, provider contact
Plan both layers per public site.
Book a consultation
Map both layers with us

DDoS Protection vs WAF: FAQ

Does a WAF on Azure Front Door still need Azure DDoS Protection?

It does, wherever the site runs inside a virtual network. Front Door gives platform protection against network level floods, while Azure DDoS Protection covers resources in a virtual network. Microsoft Learn recommends using both together for web workloads, so the WAF handles requests and the network layer handles floods.

Does Shield Advanced write the AWS WAF rules for us?

Partly. In practice, an optional automatic mitigation setting has Shield Advanced manage a rule group in the web ACL, and AWS’s response team can, with your approval, apply changes to the web ACL. The team still owns its own rules, rate limits and the decision to act.

Can a WAF rate limit block real customers during a flood?

Yes, if it is set too low. However, AWS applies limits near the set rate, not exactly. Start from known normal traffic, then adjust. That way, a busy day is not read as an attack.

Which layer handles a slow connection attack?

The WAF side. Microsoft Learn says application layer attacks target web application packets and need a WAF used alongside DDoS Protection. A slow connection attack falls within that, so the answer is a WAF with rules the team keeps current, alongside network protection.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.