Configuring Cisco ISE for SNMPv3

-

In this article I would like to cover how to configure SNMPv3 for Cisco Identity Services Engine (ISE).


In a few deployments I’ve done, I’ve come across the need to configure ISE to send SNMPv3 traps to a Network Management System (NMS). SNMPv3 is perfect for ensuring the authentication and encryption of SNMP traffic, something that can’t be done with inferior SNMP versions.

Now, one would assume that we could just go ahead and configure ISE for SNMP via the GUI however, unfortunately that’s not the case. To actually configure ISE to send traps to an NMS system we need to configure the settings via the CLI.

The demonstration in the article is performed using a standalone ISE. This demonstration also assumes that you have connectivity between your NMS platform and ISE.

To see a live demonstration with testing, refer to the video that accompanies this article.

Configuration Steps



Enable SNMP

So that we can configure the required SNMPv3 settings for ISE, SNMP needs to be enabled. 
iselab/admin(config)# snmp-server enable

Configure ISE SNMP User



With access to the ISE GUI, enter global configuration mode and configure an SNMP user. You cannot set the authentication/encryption protocol however they will be visible once the user has been configured. ISE uses SHA for authentication and AES-128 for encryption. 
iselab/admin(config)# snmp-server user SNMPv3USER v3 plain authpassword privpassword
Change any of the following fields to match the requirements of your deployment.
SNMPv3USER = Username
authpassword = Authentication Password
privpassword = Encryption Password

Configure SNMP Host


Configure the SNMP host, this is the NMS system and all configurations should match. The remote EngineID needs to match the NMS system and must be applied in HEX. 
iselab/admin(config)# snmp-server host 192.168.50.5 version 3 SNMPv3USER 0x446172742E506F776572534E4D50 authpassword privpassword
SNMPv3USER = Username 0x446172742E506F776572534E4D50 = Remote Engine ID
authpassword = Authentication Password
privpassword = Encryption Password

Verify SNMP Configuration


You can verify the auth and priv protocols used by ISE by issuing the following command. 
iselab/admin# show snmp-server user 
User: SNMPv3USER
EngineID: IMKKQSHIGMB
Auth Protocol: sha
Priv Protocol: aes-128
Issue a show run to view the SNMPv3 output in its full entirety. 
iselab/admin# show run
Generating configuration...
!!!Output Omitted!!!
snmp-server enable
snmp-server host 192.168.50.5 version 3 SNMPv3USER 0x446172742E506F776572534E4D5
0 hash 0CA52B11FA1BFB8F2B163635CB401999429018B0 36160FE3BDA1C80CF74071F0107415A7
snmp-server engineID IMKKQSHIGMB
snmp-server user SNMPv3USER v3 hash 0x5eba2e35a45a9569b48316fcf2c2b14db041038a 0
x45947b10ef5ad484d77d2d322844c08a
That’s the configuration complete for ISE, you will now need to ensure that the configuration is applied on your NMS platform. The video below walks through the configuration and testing of the SNMPv3 configuration.




#Cisco #ISE #CiscoISE #networkwizkid #CiscoISESNMPv3 #LabEveryday #ConfiguringCiscoISESNMPv3 #NetworkSecurity #ConfigureISESNMPv3 #SNMPv3 #SNMP #ISE24 #PowerSNMP #ConfigureCiscoISESNMPv3 #ISESNMPconfiguration
Kelvin Charles - Network and Cyber Security Professional.

Popular Posts

Capturing EAPOL and RADIUS Using Wireshark

-
Image
In this article we are going to take a look at how to capture Extensible Authentication Protocol Over LAN (EAPOL) and Remote Authentication Dial-In User Service (RADIUS) packets using Wireshark. This article can be useful for troubleshooting 802.1x within your environment and can also be used for learning purposes. The following topology has been used to gather the required output for this article. Note: This article will only cover the switch configurations that are required to gather EAPOL and RADIUS configuration. Overview of the Topology The supplicant is configured to perform 802.1x using EAP-TLS as the authentication method The user certificate on the supplicant will be used for authentication The supplicant has Wireshark installed Cisco ISE is used for authentication and authorisation The supplicant is assigned to VLAN 10 upon authentication and all other endpoint ports are assigned to VLAN 99 Sniffer device is running Wireshark in order to capture RADIUS flows via SPAN 802.1x
Read more

Configuring Cisco Smart License Software

-
In this article, I would like to demonstrate how to configure Cisco Smart Licensing on the virtual Cisco Adaptive Security Appliance (ASAv). This post assumes that readers already have access to there own Smart Account and would like to know the process of applying licenses. Step 1: Generate ID Token Sign into your Cisco Software Portal: software.cisco.com and navigate to “Smart Software Licensing” You will now need to create an ID token for your device, this is required for communication between the device and the licensing authority. Follow the steps below to create a new token. Click Inventory >>> General >>> New Token and select your preferred options and enter a description for your token. Once you are happy with your token settings click Create Token . You should now have a token created which can be copied over to the device you wish to license. All commands and output from this point will be related to the ASA so please seek out further advice if you wish
Read more

Cisco :: FXOS Authentication Using TACACS

-
In this article, I will describe how to enable authentication and authorization for Firepower eXtensible Operating System (FXOS) devices. The use case presented in this document illustrates how Cisco Identity Services Engine (ISE) can be utilised with attribute-value pairs (AV-Pairs) to authenticate and authorize users accessing the Firepower Chassis Manager (FCM) or FXOS platforms via TACACS+. At the time of writing this post, I found that limited documentation existed and of that documentation that did exist, the examples given weren’t as straightforward. In an effort to make this process easier for my colleagues and customers to understand I have put together the following instructions based on a previous use case given to me. Extracts of this document have been taken from a wider document I am currently creating. I will update this article with the complete document when it has been finalized. Requirements A ‘Device Administration’ license is required in order to use TACACS+ with
Read more

Configuring Remote Access VPN on Firepower

-
Image
In this article we are going to take a look at how to configure remote access VPN's on Firepower devices. This demonstration is based on the following lab environment: Cisco Virtual Firepower Management Center Cisco Virtual Firepower Threat Defense Cisco ISE 2.6 Windows host with AnyConnect VPN Windows Server 2019 (CA Server) All Firepower devices are running version 6.5 Note: ISE is used for authentication and authorization in the following lab however the configuration elements of ISE are out of scope for this demonstration. Generate a CSR for Remote Access VPN's Those accessing your network remotely need to trust the service you're running. Without the correct trust users could face issues connecting via VPN. With access to the FMC navigate to Objects > Object Management > PKI > Cert Enrollment Assuming you are opting for manual enrollment, select 'Manual' in Enrollment Type and copy the CA Certificate BASE-64 into the field. Now select the 'Certifi
Read more

Kali Linux :: CAM Table Overflow Attack Demonstration

-
Image
As part of my on-going studying for the CCNA Security 210 – 260 certification I have been exploring different types of network attacks, one of which is CAM table overflow attacks. In this article I would like to share what I have learnt and provide a demonstration of the attack carried out in a lab environment. To understand my demonstration, you first need to understand how a CAM table overflow attack works and what happens as a result of the attack.   Switches build Content Addressable Memory (CAM) tables based on mac-addresses and port numbers. When a switch receives a frame it checks the table to see if the source mac-address is already known, if the source mac-address is unknown the switch will add the mac-address to the table along with the port number. The switch then checks the destination layer two frame and if no entry exists the switch broadcasts the frame out of all ports except the port in which the frame was received. Presuming the destination mac-address wants to respond
Read more