Our company's use case is that we are a service provider, basically a wholesale provider for the internet and the data we have. We have internal users as well as external service providers who want to connect to our company, and they use MFA from Cisco Duo.
Cisco Duo - Advantage Edition
Cisco Systems, Inc.External reviews
External reviews are not included in the AWS star rating for the product.
Mfa has strengthened compliance and reduced authentication costs for internal and external access
What is our primary use case?
What is most valuable?
The most valuable feature of Cisco Duo is the MFA itself, and the integration is pretty straightforward. The documentation is good.
Cisco Duo helps improve a company through security, and we have the regulatory compliances we have to meet by having Cisco Duo's MFA enabled. With Cisco Duo, we get that checkbox filled.
What needs improvement?
More documentation on how to integrate all the external applications would be beneficial for Cisco Duo. We have lots of third-party applications, especially our in-house applications, and additional documentation on how to integrate those applications for MFA using Cisco Duo would be helpful.
I evaluate the stability and reliability of the solution as somewhat tricky. Cisco Duo Access Gateway is mostly VM-based, and while I'm not sure whether there is an on-premises hardware-based solution, having this VM-based solution can be buggy. There are a lot of issues, and when something goes down or if there is an issue in the network, the whole solution goes down, affecting the whole company because the MFA is tied to login for an administrator and to login for a user. This needs to be improved; the solution, which includes the gateways and proxies connecting to it, needs to be more reliable.
For how long have I used the solution?
I have been using Cisco Duo for around five years.
What do I think about the stability of the solution?
I evaluate the stability and reliability of the solution as somewhat tricky. Cisco Duo Access Gateway is mostly VM-based, and while I'm not sure whether there is an on-premises hardware-based solution, having this VM-based solution can be buggy. There are a lot of issues, and when something goes down or if there is an issue in the network, the whole solution goes down, affecting the whole company because the MFA is tied to login for an administrator and to login for a user.
What do I think about the scalability of the solution?
The solution scales for us.
Scalability-wise, resources for the VM are mostly what is required, and we have them in-house. For the licenses, that aspect is covered with support.
How are customer service and support?
I have used support for Cisco Duo.
I evaluate Cisco's support as very good. We have the highest level of support, including a tech specialized support team dedicated to our account. We have weekly and monthly meetings where they advise us on what to do, how to proceed with upgrades, or any enhancements.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
When we went for an MFA, we were focused on Cisco Duo, and the way it functioned seamlessly integrated with our security policies. We did not evaluate others.
How was the initial setup?
My experience with the pricing, setup costs, or licensing for Cisco Duo is straightforward. We've had good interaction with the Duo team, and they always advise us. We have the highest level of support, so they come back to us with what is the recommended licensing, expiry, renewals, and pricing.
What was our ROI?
Cisco Duo has helped my organization reduce its overall authentication-related costs. The solution is pretty concise, not having a lot of tools or integration points like other providers.
When I look at the solution compared to other vendors, Cisco Duo is a one-stop shop for the whole MFA, so percentage-wise, I would say it's about 50%.
This 50% savings is over the five years.
What's my experience with pricing, setup cost, and licensing?
Evaluating the delivered cost, I find the choice to go with Cisco Duo is good. There were not many options available in the market. We had Cisco Duo, and we just appreciated the way it's delivered. It's functionally doing the MFA, and we went for it.
Which other solutions did I evaluate?
When we went for an MFA, we were focused on Cisco Duo, and the way it functioned seamlessly integrated with our security policies. We did not evaluate others.
What other advice do I have?
I am not currently using Cisco Identity Intelligence.
I have not noticed an increase in phishing attacks in my organization recently.
I have not implemented Cisco Duo's end-to-end phishing resistance.
We manage user identities through our own Active Directory internally, not through Cisco Duo Directory.
Cisco Duo integrates with other products well; I've not had an issue, except for the custom-based applications where we faced a lot of challenges. We had to work with the Cisco Duo team to integrate our service provider applications, OSS/BSS.
My overall review rating for Cisco Duo is 8.
Security has improved as I control access, reduce shadow accounts, and cut unused apps
What is our primary use case?
The main use cases for Cisco Duo are for people who don't have a multi-factor authenticator. This is concerning because when you work in IT, you assume you are talking to technical people. Sometimes they are a director of the IT department, and when I ask them, "What do you have for an MFA?" they respond, "We don't." So I say, "Okay, let's talk about Cisco Duo and how you can implement it in order to secure your organization." That's the main case.
We place Cisco Duo Identity Intelligence with the customers against Shadow IT because sometimes we have the feeling that the customers have a lot of platforms. They have thousands of accounts they are using. In general, customers are using around 100 SaaS applications in a company, and sometimes they don't really know what they have. Sometimes, some workers are not there anymore, and it's possible that they can lose track of who is still in the company and who is not. That's why with Cisco Duo Identity Intelligence, I am able to provide a complete overview of what they have. Now they can check who is still using the system. It's good against Shadow IT, but it's also good if you are paying for an app and you don't use it anymore. You can cancel the subscription and get some money back.
What is most valuable?
What is good with Cisco Duo is I have to explain that it's not just an MFA because some customers already have an MFA in place. I can talk about other products from Microsoft or any other product, and they say, "We already have an MFA." So I have to explain to them that Cisco Duo is not just an MFA. With an MFA, you want to access something, and the MFA is going to check if you can enter, yes or no. It's not going to check your background or what you have. Cisco Duo is a pre-MFA and post-MFA. With Cisco Duo it's checking if you are allowed to submit a request to access this. If your company is just working with Windows and you are trying to access with a Mac, Cisco Duo is going to be able to say, "Why are you working with a Mac? It's not allowed," so you're not going to have a request. Or if you are, for example, working in Germany and you only have workers in Germany, and suddenly your IP address is in Spain, then I can explain to the customer, "Okay." The customer might say, "Okay, I have a request from Spain, but we don't have people working in Spain, even remotely. So we will block it directly." That's the good thing. It's comparable to when you want to go to a nightclub, they ask you if you are 18, but they also check it with your ID card and everything. It's the same with Cisco Duo. They do a complete check of you before you access.
What needs improvement?
I have not implemented Cisco Duo's end-to-end phishing-resistant capabilities such as proximity verification.
I have not deployed Cisco Duo Directory to manage the user identities, not yet, because since a lot of customers already have their own directories, it was not necessary with Cisco Duo. We still talk about it, but it was not necessary as of right now.
For how long have I used the solution?
I have been using Cisco Duo for two years.
What do I think about the stability of the solution?
I would assess the stability and reliability of Cisco Duo as good. I have nothing to say. It's never had downtime, nothing. Cisco Duo cannot see your password. It's just sending the request. At no point in time does it see or save your password. That's also the good thing. And it's working with everything, and it's native on Linux. This means with some other products, I can get Linux to work, but I have to do some tricks. With Cisco Duo, it's already in. So if I have a server with Linux, it's perfect.
What do I think about the scalability of the solution?
I think Cisco Duo is scalable in a growing company and it works well. It's very scalable. I can add users, and as far as I remember, if I cross the line with the users, I will get a notification stating, "You need to upgrade," but it's not blocked. This means it's not that I add one user and now everything is locked. I have a lot of leeway. I can improve, and I will have a notification and still have time to pay more. Regarding the scalability, I just add one new customer, and after I upgrade my license directly from the dashboard as an admin, that's it. There's nothing else to do.
Which solution did I use previously and why did I switch?
I had something before Cisco Duo. It was a Windows MFA. I don't know the name. A Windows solution. But once again, the Windows solution is like, "Can you go in, or not? Is it you?" "But where are you? And is it really you?" That's the problem.
How was the initial setup?
The experience of the deployment with Cisco Duo is pretty rough. The software itself is good. The software itself is not the problem. The problem with customers is I have to change their habits. There are some people who don't want an MFA on their phone. It's easy for people who have a company phone and people who have a private phone. In some companies, they just have a private phone; they don't have a company phone. Since it's not always GDPR-friendly, with an MFA I can still send some information. Some people don't want to do it. I think it's rough in the sense that I have to educate the customers to use it and install it, because some people don't want to install it. Or if they really don't want an app, I still have the possibility to buy keys or to install a token on a USB key. But the deployment with the software itself is good. It's more about doing the education for the customers.
What was our ROI?
I have seen a return on investment with Cisco Duo. The good thing is the MFA is free. I can use it. I have Cisco Duo on my phone for free, so everybody can use and install it, up to 10 users. So it's good. I can start with this. The return on investment is that I present the product, and the customer, even if he doesn't click immediately about the features, after that, he will just log himself into the panel and see, "Oh, there's this. I would like to try this feature." So he will upgrade your service because as soon as he discovers new functionalities and thinks it is cool, then he will buy it. The return on investment is very nice.
Which other solutions did I evaluate?
I did not really consider another solution before selecting Cisco Duo.
What other advice do I have?
I haven't noticed an increase in phishing attacks lately. We do have some in our company. We saw an improvement. I think it's always the same as before, but now it's more improved. It's comparable to the following scenario: "We are the police and you did access a website you were not supposed to. This is the company headquarters. Please click here in order to report yourself or you will be fired." I think there's been an improvement in creativity. Not in numbers, but in creativity. Before there was, "You've won an iPhone" or "You've won one million. Please click here." Now they cannot do this anymore. You have to improve your creativity to find a new way to trick the customers.
The pricing for Cisco Duo is really good in the sense that you can try it. There are different packages, and you can choose the one that fits you the most, and you can try it for free for 30 days. So it's a very good catch. And for the price, I think it's worth it. I have not received any bad feedback about the price. I think it's okay.
We were talking about proximity with Bluetooth for Cisco Duo, but now it's been released, which is good because sometimes attackers use MFA fatigue, which means they will bombard you with push requests for everything. But now you need the device you're using to log in to be connected via Bluetooth next to the device you are also using to log yourself in. So that's good. It was one feature I had the idea for, and now I saw that they are doing it. That's excellent.
I would rate this review a 9 out of 10.
Strong authentication has improved secure 2FA and supports flexible identity management
What is our primary use case?
What is most valuable?
I appreciate the secured push feature of Cisco Duo because you have to choose a number.
I value this feature because it is a security feature that enhances the security of your users, and if you also have geolocation for verified push, that would be even better.
It benefits our company as well as our customers because it is more secure. You can have geolocation or know which network the users are on, so if they do not have a push when they are in the company, but if they are on holidays or traveling somewhere, they have a push verified login, which is much more secure.
What needs improvement?
It is difficult to say how Cisco Duo can be improved. I think it is a good product, but we do not have many customers that use it, so perhaps in marketing, we should bring it more to our customers and show them the use cases for Cisco Duo.
For how long have I used the solution?
I have been using Cisco Duo for one and a half years.
What do I think about the stability of the solution?
The experience my clients have with Cisco Duo is mainly good. There are sometimes some problems, but not major ones, so it is a solid security product.
My clients have never had major problems with Cisco Duo. Everything works fine most of the time, and maybe sometimes there are minor problems, but these are more configuration problems than problems with the product itself.
What do I think about the scalability of the solution?
Cisco Duo is really good for scalability. As with almost every cloud product, the scalability is really good, so it does not matter how many users you have.
How are customer service and support?
I have never had experience with customer service and technical support.
How would you rate customer service and support?
Negative
How was the initial setup?
The setup process for Cisco Duo is quite easy and can be done really quickly. You can have test users, and I think the rollout process is great. They really think about how you deploy it, and it is fair and easily done.
What was our ROI?
The return on investment, like every security product, has to be done. It is much more costly if you do not deploy security in your company.
What's my experience with pricing, setup cost, and licensing?
I think the prices of Cisco Duo are quite fair, but the main problem is that Microsoft Authenticator is built-in with M365, so everyone is switching to that and using it instead of Cisco Duo because it costs extra as a standalone product.
What other advice do I have?
I would give Cisco Duo a rating of 9 out of 10. I do not give it a 10 because I think it is a great product that is easily set up and enhances security. My advice for other companies considering Cisco Duo is to reach out to Netcloud to help. I do not have anything else to add about my experience with Cisco Duo.
Seamless integration has expanded secure customer access and now simplifies identity management
What is our primary use case?
What is most valuable?
The feature I appreciate most about Cisco Duo is the ease of integration with my platform. It's straightforward with all the APIs they have to integrate with my platform. After that, I just put a Cisco Duo button on my login page, and then people can use their credentials. The integration is what I value the most.
Cisco Duo benefits my organization by making it easy for me to reach out to customers using Cisco Duo so they can integrate on my platform using their credentials. They don't have to change the way they connect, and it makes the whole experience seamless. That's why it's truly beneficial for my organization.
What needs improvement?
In Cisco Duo, what could be improved is having more features. We are using a front-end broker because the integration was something we struggled with. I would suggest releasing some API endpoints so we can have additional integration options beyond the basic one we used to have.
For how long have I used the solution?
I have been using Cisco Duo for four years.
What do I think about the stability of the solution?
I assess the stability and reliability of Cisco Duo as having some slowness at certain points, but it's not really an issue. Overall, the performance is good.
How are customer service and support?
I didn't have to use customer service regarding Cisco Duo.
How would you rate customer service and support?
Negative
How was the initial setup?
The experience of deploying Cisco Duo was straightforward and easy.
What was our ROI?
I can say that I've seen a return on investment from having Cisco Duo.
Cisco Duo has provided a return on investment by integrating and increasing my reach to people and customers using Cisco Duo. It has had an impact on my revenue because I was able to integrate more customers. There is a clear ROI to this.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing, setup cost, and licensing for Cisco Duo is that I've been working with Cisco for a long time, so it's straightforward. Pricing is per user, so it's easy to understand.
Which other solutions did I evaluate?
Before adopting Cisco Duo, I considered other solutions. I've worked extensively with Azure AD and Okta. However, because Cisco Duo is a Cisco product, it makes sense for me to integrate with it.
What other advice do I have?
I am not using Identity Intelligence in Cisco Duo.
I haven't noticed an increase in phishing attacks in my organization recently.
I haven't implemented Cisco Duo end-to-end phishing resistance with proximity verification, though I may consider it if needed. I wasn't aware of the feature until now.
I have deployed Cisco Duo Directory to manage user identity.
I use a front-end broker with Cisco Duo that manages all the IDPs for my platform. It integrates with Cisco Duo and different SAML providers.
I would not say that Cisco Duo helped reduce the overall authentication-related costs, but it definitely helped specifically for managing those customers.
I did not discover any feature in Cisco Duo that I didn't think I would use initially and later discovered along the way. I believe we are knowledgeable about all these SAML providers, so we knew what we wanted to leverage.
I would rate this review as an eight out of ten.
Strong authentication has met strict security needs and protects our organization from phishing
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Cisco Duo for about half a year.
What do I think about the stability of the solution?
I have not noticed any stability or reliability issues such as downtime or crashes.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
I cannot say that I have seen a return on investment from having Cisco Duo. I have experienced only a security benefit.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Unified access management has simplified secure logins for VPN, apps, and cloud services
What is our primary use case?
My main use cases for Cisco Duo are two-factor authentication and single sign-on for different solutions.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Cisco Duo for approximately three years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Strong access controls have transformed our security posture and protect remote app access
What is our primary use case?
Cisco Duo is used primarily for access management, zero trust architecture, and identity management, with MFA serving as the main feature.
What is most valuable?
My favorite feature in Cisco Duo is the remote app access.
The remote app access feature helps our company by providing strong MFA protection in the event of password and username leakage from any employee, ensuring that we can protect our applications more effectively. Cisco Duo integrates smoothly with our environment, avoiding challenges that might arise with third-party products, making it an ideal solution given that we work with Cisco for support and AI technology.
What needs improvement?
Cisco Duo could be improved by building the agent with the many agents we already use, such as Cisco AMP and Cisco Secure Client, which would simplify our environment by eliminating the need for a third agent for secure applications.
For how long have I used the solution?
We began using Cisco Duo in 2024 as a demo, and after 30 days of evaluation, we transitioned to live production for almost four applications. We plan to increase to six applications in 2025 and ultimately expand to 12 or 16 applications by 2026.
What do I think about the stability of the solution?
The stability and reliability of Cisco Duo depend on the environment and Cisco's cloud infrastructure, which is beneficial since Cisco does not compete with your applications but rather secures them.
What do I think about the scalability of the solution?
I believe there is no need for scalability concerns with Cisco Duo because it is designed to handle future expansions from the beginning.
How are customer service and support?
My experience with Cisco Duo's customer service and technical support has been perfect, as I had an interaction that went very well. I would rate the customer service and technical support from Cisco Duo a ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before choosing Cisco Duo, we were using a legacy VPN and did not publish applications that were not critical to the public, utilizing them only on a remote site.
How was the initial setup?
The deployment process of Cisco Duo is not straightforward; you need some knowledge of best practices because you are facing attackers, and it is better to let professionals handle it, especially when working in a critical environment.
What about the implementation team?
We did consider other solutions before choosing Cisco Duo and took several products for demos, ultimately deciding on Cisco Duo.
What was our ROI?
The biggest return on investment for us when using Cisco Duo includes disabling the public IP in our environment, which is a key goal for us.
Looking back at the initial investment in Cisco Duo, I find that the choice has paid off for our company, especially considering the difficulties of transitioning from traditional and legacy technology, and I hope we will continue to realize its value.
What's my experience with pricing, setup cost, and licensing?
I am not certain if Cisco Duo has reduced our overall authentication-related costs, but it has helped us manage and keep everything under control, which is our priority for safety.
Which other solutions did I evaluate?
The decision to choose Cisco Duo is based on the many features it offers that we did not find in other applications, and since we were already using Cisco for our other needs, it made sense not to switch to a competitor.
What other advice do I have?
Recently, we have noticed a heavy increase in phishing attacks targeting products not protected by Cisco Duo that are still published on the public network, as attackers are trying to obtain data.
I believe this significant spike in phishing attacks is due to AI bots, which are easier to acquire, as the cost of using them is reduced, making the attacks more commonplace despite the number of human attackers remaining the same or even decreasing.
We have deployed Cisco Duo Directory to manage user identities. We are using Cisco Duo Directory today as a standalone identity provider, connected with Microsoft Azure SAML as an identity broker.
We have implemented Cisco Duo's end-to-end phishing resistance with capabilities such as proximity verification. Our implementation of Cisco Duo strengthens our company's ability to defend against modern phishing and identity-based attacks through compliance with various benchmarks, offering multiple defense points, and isolating applications to prevent the use of shared resources among them, even ensuring isolation at the DNS system level via Umbrella.
We hope to use Cisco Identity Intelligence in the future, but we have not implemented it yet.
My advice to other companies considering Cisco Duo is to purchase it, as it really addresses security concerns and transforms the way you feel about security. My overall rating for this review is nine.
Multi-factor access has strengthened remote protection for our OT environment and users sign in flexibly
What is our primary use case?
My main use case for Cisco Duo is to protect the OT environment from remote access.
What is most valuable?
The feature I like the most about Cisco Duo is that I can choose which device I want to sign in.
It is valuable for me that I can choose because not all people have a corporate phone, so they can use their personal phone for access or different methods for performing second-factor authentication.
I can say that it is difficult to measure the direct return on investment, but what I can say is that we are safer and feel more comfortable having this security implemented than before.
What needs improvement?
I cannot think of any improvements for Cisco Duo at this time.
For how long have I used the solution?
I have been using Cisco Duo for approximately half a year.
What do I think about the stability of the solution?
I do not have problems with stability or reliability. Being a cloud solution, I think it is difficult to have problems, and we also use Umbrella with Cisco, which is very reliable and has high availability.
What do I think about the scalability of the solution?
The solution is scalable for our growth.
Which solution did I use previously and why did I switch?
We used Okta sometime before Cisco Duo.
We used Okta in a different environment, and we finished our license; we were not seeing the need to keep using Okta. For this new environment, we chose Cisco because we wanted to have a homogeneous solution, and our colleagues in other countries were happy, so it was easy for us to choose.
How was the initial setup?
The deployment experience was more difficult than we expected because we had some problems with the version of the OS that we have in our servers. We also had concerns about opening the mandatory connection to a specific URL and port from our OT environment.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing, setup costs, and licensing is that the price is acceptable because the license is by user.
Which other solutions did I evaluate?
We were considering different solutions, but we are a global company, and in another place in our company, they were using Cisco Duo, so it was our first option because we want to have a homogeneous scenario.
What other advice do I have?
I do not think I am using Cisco Identity Intelligence.
I have not seen an increase in phishing attacks recently; I think they are more or less constant, but not increasing, particularly in the last three or four months.
We have seen the number of phishing attacks increase every year, but I do not know if that surprises us; we are accustomed to having this type of risk.
I think I have deployed Duo Directory to manage the user identities.
I think I used it as an identity broker in front of the IDPs.
My review rating for Cisco Duo is 8.
Strong authentication has simplified remote access and identity management for guests and staff
What is our primary use case?
The main use case for Cisco Duo is MFA, which means multifactor authentication using the app and using keys like YubiKeys for various devices, such as RDP and remote access, but I would say remote access is the most prominent use case.
What is most valuable?
Right now, the feature I appreciate most about Cisco Duo is the Duo Directory, which is exciting because it became an IDP.
It is exciting that with Cisco Duo, I can offload guest users and contractors to Duo, so they do not have to exist in the customer environment from their AD, which is a nice way to accommodate guests and contractors needing access to applications.
I express how I appreciate Cisco Identity Intelligence to customers using the Duo Advantage license and always try to push them to at least take a look because it is essentially free with the Duo product.
I have multiple MFA vendors in our portfolio, and I try to position Cisco Duo because I think it is a really good product, but we also try to position other solutions depending on what the customer wants and where they think we can go together.
I deployed Duo Directory to manage user identities, and I think it is great because it is never a standalone provider; it always acts as an additional provider or broker functionality to be the front door and decide to go this way or go to the other IDP.
Once Cisco Duo is set up and running, it just keeps running.
What needs improvement?
I think Cisco Duo can be improved with more YubiKey support with all applications, especially for Windows login.
For how long have I used the solution?
I have been using Cisco Duo for three to four years, since the beginning of 2020.
What do I think about the stability of the solution?
I did not notice any problem with stability and reliability; it was always available with not much downtime needed.
Sometimes if I have problems, I obviously have to create a TAC case to ask for help, but most of the time, I would say it is very stable.
What do I think about the scalability of the solution?
I think Cisco Duo is scalable for organizational growth, as we have some customers using it who then onboarded new users and even bought companies and onboarded them; it is highly flexible and I did not feel any slowdown anywhere.
How was the initial setup?
The experience of deploying Cisco Duo is great; it is fast and not too complex in my opinion, as you can integrate basically anything into Duo, so I would say the experience is overall very great as an administrator.
What was our ROI?
I think Cisco Duo helped reduce the overall authentication-related cost for the company indirectly, as there is less work to do for the admins, because once it is set up, users understand the app, know how to use it, and rarely have problems, so if new devices need registering, they can do it themselves, depending on the setup.
What's my experience with pricing, setup cost, and licensing?
The pricing for Cisco Duo is kind of okay, but most of the time, your competitor is someone like Microsoft who gives it out for free with their offering, making it tough to argue with customers why they should spend additional dollars to also get Duo to improve their setup, but I think the pricing is fair.
What other advice do I have?
I am mostly part of the deployment and with the customers; I am not on the operational side of things, so I cannot really share about phishing attacks, but I mean, Cisco Duo allows phishing-resistant MFA, which is why I try to push my customers to use it, so I would argue, hopefully not.
That is why I try to push my customers to actually use proximity verification and use passkeys to strengthen security, which was mentioned in my previous answer.
I think there is a return on investment for the support team, where they can help validate customer requests and also through self-service portals, but I do not have any numbers regarding return on investment.
I would give Cisco Duo as a solution a rating of 10 because it is great.
Identity intelligence has strengthened defenses and provides better protection against phishing
What is our primary use case?
Cisco Duo primarily secures our environment.
What is most valuable?
I appreciate the features that Cisco Duo offers. Cisco Duo's team sent us some questions, for example, about the feature called Identity Intelligence. I have tried using the Identity Intelligence feature and have been working with it. I can confidently say that Identity Intelligence has improved my visibility into identity risk and has helped me make defenses against identity-based threats better.
What needs improvement?
The main issue with Cisco Duo is dependency. For example, it verifies the subscription with features Duo Push, OTP code, and phone dependency. If you lose or break your phone, users without smartphones will face connectivity issues. There is also integration challenges, support for legacy systems and cloud connectivity, management overhead, and the system can be bypassed by phishing techniques.
To improve these issues, users should be required to confirm a number to approve authentication requests. This would enable disabling auto push and then enable trust-based authentication with new device detection, new location detection, and VPN detection.
Additionally, Cisco Duo is subscription-based depending on the number of users and has a dependency on mobile devices for advanced features. The cost will become expensive for large user accounts. The system requires approve push and either OTP, with push deployments through Duo mobile applications. There is limited offline support, it requires internet connectivity and cloud dependency. Internet outages can cause authentication issues affecting VPN, Windows login, and cloud applications.
For how long have I used the solution?
I have been using Cisco Duo in my career for three years.
What do I think about the stability of the solution?
I do see instances of lagging, crashing, or downtime. We used to experience downtime, for example, during code upgradations and OS upgrades on the server, switches, and firewalls. We try to mitigate it, but we need to implement upgrades without downtime. Sometimes the device will not come up after reboot, which can cause downtime.
What do I think about the scalability of the solution?
Cisco Duo performs well regarding scalability. The scalability depends mostly on the number of users. The system has good scalability and can handle more users, more logins, and more locations without performance issues. This depends on the cloud-based, globally distributed infrastructure with no dependency on on-premises services. It can scale from 10 users up to thousands and hundreds of users. The system also has load balancing, high availability, and failover capabilities. A small office can support up to 50 users, while a large office can support more than 10,000 users.
How are customer service and support?
I have contacted customer support regarding Cisco Duo for assistance. The quality and speed of support depend on various factors. For example, when we receive any ticket, we need to assign it to ourselves first and then depend upon the SLA to work on the ticket. We need to resolve it within the SLA timeframe.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Regarding Proximity Verification feature, I have seen it in action last year.
How was the initial setup?
Cisco Duo's initial deployment is easy. We need to have a mobile application and need to install it for users on VPN, servers, clouds, cloud applications, and for admins and passwords. We need to have a security policy required and identity source such as LDAP, local users, Active Directory, and Azure AD. We need to have VPN devices for servers and firewalls with HTTP 443 port number. We need to have web applications and cloud applications, and Windows login. We need to have end-user devices for MFA, such as a smartphone and SMS. We need to have synchronization for security policy purposes, licensing, and many other components.
What about the implementation team?
Regarding the pricing for Cisco Duo, it is somewhat expensive. Cisco Duo costs depend on the technology. Up to 10 users, it is free. Premium versions go for dollars, such as $10 per user per account. As the number of members increases, the cost increases. It is very useful to have for multi-factor authentication.
What was our ROI?
I would rate the return on investment at an 8 or a 9.
What's my experience with pricing, setup cost, and licensing?
I have noticed an increase in phishing attacks in my organization recently. There has been a significant spike in the number of attacks, and they feel more sophisticated, which makes them more difficult to deal with. We used to get phishing attacks through our emails, SMS, WhatsApp, and fake website links. The domain may show a hyphen, for example, Microsoft hyphen login, and attackers will try to send a link. If you click on that link, all our data will be hijacked. We need to protect our devices and environment and should not click any unknown links. That is why we need to enter MFA with valid credentials.
Which other solutions did I evaluate?
Alternatives to Cisco Duo that we have been using in our organization include third-party applications. We can use Okta and Microsoft SSO, Microsoft Azure MFA, Rublon MFA, Twilio, and PingID from Ping Identity. There is also Secure Authentication and RSA SecurID in the market. There are many third-party alternatives available.
What other advice do I have?
The main issue with Cisco Duo is dependency. For example, it verifies the subscription with features Duo Push, OTP code, and phone dependency. If you lose or break your phone, users without smartphones will face connectivity issues. There is also integration challenges, support for legacy systems and cloud connectivity, management overhead, and the system can be bypassed by phishing techniques.
To improve these issues, users should be required to confirm a number to approve authentication requests. This would enable disabling auto push and then enable trust-based authentication with new device detection, new location detection, and VPN detection.
Additionally, Cisco Duo is subscription-based depending on the number of users and has a dependency on mobile devices for advanced features. The cost will become expensive for large user accounts. The system requires approve push and either OTP, with push deployments through Duo mobile applications. There is limited offline support, it requires internet connectivity and cloud dependency. Internet outages can cause authentication issues affecting VPN, Windows login, and cloud applications.
My overall review rating for Cisco Duo is 8.