Share your experience using Symantec VIP Access Manager

I am an IT system support person, and my use cases with Cisco Duo started out with helping clients at my firm and the firms my contracting agencies had by teaching them how to set up Cisco Duo and understand how to use it. Eventually, some of the systems I have access to on my own, usually the corporate systems and employee portals, were Cisco Duo-protected. It has been a split between using Cisco Duo and Microsoft Authenticator, depending on how the MFA has been set up. I started out as IT support, helping people install Cisco Duo on their Android and Apple devices, and I believe they actually had a computer client. Eventually, I had to use it in my own work to authenticate and gain access to the systems I support. Moreover, I have seen a lot of it used to access employee portals, either by end-user employees or my own employee portals.

My last access to Cisco Duo involved helping people either activate their Cisco Duo accounts on their individual Apple or Android devices, or if they were locked out, unlock their accounts or move them over to a new device.

The features I use in Cisco Duo include Duo Pushes to confirm my identity to the device, and eventually as MFA security was increased, I actually had to use exchange passcodes. Sometimes, I have to go into the site and get into Cisco Duo to retrieve the passcode, and many of them have been two-factor, where the sites send a passcode that I have to enter into Cisco Duo. It has been more of the latter.

I have not seen issues with lagging or crashing on Cisco Duo's end; it was usually on the client end, often because someone set up a bad upgrade or there were connection issues with the Cisco Duo cloud through the administrative site.

As support, I do not find it an issue with Cisco Duo product itself; it is more an issue of organization administration. Often, people do not receive expiration messages, and sometimes, for security reasons, accounts get disabled without notifying the end user, so they mistakenly think something has gone wrong when it really just needs to be re-enabled on the external system. It is primarily an issue on the administrative side of the firm I am working for.

I am familiar with Cisco Duo and have probably been using it since around 2020.

Cisco Duo seems very scalable. In my experience, I started with a small-medium business, and in my last contracting position, it was a large one for a major worldwide airline that had hundreds of thousands of devices that could use Cisco Duo, and it scaled very well. The administrative site was also very easy to navigate for locating people and devices. I also have a background in computer asset management, so I have the skill set to locate device records easily.

In terms of quality and speed of support for Cisco Duo, I find it just as fine as any other Cisco product. It is simpler at the endpoint; there is much less involved in calling technical support to resolve issues compared to other Cisco products. I have also dealt with firewalls and VPNs, and I can say that Cisco Duo administration is much less involved than other Cisco areas. I would rate support for Cisco Duo a 10, as I have never had a negative experience.

Positive

My experience with MFA is primarily Cisco Duo and Microsoft Authenticator, and I have used them both similarly, either as pushes for allow or deny or as stronger MFA requirements such as exchanging passcodes. From my experience, Cisco Duo seems a lot easier to install and operate. In helping add accounts to either my devices or to the devices of the people I am supporting, both systems work well. I can get passcodes or utilize QR codes. One thing I noticed about my current firm is their initial hesitation to consider QR code exchange secure, but eventually, it was re-enabled to reduce support times. As an administrator, I have done both, pushing activation to pre-installed devices already registered to a system or actually sending people a QR code to their email, and both methods worked fine with personal and corporate email.

The setup of Cisco Duo is easy. Most of the time, the setup took me walking the end user through the installation over the phone, but if they understood how to get to their App Store or Play Store, it takes probably under two minutes. Most of it depends on wide area network or internet speed; activating directly on a client device versus sending an activation email makes a difference. If it is all set up and requires only sending an activation code message, it is about a minute. Cisco Duo installs very quickly on Android and Apple devices, provided the Wi-Fi connection is good.

From what I was involved in with Cisco Duo, we actually conducted Cisco Duo pushes through the management systems, enabling that through MDMs, the Bomgar. I found it pretty easy to grab the latest version of the Cisco Duo installer to update the packages on our management systems. I do not remember having any problems; it is one of the easier applets to package or to already find packaged.

I am currently between jobs or contracts, but I believe for the MFA administrator, it would help if they set up the filters for gathering the data. Cisco Duo seems very scalable. In my experience, I started with a small-medium business, and in my last contracting position, it was a large one for a major worldwide airline that had hundreds of thousands of devices that could use Cisco Duo, and it scaled very well. The administrative site was also very easy to navigate for locating people and devices. I also have a background in computer asset management, so I have the skill set to locate device records easily. I have given this review an overall rating of 10.

My main use case for 1Kosmos BlockID has been identity and access management and multi-factor authentication implementation for enterprise users. I have worked on user provisioning and de-provisioning, configuring and authenticating policies, integration applications, troubleshooting authentication issues, and ensuring secure access to business applications. I have also been involved in day-to-day administration, user support, and monitoring of 1Kosmos BlockID environment.

