RSA Identity Governance and Lifecycle Reviews

The most valuable feature of the solution stems from the fact that it is really easy to have connectors to search for on-prem applications and provide access based on roles. In my company, with the help of the solution, we set up job templates based on the HR data we get, and we also provide IT access, a part that we have included in a matrix based on what type of users we have.

Every connector that you have in the product needs to be custom-built, so there are not a lot of standard connectors available in the product, because of which there are a lot of hidden consultancy costs. Everything in the tool needs to be developed by people who are experts in RSA products, and there is nothing that people who work in-house at a company can do. The aforementioned areas of concern can be considered for improvement in the solution.

RSA Identity Governance and Lifecycle can be deployed on the cloud or on-premise. We have our own proprietary cloud solution created along with RSA Identity Governance and Lifecycle and it's deployed on the AWS platform.

We use RSA Identity Governance and Lifecycle for a broad level use case for service, mainly on the governance of the overall lifecycle of the entities. However, the use depends on the business of the clients, but mainly on managing their entities.

RSA Identity Governance and lifecycles are good for the access certification and auditing sections.

I use this solution for joiners/movers/leavers along with the add-back, role-based access control, and certification.

The data collection is excellent and easy to do. It does not require a lot of configuration nor does it require rules to be written like other competitors do.

We are a solution provider and this is one of the products that we implement for our clients. I have helped to deploy this solution to two customers so far.

The primary use case is the addition of another layer of authentication for users to access the network.

The most valuable feature is the security, in particular, the One Time Password support.

Organizational role management: By defining the roles it made our job easier for new-hire provisioning by automatically granting/creating the tickets necessary for the job role.

• Roles
• Connectors for provisioning
• Re-accreditation or reviews

These help greatly to govern user access.

It's used for basic two-factor authentication.

It improved security.

It allows users to authenticate using two-factor authentication, which is becoming more and more of a regulatory requirement.

It has streamlined the process of authentication, which has resulted allows for less calls to our Service Desk/SOC for password resets.

Random token generation.

Soft and hard tokens for two factor authentication has been introduced.