Saviynt - Identity Cloud

I would like to discuss the use case. Saviynt Identity Cloud is primarily used for identity management and access governance, and there are also other solutions such as data access governance and privileged access management, which they call CPAM. So it's basically a converged solution in a unified platform.

Saviynt Identity Cloud is a SaaS application, which means it's cloud-based.

There are many out-of-the-box connectors available for Saviynt Identity Cloud, including some generic connectors that can be leveraged for any enterprise application integration. As long as the target application has an API exposed, it's pretty much straightforward. Whatever limitations that the target system has, only that's the limitation on the integration side. I am not aware of any existing application connector limitations.

Saviynt Identity Cloud is very seamless in terms of automating user provisioning and access reviews.

Definitely, it helps my organization identify potential risks.

There is a cost reduction once it's implemented, and it depends on the people also. How many people are managing the fulfillment can be reduced when things are automated. To begin with, that's one immediately available option to cost cut when provisioning or fulfillment is automated in all the downstream applications. Let's say you are an organization managing 500 or 1,000 applications for various business activities, and hypothetically all of them are integrated, then there is a lot of fulfillment team reduction in a way. Not necessarily everyone; you should definitely have some admins available at all times if the system breaks. Somebody has to be there to intermediately manage those workloads. But then, in an ideal scenario, fulfillment team-wise, there will be a lot of cost cutting. Then, another area could be things will be seamless for tracking the lifecycle of access from an IT audit standpoint, all through one single IGA solution. It's overall a good thing to have everything consolidated in one place. Otherwise, IT audit itself would cost more people for them to manage, needing to gather all artifacts from various directions. So there will be a lot of back and forth emails and Teams chat. Now, everything is consolidated when everything is being managed by one single IGA solution. I'm not just talking from a Saviynt Identity Cloud standpoint; in general, any IGA product when it's properly implemented, you see the value as you start implementing and using it.

When you ask about any drawbacks or downsides in Saviynt Identity Cloud, one very interesting point that I observe is when the session is being expired, if there is any timer that's running somewhere on the corner of a screen that would really help.

A notification about when it is expired would be interesting for people who are developing. Many times, we get lost in the development process and we don't save the configuration, whatever we progressed till then. And when the session expires, you have to rebuild that from scratch. There is no auto-save mechanism as in a OneDrive document. It's not a OneDrive document to be saved, so you have to manually click on save. So, at least if there is any timer that's reflecting the session time, that will allow users to actually save their work.

I think it's on the lower side if you ask me about notifications and the auto-save mechanism. For what they're providing, there should be improvements.

Notifications are definitely there, but I'm only talking about a session expiry notification. Session expiry should not be a notification in the email sense. If you start going by the email route, it would spam you. It should be a pop-up or even simpler, which will not create irritation as you are working long hours. It should be on top of a screen, there will be one small logo showcasing your image or something.

For example, with your name showing as initials such as 'SS' for Surya Sadhu, in that corner, maybe place one more circle or in the same circle, showcase some timing which says it will be like a clock from a session standpoint. That should do the trick.

There will be a few other nuances, but we cannot be discussing all of that in one call. Taking all those nuances into consideration, I'm cutting down that one mark.

I have been using Saviynt Identity Cloud for about five to six years.

I have used SailPoint for at least five to six years. We were talking about SailPoint Identity Security. I worked with the on-prem model for SailPoint Identity Security, and right now I'm working with Saviynt Identity Cloud product. SailPoint was used in the past, and I am no longer using it.

Implementing Saviynt Identity Cloud depends on the business case; in general, if you are sticking with out-of-the-box integrations and keeping things straightforward and simple, it will be pretty straightforward and configurable. Depending on the use cases and scenarios that are deriving from the business, some customizations are possible and some are not.

If you're talking about just the tenant creation within Saviynt Identity Cloud, it won't take much time; in terms of artifacts migration, whatever components or integrations that we have implemented within the product, that migration probably takes a day or two. Many of them are export-based only, and very few configurations have to be still configured manually due to the product limitation. But majorly, everything is exportable and importable.

In general, we definitely need one architect, one developer, and one tester to begin with for Saviynt Identity Cloud. But the resource count increases depending on the timeline of the project and the quantity of the project. Both parameters vary, including the complexity of the integration. Various layers of parameters at each stage have to be incorporated when you're calculating for the resource.

There is definitely a return on investment with Saviynt Identity Cloud.

Regarding analytics-driven approach, there is no right or wrong answer; it depends on the business. My overall rating for this review is 9 out of 10.