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
Anti-virus agent best practices for enVision 67Number of Views RSA SecurID Software Token Security Best Practices Guide for RSA Authentication Manager 8.x 183Number of Views Best practices for using Data Access Governance (DAG) in RSA Identity Governance & Lifecycle 60Number of Views Important Statement from RSA Regarding RSA SecurID Software Token Provisioning Best Practices 98Number of Views RSA response to Fox-IT report and Best Practices for RSA SecurID 27Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x