Edge protection during an HTTP flood
The wave of fake requests is filtered before it reaches the application, so real users keep using the site.
- User
- Bot
- Legitimate request
- Attack request
- Blocked at the edge
Step 1 of 6 · Normal traffic
Normal trafficText description
Real users (circles) and bot sources (diamonds) are on the left. Normally only user requests pass through the edge layer to the application, and application load stays low. In the attack scenario bots send a large number of HTTP requests and application load rises quickly. With protection on, rate limiting, bot management and WAF rules engage at the edge; bot requests are blocked at the edge (cross mark), user requests keep reaching the application and load returns to normal. With protection off, load stays high and real users' requests slow down.
Rate limiting, bot management and WAF are different controls; together they reduce application-layer (L7) load. Volumetric L3/L4 attacks are absorbed upstream in the provider's network before traffic reaches you. Figures are illustrative.