My main use case for Cisco Duo is identity and access management or verification, authentications, resetting passwords, self-service password reset, and managing and improving the security layer of the environment.

I use Cisco Duo for access management or verification, for example, when resetting the password for a client and we need to verify them, we could send them a reactivation text or we can send them a Duo Push. That's how we follow the process.

Other scenarios with Cisco Duo include Duo reactivation where people change their device and receive a new one. Then we have to get it onboarded and we send the reactivation text. They can activate with a single click.

The best features Cisco Duo offers and which stand out to me is Duo Push because it's the convenient option where we can just send a Duo Push and the person can just approve the push and then right away they can get in, saving the time to type in the password.

The convenience of Cisco Duo has impacted my workflow and my clients by providing ease of access, enhanced security, reduced risk, and reducing phishing and spam instances.

I would add that the integration among different applications and partner applications, such as Microsoft and other tenants, which includes Cisco Duo sitting as an agent or an intermediary between both the APIs, is a vital feature.

Cisco Duo has positively impacted my organization by reducing the metrics taken to resolve the issue. If the person can reset a password using the self-service password reset where they can verify using a Duo Push, it saves them time because they can do that in 10 minutes. When we need to do it on the domain controller and we need to sync over the password with the domain, it could take more than 30 minutes. We are definitely saving out of 30 minutes here.

I believe Cisco Duo needs to be improved on the delay process because there is a delay when we send a Duo Push or when we are signing into any applications. We can work on making it faster and speed this up. That's the part we need to work on, and on the outages, instances where we face issues with Cisco Duo and they are disabled, and systems are not working.

While the user interface of Cisco Duo is good and does not need to improve as it is quite user friendly, we do need to improve on the API because that is causing a delay in the process of revoking the tokens. The tokens are being sent a little late. Sometimes it has happened with me on multiple clients.

I have been using the solution for about four years.

In my experience, Cisco Duo is stable but not agile and not optimized, as there are delays when using the application and delays with APIs.

The customer support for Cisco Duo is great.

My organization used Microsoft Authenticator before Cisco Duo, and I switched because it was an option. I switched from Microsoft Authenticator to Cisco Duo because the GCP one is on Microsoft Azure.

Looking back at my initial investment in Cisco Duo versus the total value it has delivered over time, I see that it has paid more than what we invested, so we are getting a good return and a good service with improved security.

My advice to others looking into using Cisco Duo is that they can go for the product. I would rate this product a 9.

My main use case for Cisco Duo is to detect network-based threats.

There is one situation where malware is downloaded via a link, and Cisco Duo has blocked this URL, demonstrating how I use Cisco Duo as a detector for network-based threats.

We can correlate Cisco Duo with other data sources such as cloud and Azure, which represents another interesting scenario about how I use Cisco Duo.

The best feature Cisco Duo offers is its simplicity.

The interface is what makes Cisco Duo simple for me.

Cisco Duo has positively impacted my organization as we can analyze the logs to detect threats.

Analyzing logs and detecting threats with Cisco Duo helps customers gain confidence in our company, showing the positive effects it has had on my organization.

Cisco Duo could be improved with more interesting rules or correlation rules between all the data sources such as Windows and Azure.

I have been using Cisco Duo for six months.

I have not yet implemented Cisco Duo's end-to-end phishing resistance with capabilities such as proximity verification to strengthen my organization's ability to defend against modern phishing and identity-based attacks.

There are no other improvements needed with Cisco Duo that we have not discussed. I would rate this product an 8.

I work in a FinTech-based organization that primarily deals with card payments and payment orchestration solutions. As a FinTech company, we are required to maintain a high level of security for secure data and transactions occurring through our systems and servers. For our authentication process, we were using OpenLDAP and were searching for a solution that could be implemented with OpenLDAP to create a robust multi-factor authentication system within our infrastructure. This allows us to authenticate securely, ensuring that only authorized personnel can access the infrastructure and servers based on their identity.

We use this authentication mechanism exclusively for internal purposes and do not expose it to the public. Cisco Duo is deployed on my cloud servers.

The multi-factor authentication features of Cisco Duo have been particularly valuable to us. One key feature is Duo Unix, which can be implemented directly on Linux servers for SSH access. Additionally, we use Duo Authentication Proxy, which can be separately integrated with other tools such as OpenLDAP for server authentication. We also integrate Cisco Duo with various tools that have dashboards, such as Grafana, to enable secure login capabilities. We primarily use Duo Unix and Duo Authentication Proxy.

After searching through many tools, we found that Cisco Duo can work without requiring PAM modules and can integrate with the other services and tools we were already using. I believe we are fully reliant on Cisco Duo; it is completely reliable with our system, and we use it primarily for the authentication process. Without Cisco Duo, we cannot operate effectively. Cisco Duo is so integral to our core operations that we cannot perform any task without it.

I cannot speak extensively on this point because we are not using Cisco Duo to its full extent, as we are still in the initial phases and exploring its capabilities. So far, I have not found anything that requires improvement. I am satisfied with all the services I am currently using.

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

The only issue I encountered was related to the expiration of Duo Unix versions below 2.0.3 on February 3rd. Before the expiry date, the Duo Unix module began behaving inconsistently. Sometimes it did not prompt for authentication, allowing us to log into the server without verification. On other occasions, it responded appropriately, but there were instances when it started malfunctioning. Even though version 2.0.3 was in use during that time, it should have worked without errors. After upgrading to a version prior to that specific version, everything has functioned properly.

I have not tested Cisco Duo's scalability or examined anything related to it. However, I would like to rate it based on its flexibility, which I would rate between eight and nine out of ten.

I have not experienced any difficulty connecting with customer support or any other support specialist. The documentation provided proved to be sufficient. By reviewing the documentation and blogs available, one can easily find solutions and processes for integration and usage. The documents are comprehensive and thorough.

As I mentioned earlier, we were using another multi-factor authentication tool, but it was not compatible with our Active Directory solution. We were searching for a solution that would be compatible with our Active Directory and the other services we were using, which included dashboards and portals for logging into systems. After evaluating many tools, we discovered Cisco Duo MFA.

Initially, I was uncertain about how to implement Cisco Duo MFA. However, through the blogs available on Cisco Duo's page and the manuals and documentation provided, I gradually learned how to implement it and integrate it with our system and other tools. The documentation and blogs were nearly complete and provided me with sufficient knowledge on the implementation process.

I was the one who started implementing Cisco Duo.

I have not implemented Cisco Duo's end-to-end phishing resistance with capabilities such as proximity verification at this time.

I cannot speak to the financial planning of the organization, but I can confirm that Cisco Duo falls within the security budget that has been allocated to us.

After searching through many tools, we selected Cisco Duo because it can function without PAM modules and can integrate with the other services and tools we were already using.

We have not experienced any issues regarding phishing attacks.

I have not deployed Duo Directory, but I have created many users in the user section of the Cisco Duo admin portal. We manage user authentication, their devices, and everything else directly from the portal.

Regarding the use of Cisco Duo for our requirements, I would rate it a nine. Overall, I would rate this product an eight.

My main use case is for Cisco SSE.

It's fast. The whole process takes lesser time compared to other tools we've used before which is very helpful.

I think we'd need more experience to learn Cisco Duo because we're just at the beginning of using it.

I used Cisco Duo since last year.

It's quite stable so it is reliable.

I rate this solution a nine out of ten.

We have, but Cisco Duo was definitely the choice we made because we've been partners with Cisco for a long time so trust is built.

It was handled by a different team but I know that there were some challenges and they were quickly resolved it because there was a collaboration between Cisco and Emerson.