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 Governance & Lifecycle Recipes: Varonis - Best Practices for Planning and Implementing NTFS Permissions 29Number of Views Best practices for RSA Identity Governance & Lifecycle deployments 29Number of Views RSA Governance & Lifecycle Varonis Implementation Blueprint 29Number of Views Anti-virus agent best practices for enVision 67Number of Views RSA SecurID Software Token Security Best Practices Guide for RSA Authentication Manager 8.x 203Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process