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

40. DoS and DDoS – Availability Attacks

40.8 Lab-Safe Simulation – Ethics First

By Last updated:

Allowed pattern:

  1. Build weak origin you own on host-only
  2. From Kali, generate controlled load to that IP only
  3. Measure impact; stop on timer
  4. Fix; re-measure
  5. Snapshot / revert

Banned: public IPs, amp against open resolvers, botnet builders, stresser/booter services (illegal), classmates' laptops without written permission.

# Kali → YOUR lab nginx only (example – keep concurrency LOW)
# ab -n 200 -c 10 http://192.168.56.40/
# siege -c 5 -t 20S http://192.168.56.40/
# hping3: only with trainer limits toward host-only target; never --flood on shared LAN
Red team (attacker) does Blue team (defender) detects / stops
Ignores scope; hits production Written lab scope; network isolation; legal reminder
Uses "stresser" SaaS Blue teaches: those services are criminal tools; never
Leaves flood running overnight Timer + partner watch + kill switch

Ravindra Bagale's Tip

"Just a quick try" on a friend's shop domain = IT Act risk. Written permission + your own lab. CEH exam modules also put ethics first. Keep this in mind.

Lab

Pair work: one student runs 30-second ab against partner's lab VIP; other watches top, nginx access.log, and ss -s. Switch. Write ethics paragraph in notes (Marathi+English mix OK).

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.

Extra depth

Re-read the original short section at the top of the page, then this expansion. Together they should exceed a solid lesson length. If anything still feels thin, add your own lab screenshot and a paragraph in your notebook — that personal evidence is what interviews ask for.

  • Permission before tools.
  • Patch and config before exploits.
  • Logs and backups before blame.
  • Teach one junior the warning from this page.