Share your experience using Gemalto Protiva [EOL]

My main use case with Cisco Duo is for two-factor authentication. I need Cisco Duo authentication in my company because I have no different option to use a different solution not related to Cisco due to a limitation of a product like Cisco ISE that will not be able to use a different mechanism than Cisco Duo authenticator. I have to use Cisco Duo authentication to have two-factor authentication and fulfill security requirements in the company.

The feature I like the most about Cisco Duo is two-factor authentication. Cisco Duo helps me to defend against phishing attacks and provides security for my organization.

I really have no idea how Cisco Duo can be improved. I do not see any features that I would like to have that are not currently implemented.

I have been using Cisco Duo for about half a year.

I have not noticed any stability or reliability issues such as downtime or crashes.

I think Cisco Duo will scale with the growing needs of the organization. It will be growing because every company and every regulation requires two-factor authentication, and we have to use it by one vendor or another. I think a solution such as that will be growing in the future.

I mainly used the Microsoft solution because we have merged a lot of products with Microsoft, and using DevOps, Azure, and other services is naturally how we use Microsoft authentication for many things. However, if we cannot do it in some scope, we have to find out how to do it in a specific section.

With the deployment of Cisco Duo, I can do it with instructions. I am not an expert, but I am something between beginner and intermediate.

I cannot say that I have seen a return on investment from having Cisco Duo. I have experienced only a security benefit.

My experience with the pricing and licensing and setup costs is that I think it is fair because licensing depends on the user that uses it and consumes those tokens.

I had to reduce a lot of Microsoft Azure Authenticator, but for some reason, it is not supported in some products of Cisco. We have to divide it so that Cisco Duo also covers those needs.

I do not use Cisco Identity Intelligence. I have not noticed any increase in phishing attacks recently, but I work in a financial company where the security is critical. If something can happen one time per 25 years, it is very risky and has to be mitigated somehow. I have implemented Cisco Duo end-to-end phishing resistance with proximity verification for both. I did deploy Cisco Duo Directory to manage the user identity and am using it as a standalone identity provider. I do not think I discovered any new functionalities that I did not think of in the beginning. I did not really face any challenges doing that. I would rate this review a 10 out of 10.

My main use cases for Cisco Duo are two-factor authentication and single sign-on for different solutions.

The feature I like the most about Cisco Duo is the dashboard to have everything in one single place and manage multiple customers and multiple tenants simultaneously.

Cisco Duo benefits my organization because we do not have too many logins since everything is in one place and we can use Cisco Duo for VPN, applications, and cloud solutions. This is a main benefit and the core purpose of the product that we are utilizing.

I think Cisco Duo can be improved. I found the onboarding was very difficult, even for engineers who have been using similar solutions before. For our specific implementation, we needed to have multiple groups, multiple companies, and multiple third parties, and I felt that the examples and material provided were insufficiently detailed. The onboarding videos, materials, how-to guides, and documentation should be improved dramatically.

I have been using Cisco Duo for approximately three years.

I did not notice any downtime or crashes with Cisco Duo. We focused on making modifications and changes only during maintenance windows, and afterwards in production, we did not have any downtime.

Cisco Duo's scalability works well with the growth of our company and does not seem to have a limit. We could add as many users and as many sites as needed, so scalability is not an issue.

Before implementing Cisco Duo for this particular customer, I did not consider another solution. However, for other customers, we also use some open-source solutions and cloud providers, which unfortunately seem to be winning over Cisco Duo.

I cannot say I have seen a clear return on investment. However, as I was only the integrator, it is difficult for me to make an estimation on the customer's actual ROI. That said, considering that they did not have any more attacks, it is probably positive, but I am not able to fully evaluate that.

My experience with pricing, setup cost, and licensing for Cisco Duo is that it is not an expensive product. The issue was that we had a customer migrate away because they moved to one of the cloud providers for identity management as well. The difference in cost to upgrade to directory services on that platform was cheaper than having Cisco Duo. However, generally, if a customer is not tied to a specific cloud vendor, then the pricing is acceptable.

I do not recall seeing Cisco Identity Intelligence or using it.

I have noticed an increase in phishing attacks recently, and this was exactly the reason one of our customers asked us to implement Cisco Duo because they were attacked before and lost quite a bit of money. After that incident, we deployed Cisco Duo for them. While using Cisco Duo, we did not have any issues regarding other attacks.

When implementing Cisco Duo, I implemented end-to-end phishing resistance with the proximity verification as the full solution.

I deployed Cisco Duo Directory to manage user identity.

I am using it as an identity broker because we were not integrating to the customer's Active Directory. It was actually functioning as an identity proxy rather than as a directory per se.

The organization's overall cost for authentication was higher, but the indirect cost of being attacked and losing data is significantly greater.

I discovered new benefits after initial implementation when we started with basic VPN authentication and then developed many other flows based on that. We learned that there were not enough examples or documentation available so we could start from the beginning knowing everything about the product.

The deployment experience was complicated as it was a trial and error process. We had multiple existing systems, and for each system we wanted to integrate with Cisco Duo, the approach was different. One was connecting directly, one was using the API, one was using SAML, and one was using directory services, making the process quite challenging.

I would rate this review an eight out of ten.