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

• The access request work flow and back end process is exceptional. It effectively manages all of the various pieces of a request and presents the completed request to the provisioning agent as a single record. This is very helpful to the efficiency of the process since the provisioning agent only sees the completed request rather than seeing each component as it is approved. Other systems deliver the various request components to provisioning as they are approved but cannot be provisioned without all the components. Thus creating complexity for the provisioning agent and impacting the SLAs with what looks like a delay with the provisioning process.
• The system is robust enough to effectively handle the scale that we need. With 750+ applications, 24,304 individual entitlements to select from, and an average of 10,200 request transactions per month. We have never had any performance issues.
• The system flexible enough to accommodate our complex business needs without needing to customize the base system. We have been able to add significant functionality to the system in order to support the business needs by extending the code rather than altering the base code. This has enabled a simple upgrade of the system without having to re-apply code enhancements.

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

• Technical adoption requires a high level of training and experience by the implementing teams.
• SailPoint and partners offers very good training courses which I think are very good. An area of improvement can be in providing cloud VMs that users can work with to learn the IIQ tool more effectively at their own pace.

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

SailPoint is a more customizable solution than Okta, it is also not just a cloud application. Our use of IIQ to manage external suppliers via Azure AD guest accounts was not available on other platforms at the point of deployment. The integration with SAP and other Microsoft services is also second to none.

Incentivized

• 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

• The ability to automate the employee onboarding processes greatly reduces the staffing requirements for account creation and access assignment
• The self-service capabilities for the account registration and password management tasks have greatly reduced the number of calls to our Help Desk
• The role mining capabilities have reduced the amount of time required to assign and update our user application set mapping