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

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

37.3 SNMP Enumeration

By Last updated:

SNMP (Simple Network Management Protocol) – devices (routers, printers, servers) monitoring sathi. UDP 161. Junya setups madhe community string public (read) / private (read-write) – passwords sarkhe, pan plain/default!

sudo apt install -y snmp snmp-mibs-downloader snmpcheck
# Walk the tree with community "public" (lab only – Metasploitable may expose SNMP)
snmpwalk -v2c -c public 192.168.56.20
snmp-check 192.168.56.20 -c public

Jar SNMP open asel tar hostname, interfaces, processes, sometimes software inventory – attacker la map milto. Write community asel tar config pan badlu shakto – khup dangerous.

Defence: default communities kadhun taka; SNMPv3 (auth + encryption) prefer kara; ACL – fakt NMS IP allow; UDP 161 internet kade expose karu naka; read-only wherever possible. He khup important aahe.

Ravindra Bagale's Tip

Students learn the public community in the lab and then try it on a real router "just to see". That is unauthorized access. SNMP enum only on your own lab device or within written scope. Interview: "How do you harden SNMP?" – v3, ACL, no defaults.

Lab

nmap -sU -p 161 192.168.56.20 – SNMP open aahe ka? Open asel tar snmpwalk -v2c -c public 192.168.56.20 try kara (lab). Closed asel tar note: "service not exposed – good for this host" ani SNMPv3 defence 5 bullets aaplya notes madhe liha.

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.