Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Cloud DDoS Protection Layers?

Cloud DDoS protection works in layers: anycast absorption and scrubbing at the network edge, application-aware filtering at layer 7, and origin controls that stop direct attacks.

Illustration for the cybersecurity term Cloud DDoS Protection Layers
Home / Blog / Cybersecurity Terms / What Are Cloud DDoS Protection Layers?
17 November 2026

What Are Cloud DDoS Protection Layers?

What Are Cloud DDoS Protection Layers?

Cloud DDoS protection is not a single product you switch on. It is a stack of defences that each handle a different kind of attack, and an outage usually happens where the layers fail to meet. Volumetric floods are absorbed at the network edge; application-layer floods have to be judged request by request; and neither helps if the attacker can reach your origin servers directly.

Layer 3 and 4: Absorbing Volume

Network-layer attacks aim to exhaust bandwidth or connection state with UDP reflection, SYN floods, or raw packet volume. Defence here is a matter of capacity and geography. Providers advertise anycast networks that announce the same address from dozens of locations, so a distributed flood is split across the edge rather than converging on one data centre, and scrubbing infrastructure drops malicious packets before they reach you.

The scale involved keeps growing. Cloudflare reported mitigating a 5.6 Tbps UDP flood in October 2024, at the time the largest publicly disclosed attack. No on-premises appliance absorbs that. AWS Shield Standard, Azure DDoS Protection Infrastructure, and Google Cloud Armor’s network tier provide always-on baseline coverage at no extra charge, with paid tiers adding detection tuned to your traffic, access to a response team, and cost protection for scaling charges incurred during an attack.

Layer 7: Judging Requests

Application-layer attacks are cheaper for the attacker and harder for you. A few thousand requests per second against a search endpoint that queries a database can be more damaging than a terabit of packets, and the traffic looks superficially legitimate. The HTTP/2 Rapid Reset technique, tracked as CVE-2023-44487 and disclosed in October 2023, produced record request-rate attacks by rapidly opening and cancelling streams, and required protocol-level fixes across the industry.

Controls at this layer include rate limiting by IP, token, or session; JavaScript and proof-of-work challenges; bot management based on fingerprinting and behaviour; caching so that repeated requests never reach the application; and the managed rule groups described in our entry on cloud WAF configuration. Tuning matters more than coverage here, because an over-eager rule blocks customers as effectively as any attacker.

Protecting the Origin

A great many successful attacks bypass the whole edge by hitting the origin address directly, discovered through old DNS records, certificate transparency logs, mail server headers, or a forgotten staging host. Closing that gap is unglamorous and highly effective:

The Layer People Forget: Cost

Autoscaling turns an availability attack into a financial one. If the application scales smoothly under a flood, the service stays up and the invoice does not. Set maximum scaling limits deliberately, enable the cost protection available in paid DDoS tiers, and configure billing alerts so that a sustained attack is visible in minutes rather than at month end, as covered in our entry on the cloud cost anomaly.

Preparing Before It Happens

Decide in advance who declares an incident, who can authorise emergency rule changes, and how you contact your provider’s response team out of hours—several paid tiers require you to be enrolled before an attack to get that support. Keep DNS time-to-live values low enough to reroute quickly. Record what normal traffic looks like, because the fastest way to identify attack traffic is to know your own baseline. Then rehearse it: a tabletop exercise with the network, application, and communications teams exposes gaps that no configuration review will.

Ransom DDoS, where an extortion demand arrives alongside a short demonstration attack, remains common against UK financial and gaming targets. NCSC guidance is consistent with Action Fraud advice on this: do not pay, preserve the correspondence, and report it. Paying funds the next campaign and marks you as a reliable target.

At Privia Security, we measure how much your stack actually absorbs through controlled DoS and DDoS testing services.

FAQ – Frequently Asked Questions

Is the Free Tier of Cloud DDoS Protection Enough?

For many organisations it handles ordinary network-layer noise, which is most of what they will ever see. Paid tiers add detection tuned to your own traffic baseline, faster mitigation for application-layer attacks, access to a response team during an incident, and billing protection for scaling costs. If downtime has a measurable hourly cost or you have been extorted before, the paid tier usually pays for itself once.

Can a WAF Stop a DDoS Attack?

It stops some of them. A web application firewall with rate limiting and bot management is effective against application-layer floods, because it can inspect and judge individual requests. It is useless against a volumetric flood that saturates the link before any request is parsed. The two layers are complementary, and buying one while assuming it covers the other is a common and expensive mistake.

How Do Attackers Find My Origin Server?

Old DNS records that still point at the real address, certificate transparency logs listing hostnames you no longer advertise, email headers revealing a mail server on the same network, error pages that leak internal addresses, and staging environments left publicly reachable. Audit all of these, then enforce the restriction at the firewall so that discovery alone is not enough to reach you.

Should We Pay a Ransom DDoS Demand?

No. UK law enforcement and NCSC guidance are consistent that payment funds further attacks and identifies you as a paying target, and many demonstration attacks are never followed by the threatened larger one. Preserve the demand and any communications as evidence, report through Action Fraud, inform your provider’s response team, and focus effort on mitigation and capacity instead.

Related Terms

You May Be Interested In These

What Is a Ransomware Response Playbook?

Cybersecurity Terms

17 November 2026

What Is a Ransomware Response Playbook?

Read More
What Is a PLC?

Cybersecurity Terms

17 November 2026

What Is a PLC?

Read More
What Is the Traffic Light Protocol?

Cybersecurity Terms

17 November 2026

What Is the Traffic Light Protocol?

Read More