Cisco Identity Services Engine (ISE) Review
Use Cases and Deployment Scope
Pros
- It does a great job of authenticating users. Anytime one of our users logs into the network, before they're ever able to do anything inside the network, they have to authenticate with Cisco Identity Services Engine. We can do that with IoT devices as well, and it enables us to send down customized access lists that control access right at the port. So even from the beginning, before they're able to do anything else, we're controlling what they can and cannot access.
Cons
- I would say the biggest thing about Cisco Identity Services Engine right now—and it's the same thing it's always been—is that it can be extremely complicated. There is a bit of a learning curve to it. They've made quite a bit of improvement since the early days, but still, unless you use it often enough, you're going to have a bit of a hike to get to the point where you're really good at it. I would say that's probably the biggest problem with it. There's a lot of stuff there, so it's understandable, but that's probably the biggest hurdle you have to overcome.
Return on Investment
- Well, we're subject to a lot of compliance rules. The nice thing about Cisco Identity Services Engine is that when you're trying to lock everything down in the financial industry, it makes it a lot easier to do, that's for sure. When we're doing auditing and things like that, we can pull the reports right out of Cisco Identity Services Engine with no problem. We do that annually, and it meets a lot of our auditing requirements, which is very helpful.

