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

37. Enumeration: NetBIOS, SMB, SNMP, LDAP, SMTP, NFS and DNS

37.4 LDAP Enumeration

By Last updated:

LDAP (Lightweight Directory Access Protocol) – directory service (users, groups, computers). Port 389 (LDAP) / 636 (LDAPS). Active Directory LDAP var chalte – deep AD enum Chapter 38 (Impacket, BloodHound).

Basics against OpenLDAP / lab directory (jar Metasploitable kiwa tumcha OpenLDAP lab asel):

sudo apt install -y ldap-utils
# Anonymous bind attempt (lab) – should FAIL on hardened servers
ldapsearch -x -H ldap://192.168.56.20 -b "dc=lab,dc=local" -s base
ldapsearch -x -H ldap://192.168.56.20 -D "" -w "" -b "dc=lab,dc=local"

Anonymous bind risk: konihi credentials shivay directory read – usernames, emails, group membership. Production madhe anonymous bind disable; LDAPS; least-privilege bind accounts; network ACL.

Metasploitable 2 var full AD nahi – mhanun ithe concepts + commands; Windows AD lab setup Chapter 38 madhe. Samjla ka?

Ravindra Bagale's Tip

Students get scared by ldapsearch syntax (-b, -D, -x). The Base DN (dc=lab,dc=local) is the root path of the directory – the domain parts. First look at the root attributes with -s base, then search deeper. AD tools come later – get the idea clear first.

Lab

Kali var ldapsearch -h vacha. Jar tumchya lab madhe OpenLDAP/AD nahi, tar notes madhe liha: (1) anonymous bind kay aahe, (2) LDAPS vs LDAP, (3) Chapter 38 madhe Impacket ne kay try karu. Jar LDAP port open asel (nmap -p 389,636 192.168.56.20) tar base query try kara – fail/success note kara.

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)

  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.