Cisco Identity Services Engine (ISE) vs. S3M Security

Cisco ISE integrates will with a Cisco solution such as firewalls, network switches and routers. It does an incredible job of granting access based on the role that an individual or groups have, and the ability to remove access to that individual or group is also east. In our environment ISE is used to authenticate external users that have access by vpn, and also to manage access to the large network infrastructure

Incentivized

• The most beneficial thing that I love about it, there are tons of things that I love about ISE and that it does well, but the most fascinating that I feel about is its integration with DNA center or Catalyst Center using PX Grid as the protocol wherein ISE acts as a policy server for the entire campus hand in hand with Catalyst Center to make sure that the policy policy follows the user and also in the background hand in hand with DNA Center or Catalyst Center makes sure microsegmentation is implemented so that east west traffic is blocked and takes care of the campus.

Incentivized

• Probably better enhancement in terms of troubleshooting. For example, if there is a failure in the network and if you want to locate a specific endpoint, how we can make it more intuitive. That is one place we are exploring and we are talking to Cisco as well, that let's say, if you want to check for the failures for a specific MAC address or a user ID, how do we do it? And can we integrate this with our third party tools like Slack or Splunk, right? So that's where if you see a failure, we see the failure over there and then we act on it. So these are some of the things which we are working with Cisco.

Incentivized

We are so very reliant on Cisco Identity Services Engine at this point that finding another solution would be a big hassle for us.

Incentivized

For us the solution is very easily useable on its own. Perhaps that has to do because we started using ISE in the 1.2 days and have seen it grow during the years. Policy creation, etc. is all very visible and thus easy to use. Deployment of multiple nodes is also incredibly easy and flexible. You can easily add or remove nodes as you wish.

Incentivized

We do have to occasionally reboot the servers when they get low on memory, but we're also a few versions behind. Availability has generally been pretty good though with no major outages in the time that we've had it implemented.

Incentivized

yes it does. depending on where you coming from. Logs are pretty busy same as report. it also depending on devices count and design.

Incentivized

Cisco support is second to none, both in terms of how you access support but also the knowledge of the individual support teams. If you focus on one technology and provide "manufacturer support" then you can rest assured that you are accessing Cisco's top individuals. I feel like this is a USP for Cisco support.

Incentivized

Training can only cover certain areas, there are a lot of areas training just can't cover. You have to learn by doing it.

Incentivized

I think our system integrators lacks some competencies and this has led to an implementation that is still perfectible. (i.e. dedicating an interface for intra-cluster communication)

Incentivized

The only other one I've ever used is ClearPass, which is the Aruba product. It's a decent RADIUS server. I don't know—it's more of a vanilla RADIUS server. It doesn't have nearly as many bells and whistles. It's a significantly easier product to use, that's for sure. It took me a lot less time to learn than Cisco Identity Services Engine. 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.

Incentivized

It's fully customised and comprehensive. only thing is you need to know what you want. Proper research and planning would save lots of time and effort .

Incentivized

• Greater device connection visibility for troubleshooting in general and dacl status.
• Great individual device policy management, but difficult to manage or select multiple devices at once.
• Easy to identify simple issues where users use the wrong password for wireless or other similar problems with an authoritative answer and not asking "Are you sure you typed it in correctly?"

Incentivized