Google Cloud Identity vs. SailPoint Identity Security Cloud

For example, if the system you are building is a general application service that does not primarily focus on ID management, it would be wise to use a service like Google's rather than developing your own IDaaS. While there may be cases where an IDaaS other than Google's is acceptable, Google is likely one of the best solutions when considering user recognition and ease of use. On the other hand, Gmail addresses are commonly used for other purposes, and users may not pay much attention to password management, so you should avoid using them for systems that require security. To strengthen security, you should consider making multi-factor authentication mandatory, etc.

Incentivized

We are happy with the management of the Id, accounts where the user can request any access easily. Also the many connector which Sailpoint is offering in order to onboard lots of applications is quite helpful. The access review module has also have been improve so that large campaigns can we work out easily.

Where we see some improvement is on the UI as here it is not so intuitive for the end user, so that we need to make lots of communications and training so that the user is able to understand how to use it.

For the administration and creation of roles it also would be great to have some improvements here to make it more easily its management.

• Two-factor authentication available.
• The Google authentication method is familiar to many users.
• It is expected that it will also support authentication methods that will become common in the future.

Incentivized

• Brings users access, profiles and accounts all into one place
• Manages the Life Cycle Management process across ALL identities, permanent and Temporary
• Secures and manages access to critical applications and resources across the group
• Enables Info. Security to customise, share and delegate authority across the group
• Single version of the truth across our technology platform

Incentivized

• This time, I investigated it in advance, and it worked as expected, so I don't have any specific ideas for improvement.
• Additionally, if we were using another IDAAS, it would have been beneficial to have knowledge on how to integrate it with Google tools, along with some relevant case studies.

Incentivized

• The user interface is not very intuitive. It is hard for the occasional user to navigate through the request process. There are no instructions on the screen to help the user to know what to do. It is left up to the user to figure out what to click on and how to navigate through the process.

Incentivized

I chose Google because I thought it would be the best fit, but I didn't fully consider other cloud platforms (Azure, AWS, etc.), so I rated it 8. We assume that current Japanese users are familiar with Google, because we feel that there are far more people with Google email addresses than those with IDs on other cloud services.

Incentivized

Overall usablity is excellent. The product is capable of performing all the expected tasks for a IAM solution.

Incentivized

Support for Customizations is very limited.

Incentivized

Implementation was done correctly and all the requirements were met.

Incentivized

We adopted Google Cloud Identity as an additional feature because it allowed us to integrate with it using multi-factor authentication. The IBM Cloud platform remains valid, and we have no plans to discontinue its use for identity management. From the user's perspective, we simply added more authentication options. This also ensures we are prepared for future use when multi-factor authentication becomes available for user apps on the IBM Cloud.

Incentivized

The on-prem SailPoint IdentityIQ platform provides the necessary customization that is required in our dynamic environment. Although we may look at a cloud-based Identity Management service again in the future, (there are many advantages), our identity management, authentication, and application assignment processes cannot be quickly consolidated to a single cloud-based service at this time.

• From a business perspective, there were two steps.
• First, we switched from our in-house ID management system to a cloud service. This allowed us to focus our development resources on application development.
• At the same time, we were able to localize the handling of personal information, which resulted in increased efficiency in management aspects, including handling external inquiries, and in the development of encryption.
• The second step was adding Google Cloud Identity as an option.
• This allows more users to easily use our services. It can be said that this has improved user convenience.
• I expect Google to accommodate future changes in authentication requirements, such as biometric authentication.

Incentivized

• Over 300,000 password change/reset calls avoided to the helpdesk annually.
• 1,000 plus accounts with proper accesses provisioned via automated birthright processes weekly versus 1-2 days of manual provisioning and approvals. With a call center population that churns many people per week, this brings many dollars of efficiency to the operations teams.
• Flexibility on terminations to manage accounts and access for target applications based on regulatory or business rules to ensure compliance and avoid fines for non-compliance.

Incentivized