143-420 · Question #125
You want to disable certain non-secure management interfaces on your switches. Which two interfaces would you consider disabling? (Choose two.)
The correct answer is A. SNMP D. HTTP. See the full explanation below for the reasoning.
Question
You want to disable certain non-secure management interfaces on your switches. Which two interfaces would you consider disabling? (Choose two.)
Options
- ASNMP
- BSCP
- CSSH
- DHTTP
How the community answered
(24 responses)- A71% (17)
- B8% (2)
- C21% (5)
Community Discussion
4The correct answers are A, SNMP, and D, HTTP. Both of these protocols transmit data in cleartext, which is exactly what you want to avoid when securing management interfaces on a switch. HTTP sends credentials and session data unencrypted, and SNMP versions 1 and 2c use community strings that travel in plaintext across the wire, making them easy targets for interception. SSH and SCP, on the other hand, are already encrypted protocols, so they are the ones you want to keep enabled as your secure management alternatives. Our group landed pretty firmly on this one, but if anyone has seen a version of this question where the context points to SNMPv3 specifically, weigh in below because that could change the calculus a bit.
The SNMPv3 point is worth flagging even now, because if the stem specifies v3 with authPriv mode you are looking at authenticated and encrypted traffic, which flips it from a liability to an acceptable management channel and knocks it off the disable list entirely.
SNMP and HTTP are the usual suspects here because neither one encrypts traffic in their common default configurations, which means credentials and data move across the wire in plaintext. Are you clear on why SSH and SCP stay on the safe list, or do you want to talk through what makes a management interface "secure" versus not?
I thought SCP for sure but SNMP and HTTP make sense, both send creds in plaintext.