SoylentNews is people
SoylentNews
Intruders Gain Access to User Data in LastPass Incident
The password manager says credentials safely encrypted, confirms link to August attack:
Intruders broke into a third-party cloud storage service LastPass shares with affiliate company GoTo and gained access to "certain elements" of customers' information, the pair have confirmed.
LastPass did not define what it meant by "certain elements," saying it was unsure what data was looked at: "We are working diligently to understand the scope of the incident and identify what specific information has been accessed this morning."
[...] It did maintain, however, that services were unaffected and that customers' passwords remained "safely encrypted" – without ruling out that some of the data was stolen. The company is known to use a one-way salted hash for master passwords, with a fuller description in this technical whitepaper. The master passwords are used to lock users' password vaults, where their logins for various websites etc. can be stored, with the passphrase only ever entered by the user on their browser or app and not sent to or stored by LastPass.
Users who lose their master passwords can lose access to their vaults, although there are some recovery options.
LastPass Security Breach Worse Than Initially Reported
LastPass Security Breach Worse Than Initially Reported:
[...] In a blog post dated November 30th, LastPass CEO Karim Toubba informed customers that “an unauthorized party ... was able to gain access to certain elements of our customer's information." The CEO didn't specify what type of information was compromised in the blog post. However, he assured customers that their passwords were safe as the company's Zero Knowledge architecture protects them.
The Zero Knowledge technology employed by LastPass means that no plain-text passwords are stored on company servers and that only customers can access their unencrypted passwords.
[...] Toubba explained that while customer data was not accessed during the August attack, information that the hackers obtained was subsequently used to get customer info. The CEO went on to assure his client base that the company is working hard to understand the full scope of the breach and is deploying enhanced security measures and closely monitoring for any further attacks.
The admission is surely an embarrassment for LastPass, but it’s not the first time in recent memory the company has suffered a massive security breach. Less than a year ago, the company suffered a brute-force attack from hackers, causing a slew of unauthorized login attempt notifications to go out to many of its customers.
(Score: 2) by Sjolfr on Sunday December 04 2022, @07:54PM
From my experience failing to do so, at some point in the change process, becomes an inevitability especially when you're making changes all alone, doing a lot of changes, and not having the money/resources for multiple environments to test changes and eventually push changes in to production. This challenge grows exponentially when you are also maintaining multiple levels of the stack; hardware, OS, DB, clustering, networking, application, etc.. In complex environments even the firmware/BIOS levels are points of failure.
A lot of folks take these things for granted because, in and of themselves, they aren't that tough to manage. Just remember that a systems' complexity grows at a rate greater than the sum of the of its' parts. It's even more so when updates and maintenance have fallen behind. Don't even get me started on that topic.
Then, add on the expectation that people have regarding documenting and communicating all the changes and all the challenges and all the failures to keep things perfect and you have, what some would say, is a perfect storm of "why the fuck am I doing this". Spending 30 minutes to write some update communications isn't that hard untill you've spent 2 days making changes and are tired as hell. It's the breeding ground for memes like "No I will not fix your computer" and "Leave me alone or I will turn you in to a very small shell script". For me it was a part of the cost of working in the basement and making sure core infrastructure just worked instead of sitting in useless meetings.
Yup, frustrating and worth voicing ... but cut some slack too, no one is perfect.