this post was submitted on 30 Mar 2024
294 points (98.7% liked)
Technology
59429 readers
3079 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Social Security numbers should really not be considered secret data. Too many places have leaked them.
Maybe -- maybe -- they're okay for uniquely-identifying someone, but they're a really bad way to authenticate someone.
I mean, this breach alone -- if these are Americans -- is something like 20% of the US population.
You can't rely on something as authentication data if 20% of the population has irrevocable credentials that are floating around.
Just because way too many sites have a security that more or less non-existent, this should not be an excuse. Every breach should be severely punished. The only way corporations learn to take customer data safety seriously is through their wallets.
As long as customer data safety is just a cost factor, and penalties are just a mild slap on the wrist, there is no incentive to consider this as "just another cost of running business issue".
I heard a security researcher say something like that a couple decades ago I think. The solution isn't to "safeguard SSN's", it's to make them pointless to have. Make it so you can't do anything with them.
Like you point out: this one breach alone could be 1/4 of the us population.
For serious, emergency recovery, what I'd kind of like is some kind of service that performs physical validation of identity. Like, okay, say I lose my credentials to get into a bank account. So the bank gives me a recovery number, and I go down to the police station or something like that, and they do an identity check as part of that and sign off that you're who you say you are. Then if you're an identity thief, you're liable to get arrested right there. Charge a fee to cover the costs. Have a federal government server have to cryptographically sign that they're doing an identity validation so that the local cops can't silently sign off on someone else as being you. That should only come up if you've lost your credentials to something serious and need to get access again.
As an intermediate form of access, I suppose 2FA, though I'm not totally thrilled about having my keystore on a device that's network-connected, like a phone or computer, and has software getting put on it. Would rather have a physical USB-C dongle acting as a keystore with a small screen to identify the contents of a transaction being performed, and a physical "approve" button on the dongle. Plug that into a computer or smartphone or whatever. Maybe have different dongles for more- and less-sensitive stuff -- one for credit card payments that you carry around, one for insurance or something that you don't. Use pubkey authentication, not this shared-secret SSN stuff, so that if someone gets a company's database, it's useless in terms of letting them authenticate as you.