Oh yea, agree it’s a dumb move. This should be on-prem data IMO.
Comment on The entire Social Security database was uploaded on a random cloud server, Whistle-Blower Says
jacksilver@lemmy.world 2 weeks agoI agree that “random server” is a bad choice of words, but do want to add additional information context as the concern isn’t necessarily unwarranted. Another qoute from the article:
“I have determined the business need is higher than the security risk associated with this implementation and I accept all risks,” wrote Aram Moghaddassi, who worked at two of Mr. Musk’s companies, X and Neuralink, before becoming Social Security’s chief information officer, in a July 15 memo.
Its also sounds like they did spin up a new database with limited security/oversight to “move” faster. Why that’s worrisome is they aren’t denying there is a risk or lack of security, they are just saying it’s justified.
fmstrat@lemmy.nowsci.com 2 weeks ago
nieceandtows@programming.dev 2 weeks ago
Could you please explain like I’m 10?
jacksilver@lemmy.world 2 weeks ago
The SSA stores a lot of sensitive data. Normally with sensitive data you want to be very careful with who can access it and how.
What is potentially worrisome in this situation is it seems like the SSA is taking on the “move fast and break things” attitude of Silicon Valley.
More technically, most government agencies use AWS and Azure (cloud providers) to host data. So spinning up a new server isn’t inherently bad. However, creating a new server that is secure and has the correct access controls (user permissions regarding who can see/change content) can be challenging. The whistle blower believes they are not doing this right, and it sounds like the head of the SSA isn’t disagreeing, just saying he thinks the risk is worth it.
nieceandtows@programming.dev 2 weeks ago
That makes sense, thanks for the explanation