RSA recently sent a notification to a limited number of customers, partners and vendors explaining that RSA identified unauthorized access to two RSA Microsoft email accounts that occurred between October 29, 2024 and November 3, 2024. The incident was fully contained on November 4, 2024 and is still being actively evaluated.
During the event, an external actor had visibility into two RSA employee’s email boxes and sent a malicious OneNote file link to some of the employee’s contacts. This unauthorized access has been removed and the OneNote file has been deleted.
RSA has informed the employees’ contacts of this incident. We take the protection and privacy of our customers, partners and vendors very seriously and will continue to update them if our analysis reveals any significant new information.
Aside from improper access to 2 e-mail accounts, which resulted from a phishing attack, after a thorough review over the past week, RSA has no indication of any access to other RSA systems and services. RSA continues to work with our internal security team, Security Operations Center and Microsoft to monitor for and prevent unauthorized use of our email system.
For further information, please contact security@rsa.com.
Related Articles
How to resize the Oracle database alert.log for RSA Identity Governance & Lifecycle 106Number of Views Connecting to database gives error: "sslv3 alert handshake failure" 96Number of Views Disk Usage Threshold Alert 9Number of Views Email and log file timestamps are incorrect in RSA Identity Governance & Lifecycle 70Number of Views RSA SDK for iOS and Android Patch Release - Now Available 16Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…