Simple Network Management Protocol Version 3 (SNMPv3) is based on the basic structure and architecture of SNMPv1 and SNMPv2. However, SNMPv3 enhances the basic architecture to incorporate administration and security capabilities, such as authentication, access control, data integrity check, data origin verification, message timeliness check, and data confidentiality.
To implement message level security and access control, SNMPv3 introduces the user-based security model (USM) and the view-based access control model (VACM).
-
User-Based Security Model. The user-based security model (USM) provides message-level security. It enables you to configure users and security parameters for the SNMP agent and the SNMP manager. USM offers the following features:
-
Data integrity: To protect messages from being modified during transmission through the network.
-
Data origin verification: To authenticate the user who sent the message request.
-
Message timeliness: To protect against message delays or replays.
-
Data confidentiality: To protect the content of messages from being disclosed to unauthorized entities or individuals.
-
View-Based Access Control Model. The view-based access control model (VACM) enables you to configure access rights to a specific subtree of the MIB based on various parameters, such as security level, security model, user name, and view type. It enables you to configure agents to provide different levels of access to the MIB to different managers.
NetScaler supports the following entities that enable you to implement the security features of SNMPv3:
-
SNMP Engines
-
SNMP Views
-
SNMP Groups
-
SNMP Users
These entities function together to implement the SNMPv3 security features. Views are created to allow access to subtrees of the MIB. Then, groups are created with the required security level and access to the defined views. Finally, users are created and assigned to the groups.
The view, group, and user configuration are synchronized and propagated to the secondary node in a high availability (HA) pair. However, the engine ID is neither propagated nor synchronized as it is unique to each NetScaler appliance.
To implement message authentication and access control, you need to do the following: