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

48. CEH v13 Exam Modules Map and Practice Questions

48.3 Modules 06–10 Map (System Hacking through DoS)

By Last updated:

Modules 06–10 = access, malware awareness, sniff, people, availability. Ghabru naka – defensive framing.

Module 06 – System Hacking
Book: ch22 (Password Attacks), ch23 (Exploitation with Metasploit – OWN lab), ch26 (Privilege Escalation).
Focus: credential weakness, post-access awareness, privilege paths on OWN Metasploitable – paired with hardening.
Blue: MFA, password policy, patch, remove risky SUID/sudo misconfig, EDR/log review.

Module 07 – Malware Threats
Book: ch39 (Malware Threats), ch28 (Digital Forensics awareness).
Focus: families at concept level (virus/worm/trojan/ransomware ideas); delivery themes; no payload building.
Blue: backups offline-ish, least privilege, mail/web filtering, IR playbook, do not run mystery samples on prod.

Module 08 – Sniffing
Book: ch24 (Traffic Sniffing and Analysis).
Focus: why cleartext on a shared segment is dangerous; Wireshark for defence and lab learning.
Blue: TLS everywhere practical; avoid FTP/telnet; network segmentation; detect promiscuous oddities in lab study.

Module 09 – Social Engineering
Book: ch27 (Social Engineering Awareness).
Focus: phishing / pretext themes; consented simulation only; 1930 / cybercrime.gov.in awareness for India.
Blue: MFA, report button culture, DMARC chain, verify payment-change calls.

Module 10 – Denial-of-Service
Book: ch40 (DoS and DDoS – Availability Attacks).
Focus: availability pillar; volumetric vs application-layer ideas; never run flood tools at third parties.
Blue: rate limits, autoscaling/capacity, upstream DDoS service pattern, playbooks.

Red team (attacker) does Blue team (defender) detects / stops
Password spray / weak SSH on OWN .20 only fail2ban-style blocks; key auth; alert on 4625-style failures
Cleartext sniff demo on host-only lab bridge Force HTTPS; kill telnet/FTP in hardening checklist
Phish kit against classmates "for fun" Consented sim only; MFA; report path; never real victims

Ravindra Bagale's Tip

In Module 06, students put Metasploit screenshots in their portfolio and call them a "production hack". That is career death. Caption: OWN lab / fictional Sahyadri. The exam also expects the language of ethics. Remember this.

Lab

Raja-Rani OWN Amazon Linux: sudo yum update -y habit; ensure SSH keys; sudo service sshd status (or sshd name on your image). From Kali, confirm password auth is off if you hardened it. Document Module 06 Blue controls in four bullets.

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.