Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
SNMP v1 and v2c authenticate with a cleartext community string, and the defaults are public and private. Version 3 fixes it, and almost nobody has finished migrating.

What Is SNMP Security?
Simple Network Management Protocol is how monitoring systems read counters, interface states, and configuration from network devices, and how those devices send traps when something changes. It is everywhere, it is usually configured once during installation, and in its older versions it offers no meaningful security at all.
Versions 1 and 2c authenticate with a community string, which is a password sent in plaintext in every packet. There are conventionally two: a read-only string and a read-write one. The defaults, shipped by nearly every vendor for decades, are public and private.
Read access alone is a serious disclosure. A read-only query against a router or switch returns the full interface list with addresses and descriptions, the ARP and routing tables, the system version and model, uptime, and often the hostnames and locations entered at installation. For an attacker performing internal reconnaissance that is a network map obtained without touching a single host. Tools such as snmpwalk, onesixtyone, and the Nmap SNMP scripts do it in seconds, and community strings are guessable by brute force because there is no lockout.
Read-write access is worse. On Cisco devices, the CISCO-CONFIG-COPY-MIB allows an attacker with the write string to instruct the device to TFTP its running configuration to a server they control — which yields enable password hashes, VPN pre-shared keys, and the configuration of every interface. Writing a modified configuration back is equally possible.
Version 3 replaces the community string with the User-based Security Model, offering three levels:
| Level | Authentication | Encryption |
|---|---|---|
| noAuthNoPriv | None | None |
| authNoPriv | HMAC with SHA | None |
| authPriv | HMAC with SHA | AES |
Only authPriv is worth deploying. Use SHA-256 or better for authentication and AES-128 or AES-256 for privacy; MD5 and DES are still offered by most implementations and should not be selected. Give each monitoring system its own SNMPv3 user rather than sharing one, so that credentials can be rotated independently and access can be attributed.
SNMP has been used as a reflection and amplification vector, with GetBulkRequest producing responses far larger than the query. A device with a default community string reachable from the internet is both an information disclosure and a weapon pointed at someone else. The fix is the same in both cases: SNMP should never be reachable from the internet, and UDP 161 should be blocked inbound at the perimeter without exception.
SNMP sits in the same category as NTP and TFTP: infrastructure protocols that predate any threat model, are rarely reviewed, and quietly provide an attacker with exactly the information they need. A network device configuration audit usually finds them all at once. Our Infrastructure and Architecture Review Services cover management plane hardening across the switching and routing estate.
Yes. A read-only query returns interface lists with addresses, routing and ARP tables, software versions, hardware models, and configured descriptions. That is a complete internal network map handed to an attacker performing reconnaissance, obtained without compromising a single host. It also reveals software versions precisely enough to select an exploit.
Set a long, random, unique community string rather than a default or a word, make it read-only, and apply an access control list permitting only your monitoring servers to query it. Place the device on a management network that general users cannot reach. If the device supports no access control at all, consider whether SNMP can simply be disabled.
Use the authPriv security level with SHA-256 or stronger for authentication and AES-128 or AES-256 for encryption. Avoid MD5 and DES, which most implementations still offer. Create a separate SNMPv3 user per monitoring system so credentials can be rotated independently, and use SNMP views to limit each user to the MIB subtree it actually needs.
Yes. GetBulkRequest queries produce responses much larger than the request, so an internet-reachable device with a guessable community string can be used as a reflector in an amplification attack against someone else. Blocking UDP 161 inbound at the perimeter prevents this and also prevents the information disclosure, which is the same control for both problems.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.