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
RSA SecurID Authentication Engine Security Best Practices Guide (Japanese) 71Number of Views Best practices for RSA Identity Governance & Lifecycle deployments 27Number of Views RSA SecurID Software Token Security Best Practices Guide for RSA Authentication Manager 8.x 180Number of Views Anti-virus agent best practices for enVision 67Number of Views RSA response to Fox-IT report and Best Practices for RSA SecurID 27Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x