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 7.3 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.
N/A
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
No
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.
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 …
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 …
Owing to the general findings formulated in this paper, comparing Okta and Microsoft Entra ID to IBM Verify, the latter appears to be the only tool that delivers a number of features for integrating with legacy systems. However, since IBM Verify has the upper hand in terms of …
During our proof of concept and demonstrations, we were clearly able to see how much better the identity, access and authorisation features were compared to the competition. We were compelled to make a decision, not only on this, but also on the ease and simplicity of …
IBM Security Verify is a robust product which has all the features. Its advanced AI capabilities helps it make a superior product when compared to competition. The most important factor with IBM Security Verify is that it comes under the IBM umbrella which makes it more …
IBM Security Verify stacks up with Microsoft Entra ID better than SecurID due to categories in common such as, Self Service password resets, Multi-Factor Authentication, User Provision and Governance Tools, SSO, and IAM. SecurID not so much because it doesn't have that full …
IBM Security Verify was more effective and useful for our business as compared to 360 Total Security and Norton Small Business both. All or team that used the product had good success, my only complaint is that cost for IBM Security Verify was more expensive for a small …
For the feature set, Verify was by far the more attractive product. We use some other Fortinet systems, so naturally, we wanted to see what else was available outside of this ecosystem. Verify wasn't the cheapest solution, but it does provide a level of confidence that you are …
There are very few competitors in this space, and you don't have to look too much into this. If it gets your work done, you can add users and start using the software; it's not a project management software where you would have to evaluate for months on the go and then make a …
I believe that the decision for selecting IBM Security Verify was based on our IT technical analysis but also due to our trust that this provider would deploy a solution according to our needs and expectations. The free trial made it possible to test it and understand, at an …
I don't care for the IBM Security Verify. I find it old and clunky compared to newer programs that offer the same service. IBM was selected because we are a large organization, and we need the reassurances that only large (think Microsoft, alphabet, IBM, Dell, etc) can offer. …
We actually use the F5 load balancer instead of the ISAM for those functions. We did evaluate some similar Microsoft Azure offerings but did not select.
We evaluated Oracle Identity Manager and were ready to move ahead with the purchase plan, but then found that IBM addressed the needs of our company in a more robust fashion. The price was significantly higher, yet in the grand scheme of things, the safety of both our data and …
Compared to Okta, IBM Verify is easier to implement and more user-friendly for our employees. It provides strong security using multi-factor authentication and maintains easy settings. We chose IBM Verify because it met our needs without any significant development work.
Okta has good user experience for end users and setup process however IBM verify has a stronger capability for integration, auditing. Microsoft Entra integrates well within the Microsoft tech stack, easier for users to adopt due to familiar environment. Store scalability and …
These tools provided similar functionality in multi-factor authentication and identity security, but IBM Verify offered stronger enterprise integration, compliance alignment, and reliability for our needs.
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.
It is brilliant for use as an identity and access management tool and ensures the safeguarding of our systems and upholds data integrity as a consequence. It was very easy to set up and apart from a straightforward installation, we have found customisation and configuration easy. It was easy to deploy in the cloud after using it previously on premises.
MFA authentication - you can verify the users using the mobile app.
Password repository - We don't have to remember passwords for each app; we only need one for IBM security, which then authenticates us and lets us access the app.
Sharing access to new users, we just create a new user in IBM and it authenticates and takes care of the user.
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.
Throughout the system testing we conducted, we never encountered an issue that wasn't easily solvable. We did find some of the documentation confusing at times, but we overcame this quickly with some speedy support assistance. Implementation into production was a lot smoother following the testing we conducted.
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.
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.
Providing an additional layer of authentication security, IBM Security Verify helps protect customer data, reduce the risk of fraud, and improve the customer experience.
Lead to increased customer loyalty, improved customer retention, and better overall customer satisfaction.
Reduce the cost of fraud prevention, thereby improving the bottom line.