Which credentialing practice helps minimize exposure when configuring SNMP access in NPM?

Which credentialing practice helps minimize exposure when configuring SNMP access in NPM?

• A. Use SNMPv1 without encryption.
• B. Prefer SNMPv3 and scope credentials to least-privilege.
• C. Store credentials in clear text on the server.
• D. Share credentials with all admins.

Answer: (C)

Minimize exposure by using SNMPv3 and granting only the minimum privileges needed for monitoring. SNMPv3 provides authentication and option encryption, so credentials and data aren’t exposed in transit. Coupling that with least-privilege scoping means the account can perform only the actions and access only the data necessary for monitoring, reducing the blast radius if the credentials are compromised. Avoid using older SNMP versions that send credentials in plaintext, and never store credentials in clear text or share them broadly among admins. Proper credential management—encrypted storage, rotation, and restricting access to those who truly need it—further reduces risk.

Minimize exposure by using SNMPv3 and granting only the minimum privileges needed for monitoring. SNMPv3 provides authentication and option encryption, so credentials and data aren’t exposed in transit. Coupling that with least-privilege scoping means the account can perform only the actions and access only the data necessary for monitoring, reducing the blast radius if the credentials are compromised.

Avoid using older SNMP versions that send credentials in plaintext, and never store credentials in clear text or share them broadly among admins. Proper credential management—encrypted storage, rotation, and restricting access to those who truly need it—further reduces risk.