Skip to main content
Cisco Meraki

Adaptive Policy and Cisco ISE

Overview

clipboard_ed7fb37e114dcabc8793b6dc52e9635a3.png

 

The purpose of this document is to give a quick overview of how to use Cisco's Identity Services Engine (ISE) to assign Security Group Tags (SGTs) to clients. 

Adaptive policy leverages SGTs for endpoint classification, identity propagation, and policy enforcement. Even though Adaptive Policy's actual policy lives and breathes in dashboard, Cisco ISE can be utilized to dynamically assign SGTs to clients based on a number of conditions such as device profile, posture, user, machine, and more. This is all done through the use of RADIUS and the AV-Pair for security group tags. 

ISE SGT Creation

Within Cisco ISE, SGTs need to be created to allow for assignment to rules within the Authorization policies. If this is a brand new install of ISE and there is no pre-existing TrustSec configuration, to get started the following configurations can be implemented:

For pre-existing TrustSec installs that want to leverage ISE to send already created SGTs, this section can be skipped and the guide can be continued starting with the section titled: Adaptive Policy Group Tag (SGT) Creation in Dashboard
 

There is an open-sourced tool to sync Adaptive Policy with Cisco ISE located herehttps://github.com/meraki/adaptive-policy-ise-sync

This tool is NOT supported by Meraki Support and is best effort. As such, bugs can only be brought up through the github issues tool. 

Enabling Manual SGT Number assignment (optional)

To make sure there is flexible configuration of SGT name to number assignment in ISE, it is easiest to disable automatic number assignment so that it is end user configurable.

  1. Navigate to Work Centers > TrustSec > Settings
    clipboard_e774968eac17ad630c42d42c62b11e8f8.png
     
  2. Scroll down to "Security Group Tag Numbering" and select "User Must Enter SGT Numbers Manually" and click "save"
    clipboard_e35138c25b864a3bb20379d3f0ab33041.png

Configuring Security Group Tags for Authorizations

To create SGTs that are assignable in the authorization rule-sets:

  1. Navigate to Work Centers > TrustSec > Components
    clipboard_e1602eb2080a257ccd9431f985e0988a5.png
     
  2. Next select "Add" in the menu to add a new SGT
    clipboard_e214c1f47d5c72d6d56950c157e5ddb71.png
    In this menu, SGTs can be created and named according to their purpose. The name is locally significant to ISE at this time, and is not used in the RADIUS AV-Pair, however for sanity's sake, should match the Adaptive Policy Group name and number in dashboard.
     
  3. Fill out the Name / Select an icon (significant to ISE UI only) / Tag Value and click "Submit"
    clipboard_edf18438d60bfed4af8f222e51936d242.png

 

Adaptive Policy Group Tag (SGT) Creation in Dashboard

Adaptive Policy global administration in dashboard is located in Organization > Configure > Adaptive policy and groups in the Groups menu.

clipboard_e388d30f6aadfce44a6ee288db0ed4af8.png

 

1. Creating an Adaptive Policy Group (SGT) in dashboard is as simple as clicking the "Add Group" button:

clipboard_e5836b573d7a913c463d5df32c0977640.png

 

2. Next fill out the following window: 

clipboard_e8147c8925c9f6c956c2259058e861544.png

3. Click Review changes and then Submit.

 

This function needs to be performed in both ISE and dashboard to where both sides match the required SGT values. 

Cisco ISE Network Devices and Rule-set configurations

Once the tag has been created in both Cisco ISE and dashboard, rules can be configured in Cisco ISE to send the SGT as a RADIUS attribute to a supported Meraki MR or MS390. These can be combined with any other supported attribute such as VLAN-ID or session-timeout. For the sake of brevity in this document these combined examples will be omitted.

Network Devices and Groups

Meraki devices need to be configured as RADIUS clients within Cisco ISE before ISE will allow authentication requests to be processed. This can be done in a couple of ways including setting a Default Network Device, or configured specific devices and groups for use within ISE. There are a number of ways to group devices in ISE including device type, location, etc, that will not be covered in this documentation. To configure a Meraki device in ISE perform the following configurations:

 

  1. Navigate to Administration > Network Devices and Groups > Network Devices 
    clipboard_e79a202ea93158e3b10eed3ea3d42527c.png
     
  2. Select "Add"
    clipboard_ed16f7a5d539204a092da9d2c583a80e6.png
     
  3. Next step is to fill out the device details. This once again can be filled out to be very granular down to a specific/set of device IP address/es, Specifying Location (which can be used as a conditional match in ISE), and Device Type (which can also be used as a conditional match in ISE). In this example the bare minimum of Name, IP info, and The RADIUS Shared Secret that will be used is filled out.
    clipboard_ee34badf23239d92a15460e882844ed26.png
     
  4. Next click "Submit"

 

