Cisco Duo is a two-factor authentication system (2FA), acquired by Cisco in October 2018. It provides single sign-on (SSO) and endpoint visibility, as well as access controls and policy controlled adaptive authentication.
$3
per month per user
IBM Cloud App ID
Score 10.0 out of 10
N/A
IBM Cloud App ID helps
developers who are not security experts to add authentication to their
apps, and protect their APIs and app back-ends running on IBM Cloud. Developers
can add a variety of login-in types: Email or username and password Enterprise Social App ID includes a cloud user repository to on-board new
users, so they can log-in with email/username & passwords, with pre-built
self-service workflows (password reset, email validation etc.)…
Cisco Duo was much easier to setup and was trusted more than JAMF. I think having a familiar name like Cisco people were more willing to download than the application Jamf had
When we evaluated Microsoft MFA vs Cisco Duo, we found that Cisco Duo had more integrations into systems that we were supporting. We also found that Cisco Duo could support a more types of authenticators (Yubikeys, verified push to an app, OTP tokens such as d100, etc). The …
Cisco Duo exceeds the WatchGaurd AuthPoint product on every metric. Its easier to implement. More flexible in how its applied. And it allows much more features and granularity in how it can control access
Ultimately we ended up going with Cisco Duo because we are a Cisco shop. All of our networking infrastructure, our phones, our wireless environment is Cisco based. It made logical sense to stay with a product that we already have a line of support with. With a smaller …
We did look at Okta for our 2FA solution and while it did support end user 2FA, Okta did not have the feature set that Cisco Duo was offering. One of our requirements was 2FA support for custom applications. Cisco Duo had the solution and support staff to help us roll that out.
In my opinion, the IBM Cloud App ID are far from, thus, requires a lot of improvement compare to these matured, has long years of experiences in offering similar application of purpose. The IBM has a lot of room to improve more so that their client would definitely choose their …
The reputation of IBM Cloud App ID across the market and pricing solution for our large organization was the main driving factor. Also, user documentation and customer support were an add on.
IBM Cloud App ID is our first supplier when it comes to app authentication. IBM is a very known provider and we didn't have to research its trustworthiness or hesitate [on] our purchase decision. Even though it can be a bit expensive, efficiency is our top priority.
Both the software have different use cases, like IBM Cloud App ID, which will be more suitable for internal websites and apps or specific event website authentications, Auth0 can be suitable for consumer websites, e-commerce sites, where social media login is preferred more by …
I was building my application’s back end on IBM Cloud Functions, so naturally I had to use App ID. Because of the seamless integration between App ID and Cloud Functions, I can create protected API endpoints for my Single Page Application (SPA) and not have to write middleware …
The features that IBM App ID includes are incredibly beneficial to the developer process in terms of simplicity and security. I have found using this app a prominent staple in app development and plan to use it furthermore.
For secure access to apps and business data, I recommend Cisco Duo. It offers SSO, MFA, and Passwordless access, ensuring teams can securely access business data. It is easy to customize and comes with top-tier security features. It protects business data, apps, and users.
Whenever you need to provide Security Provider functionality for a web based application it is well suited. You can also integrate with other directory services (e.g. SAML, Facebook, Google), but not so easily with other Auth0 based services. The customization of the login page is very intuitive, but does not allow much customisation. using the integrated Cloud Directory, you do not need to integrate with existing security providers and you can build up your own user base - including Multi-Factor Authentication settings and password policies.
We use Cisco Duo with different type of device and application, but we never face any difficulties to integrate Cisco Duo with any of them.
We integrated Cisco Duo with some of our active directory and some of the OS are quite old but Cisco Duo works totally fine with them.
The end user application is very easy to use. We never had any complain from non tech team members of having trouble of using Cisco Duo.
There are several authentication methods available rather than passcode. I personally like the push notification which is always on time and quite fast.
Should have device to device connection ability whereas internet is not met.
Changes of device can be sorted and easily made using a second email address or any other identification method.
Troubleshooting should be easy to sort out. One time, a Duo admin deleted the authentication group, and some employees were not getting push notifications. It was very hard to find out the cause. Duo should have some troubleshooting finder.
Sometimes push notifications are delayed, and the code does not work. At that time, we need to enroll the device again. Not sure why it happens. Duo should give reasons for the error.
There are a lot of competing solutions on the market; however, Duo "just works", and there is little to no learning curve for the new members to be acclimated to it. As long as that continues I see it as the preferred option moving forward
La interfaz es intuitiva y fácil de navegar, lo que permite a los usuarios administrar sus dispositivos y acceder a las políticas sin problemas. La integración con las aplicaciones SSO y SaaS facilita aún más el proceso de acceso, mejorando la experiencia del usuario.
In the last 5+ years we've been using Duo, there may have been 1 outage that impacted us. We do receive periodic notifications of issues but, for the most part, they impact carriers or functionality that we either don't use, or do not care about.
I have not needed direct support for Cisco Secure Access by Duo as I have not had a problem with it, but I have full confidence that the support is outstanding. It is now a core component of the corporate technology stack - a problem would mean a serious degradation in the ability of the company to function.
Documentation could have been better. I had to piece together different KB/admin guides to make certain things work and I also had to use third-party guides to get bits of information that were missing from Cisco Duo documentation. Support was also engaged multiple times to figure out an issue and after some back and forth it was usually determined that the information I needed was hidden somewhere else and had no direct correlation with the document that was linked from the platform.
Ultimately we ended up going with Cisco Duo because we are a Cisco shop. All of our networking infrastructure, our phones, our wireless environment is Cisco based. It made logical sense to stay with a product that we already have a line of support with. With a smaller support / tech group we depend on outside Cisco support. That support is already here for us, so we stayed with a Cisco product.
Both the software have different use cases, like IBM Cloud App ID, which will be more suitable for internal websites and apps or specific event website authentications, Auth0 can be suitable for consumer websites, e-commerce sites, where social media login is preferred more by the users. Both have their own capabilities so can be chosen according to their needs.
Cisco Duo has saved us from automated attacks on VPN. We had an instance is 2024 where our VPN was being brute force attacked, and we had several users' weak passwords compromised; however the VPN security groups, and the MFA kept the attacks from gaining access. We've since replaced our firewall with capabilities for limitations on country access for VPN, and beefed up our password complexity settings,