All DDoS Definitions
DDoS Testing Definition

Always-On Mitigation

Always-on mitigation is a defensive deployment model in which all traffic flows through DDoS scrubbing continuously, rather than being diverted only after an attack is detected. Because the scrubbing path is always in line, there is no detection-and-cutover delay: the reaction window that on-demand (reactive) protection incurs while it recognizes an attack and reroutes traffic is eliminated. The trade-off is steady-state latency and cost from inspecting clean traffic at all times.

Always-on vs on-demand: where the exposure window lives Always-on Traffic Scrubbing, always inline every packet inspected Origin Exposure window = 0 cost: steady latency + spend On-demand Traffic Origin, direct until attack starts Detect + divert origin exposed here Scrubbing engages traffic now filtered Always-on removes the cutover lag; on-demand stays fast in steady state but opens a gap as it reroutes. A pulse-wave attack is timed to strike exactly inside that on-demand window. A test drives attack-like load against production carefully to see which model actually holds, and for how long. BlackNeuron
Diagram: always-on mitigation has no cutover window, while on-demand exposes the origin during the detect-and-divert delay

Why it matters in DDoS testing

The deployment model dictates what failure looks like. Always-on removes cutover lag but still has to hold under volume; on-demand stays fast in steady state but exposes the origin during the diversion window, exactly when a pulse-wave attack strikes. Validating either model means generating attack-like load against production carefully, the discipline covered in running a DDoS test without disrupting production.