Hi @Abdullah2u
In order for ISE to perform profiling, there are a few answers. Since you have a Cisco WLC, you should be using the Device Sensor option on your SSID Advanced Settings (called RADIUS Profiling) which will provide HTTP and DHCP profiling to ISE via RADIUS Accounting Interim-Update requests. If you do not have ISE Plus Licenses installed, then you won't be able to benefit from this, since Profiling requires active Plus Licenses.
Assuming you have Plus Licenses installed, then ISE will decode (profile) the WLC's Device Sensor data and display this in the Live Logs etc. You get better visibility of the end devices.
To create Policy Sets using profiled information, you need to spend some time researching how that works. I recommend the www.labminutes.com series - explains it really well.
The trick with profiling in ISE POlicy Sets in general, is that it can be a chicken and egg problem. e.g. with 802.1X you don't know if the device is an Android device until you Authorize the device with 802.1X - so there is no way to make that a condition of the primary authorization Policy. ISE can however collect information about endpoints via things like SNMP polling. In the wired profiling scenario, you can ask ISE to SNMP poll a switch and it can learn a lot about attached devices before you even start thinking about profiling policies. But with wireless I have not found that to be the case. Wireless clients come and go and with 802.1X you have to succeed 802.1X in order to get onto the network. Perhaps there is a way to re-authorize a user once you have profiled them as an Android device (to use the same example as before) and then place that Policy Set Rule higher up to ensure that it gets matched. The more specific Policy Set Rules need to be placed higher up than less specific Rules, or else the more specific ones will never get matched.
See how you go.
