37. Enumeration: NetBIOS, SMB, SNMP, LDAP, SMTP, NFS and DNS
37.1 What Is Enumeration and Why It Matters
Reconnaissance – publicly available info (whois, search, OSINT). Scanning – live hosts, open ports, service versions (Nmap). Enumeration – open service la query karun structured details: user lists, share names, SNMP OIDs, DNS zone dump. Samjla ka?
| Phase | Example question | Tool idea |
|---|---|---|
| Recon | Company cha domain kay? | whois, theHarvester |
| Scan | Port 445 open aahe ka? | Nmap |
| Enum | Share madhe konti folders? Konti users? | smbclient, enum4linux |
Ethics: permission nahi – gunha. Lab madhe practice, report madhe findings + remediation donhi liha. CEH / job interview madhe pan hech expected aahe: "I enumerate only in scope, and I always recommend the fix."
Ravindra Bagale's Tip
Students look at Nmap -sV output and say "enumeration done". Version detection is part of scanning; enumeration is when you use the service's protocol to pull out users/shares/zones. Explain the difference clearly in interviews – it earns marks.
Ravindra Bagale's Tip – मराठी
Students Nmap -sV output बघून म्हणतात "enumeration झाले". Version detect हा scanning चा भाग आहे; enumeration तेव्हा होते जेव्हा तुम्ही service protocol वापरून users/shares/zone काढता. Interview मध्ये फरक clear सांगा – marks मिळतात.
Ravindra Bagale's Tip – हिंदी
Students Nmap -sV output देखकर कहते हैं "enumeration हो गया". Version detect करना scanning का हिस्सा है; enumeration तब होता है जब आप service protocol इस्तेमाल करके users/shares/zone निकालते हो. Interview में फ़र्क clear बताओ – marks मिलते हैं.
Lab
Kali var nmap -sV -p 21,22,25,53,139,445,161,389,2049 192.168.56.20 chalaa. Konte services "enum candidates" ahet te note kara (SMB, SMTP, DNS, NFS...). He chapter sathi aapli hit-list. Production IP nako – fakt lab.
Extended teaching notes
Why this lesson matters
Enumeration maps what a network exposes. Defenders use the same ideas to close shares, fix SNMP community strings, restrict LDAP binds and stop zone transfers.
Hardening related services
[('SSH', 'Key auth, no root login, Fail2ban or equivalent, SG limited to your IP/VPN.', '', ''), ('SMB / NFS / LDAP / SNMP', 'Do not expose to the internet; patch; strong auth; disable unused versions (e.g. SMBv1).', '', ''), ('SMTP', 'Authenticated relay only; SPF/DKIM/DMARC for your domains.', '', ''), ('DNS', 'Restrict zone transfers; monitor for unexpected records (crt.sh for certs).', '', ''), ('Firewalls', 'Host firewall + cloud SG/NSG; default deny; document every allow.', '', '')]
Lab rule
Run enumeration only against host-only lab VMs you own. Then write the defensive fix for each open service you found.
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)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- 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.