Google Cloud Identity vs. SecurID

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

Easy to implement and support. Flexible platforms and user-friendly interface. Not a lot of customization is available to customers and response time of support could be better. There are now competing products that utilize new features like facial recognition. Using camera and fingerprint sensors are becoming standard in smartphones so RSA SecureID should offer those as options.

Incentivized

• 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

• RSA Authentication Manager is easy to deploy and configure.
• It is a scalable solution meant for a large enterprise.
• Some of the key features of RSA Authentication Manager where it particularly does well are provisioning, mapping, and logging.
• It has a very nice console with good administrative and troubleshooting options.
• Reliable security for VPN, applications, and wifi.

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

• Slow to provide updates to latest operating system versions.
• While the GUI is clean and easy to use, it does look very dated.
• There is not an option for a temporary code to log in. It would be nice for situations where you are at a remote site but don't have your device (laptop, phone, etc.) with you, as well as other situations.

Incentivized

Long story short, does the job. Can use company credentials to setup and access the account for SecurID. Easy to setup and implement. Doesn't have a high learning curve.

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

Using it very frequently, it's important that its straight forward and I do not have to go through unnecessary hoops to achieve something seemingly simple. Can setup using the company credentials and do not have to setup up a separate account. Setup was fast and easy. GUI is very straight forward and quick.

Incentivized

Their support for onboarding and set-up is quite good. The only issues we tend to have are obtaining new user devices. These need to be planned ahead of time.

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

Overall MS AAD is good but we have had a few too many reliability issues with the product that have lead to enterprise authentication outages over the last year. The Senior executives have a preference on Securid to be more reliable than MS AAD. SecurID does a better job in Integration for legacy on-premise applications for instance.

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

• Implementing RSA SecurID has allowed us to help our clients understand we are committed to compliance.
• Implementing RSA SedcurID has, however, negatively impacted employee productivity. Employees need to be aware of the additional steps they need to take to authenticate to a protected system.
• RSA SecurID has helped us with our compliance audits.

Incentivized