My main use case for Cisco Duo is providing MFA for all of our users and use cases.

The first focus with Cisco Duo is securing externally available applications, such as SaaS applications. Mostly, we ingest or enforce Cisco Duo via our SSO IDP point because then we do not have to worry about the native integration with whatever application we are trying to secure. If it is SSO capable, we inject Cisco Duo into that.

When it came about, I was a big fan of the risk-based authentication feature of Cisco Duo. That was a big win. Additionally, the Verified Push after the Cisco breach was important, as Cisco recognized that they had to do something about that and they came up with the Verified Push, which is also a very good idea. Nowadays, if I would have known a couple years back what I know today, I would not have worried about that too much because I would have just moved over to passwordless and phishing-resistant MFA means in the first place.

The major improvement I would suggest for Cisco Duo would have been to collaborate with Microsoft more closely and get positioned in a way as a recognized MFA authentication method on Entra. Since Microsoft forced all of their customers to enforce MFA when logging into anything in the Microsoft universe, Cisco Duo was not a recognized way of doing that. It was enforced as an external authentication method, as Microsoft calls it, and it was not a native Cisco Duo integration. Even the external one was not possible to select as a default, so we had to use something else along with it, which for us was Microsoft. That was very annoying.

Cisco Duo did not help reduce the cost of the overall authentication method that we have in our company; instead, it increased, obviously. Cisco Duo was the first technology that we introduced, which had to not just change or implement a certain technology. That was the easy part; the hard part was changing the habits and the culture, getting people to accept what MFA is and to go through the hassle of MFA every single time. The total cost of ownership increased, along with the implementation and the license cost, as well as the reluctance of users to handle IT systems. Security is always a fine balance, where we have to explain to the users what we are doing, why we are doing it, and not overdo it.

Where it lagged behind a lot is in the RDP integration, because we have users, especially in Germany or other jurisdictions, where we cannot force users to use their phone. Therefore, we had to give them some kind of Passkeys, and they are not supported in every use case, or if they are accepted, it is extremely tedious. With standards such as OAuth or FIDO2, that can vastly be improved. Apart from that, it is a very solid MFA solution.

I have been using Cisco Duo for seven or eight years.

Regarding the stability and reliability of Cisco Duo, it is very good. It always does exactly what it is supposed to do, with no downtime over the years that we have had it in use, despite the issues I mentioned with Microsoft, where we were not able to integrate Cisco Duo at all.

Prior to Cisco Duo, I did not use another MFA solution; that was the first one.

I would describe the experience of deploying Cisco Duo as super simple. It was straightforward, one of the easiest consoles I ever had to implement.

I can still say that I have seen a return on investment from Cisco Duo, as having MFA is a basic requirement nowadays. MFA is considered state-of-the-art if you look at things such as GDPR or any other information security framework, so not having MFA means you cannot put a price tag on that because you will be hit with ransomware immediately.

My experience with the pricing, setup costs, and licensing of Cisco Duo is that we have it as part of an Enterprise License Agreement, so that is probably not comparable.

Before adopting Cisco Duo, I evaluated a couple of other solutions, but at that time, Cisco Duo won out primarily because it was available as part of the Enterprise License Agreement, and we were a big Cisco shop already.

I am not using Cisco Identity Intelligence.

I have not noticed an increase in phishing attacks recently in my organization because we are pretty well set up in terms of email protection.

I just learned about the Proximity Verification capability with Cisco Duo. We do not have it because we are already using Passkeys, so we no longer need Proximity Verification.

I did not deploy Cisco Duo Directory to manage the user identity.

I would give this review an overall rating of 8.

In my current role, I have been Head of the Information Security section for two years. Before that, I was a network and security administrator for more than 13 years.

Regarding Cisco Duo Mobile, I am currently the admin for the portal, managing more than 500 users. It is a great system regarding multi-factor authentication, specifically after we did the integration with Active Directory, allowing us to manage the users who use the VPN, our main gateway for VPN Cisco ASA Secure, with full administration.

