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 economic circuit breaker implements per-key daily token and dollar hard caps with auto-suspend at 80% of budget – it prevents the worst financial damage from DoS attacks with minimal implementation effort. Context: AI DoS is fundamentally Economic Denial of Service. Pay-per-use cloud AI means attackers directly cost you money. Budget caps stop the bleeding before costs spiral out of control. Remember: Per-key budget caps with auto-suspend – stops financial damage immediately.

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: Computational asymmetry means the attacker-defender cost ratio heavily favors attackers – crafting an expensive prompt takes seconds but processing it takes minutes of GPU time worth significant money. Context: A 10-word prompt can trigger a 4000-word response with complex reasoning. The attacker invested virtually nothing while the defender spent real compute resources. Remember: Attackers spend seconds – defenders spend dollars in GPU time.

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: The three attack types are sponge examples/token bombs (50-500x cost multiplier) and compute-heavy prompts (10-200x cost) and model degradation via poisoning (permanent damage). Context: Each type has different mechanisms and detection difficulty. Sponge attacks maximize output tokens while compute-heavy attacks force deep reasoning and model degradation poisons training data. Remember: Three types – sponge/token bombs and compute-heavy and model degradation.

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.