RSA SecurID Access - Detailed Review

Frequently Asked Questions about RSA SecurID Access

What is RSA SecurID?

RSA SecurID is a two-factor authentication mechanism designed to protect sensitive data by adding an extra layer of security to the user’s login process. It combines something you know (a password or PIN) with something you have (an authenticator such as a hardware token or a software token on a smartphone).

How does RSA SecurID work?

RSA SecurID works through a unique code generation process. The authenticator (hardware or software token) generates a random, one-time-use code at regular intervals, typically every 60 seconds. The RSA SecurID server also generates and stores a similar code. To gain access, the user must enter their username, PIN, and the code displayed on their authenticator. If the entered code matches the code on the server, access is granted.

What are the different editions of RSA SecurID Access?

RSA SecurID Access comes in several editions, including the Base Edition, Enterprise Edition, and Premium Edition. Each edition offers different features and pricing tiers based on the number of users. For example, the Base Edition and Enterprise Edition have varying subscription licenses for different user counts, with the Enterprise Edition offering more advanced features.

What are some common vulnerabilities of RSA SecurID?

Despite its security benefits, RSA SecurID faces several vulnerabilities. These include the reliance on physical tokens, which can be lost or stolen; predictable random number generation, which could allow sophisticated attackers to bypass the security; man-in-the-middle attacks, where an attacker intercepts communication between the user and the server; and phishing attacks, where users are tricked into divulging their PINs and token codes.

How can RSA SecurID be integrated with other systems?

RSA SecurID can be integrated with other systems using protocols like RADIUS. To configure RSA SecurID with a RADIUS client, you need to set up a RADIUS client in the RSA SecurID Access Console and configure the corresponding agent host record in the Authentication Manager Security Console. This allows for central user management and the application of specific RADIUS profiles to users.

What steps can be taken to protect RSA SecurID from attacks?

To protect RSA SecurID deployments, it is recommended to secure the Authentication Manager database, ensure strong policies regarding exported data, monitor Authentication Manager logs for unusual activity, and educate users and help desks on best practices to avoid social engineering attacks such as phishing. Following RSA SecurID Security Best Practices is crucial for strengthening the security of the system.

Can RSA SecurID be compromised by external attacks?

Compromising an RSA SecurID deployment requires an attacker to possess multiple pieces of information, including details about the token, the customer, individual users, and their PINs. Some of this information is controlled only by the customer and not held by RSA. Successful attacks often involve a combination of technical and social engineering techniques.

How does RSA SecurID protect against simultaneous login attempts?

RSA SecurID authentication servers are designed to prevent simultaneous login attempts by declining both authentication requests if two valid credentials are presented within a given time frame. This helps prevent password sniffing and other forms of simultaneous login attacks.

What is the role of RSA Authentication Manager in RSA SecurID?

RSA Authentication Manager plays a crucial role in RSA SecurID by verifying the authentication requests. It manages the tokens, user credentials, and the generation and validation of the one-time passwords. The manager also provides tools for monitoring and managing the authentication process, including log monitoring and user permission settings.

How does RSA SecurID handle token loss or theft?

If a physical token is lost or stolen, it is essential to report the incident immediately to the system administrators. They can then take steps to deactivate the lost token and issue a new one to the user. This prevents unauthorized access, as the attacker would need both the token and the user’s PIN to gain access.

What are the best practices for using RSA SecurID?

Best practices include securing the Authentication Manager database, monitoring logs for unusual activity, educating users about social engineering attacks, and ensuring strong policies regarding exported data. Regularly reviewing and updating the security settings and following RSA’s security guidelines can help strengthen the protection of RSA SecurID deployments.