An important feature that saves time is the automatic unlock; when an employee forgets to approve or deny three times in a row, Cisco Duo Mobile portal locks their account. There is a feature to automatically unlock it within five or six minutes, allowing the time for this automatic unlock to be determined.

One important benefit of using Cisco Duo solution is to ensure that the person using the VPN has their username, password, and mobile; they must approve or decline if they do not have their mobile. Another important benefit is managing users who have access to the VPN because sometimes there are users designed to have access, but the system administrator forgets to remove them, which we can effectively manage from the portal itself.

I have not implemented Cisco Duo's end-to-end phishing resistance.

No additional features are needed at this time.

I rate it a nine because there is still a specific feature regarding Cisco Duo Desktop that must be enabled and optimized better than the current situation. It is not about mobile but about the desktop functionality.

I graduated with a Management Information System degree 15 years ago, and all of my experience is based in the financial sector.

I assess the stability and reliability of Cisco Duo solution as mainly stable, safe, and at 98%.

Cisco Duo scales well with the growing needs of our company; we partner with Cisco, and since all of our components are Cisco, we are always attending Cisco Live EMEAR every year, finding new solutions and technologies, importing new products to our data center regularly.

I have not expanded the usage of Cisco Duo since the first implementation.

Cisco customer support is great.

The reason for this is that all of the Cisco TAC engineers at support are fantastic. They are available 24/7, and they do not leave sessions unresolved; when an engineer's shift ends, they assign a colleague to continue solving the case.

Before adopting Cisco Duo, I did not use a different solution.

My experience deploying Cisco Duo is great and went smoothly.

What went well is that you primarily need a license to access the main admin portal and at least two servers with minimum specifications, making it easy to configure. It is straightforward, requiring just one certificate.

I encourage anyone considering implementing Cisco Duo to move to Cisco Duo Mobile.

I did not evaluate other solutions from other vendors before implementing Cisco Duo.

Recently I have seen an increase in phishing attacks in our organization. These attacks feel like they are getting more sophisticated.

I did the integration with Active Directory instead of deploying Cisco Duo Directory to manage user identities. In the financial sector, Cisco Duo is fine as it is.

Regarding the price, the pricing of Cisco Duo is okay.

The main reason to implement Cisco Duo is that all of our data center infrastructure is Cisco. If we connect everything, the visibility will be 100%, which is why we need to cover everything with Cisco.

I am currently using Cisco Identity Intelligence.

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.

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.

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.

I have been using Cisco Duo for around five years.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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 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.

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.

I have been using Cisco Duo for two years.

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.

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.

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.

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.

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.

I did not really consider another solution before selecting Cisco Duo.

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.

I mainly use Cisco Duo for 2FA and sell that to our customers and the engineering team.

I would like to sell Cisco Duo's end-to-end phishing resistance more to customers.

We are talking with a customer to sell them Cisco Duo Directory to manage user identities.

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.

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.

I have been using Cisco Duo for one and a half years.

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.

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.

I have never had experience with customer service and technical support.

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.

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.

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.

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.

My main use cases with Cisco Duo involve managing access. I've integrated it into my platform so that customers can connect using Cisco Duo. It manages all the users connecting on my platform and provides SAML integration so they can use their Cisco Duo account credentials to connect.

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.

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.

I have been using Cisco Duo for four years.

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.

I didn't have to use customer service regarding Cisco Duo.

The experience of deploying Cisco Duo was straightforward and easy.

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.

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.

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.

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.

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.

Cisco Duo is used primarily for access management, zero trust architecture, and identity management, with MFA serving as the main feature.

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.

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.

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.

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.

I believe there is no need for scalability concerns with Cisco Duo because it is designed to handle future expansions from the beginning.

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.

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.

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.

We did consider other solutions before choosing Cisco Duo and took several products for demos, ultimately deciding on Cisco Duo.

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.

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.

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.

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.

My main use case for Cisco Duo is to protect the OT environment from remote access.

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.

I cannot think of any improvements for Cisco Duo at this time.

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

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.

The solution is scalable for our growth.

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.

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.

My experience with the pricing, setup costs, and licensing is that the price is acceptable because the license is by user.

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.

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.