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

48. CEH v13 Exam Modules Map and Practice Questions

48.2 Modules 01–05 Map (Intro through Vulnerability Analysis)

By Last updated:

Modules 01–05 = foundation. Ethics, footprint, scan, enum, vuln analysis. Aata pudhe jaauya.

Module 01 – Introduction to Ethical Hacking
Book: ch17 (Why Learn All This Before Kali), ch18 (Ethics, the Law and a Safe Kali Lab), ch34 (Indian Cyber Law), ch35 (Careers, Certifications and Bug Bounty).
Focus: types of hackers (awareness), CIA triad, five phases at high level, legal permission, lab design.
Blue: policy, written scope, Acceptable Use, IT Act awareness.

Module 02 – Footprinting and Reconnaissance
Book: ch19 (Information Gathering and Scanning), ch36 (Amass, WhatWeb and friends).
Focus: passive OSINT vs active probes; whois/DNS/subdomain ideas; technology fingerprint purpose.
Blue: shrink public footprint; monitor certificate / DNS noise; no secrets in public repos.

Module 03 – Scanning Networks
Book: ch01–ch03 (IP, ports, TCP/UDP), ch19 (Nmap family).
Focus: host discovery and port/service awareness on OWN ranges; TCP vs UDP sense.
Blue: SG/firewall least privilege; detect noisy scans; close unused ports on public EIP.

Module 04 – Enumeration
Book: ch37 (NetBIOS/SMB/SNMP/LDAP/SMTP/NFS/DNS enum), ch38 (AD awareness).
Focus: what "extra detail after scan" means – shares, users, banners – without exploit steps.
Blue: disable unused services; null-session style risks closed; log auth to directory services.

Module 05 – Vulnerability Analysis
Book: ch20 (Vulnerability Scanning and Assessment).
Focus: scanner reports as prioritisation input, not automatic exploit. CVE idea + risk ranking.
Blue: patch SLAs; internet-facing first; false-positive hygiene; change tickets.

Red team (attacker) does Blue team (defender) detects / stops
OSINT + noisy Nmap on out-of-scope cafe Wi-Fi Written IP list; host-only adapter; refuse out-of-scope
Runs vuln scanner then "auto-exploit" mindset Triage CVE by exposure; patch; re-scan OWN asset only

Ravindra Bagale's Tip

Modules 03–04 get confused: scanning = "what is open?", enumeration = "extra detail from that open service". Students mix both into a single nmap flag. In exam MCQs, watch the phase order. Got it?

Lab

On Kali 192.168.56.10 against only Metasploitable 192.168.56.20: gentle nmap -sS -T2 -p 22,80,139,445 192.168.56.20. Note open ports. Write one line per port: "Blue would …". No exploit. Snapshot notes for Module 03–04.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

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.