According to a protected disclosure filed with the Office of Special Counsel, Borges told the Government Accountability Project that DOGE officials working at Social Security created a “live copy” of the country’s Social Security records in a separate cloud environment that sidestepped usual security checks.
The group says those lapses put the Social Security information of more than 300 million Americans at risk.
They actually need to publicly release everyone’s SSNs so that they can’t be used for authentication anymore, which they never should have been
I’ve been saying this for literal years now. They should release a publicly searchable database of every single SSN, name, and DOB. Force organizations to stop using those as a form of ID, because they’re not secure and never have been.
Give it like a year of lead time. Like announce “March 1 2027, we’ll post the database” and then that gives institutions a full year to figure something new out.
Why not photos too? jfc.
SSNs are generally considered public information but how the SSN is linked to other information is usually the more difficult bit to find and it’s generally pay-walled. (Any jackass with a business license and a credit card can usually buy background check information for ‘hiring’.)
But no, it shouldn’t be solely used for authentication. That is just dumb. However, it can be used as part of a larger verification and validation scheme while building authentication/authorization profiles. In most systems that I have seen that use full or partial SSNs, it is always linked to several other identifiers that need to match.
They are definitely not. People consider it increased risk for identity theft if they hear their SSN was stolen and you just cited how people are still using them in part for authentication. They need to be completely useless for authentication
I am making a slightly different point and have a bias to this perspective: https://www.legis.iowa.gov/docs/publications/SD/19230.pdf
I am saying that an SSN can be part of a larger validation scheme, not the only key to the castle. Specifically for government sites, SSNs can be linked to IRS data to verify places of last residence. A person generally needs to verify multiple items that are referenced by the SSN before basic authentication can be established and set by the user. (This is part of the full Authentication, Authorization and Access Control triad.)
An SSN is just a broad level identifier. If you look at many laws around the release of SSNs, the redaction is usually in place to prevent the linking of different documents and other data points.
If I released my SSN in this chat, I could be fully doxxed in a matter of seconds. It’s mainly because there are many legal systems in place that use an SSN as a primary key, of sorts. (It’s a bit more than that, as SSNs can be duplicated in some circumstances.)
So to say, at a high level, an SSN is considered private is absolutely correct. However, it’s so easily referenced and obtainable it really isn’t fully private either.
If I was to generate a full list of every possible SSN in the US (which I have done, multiple times), that list is effectively useless to anyone who obtains a copy of it. So, by itself, an SSN is effectively public.
000-00-0002