RSA Identity Governance and Lifecycle could improve out-of-the-box customization.

The solution has to adapt better because all the other competitors have their own SaaS solutions which have their own multi-tenant functions with ease of integration with the enterprise.

Every connector that you have in the product needs to be custom-built, so there are not a lot of standard connectors available in the product, because of which there are a lot of hidden consultancy costs. Everything in the tool needs to be developed by people who are experts in RSA products, and there is nothing that people who work in-house at a company can do. The aforementioned areas of concern can be considered for improvement in the solution.

This product is missing a lot of features which other competitors are providing. One of the key features that are missing right now is risk scoring. Additionally, there is not much scope for customization - everything is hard-coded and predefined, so it does not allow the developers to make many modifications.

• User interface
• Workflow
• More connectors

When the 7.x release of Authentication Manager came out, the administrative interface and user interface (for self-provision) relied on the same TCP port even though the URLs were slightly different. We did not want the same port which administrators used open to the public internally, we saw that as a security concern in the fundamental way this system operated. We were excited that the self-provision feature was now built into the box but disappointed at the implementation. We hadn’t planned on standing up a separate web server in the DMZ for the purpose of brokering the self-provision process since 99% of our users were onsite, meaning they could get their tokens prior to leaving the office. When I questioned RSA about this matter, their response was to utilize a Web Application Firewall to block access to the specific administrative URL. We thought this was a bit too involved especially now that we’d need to implement a WAF, so we changed the policy and discontinued the self-provisioning option for users. While consulting on the product, I don’t come across a lot of companies using this feature so it’s not a deal breaker for most, but it’s certainly a nice to have if you would like to offload some of the administrative overhead as the self-provision feature also allows users to reset their PIN and perform some maintenance tasks.

It could be a little more flexible with the installation of the product. Only virtual Linux environements for hardware appliances are allowed for a deployment.

Better integration with other solutions such as Oracle Database is needed. Currently, some SQL databases cannot be integrated with RSA.

Technical support in Pakistan can be improved.

The software tokens are a huge improvement over hardware tokens but it could be cheaper.

Application and appliance stability needs improvement.