DDoS emotions
summary
A DDoS can hit like a targeted assault on infrastructure, customers and staff, not a routine outage: one example shows a sustained 160 Gbps flood with probing hours before the spike, another incident sources ~40 million pps from compromised PHP hosts. Operations discover a third‑party DNS forwarder and an already‑purchased but unconfigured mitigation device; getting it live after many hours stops the attack. Staff burnout, hunger and blame spiral without rotations, food for remote teams, pretested tooling, tabletop drills, traffic metadata and carrier partnerships to make attacks more expensive than the attacker’s gain.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:06Distributed Denial of Service
- 1:37Blue Frog Anti spam DDOS engine
- 2:47Declare an incident
- 3:12Outage is back!
related talks
45mAnatomy of a DDoS
37mAnatomy of a DDoS
40mThe new reality of DDOS
52mNot all attacks are malicious: DDoS from outside and within
35mHow We Organize Large-Scale DDoS Exercises in the Netherlands
52mInvestigating DDOS - Architecture Actors and Attribution
46mThe Mechanics of DDoS
23mThe Role of IoT and 5G Devices in DDoS Attacks