Objective
I would like to protect access to my network devices (Wired switches, Wireless lan controllers and Firewall) and enhance authentication using MFA.
Network Policy
Employee’s can connect to my network devices and can view and edit the configurations. Contractors can connect to my network devices but can only view the configurations.
Connection Flow
![use2case.png use2case.png](https://community.cisco.com/t5/image/serverpage/image-id/28262i1689175F92683C18/image-size/large?v=v2&px=999)
1. User initiates a SSH connection to the router
2. Router sends TACACS+ authentication request to ISE
3. ISE sends RADIUS to Duo Security's authentication proxy
4. Primary authentication uses Active Directory
5. Duo authentication proxy connection established to Duo Security over TCP port 443
6. Secondary authentication via Duo Security's service
7. Duo authentication proxy receives authentication response
8. SSH access granted per ISE Device Admin policy set
Assumptions
This guide assumes:
- The reader is familiar with the Cisco Identity Services Engine (ISE) features and functions
- The reader is familiar with the configuration of ISE AAA functions
Enable ISE Device Administration Service (TACACS)
Step 1. Navigate to Administration->System->Deployment
Step 2. Enable "Device Administration Service" on the appropriate node
Step 3. Click Save
Configuration for RADIUS communication between ISE and DUO
Step 1. On ISE, navigate to WorkCenters->Device Administration->Ext Id Sources->RADIUS Token
![Picture1.png Picture1.png](https://community.cisco.com/t5/image/serverpage/image-id/28266iDDE4302857F7549C/image-size/large?v=v2&px=999)
Step 2. Click Add
Step 3. Starting from left to right, configure the settings within each tab menu item as follows:
a. In the General tab, configure a name for the configuration
b. In the Connection tab, configure the Primary Server details:
Step 4. Click Submit
Create an Active Directory Join Point in ISE
With DUO auth proxy as the authentication ID source, no group information is returned. As a result, we also connect ISE to Active Directory as the authorization ID source.
Note: If you already have integrated ISE with AD, skip this section
Step 5. Under Work Centers->Device Administration, select the submenu Ext Id Sources. In the left-hand pane, select Active Directory
Step 6. Click +Add in the right-hand pane and fill in as below and click Submit. Click "Yes" when asked "Would you like to Join all ISE Nodes to this Active Directory Domain?".
![Picture5.png Picture5.png](https://community.cisco.com/t5/image/serverpage/image-id/28277iE57C6A43BD2CEE3E/image-size/large?v=v2&px=999)
Step 7. In the Join Domain pop-up windows, fill in the necessary details:![Picture6.png Picture6.png](https://community.cisco.com/t5/image/serverpage/image-id/28278i0D79D95093030538/image-size/large?v=v2&px=999)
Step 8. Click OK to start the join operation. A window "Join Operation Status" will pop up. Wait until the node status changes to Completed and then click Close
Step 9. Navigate to the Groups tab and add the Employees and Contractors groups![Picture7.png Picture7.png](https://community.cisco.com/t5/image/serverpage/image-id/28279iFBBD783F1D77EE03/image-size/large?v=v2&px=999)
Add Network Device
Step 10. Navigate to Work Centers->Device Administration-> Network Resources-> Network Devices
Step 11. Click Add. Provide Name, IP Address, select TACACS Authentication Settings checkbox and provide Shared Secret key.![Picture11.png Picture11.png](https://community.cisco.com/t5/image/serverpage/image-id/28329i0C9746AD4EFEE0A6/image-size/large?v=v2&px=999)
Enable Device Administration
Step 10. Navigate to Work Centers->Device Administration. Select Deployment from the left-hand pane to jump to the page Device Administration Deployment. Select the appropriate ISE node configuration option
![Picture8.png Picture8.png](https://community.cisco.com/t5/image/serverpage/image-id/28281iDCD7B0F978DB0B8F/image-size/large?v=v2&px=999)
Step 11. Click Save when finished
Assigning device administration privileges based on Active Directory group membership
Step 12. Navigate to Work Centers->Device Administration->Device Admin Policy Sets
Step 13. Configure the identity store for the Authentication Policy to the policy that you configured in step 3a
![Picture9.png Picture9.png](https://community.cisco.com/t5/image/serverpage/image-id/28289i63F02F489E229140/image-size/large?v=v2&px=999)
Step 14. Configure the authorization results within the authorization policy to assign the command sets and shell profiles for each user group. See below for an example:
![Picture10.png Picture10.png](https://community.cisco.com/t5/image/serverpage/image-id/28291iB87424E6F5E731E1/image-size/large?v=v2&px=999)
Validation
- SSH to the network device
- Log in
- When prompted for password, enter in this exact sequence : “ <login password>, <pin code on Duomobile app>”
- Once logged in, verify that the user is able to execute the defined command sets
- To review logs, on ISE Navigate to Operations-> TACACS->Live logs