DoS & DDoS Attacks : A Complete Incident Response Playbook

The article includes:

  • DoS vs DDoS separation
  • Volumetric, Protocol, Application-layer, Reflection/Amplification, and Multi-Vector attacks
  • Full IR lifecycle: Detection → Triage → Containment → Eradication → Recovery → Lessons Learned
  • SOC-ready terminology (NetFlow, SYN backlog, WAF, BGP blackholing, uRPF, BCP 38, etc.)
  • Suitable for SOC runbooks and playbooks.

Incident Response (IR) Table – Denial of Service (DoS) & Distributed Denial of Service (DDoS)

1. DoS (Denial of Service) – Single-Source Attacks

1.1 Volumetric DoS (Single Source Flooding)

IR PhaseTechnical Details
Attack DescriptionA single host overwhelms the target with excessive traffic (ICMP, UDP, TCP) to exhaust bandwidth or network stack resources.
Attack VectorsICMP Echo Flood, UDP Flood, TCP SYN Flood (single IP), malformed packet floods
Assets AffectedNetwork interfaces, routers, firewalls, web servers
Detection MethodsNetFlow/sFlow analysis, IDS/IPS flood signatures, interface utilization spikes
Indicators of Compromise (IoCs)High PPS/BPS from one IP, packet drops, increased latency, interface saturation
Initial TriageIdentify source IP, protocol, and traffic rate; validate against baseline
ContainmentACL blocking, firewall rate limiting, null routing offending IP
EradicationBlock source upstream, update IDS rules, patch misconfigured services
RecoveryRestore normal routing, validate service availability, monitor traffic normalization
Post-Incident ActionsUpdate thresholds, improve rate-limiting policies, document attack pattern

1.2 Protocol Exploitation DoS

IR PhaseTechnical Details
Attack DescriptionExploits weaknesses in protocol implementations to crash or stall services
Attack VectorsPing of Death, Teardrop, LAND attack, malformed TCP/IP packets
Assets AffectedOS kernel, network stack, legacy systems
Detection MethodsIDS signature matches, kernel logs, system crash dumps
IoCsKernel panic logs, malformed packet headers, unexpected reboots
ContainmentDisable vulnerable service, apply temporary packet filters
EradicationPatch OS/network stack, firmware upgrades
RecoverySystem reboot, integrity checks, service restart
Lessons LearnedDecommission legacy protocols, enforce RFC compliance

1.3 Application-Layer DoS (Single Source)

IR PhaseTechnical Details
Attack DescriptionTargets application resources via legitimate-looking requests
Attack VectorsHTTP GET/POST flood, slow HTTP headers (Slowloris)
Assets AffectedWeb servers, application servers, databases
Detection MethodsWeb server logs, WAF alerts, thread exhaustion metrics
IoCsHigh request rate from single IP, long-lived connections
ContainmentWAF IP blocking, connection timeouts, CAPTCHA enforcement
EradicationApplication tuning, thread pool limits
RecoveryRestart services, validate application performance
Post-IncidentImprove WAF rules, app-layer rate limiting

2. DDoS (Distributed Denial of Service)

2.1 Volumetric DDoS

IR PhaseTechnical Details
Attack DescriptionMassive traffic flood from multiple distributed sources exhausting bandwidth
Attack VectorsUDP Flood, ICMP Flood, DNS Flood
Assets AffectedISP links, edge routers, firewalls
Detection MethodsTraffic anomaly detection, ISP alerts, BGP monitoring
IoCsSudden bandwidth spikes, packet loss, unreachable services
Initial TriageIdentify traffic type, volume, source ASNs
ContainmentTraffic scrubbing, rate limiting, BGP blackholing
EradicationCoordinate with ISP/CDN, deploy mitigation services
RecoveryGradual traffic reintroduction, link stability verification
Post-IncidentIncrease capacity, improve ISP coordination

2.2 Reflection & Amplification DDoS

IR PhaseTechnical Details
Attack DescriptionExploits third-party servers to amplify traffic toward victim
Attack VectorsDNS, NTP, SSDP, CLDAP, Memcached
Assets AffectedNetwork bandwidth, upstream providers
Detection MethodsAsymmetric traffic patterns, spoofed source IPs
IoCsLarge response packets, unexpected protocol traffic
ContainmentBlock reflection protocols, enable uRPF
EradicationWork with reflectors’ owners, patch open services
RecoveryMonitor spoofing reduction, restore services
Lessons LearnedEnforce ingress/egress filtering (BCP 38)

2.3 Protocol-Based DDoS

IR PhaseTechnical Details
Attack DescriptionExhausts stateful devices using protocol weaknesses
Attack VectorsTCP SYN Flood, ACK Flood, RST Flood
Assets AffectedFirewalls, load balancers, servers
Detection MethodsHalf-open connection tracking, SYN backlog alerts
IoCsSYN queue exhaustion, connection failures
ContainmentSYN cookies, connection rate limits
EradicationDevice tuning, firmware updates
RecoveryValidate session stability
Post-IncidentOptimize state table sizing

2.4 Application-Layer DDoS (Layer 7)

IR PhaseTechnical Details
Attack DescriptionDistributed, low-and-slow requests mimic legitimate users
Attack VectorsHTTP floods, API abuse, Slow POST
Assets AffectedWeb apps, APIs, backend services
Detection MethodsBehavioral analytics, WAF anomaly scoring
IoCsHigh request diversity, session exhaustion
ContainmentWAF challenges, geo-blocking, bot mitigation
EradicationImprove bot detection, API authentication
RecoveryScale backend resources
Lessons LearnedImplement zero-trust & adaptive rate limiting

2.5 Multi-Vector DDoS

IR PhaseTechnical Details
Attack DescriptionCombination of volumetric, protocol, and application attacks
Attack VectorsUDP flood + SYN flood + HTTP flood
Assets AffectedEntire infrastructure stack
Detection MethodsCorrelated SIEM alerts, cross-layer telemetry
IoCsSimultaneous anomalies at L3–L7
ContainmentLayered defenses (CDN + WAF + ISP scrubbing)
EradicationCoordinated mitigation strategy
RecoveryPhased service restoration
Post-IncidentRed-team simulations, IR playbook updates

3. Strategic Post-Incident Improvements

  • Implement always-on DDoS protection
  • Deploy CDN and Anycast architectures
  • Maintain tested IR playbooks
  • Conduct regular DDoS simulation exercises
  • Establish ISP and CERT escalation paths