Reliable, Proven Cisco Solution
May 03, 2021
Reliable, Proven Cisco Solution
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Duo Security
Duo Security is used in our company as an additional step of identify verification.
With remote working we needed a reliable solution with proven experience in security.
We chose Duo because it is owned by Cisco and they offer:
1. Good security
2. Fast replies on support requests
3. Reliable service
With remote working we needed a reliable solution with proven experience in security.
We chose Duo because it is owned by Cisco and they offer:
1. Good security
2. Fast replies on support requests
3. Reliable service
- Reliable Service
- Good Support
- Good Reporting
- Mobile app sometimes needs to be re-registered.
- Push notifications stop to work from time to time.
- Stability - The service is very stable.
- Client oriented - Duo team provided free licenses when we needed.
Cisco's MFA provided required reports for IT. Ex:
1. See the log of "Failed" connections and the "Success" connections.
2. See the location, as an IP and City name, from where the employees are connections. This helps trace the "Risky" users.
3. Provide a list of inactive users, this helps to understand what is the cause and if those employees are using the service
4. Allow users to report a "suspicious" connection
1. See the log of "Failed" connections and the "Success" connections.
2. See the location, as an IP and City name, from where the employees are connections. This helps trace the "Risky" users.
3. Provide a list of inactive users, this helps to understand what is the cause and if those employees are using the service
4. Allow users to report a "suspicious" connection
We had a region, situated in Europe, where a specific client was not able to register the application through the link provided. Duo team helped us to trace and see if the client made a connection form that endpoint to their service.
The conclusion was that the local mobile provider did block those requests.
The conclusion was that the local mobile provider did block those requests.