SolarWinds Access Rights Manager (ARM) is designed to assist IT and security admins to quickly and easily provision, deprovision, manage and audit user access rights to systems, data, and files. By analyzing user authorizations and access permission you get visualization of who has access to what and when they accessed it. Demonstrate compliance with most regulatory requirements with customized reports. Provision and deprovision users using…
N/A
Cisco Identity Services Engine (ISE)
Score 8.9 out of 10
N/A
The Cisco Identity Services Engine (ISE) offers a network-based approach for adaptable, trusted access everywhere, based on context. It gives the user intelligent, integrated protection through intent-based policy and compliance solutions.
ISE has multiple cisco servers to provide redundancies to manage whenever a user logs into a cisco system. System administrators can conduct audits in the network to see who logged in and made what changes to the network. Users are granted different network privileges. which …
It [SolarWinds Access Rights Manager (ARM)] is well suited for small to medium sized companies who want to enhance and ease up their daily work. As well as it is suited for organized structures, it has its problems with very complex environments. For example, if you are working with direct and multiple permissions instead of having more granular group based permissions.
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
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.
Licensing model when we changed over to SolarWinds was [I feel] a nightmare. It needs to be more streamlined and SolarWinds needs to understand what their customers require. When we changed over to SolarWinds we found it very hard to get answers to what modules we were still licensed for.
Our current system is not functioning. We can't login to the application with the accounts we created that were working. The error that appears doesn't help to resolve it. So at present we just renewed licenses for this year and we can't use the system.
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.
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.
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.
It was my first exposure to this type of product and I wasn’t given the time to figure out how best to implement it. I would say get a plan together of what you are tying to accomplish first
I did participate in the implementation of Cisco ISE and while there were times when it was confusing and we had a lot of trial and error, overall the experience was fine.
I found the installation and configuration to be much easier and more straightforward. What also assisted in the decision to go with Access Rights Manager, was the fact we already made use of Solarwinds products. Knowing from previous experiences with their support staff, meant we knew how great their after-hours support was whenever we had any technical issues with the platform. We felt it would be better to keep it all under one roof so to speak
I think all give some visibility of device monitoring and management, but Cisco Identity Services Engine gives a good way to manage more details about the device in a centralized way that gives a wider range of monitoring and control than the other softwares individually. I don't think Cisco Identity Services Engine eliminates the need for these other software as of now, but there is potential for Cisco Identity Services Engine to be able to take over more of these roles.
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 .
I don't know about negatives because we haven't seen it right now, but positive impact is one is the roadmap we have. And now since we are going ahead with doing the deployment of Cisco ISE, we see that we are getting closure to, so at the end of the day, we have to make sure that operationally we stay excellent. So that's where operational excellence comes in. Cisco ISE is basically addressing that for us. Right now we are in a situation if there is a WIFI issue or if there is an authentication issue, it gets really difficult to isolate the problem. But with Cisco ISE , this functionality is going to come in. So we believe that it would be a good ROI.
