Summary:
Providing remote users with self-service or emergency access is a risk/benefit trade-off that organizations must carefully consider and plan for. While self-service can provide a convenience to legitimate users, when implemented poorly, it also presents a potential channel of attack for would-be hackers. If your organization provides user services through the RSA Authentication Manager Self-Service Console, and if you make these services available on the public Internet, RSA recommends that you take the time to review recommended best practices found in the RSA Authentication Manager documentation.
For more information, please refer to this knowledge base article on the RSA Link website: 000035290 - Security Best Practices for RSA Authentication Manager Self-Service Console
For additional documentation, downloads, and more, visit the RSA SecurID Suite page on RSA Link.
EOPS Policy:
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.
Related Articles
Alternative to running RSA ACE/Server 5.1 patch installer for installation issues on hardened systems 4Number of Views RSA Governance & Lifecycle Varonis Implementation Blueprint 29Number of Views Best practices for RSA Identity Governance & Lifecycle deployments 29Number of Views Best Practices for backup and restoration of FIM configuration and secrets files 16Number of Views Best practices for installing, configuring and using the RSA MFA Agent 9.x for PAM/Unix 10Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide