Which credential protocol is recommended for securing NPM configurations?

Which credential protocol is recommended for securing NPM configurations?

• A. FTP
• B. Plain HTTP
• C. SNMPv2c with community string
• D. SNMPv3 with encrypted credentials

Answer: (D)

Securing credentials for NPM configurations requires a protocol that provides both authentication and encryption. SNMPv3 is designed with these security features, offering privacy (encryption) and authentication to protect credentials as they’re used by the management system and transmitted to devices. This means the credentials can be kept confidential even if someone eavesdrops on the network, and their integrity can be verified. The other options fall short: FTP and Plain HTTP transmit data in the clear, so credentials could be captured easily. SNMPv2c relies on community strings and does not encrypt traffic, leaving credentials exposed. Therefore, SNMPv3 with encrypted credentials is the appropriate choice for securing NPM configurations.

Securing credentials for NPM configurations requires a protocol that provides both authentication and encryption. SNMPv3 is designed with these security features, offering privacy (encryption) and authentication to protect credentials as they’re used by the management system and transmitted to devices. This means the credentials can be kept confidential even if someone eavesdrops on the network, and their integrity can be verified.

The other options fall short: FTP and Plain HTTP transmit data in the clear, so credentials could be captured easily. SNMPv2c relies on community strings and does not encrypt traffic, leaving credentials exposed. Therefore, SNMPv3 with encrypted credentials is the appropriate choice for securing NPM configurations.