The cloud storage service accessed by the threat actor is physically separate from our production environment. It likely did already before they declared victory in September 2022, which also sheds a bad light on them. Note also how LastPass avoids mentioning when this “target another employee” happened. Yes, this interpretation is far less favorable of LastPass, which is why they likely try to avoid it. And because of that failure people’s data is now gone. So the more correct interpretation of events is: we do not have a new breach now, LastPass rather failed to contain the August 2022 breach. But using information gained in the initial access in order to access more assets is actually a typical technique used by threat actors. LastPass is trying to present the August 2022 incident and the data leak now as two separate events. While no customer data was accessed during the August 2022 incident, some source code and technical information were stolen from our development environment and used to target another employee, obtaining credentials and keys which were used to access and decrypt some storage volumes within the cloud-based storage service. We’ll soon see how transparent they really are in their statement. LastPass is actually required by US law to immediately disclose a data breach. In fact, this has little to do with any commitment.
#Matching login lastpass update
In keeping with our commitment to transparency, we want to provide you with an update regarding our ongoing investigation. Let’s start with the very first paragraph: As I know that not everyone can see through all of it, I thought that I would pick out a bunch of sentences from this statement and give some context that LastPass didn’t want to mention.
#Matching login lastpass full
Their statement is also full of omissions, half-truths and outright lies. LastPass likely could have prevented this if they were more concerned about keeping their users secure than about saving their face.
Security professionals weren’t amused, this holiday season became a very busy time for them. As people have speculated, this timing was likely not coincidental but rather intentional to keep the news coverage low.
Right before the holiday season, LastPass published an update on their breach.
0 kommentar(er)
