Cisco ise 2.4 creating scheduled reports

#CISCO ISE 2.4 CREATING SCHEDULED REPORTS FULL#

This was a bit of a problem: If the customer is rolling out ISE or it's not deployed everywhere, pxGrid really isn't getting a full picture of who is on the network to share with other tools. This meant that you had to have ISE deployed everywhere to have full identity mapping on ISE, other Cisco Security tools, and ISE Ecosystem Partners. With the revamped PassiveID, ISE seeks to solve two problems:ДЎ) Ensure that Easењњonnect is now easier to setupДў) Have ISE function as the context directory agent for other Cisco and pxGrid partnersДЇor #2, I will expand on that: In the past, ISE had to see an authentication to share the user and context information with third party systems via pxGrid.

This functioned well but required a LOT of backend work to prepare Active Directory to share the WMI logs and if you read my earlier post here, you will see what I mean The creators of ISE decided to revamp this process and create a better way to do this in ISE 2.2 and later. This allowed ISE to grant network access beyond the typical 802.1x and profiling methods. Based on those login events, ISE would make a decision to grant access. In ISE 2.0, there was a feature added called Easењњonnect which utilized WMI logs from the Active Directory Domain Controller to check for login events. In this particular post, I'll be doing it all from ISE 2.3 but bear in mind that you can do all this from ISE 2.2 as well. In this post, I'm going to review the PassiveID features of ISE that are new as of ISE 2.2 and 2.3.

Cisco ise 2.4 creating scheduled reports