My main use case for Cisco Identity Services Engine (ISE) is providing MAC technology and Network Admission Control, which allows us to enforce authentication for users as we implement Zero Trust for cybersecurity to enhance our cybersecurity.
Also, the great feature of Cisco Identity Services Engine (ISE) is using posture, which allows us to deploy conditions per the device or checklist for any request to join a device to our network and also profiling.
For a specific example of how I'm using Cisco Identity Services Engine (ISE) for network admission control or posture assessment in my environment, we have implemented the AAA and 802.1X integrating Cisco Identity Services Engine (ISE) with our edge switches, so any user wanting to join the network must first enter a username and password from the domain controller. After this, the switch will ask Cisco Identity Services Engine (ISE) for this user, and Cisco Identity Services Engine (ISE) will ask the domain controller if this user already exists or not. Based on the existence of the username and password provided, we can permit or deny access. We are also providing posture assessment on the device, checking if antivirus is enabled, the version of antivirus, and if it is updated or not, along with whether it is allowing our service, for example, confirming if the required service is open or disabled. After evaluating these conditions, we either allow the device to join our network or deny access.