Customers and business partners alike will have questions and concerns about how any attack could last for so long before it was detected and action was taken. LastPass has not shared details of who it believes to have been responsible - perhaps because it simply does not know.
While it is clearly good news to hear that customer data can not been compromised, there are still lots of questions to be answered. While the method used for the initial endpoint compromise is inconclusive, the threat actor utilized their persistent access to impersonate the developer once the developer had successfully authenticated using multi-factor authentication.Īlthough the threat actor was able to access the Development environment, our system design and controls prevented the threat actor from accessing any customer data or encrypted password vaults. Our investigation determined that the threat actor gained access to the Development environment using a developer’s compromised endpoint. We can also confirm that there is no evidence that this incident involved any access to customer data or encrypted password vaults". There is no evidence of any threat actor activity beyond the established timeline. During this timeframe, the LastPass security team detected the threat actor’s activity and then contained the incident. Our investigation revealed that the threat actor's activity was limited to a four-day period in August 2022. In an update to the blog post from the end of August, LastPass CEO Karim Toubba says: " We have completed the investigation and forensics process in partnership with Mandiant.
Microsoft issues patch for serious security vulnerability affecting everything from Windows 7 to Windows 11.Uber suffers 'cybersecurity incident' with hackers gaining access to internal systems and vulnerability reports.Microsoft Teams for Windows, macOS and Linux insecurely stores authentication tokens in unprotected cleartext - and a fix is NOT in the pipeline.
0 kommentar(er)
