312-50 ยท Enumeration
What are the core enumeration countermeasures?
Disabling unused services, restricting null sessions, SNMP v3, blocking ports at the perimeter, limiting directory access, and monitoring.
Key points
- Disable services you do not need, restrict anonymous and null-session access, use SNMPv3 with authentication and encryption, block NetBIOS/SMB and other management ports at the perimeter, limit what directories and DNS return, and monitor logs for repeated probing.
Source: https://www.rfc-editor.org/rfc/rfc3414
Practice questions
Which action stops SNMP community strings from crossing the network in cleartext?
- Use SNMPv3 with authentication and encryption
- Keep public but shorten it
- Disable logging on the agent
- Use UDP 162 for requests
Show answer
Answer: A. Use SNMPv3 with authentication and encryption
v3 protects the exchange. The other options leave v1/v2c cleartext or are unrelated.
Which measures reduce enumeration exposure?
- Disable unused services
- Restrict anonymous access
- Block NetBIOS/SMB ports at the perimeter
- Allow zone transfers to any host
- Keep default community strings
Show answer
Answer: A. Disable unused services, B. Restrict anonymous access, C. Block NetBIOS/SMB ports at the perimeter
The first three shrink the attack surface; the last two are the weaknesses attackers look for.
Replacing the community string public with a custom value makes SNMPv2c traffic encrypted.
Show answer
Answer: False
A custom string only resists guessing; v2c still sends it in cleartext. Encryption needs v3.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