At this point the endpoint/s is/are configured and will be able to be successfully processed by Cisco ISE.

Policy Sets

Within Cisco ISE there is a concept of Policy Sets. These are collections of policies that are utilized by creating condition matches on the initial authentication request. These condition matches can be fairly complex, however some of the easiest methods of sorting requests are by using Network Access Device filters like Location, Device-type, or even criteria like the SSID the request is coming from. If no filter is matched the traffic will go through the default policy set. This is often used for initial deployments or a proof of concept. For this document the default policy will be used.

clipboard_ed36419678b36eaaf748fa70ee155bf5d.png

Creating a rule-set to send back an SGT and optionally other data
  1. To create a rule in the default rule-set click the right arrow here: 
    clipboard_ee11395a604ba8bc5034ed36f0184e20e.png
     
  2. Click the Authorization section of the policy set here: 
    clipboard_e66d211286f889c794fb534279ec1d1bf.png
     
  3. Next a new rule can be created. However before creating a new rule, take note that the rules are processed in a top down fashion. The most specific rules should be up top (where the match is extremely specific to the authentication request) and the least specific match should be towards the bottom. To create a new rule, click the sprocket to the right of a rule and choose "Insert new rule above" or "Insert new rule below" being cognizant that the choice can affect other authentication requests depending on the specificity of the rule:
    clipboard_ea10ba6d4427c00061950f426384c8089.png
     
  4. Now we will create a rule that matches a domain authenticated wired 802.1X request using the following conditions:
    clipboard_e551c72b897d46a7a4a0c3afa432965e4.png
     
  5. Next we will click "Use" at the bottom. Once the use button is clicked we will be returned to the rule list with our new rule in the list, however there is no "Results Profile" or "Security Groups" selection made. 
    clipboard_e7b0d039cd55061bd4a974e6f24ab9139.png
     
  6. To configure an SGT in the response as well as other attributes such as VLAN 300, we can use a configured Result Profile of VLAN 300, and select and SGT value in the Security Groups list. For this demonstration the VLAN300 Result profile is used (The result profiles are configured under Policy > Policy Elements > Results > Authorization Profiles), and the SGT of ExampleTag as created above. 
    clipboard_e9d159e24021612a08f8f1357f32e41a3.png
     
  7. Once this is complete click "Save" below to install the configuration. 

 

MS access policy configuration and application 

To perform 802.1X authentication on an MS switchport please follow our MS Switch Access Policies (802.1X) documentation. 

 

Note: In Dashboard, you can assign either an Access Policy or a Static Tag, not both. If you are using RADIUS to assign policy, ensure that the RADIUS server is always sending back a SGT Value.

MR WPA2-Enterprise configuration

To perform WPA2-Enterprise authentication with MR use the following configuration guide in our Configuring RADIUS Authentication with WPA2-Enterprise documentation.

 

One thing to note with MR that is different than MS. You CAN apply a default tag to the SSID and override it with a RADIUS response.

Monitoring and Troubleshooting

There are two key places to monitor the outcomes of an 802.1X authentication including dashboard and within Cisco ISE. 

Cisco ISE

To monitor the authentication and Authorization status in Cisco ISE, navigate to Operations > RADIUS > Live Logs. This is where all authentication and authorization traffic hits the server and is displayed in an easy to read format. 

As seen in the following screenshot, we have a wired dot1x client matching the rule created in the previous configuration where the VLAN ID sent back was 300, and the tag of 100 (ExampleTag). In this screenshot there are 2 line items created for a single authorization. The green highlighted is the Authorization rule hit, and the subsequent blue highlighted line is the session that is started for that authentication. 
clipboard_e3420e5a2444412528dd31a341a642ad3.png
 

To see more details on the authentication request, clicking the Details icon will open a new link to an in-depth review of the authentication and authorization process. 

Dashboard

Within dashboard, authentication details can be seen under the specific network device's event logs, as well as the current state of the client under the interface details on MS, and the summary data on MR. 

MS

To check the adaptive policy group assignment on MS, navigate to Switch > Monitor > Switches > then the appropriate switchport.
Here you can see the currently connected clients, their IP addresses and other relevant info, including the Adaptive Policy group: 
clipboard_e14f9de6dfb75b825009b34c4560eec3b.png

MR   

Navigating to Wireless > Monitor > Access points > then the appropriate AP.
Here you can see the connected client, a number of other relevant bits of data, including the Adaptive Policy Group here:
clipboard_e0473f159da2d1a3c238a3dd244ccb675.png

 

For more information on Adaptive Policy please see the following Overview documentation here: 
https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Adaptive_Policy/Adaptive_Policy_Overview

  • Was this article helpful?