Ravindra BagaleCourses & study guides मराठी Track your progress

40. DoS and DDoS – Availability Attacks

40.2 Volumetric and Flood Concepts – Defender View

By Last updated:

Volumetric = "pipe bharun tak". Common names you hear in CEH exam modules:

  • UDP flood – many UDP packets to random / chosen ports; target spends CPU checking / responding
  • ICMP flood – ping-style overload (less common alone at huge scale today, still taught)
  • HTTP flood – many GET/POST to heavy pages (looks more "legitimate" than raw UDP)

Blue does not need to craft the perfect flood. Blue needs: traffic baselines, sudden PPS/bps alerts, ability to ask ISP/cloud to scrub, and origin that fails soft (cache, queue, 503) instead of total crash.

# Amazon Linux / CentOS-class lab host YOU own – watch interface counters (concepts)
ip -s link
# Or: watch -n1 'cat /proc/net/dev'
# Kali lab (host-only only): sudo apt install hping3 apache2-utils  # for later controlled labs
Red team (attacker) does Blue team (defender) detects / stops
UDP flood to saturate uplink Upstream scrubbing; drop UDP to unused ports at border; capacity planning
HTTP GET flood on search / login CDN cache; rate limit; CAPTCHA / bot management; WAF
Spoofs sources where protocol allows BCP38 / anti-spoof at ISP; don't rely on source IP alone

Ravindra Bagale's Tip

Students see one flood packet in Wireshark and say "DDoS proven". Proof = volume + impact + distribution. A small lab stress test ≠ an internet DDoS. Interview: "I measure availability with baselines and scrubbing options, not one packet capture."

Practice task

Sahyadri Traders (Nashik) sathi 8-line capacity checklist: peak festival traffic estimate (honest guess, no fake Gbps), CDN yes/no, origin rate limit yes/no, who calls ISP at 2 AM. Mag Red vs Blue table madhun volumetric row copy karun "how we verify" column bhara.

Extended teaching notes

Why this lesson matters

Availability attacks try to exhaust bandwidth, connections or app workers. Learning them is about detection and defence — never about stressing networks you do not own (that can be illegal and harmful).

  • Rate limits and WAF/CDN at the edge.
  • SYN cookies / tuning on servers.
  • Autoscaling with care (cost controls).
  • Keep IoT devices off default passwords (Mirai lesson).
  • Lab simulations only on isolated networks you own.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.