1Kosmos BlockID is used in our environment for managing the user's identity life cycle, including provisioning and de-provisioning. For user provisioning, whenever a new employee joins our organization, we receive that onboarding request from HR or the hiring manager. First, we verify the user details and create or synchronize the user account with our identity source, such as Active Directory. Then we assign the required roles, groups, and access policies based on the user's department and job role. After that, we configure the appropriate authentication methods, such as multi-factor authentication, and provision access to the required business applications through single sign-on. Finally, we test the access and confirm successful onboarding with the user and application owner. For de-provisioning, whenever an employee resigns or is terminated, we receive an off-boarding request through the ITSM process. We immediately disable the user account, revoke all active sessions and MFA registrations, remove group membership and application access, and document the action for the audit process. This ensures that the user no longer has access to any corporate resources and helps maintain security compliance.

Apart from user provisioning and de-provisioning, I have been involved in the day-to-day administration and support of 1Kosmos BlockID environment. My responsibilities include monitoring authentication activities, troubleshooting login and MFA use issues, managing user access requests, supporting SSO integrations, reviewing security policies, and coordinating with application owners and internal teams. I also participate in incident resolutions, user onboarding support, access reviews, and audit-related activities to ensure compliance and security standards are maintained. This hands-on experience helps me develop a strong understanding of identity and access management processes and best practices.

1Kosmos BlockID has had a positive impact on our organization by improving security, simplifying user access management, and enhancing the user experience. After implementing MFA and passwordless authentication, we observed a reduction in password reset requests and authentication-related support tickets. It also improved onboarding and offboarding processes through centralized user management and helped strengthen compliance and security standards across the organization.

I have observed a positive return on investment after implementing 1Kosmos BlockID. Although I do not have the exact financial metrics, we experienced a reduction in password reset requests and authentication-related support tickets, which saved IT support time. We also improved user onboarding and offboarding efficiency through centralized identity management and automation. Additionally, stronger authentication and passwordless access improved security and reduced operational overhead.

In my experience, the best features of 1Kosmos BlockID include passwordless authentication, multi-factor authentication, single sign-on, user provisioning, de-provisioning, and strong security with easy integration capabilities. Passwordless authentication has helped our team improve security and reduce password-related support tickets and account lockout issues. It also provides a better user experience through biometric and MFA-based authentications. The easy integration capabilities help us connect enterprise applications and identity systems quickly, using standard protocols, which reduces deployment time and simplifies user access management. Other useful features include single sign-on, user lifecycle management, self-service options, and centralized administration.

1Kosmos BlockID is a strong identity platform. However, it can be improved by providing more detailed reporting and analytics, simplifying the administration interface, enhancing third-party application integrations, and offering more advanced troubleshooting and monitoring features for administrators.

In addition to reporting and integration, I believe 1Kosmos BlockID could be improved by enhancing the user interface to make administration and troubleshooting more intuitive. More detailed product documentation, implementation guides, and real-world use cases would also help administrators and support teams. Additionally, improved dashboards, logging, and monitoring capabilities would make it easier to identify and resolve authentication and integration issues quickly.

I have been using 1Kosmos BlockID for the last two years.

In my experience, 1Kosmos BlockID has been a stable and reliable platform. We experienced good availability and consistent performance in our production environment. While there were occasionally issues related to integration or user onboarding, these were manageable and did not significantly impact business operations.

In my experience, 1Kosmos BlockID has good scalability. It can support a growing number of users, applications, and authentication requests while maintaining performance and security. This makes it suitable for enterprise environments and future expansions.

Customer support has been good. I would rate the customer support a seven out of ten.

Before implementing 1Kosmos BlockID, we were using traditional Active Directory-based authentication along with conventional MFA solutions. We migrated to 1Kosmos BlockID to strengthen security through passwordless authentication and improve the user experience, centralize identity management, and enhance compliance and identity verification capabilities.

Our organization procured 1Kosmos BlockID through the AWS Marketplace. This simplified the procurement and deployment process and allowed us to integrate the solutions more efficiently with our existing AWS-based infrastructure.

I was primarily involved in the technical implementation, administration, and support of 1Kosmos BlockID, so I was not directly responsible for pricing, licensing, or commercial negotiations. However, based on discussions with our management and procurement teams, the pricing and licensing model is considered competitive for enterprise identity and access management requirements.

I have observed a positive return on investment after implementing 1Kosmos BlockID. Although I do not have the exact financial metrics, we experienced a reduction in password reset requests and authentication-related support tickets, which saved IT support time. We also improved user onboarding and offboarding efficiency through centralized identity management and automation. Additionally, stronger authentication and passwordless access improved security and reduced operational overhead.

At this moment, I do not have the exact metrics available. However, based on our operational experience, we observed a significant reduction in password reset requests and authentication-related support tickets after implementing passwordless authentication and MFA. We also saw improvements in user onboarding efficiency and overall user experience, which I cannot provide percentage metrics for. The feedback from both users and the IT support team was very positive.

During the evaluation process, we considered other identity and access management solutions; however, 1Kosmos BlockID was selected because of its strong passwordless authentication capabilities, identity verification features, security model, and ease of integration into our existing environment.

My advice to organizations considering 1Kosmos BlockID would be to clearly define their identity and access management requirements, especially around MFA, passwordless authentication, and user lifecycle management. I would also recommend conducting a proof of concept and validating integrations with experienced applications and infrastructure before full deployment. Overall, 1Kosmos BlockID is a strong solution for organizations looking to improve security, user experience, and identity management. I would rate this product an eight out of ten.