Distributed denial of service attack
A distributed denial-of-service attack uses traffic or requests from multiple sources to overwhelm a target and impair its availability or function.
Secure APIs
A distributed denial-of-service attack is a denial-of-service attack that uses traffic or requests from multiple distributed sources to overwhelm a service or resource.
- How it is used
- Frames unrestricted resource consumption as an API configuration and management vulnerability with availability and cost consequences.
- How deep it goes
- Explains request flooding, cloud cost escalation, layered defenses, and endpoint-specific rate limits, stopping short of implementation detail.
- Examples
- Illustrates three attacking servers, expensive analytics requests, and serverless platforms such as AWS Lambda, GCP, and Azure Functions.
- What you can do after
- Operate/configure layered protections and tailor rate limits to endpoint cost, sensitivity, and legitimate user flows.
Read how Secure APIs explains distributed denial of service attack →
Azure Security
A distributed denial-of-service attack is an attack that overwhelms a target with traffic or requests from multiple sources to disrupt availability.
- How it is used
- Protects public-facing Azure applications and resources from availability loss, financial damage, reputational harm, and attack-driven scaling costs.
- How deep it goes
- Explains public IP protection, traffic thresholds, protocol metrics, inspection, dropping behavior, and Basic-versus-Standard availability.
- Examples
- Uses an online ordering application, seasonal customer traffic, Application Gateway v2, and Virtual Machine Scale Sets as concrete scenarios.
- What you can do after
- Operate Azure DDoS Protection with an understanding of its entry points, traffic thresholds, mitigation decisions, and Basic SKU defaults.
Read how Azure Security explains distributed denial of service attack →
Grokking Web Application Security
A distributed denial-of-service attack is a denial-of-service attack launched simultaneously from many networked systems or addresses.
- How it is used
- Frames web-application unavailability as a direct consequence of a network attack.
- How deep it goes
- Defines DDoS through request flooding and distributed sources, but stops short of prevention or response procedures.
- Examples
- Uses the 2016 Dyn attack and the resulting unavailability of Amazon.com and Zillow.com.
- What you can do after
- Understand how distributed request flooding can exhaust server resources and disrupt legitimate access.
Read how Grokking Web Application Security explains distributed denial of service attack →
Related concepts
- denial-of-service attackkind of · A denial-of-service attack is an attempt to make a system or service unavailable or degrade its ability to serve legitimate users by exhausting or disrupting its resources.
- rate limitaddressed by · A rate limit is a bound on the frequency or volume of operations permitted within a defined interval, scope, or concurrency limit.
- Azure DDoS Protection Standardaddressed by · Azure DDoS Protection Standard is an Azure service tier that provides enhanced protection for Azure resources against distributed denial-of-service attacks.
- web application firewalluses · A web application firewall is a security system that inspects and filters application-layer web traffic to detect or block malicious requests targeting web applications and APIs.
- API securitykind of · API security is the protection of application programming interfaces, their functionality, and exposed data from unauthorized access, misuse, alteration, and disruption.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.