![]() |
Table Of Contents
AES and 3-DES Encryption Support for SNMP Version 3
Prerequisites for AES and 3-DES Encryption Support for SNMP Version 3
Information About AES and 3-DES Encryption Support for SNMP Version 3
Management Information Base Support
How to Configure AES and 3-DES Encryption Support for SNMP Version 3
Adding a New User to an SNMP Group
Verifying SNMP User Configuration
Feature Information for AES and 3-DES Encryption Support for SNMP Version 3
AES and 3-DES Encryption Support for SNMP Version 3
First Published: May 2005Last Updated: June 5, 2007The AES and 3-DES Encryption Support for SNMP Version 3 feature enhances the encryption capabilities of SNMP version 3. Data Encryption Standard (DES) support was introduced in Cisco IOS Release 12.0 and expanded in Cisco IOS Release 12.1. This support for Simple Network Management Protocol (SNMP) version 3 User-Based Security Model (USM) is complaint with RFC 3414, which defines DES as the only required method of message encryption for SNMP version 3 authPriv mode.
The AES and 3-DES Encryption Support for SNMP Version 3 feature adds Advanced Encryption Standard (AES) 128-bit encryption in compliance with RFC 3826. RFC 3826 extensions have been included in the SNMP-USM-AES-MIB. In addition, Cisco-specific extensions to support Triple-Data Encryption Algorithm (3-DES) and AES 192-bit and 256-bit encryption have been added to the CISCO-SNMP-USM-MIB. Additional information can be found in the Internet-Draft titled Extension to the User-Based Security Model (USM) to Support Triple-DES EDE in "Outside" CBC Mode that can be found at the following URL: http://www.snmp.com/eso/draft-reeder-snmpv3-usm-3desede-00.txt.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for AES and 3-DES Encryption Support for SNMP Version 3" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for AES and 3-DES Encryption Support for SNMP Version 3
•
Information About AES and 3-DES Encryption Support for SNMP Version 3
•
How to Configure AES and 3-DES Encryption Support for SNMP Version 3
•
Feature Information for AES and 3-DES Encryption Support for SNMP Version 3
Prerequisites for AES and 3-DES Encryption Support for SNMP Version 3
•
The network management station (NMS) must support SNMP version 3 to use this feature of the SNMP agent.
•
This feature is available in only Cisco IOS software images where encryption algorithms are supported.
Information About AES and 3-DES Encryption Support for SNMP Version 3
To configure the AES and 3-DES Encryption Support for SNMP Version 3 feature, you should understand the following concepts:
•
Management Information Base Support
SNMP Architecture
The architecture for describing Internet Management Frameworks contained in RFC 3411 describes the SNMP engine as composed of the following components:
•
Dispatcher
•
Message Processing Subsystem
•
Security Subsystem
•
Access Control Subsystem
Applications make use of the services of these subsystems. It is important to understand the SNMP architecture and the terminology of the architecture to understand where the Security Model fits into the architecture and interacts with the other subsystems within the architecture. The information is contained in RFC 3411 and your are encouraged to review this RFC to obtain an understanding of the SNMP architecture and subsystem interactions.
Encryption Key Support
In the AES and 3-DES Encryption Support for SNMP Version 3 feature the Cipher Block Chaining/Data Encryption Standard (CBC-DES) is the privacy protocol. Originally only DES was supported (as per RFC 3414). This feature adds support for AES-128 (as per RFC 3826) and AES-192, AES-256 and 3-DES (as per CISCO-SNMP-USM-OIDS-MIB).
•
AES encryption uses the Cipher Feedback (CFB) mode with encryption key sizes of 128, 192, or 256 bits.
•
3DES encryption uses the 168-bit key size for encryption.
The AES Cipher Algorithm in the SNMP User-based Security Model draft describes the use of AES with 128-bit key size. However, the other options are also implemented with the extension to use the USM. There is currently no standard for generating localized keys for 192- or 256-bit size keys for AES or for 168-bit size key for 3-DES. There is no authentication protocol available with longer keys.
Management Information Base Support
The AES and 3-DES Encryption Support for SNMP Version 3 feature supports the selection of privacy protocols through the CLI and the Management Information Base (MIB). A new standard MIB, SNMP-USM-AES-MIB, provides support for the 128-bit key in AES. The extended options of AES with 192- or 256-bit keys and 3-DES are supported as extensions to the SNMP-USM-MIB, in the Cisco-specific MIB, CISCO-SNMP-USM-EXT-MIB.
How to Configure AES and 3-DES Encryption Support for SNMP Version 3
This section contains the following procedures:
•
Adding a New User to an SNMP Group
•
Verifying SNMP User Configuration
Adding a New User to an SNMP Group
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server user
DETAILED STEPS
Verifying SNMP User Configuration
To display information about the configured characteristics of Simple Network Management Protocol (SNMP) users, use the show snmp user command in privileged EXEC mode.
SUMMARY STEPS
1.
enable
2.
show snmp user name
Note
The show snmp user command displays all the users configured on the router. However, unlike other snmp configurations, the snmp-server user command will not appear on the "show running" output.
DETAILED STEPS
Step 1
enable
Enters privileged EXEC mode. Enter your password when prompted.
Step 2
show snmp user name
The following example specifies the username as abcd, the engine ID string as 00000009020000000C025808, and the storage type as nonvolatile:
Router# show snmp user abcdUser name: abcdEngine ID: 00000009020000000C025808storage-type: nonvolatile active access-list: 10Rowstatus: activeAuthentication Protocol: MD5Privacy protocol: 3DESGroup name: VacmGroupNameGroup name: VacmGroupName
Additional References
The following sections provide references related to the AES and 3-DES Encryption Support for SNMP Version 3 feature.
Related Documents
Related Topic Document TitleSNMP configuration tasks
Cisco IOS Network Management Configuration Guide, Release 12.4
SNMP commands
Cisco IOS Network Management Command Reference, Release 12.4T
Standards
Standard Titledraft-reeder-snmpv3-usm-3desede-00.txt
Extension to the User-Based Security Model (USM) to Support Triple-DES EDE in "Outside" CBC Mode
MIBs
MIB MIBs Link•
SNMP-USM-AES-MIB
•
CISCO-SNMP-USM-OIDS-MIB
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents only commands that are new or modified.
show snmp user
To display information about the configured characteristics of Simple Network Management Protocol (SNMP) users, use the show snmp user command in privileged EXEC mode.
show snmp user [username]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
An SNMP user must be part of an SNMP group, as configured using the snmp-server user username group-name command.
When the username argument is not entered, the show snmp user command displays information about all configured users. If you specify the username argument, if one or more users of that name exists, the information pertaining to those users is displayed. Because this command displays users configured with the SNMP engine ID of the local agent and other engine IDs, there can be multiple users with the same username.
When configuring SNMP, you may see the logging message "Configuring snmpv3 USM user." USM stands for the User-based Security Model for version 3 of the Simple Network Management Protocol (SNMPv3). For further information on the USM, see RFC 2574.
Examples
The following is sample output from the show snmp user command. The output indicates the username as authuser, the engine ID string as 00000009020000000C025808, and the storage type as nonvolatile:
Router# show snmp user authuserUser name: authuserEngine ID: 00000009020000000C025808storage-type: nonvolatile active access-list: 10Rowstatus: activeAuthentication Protocol: MD5Privacy protocol: DESGroup name: VacmGroupNameTable 1 describes the significant fields shown in the display.
snmp-server user
To configure a new user to a Simple Network Management Protocol (SNMP) group, use the snmp-server user command in global configuration mode. To remove a user from an SNMP group, use the no form of this command.
snmp-server user username group-name [remote host [udp-port port]] {v1 | v2c | v3 [encrypted] [auth {md5 | sha} auth-password]} [access [ipv6 nacl] [priv {des | 3des | aes {128 | 192 |256}} privpassword] {acl-number | acl-name}]
no snmp-server user username group-name [remote host [udp-port port]] {v1 | v2c | v3 [encrypted] [auth {md5 | sha} auth-password]} [access [ipv6 nacl] [priv {des | 3des | aes {128 | 192 |256}} privpassword] {acl-number | acl-name}]
Syntax Description
Command Default
See Table 2 in the "Usage Guidelines" section for default behaviors for encryption, passwords, and access lists.
Command Modes
Global configuration
Command History
Usage Guidelines
To configure a remote user, specify the IP address or port number for the remote SNMP agent of the device where the user resides. Also, before you configure remote users for a particular agent, configure the SNMP engine ID, using the snmp-server engineID command with the remote option. The remote agent's SNMP engine ID is needed when computing the authentication and privacy digests from the password. If the remote engine ID is not configured first, the configuration command will fail.
For the privpassword and auth-password arguments, the minimum length is one character; the recommended length is at least eight characters, and should include both letters and numbers.
Table 2 describes the default user characteristics for encryption, passwords, and access lists.
SNMP passwords are localized using the SNMP engine ID of the authoritative SNMP engine. For informs, the authoritative SNMP agent is the remote agent. You need to configure the remote agent's SNMP engine ID in the SNMP database before you can send proxy requests or informs to it.
Working with Passwords and Digests
No default values exist for authentication or privacy algorithms when you configure the command. Also, no default passwords exist. The minimum length for a password is one character, although Cisco recommends using at least eight characters for security. If you forget a password, you cannot recover it and will need to reconfigure the user. You can specify either a plain-text password or a localized message digest 5 (MD5) digest.
If you have the localized MD5 or SHA digest, you can specify that string instead of the plain-text password. The digest should be formatted as aa:bb:cc:dd where aa, bb, and cc are hex values. Also, the digest should be exactly 16 octets long.
Examples
The following example shows how to add the user abcd to the public SNMP server group. In this example, no access list is specified for the user, so the standard named access list applied to the group applies to the user.
Router(config)# snmp-server user abcd public v2cThe following example shows how to add the user abcd to the public group. In this example, access rules from the standard named access list qrst apply to the user.
Router(config)# snmp-server user abcd public v2c access qrstIn the following example, the plain-text password "cisco123" is configured for the user "abcd" in the SNMPv3 group "public":
Router(config)# snmp-server user abcd public v3 auth md5 cisco123When you enter a show running-config command, a line for this user will be displayed. To learn if this user has been added to the configuration, type the show snmp user command.
If you have the localized MD5 or Secure Hash Algorithm (SHA) digest, you can specify that string instead of the plain-text password. The digest should be formatted as aa:bb:cc:dd where aa, bb, and cc are hex values. Also, the digest should be exactly 16 octets long.
In the following example, the MD5 digest string is used instead of the plain text password:
Router(config)# snmp-server user abcd public v3 encrypted auth md5 00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FFIn the following example, the user "abcd" is removed from the SNMP group "public":
Router(config)# no snmp-server user abcd public v2cIn the following example, the user "abcd" from the SNMP group "public" specifies the use of the 168-bit 3DES algorithm for privacy encryption with "secure3des" as the password.
Router(config)# snmp-server user abcd public priv 3des secure3desRelated Commands
Feature Information for AES and 3-DES Encryption Support for SNMP Version 3
Table 3 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 3 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2005, 2007 Cisco Systems, Inc. All rights reserved.