Google Cloud Identity is a unified identity, access, app, and endpoint management (IAM/EMM) platform that gives users access to apps with single sign-on, provides multi-factor authentication to protect users and company data, and enforces policies for personal and corporate devices and endpoints.
N/A
IBM Verify
Score 8.9 out of 10
N/A
IBM Verify, formerly known as IBM Cloud Identity, is an identity-as-a-service (IDaaS) offering that aggregates dynamic user, device and environmental context to automate risk protection and continuously authenticate any user to any resource.
$1.71
per month per user
Pricing
Google Cloud Identity
IBM Verify
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Google Cloud Identity
IBM Verify
Free Trial
No
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Sample Pricing Breakdown (NOTE: for competitive pricing per contract, please consult with your IBM Security Account Rep)
Users: 5,000
SSO* -- USD 1.71 per user per month
MFA* -- USD 1.71 per user per month
Adaptive Access* -- USD 1.71 per user per month
Lifecycle and provisioning** -- USD 2.01 per user per month
Identity analytics** -- USD 2.13 per user per month
* Single sign-on (SSO), multifactor authentication (MFA) and adaptive access pricing based on total active monthly users per use case. Costs decrease if users are active less than once per month.
** Lifecycle and provisioning and identity analytics pricing based on total users per use case.
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.
The software is a unified identity verification platform with robust identity governance systems and multi-factor authentication tools. Effectiveness of the product in privileged access management and real-time activity monitoring. IBM Verify is very affordable and supports single sign-on in the cloud. It has a steep learning curve.
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.
It works flawlessly, i have never faced any major issues with this. It has all the features such as Iam and security management. I think its a good investment and the benefits we reap from this software are worth the price.
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.
While setup and implementation takes work and time, the flexibility and possibilities make up for that in the long run. This is not a product you can just install and run, but if you design and implement your ruleset well, it will save you a lot of work afterwards. Just make sure that the systems you want to use it for have an existing and proven connector.
It has never let us down since its inception and installation. User credentials and secure access have always been guaranteed. Ironclad security (through single sign-on, MFA, etc.) has ensured that our user credential details are safe as is our information/data. The correct access is given to users, based on role-based access with segregation of duty and the principle of least privilege being deployed. The IBM support has also been first class and they have proactively resolved any minor issues we have encountered.
The support team has always been the primary consultation base when we are faced by performance problems. From the deployment stage the team has managed to monitor the operation lifecycle and give best insights based on their observation. It works 24/7 to enhance productive service delivery to clients. The IBM Security Verify Support team has been the main player in the successful performance of this software.
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.
We conducted a comparison study between IBM Verify and Okta as well as Duo Security before making our selection. IBM Verify emerged as the perfect fit because its superior capability to integrate with our current system environment surpassed competitor security solutions. IBM Verify demonstrated superior reliability through its enterprise-class scalability and fully transparent auditing mechanisms.
The licensing terms were favourable due to their flexibility based on the size and purpose of implementation. The billing frequency is done on quarterly basis. The vendor team has enacted best user policies that gives the company the full control of this platform. It is cost-effective as compared to most security verification tools in the market.
In the case of adjustments, we were often able to carry them out completely on our own and only used professional services for new requirements. Particularly in the case of access management, it is very positive that we usually needed IBM for a task in less than an hour and then developed the solution further on our own.
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.