What is a key difference between SNMP v2c and SNMP v3?

• A. v2c includes encryption by default.
• B. v2c uses weaker authentication than v3.
• C. v3 adds security features (auth/privacy) vs v2c insecure.
• D. v2c and v3 have identical security.

Answer: (C)

SNMP v3 stands out because it adds built-in security for management traffic, namely authentication to verify who is sending the messages and privacy to encrypt the payload so sensitive data isn’t exposed. In contrast, SNMP v2c relies on a simple community string, which is typically sent in the clear and provides no formal authentication or encryption. This makes v2c insecure for many environments since anyone who can sniff traffic could read or tamper with the data.

The security improvements in v3 come from its User-based Security Model (USM), which supports authenticated messages (using algorithms like MD5 or SHA) and encrypted payloads (using DES or AES), along with access control mechanisms to restrict who can query or set information. That combination—authenticity and confidentiality—is why v3 is distinguished from v2c.

So the correct distinction is that SNMP v3 adds security features (authentication and privacy) that SNMP v2c does not provide, making v3 the more secure option. The other statements either misstate the level of security in v2c or claim equivalence in security, which isn’t accurate.