Which SNMP versions transmit community strings in plain text and are considered insecure?

Which SNMP versions transmit community strings in plain text and are considered insecure?

• A. SNMP v1 and v2c
• B. SNMP v3
• C. SNMP v2c
• D. HTTP

Answer: (A)

Community strings act like passwords for SNMP access. In SNMP v1 and SNMP v2c, these strings are sent in clear text with each request and response, so anyone monitoring the network can read them and potentially gain unauthorized access. That lack of encryption makes these versions insecure for managing devices. SNMP v3, on the other hand, adds security features such as authentication to verify who is making the request and privacy to encrypt the data, protecting the information from eavesdropping and tampering. That’s why SNMP v3 is considered secure. HTTP is a different protocol and not part of SNMP’s security model, so it isn’t the right answer in the context of SNMP versions. Therefore, the insecure options are the versions that transmit community strings in plain text: SNMP v1 and v2c.

Community strings act like passwords for SNMP access. In SNMP v1 and SNMP v2c, these strings are sent in clear text with each request and response, so anyone monitoring the network can read them and potentially gain unauthorized access. That lack of encryption makes these versions insecure for managing devices.

SNMP v3, on the other hand, adds security features such as authentication to verify who is making the request and privacy to encrypt the data, protecting the information from eavesdropping and tampering. That’s why SNMP v3 is considered secure.

HTTP is a different protocol and not part of SNMP’s security model, so it isn’t the right answer in the context of SNMP versions.

Therefore, the insecure options are the versions that transmit community strings in plain text: SNMP v1 and v2c.