SNMPv3 adds authentication and encryption to SNMP. Setting it up takes a few minutes per device once you know the three choices: security level, authentication method and privacy method.
Why SNMPv3
SNMP v1 and v2c send a community string in clear text, and anyone who captures it can read your device data and sometimes change it. SNMPv3 identifies a named user, can verify that messages are not altered and can encrypt them.
The three security levels
| Level | Authentication | Encryption |
|---|---|---|
| noAuthNoPriv | No | No |
| authNoPriv | Yes | No |
| authPriv | Yes | Yes |
Use authPriv wherever the device supports it.
Step by step
- Create a read-only SNMPv3 user on the device with a long authentication password and a different privacy password.
- Choose SHA for authentication and AES for privacy where available; avoid MD5 and DES unless old devices demand them.
- Limit the SNMP view to the information monitoring needs.
- Restrict access to the IP address of your monitoring server.
- Add the same user, protocols and passwords as a credential profile in your monitoring tool.
- Test with a GET and a WALK before adding the device to production monitoring.
Common mistakes
- Using the same password for authentication and privacy
- Mismatched protocols between device and monitoring tool
- Forgetting the engine ID after a device replacement
- Opening SNMP to the whole network instead of one server
- Leaving v2c enabled with a default community such as public
NexoraUNMS stores SNMPv3 credential profiles and includes an SNMP manager to test queries before a device goes live. See SNMP monitoring in NexoraUNMS.
Related guides: NexoraUNMS – Unified Network Management Software
SNMP Network Management SoftwareSNMP Trap vs Syslog: Differences and When to Use EachNexoraUNMS – Unified Network Management Software
See NexoraUNMS on a Live Demo Network
Watch monitoring, topology, alerts and configuration backup working together on sample data. Free demo from NexoraSoft; no obligation.
Book a Free Demo +91 98115 51004