RSA response to Fox-IT report and Best Practices for RSA SecurID
Originally Published: 2020-01-14
Last Modified: 2023-10-06
Article Number
Applies To
CVE Identifier(s)
Article Summary
Resolution
- The adversary must have access to a software token XML file.
- The file must have been created without a password.
Important Statement from RSA Regarding RSA SecurID Software Token Provisioning Best Practices
Disclaimer
Related Articles
RSA SecurID Authentication Engine Security Best Practices Guide (Japanese) 79Number of Views RSA SecurID Software Token Security Best Practices Guide for RSA Authentication Manager 8.x 210Number of Views Best practices for using Data Access Governance (DAG) in RSA Identity Governance & Lifecycle 100Number of Views Best practices for RSA Authentication Manager 8.x 395Number of Views Best Practices to Mitigate Password-Spraying Attacks 384Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?