DoS Attacks on AI: Technical Defense Guide | Quiz

Why: Coordinated API resource exhaustion requires activating circuit breakers to halt new requests and fail over to healthy instances while investigating the coordinated attack pattern across multiple accounts. Context: Each account is within limits individually making per-account rate limiting ineffective. Circuit breakers at 95% GPU utilization for more than 5 seconds protect against this coordinated abuse. Remember: Coordinated attacks need infrastructure-level circuit breakers not per-account limits.

Why: An output/input token ratio above 3 should trigger a warning alert while a ratio above 5 indicates critical status – this signals that requests are generating disproportionately large outputs. Context: Normal queries have reasonable output/input ratios. When attackers use token bombs they craft short inputs designed to trigger maximum-length outputs creating abnormally high ratios. Remember: Ratio above 3 is warning – above 5 is critical.

Why: Server-side output caps enforce maximum output tokens at the infrastructure level regardless of what clients request – this single control blocks the majority of token bomb attacks. Context: Never trust client-requested output limits. Attackers will always request maximum output to maximize resource consumption. Server-side enforcement is essential because it cannot be bypassed. Remember: Never trust client limits – enforce output caps at infrastructure level.

Why: The three-layer defense strategy covers input validation and complexity analysis to stop expensive processing before it starts – resource management and quotas to control consumption – and monitoring and anomaly detection to catch attacks in progress. Context: Each layer provides different protection. Input validation prevents expensive requests and resource management limits damage and monitoring enables rapid response. Remember: Three layers – input validation and resource management and monitoring.

Why: Sponge examples are inputs specifically designed to maximize processing time by triggering extended chain-of-thought reasoning and recursive patterns and maximum-length generation. Context: These attacks exploit model architecture weaknesses. A single request can tie up GPU resources for minutes instead of seconds while legitimate users queue up or time out. Remember: Sponge attacks maximize processing time – like ordering the most elaborate dish on the menu.

Why: Traditional DDoS overwhelms through massive request volume while AI DoS uses carefully crafted inputs that maximize computational cost – one complex request can equal 1000 normal requests in resource consumption. Context: The restaurant analogy explains this well – traditional DDoS is 1000 people calling simultaneously while AI DoS is one person ordering a 3-hour dish that blocks the kitchen. Remember: Traditional DDoS is volume-based – AI DoS is complexity-based.

Why: AI DoS attacks exploit the computational intensity of AI systems by crafting inputs that consume disproportionate resources – not through network flooding but through complexity. Context: Unlike traditional DDoS which relies on massive request volumes – AI DoS can cause service degradation and cost explosion with just a few carefully designed requests. Remember: AI DoS is about complexity not volume – one request can consume 1000x resources.