There has been a need for aggressive development to modernize the product and align it with contemporary security requirements. While the rebranding has been a step forward, further enhancements are essential to meet the evolving demands of the market. It lacks features such as ActiveSync Exchange security, and it doesn't offer alternatives like password-less authentication via biometrics or patches. While Symantec mainly relies on traditional token-based or password-based methods, newer authentication methods are missing from its repertoire. Support services often lack promptness and depth of knowledge, leaving customers waiting for weeks to resolve issues. In the realm of multifactor authentication, swift resolution of problems is critical, as any slowdown or interruption can significantly impact operations. Urgent improvement is necessary to ensure that support responses are faster and more effective, aligning with the demands of MFA implementation.

This solution could be improved with risk-based authentication. I think that this product has everything that most customers are looking for, but modern technology has people looking for security tools with risk-based authentication, which they have a separate tool for. If they could integrate this, it would improve Symantec Advanced Authentication. They have to look at what's newly trending and how things are moving forward, and then adapt and adopt those features. 

Symantec's technical support should also be improved, in terms of response time. 

It would be nice to have some level of integration with a separate user store (i.e., Active Directory integration) such that the user name would stay the same across identity management platforms. I would like some level of integration with AD to avoid having two separate user stores. We only want one user store to maintain.

Arcot itself is based on a browser technology. This means that the office ID is effectively stored as a cookie in the browser. One of the things we have seen from our customers is that certain policies dictate that browser caches are cleared, which means cookies get deleted. This then means that some classes of users have to continuously download the office ID and go through the long process. So we would like to see that addressed, where the office ID becomes a bit more persistent or presented in a better way.

They definitely need to automate a few processes like the Wiley process. Even though Wiley is part of the CA group, it is not present in CA Advanced Authentication. I want that to be integrated, and not have to implement Wiley in-house during implementation.

Regarding database, they don't support some of the systems like ours. We had to get a workaround implementation for that. The CA consultant definitely helped us with that but still, we had to face a few issues while integrating it with FedEx.

Advanced Authentication talks about the Device ID. But how the device ID is captured, I want to know more about that. 

We are looking for something that can fingerprint a check. For example, if you lose your credit card, they can double-check your identity with your fingerprint.

We have seen quite a few issues with bugginess. It is indeed pretty buggy and we have had to install some fixes.

It needs faster implementation on the cloud for our customers.