3 ms·
The executive branch is the proper solution. If Congress mandates a solution, then it'd be like the VHS stuff all over again. Congress writes a thingy about VH
by dragontamer 8y ago
The executive branch is the proper solution.
If Congress mandates a solution, then it'd be like the VHS stuff all over again. Congress writes a thingy about VHS in the 1980s, and its completely irrelevant 10 years later. (If a law states that something with VHS is done a certain way, will it apply to DVDs or BluRays when they are invented 10 years later? Or to streaming media 20 years later??)
The Executive Branch is the one that actually runs the government. Legislative Branch / Congress sets policies, but shouldn't set solutions. Law goes out of date incredibly quickly.
Ex: If Congress says that RSA Tokens are to be used instead of SSNs, what happens if a better invention (ex: Google Titan) comes out? Furthermore, even if Congress writes a certain policy down (ex: Two Factor Authentication is necessary to protect bank accounts), the Executive Branch is still the ones who enforce the matter.
So in the case of Two Factor Authentication (legal requirement of banks to protect your bank account), the Executive Branch says that "3-personal questions + Password" counts as two-factor security in the USA. And that's why you have so many banks implementing "3-secret questions".
------------
So regardless, the job will come down to the Executive Branch.
- hannasanarion 8y agoSocial security isn't a piece of technology, it's a government program. How is it in any way like VHS?
- dragontamer 8y agoWhatever will replace SSNs will be a piece of technology. Ideally, something that uses public/private key encryption. There's a lot of things that use public/private keys however, or security tokens, or whatnot. Should it be a smartphone app? A hardware dongle? Etc. etc. If a hardware dongle, which one? As such, its the Executive Branch's job to research the various technologies, and implement a new standard to solve the online identity problem. ---------- For example, 18f (White House's crack website team) has the following: https://login.gov/ https://login.gov/ Github code here: https://github.com/18F/identity-idp https://github.com/18F/identity-idp If single-sign on were widely deployed across US Agencies (and tied to financial services / private sector banks), we'd be in a way better place. In any case, this is clearly the realm of the Executive Branch. Specifically 18f probably should continue to lead the effort, as they have been.
- freehunter 8y agoAll Congress has to do is pass a law saying "private companies are not allowed to store SSNs" and let those private companies figure out what the replacement is. Congress doesn't need to legislate the replacement technology.
- dragontamer 8y agoThat fundamentally misunderstands the problem. SSNs are fine and useful. They just shouldn't be the "password" to financial systems. When every damn bank uses "Whats your pin and SSN" to gain access to an account... that's the problem. The issue is that private companies use SSNs for security. There's nothing wrong in using SSNs as an identifier. The USA needs to start assuming that SSNs are public information, and to build security through other means. SSNs were never a secret number to be used for authentication / authorization purposes.
- tialaramex 8y ago> There's nothing wrong in using SSNs as an identifier. There's plenty wrong with this. SSNs were already a pretty bad identifier when they were invented and didn't get better. There's no check digit, so if you make any mistake at all it's probably a different person's valid SSN. Until relatively recently they were assigned both chronologically and geographically, so one digit error in SSN plus Address plus date of birth... Causes no red flags, it looks about right. Modern ones are randomly assigned, but it'll be decades before that's most people. Like most similar systems the US SSN also very explicitly says it isn't suitable for any purpose except numbering Social Security recipients. People you want numbers for may or may not have SSNs. Don't worry though, since they all look pretty similar and there's no check digit the people who don't have one long learned to give a bogus SSN, probably belonging to somebody else. Somebody you know probably does this today. What a useful "identifier".
- dragontamer 8y agoWhat you say is true, but is entirely tangential to the topic of Equifax breaches. > Don't worry though, since they all look pretty similar and there's no check digit the people who don't have one long learned to give a bogus SSN, probably belonging to somebody else. Its trivial to use US Government sources to do a name-check on the SSN, to ensure that you've got the right person. https://www.ssa.gov/employer/ssnv.htm https://www.ssa.gov/employer/ssnv.htm https://www.ssa.gov/cbsv/ https://www.ssa.gov/cbsv/ The latter costs money, but not much money in terms of doing business. --------- The fact remains: People use SSNs because the Social Security Administration is very good about keeping SSNs in order. Perhaps the number could be designed a bit better, but the system has been in use since the 1930s and there's no better number to use in the USA in most cases.
- jedberg 8y agoThe legislative solution would be to mandate a national ID with a cryptographic token, and then leave it up to the executive to define the implementation. Right now, even if they wanted to, the executive can't force a national ID.
- dragontamer 8y ago> The legislative solution would be to mandate a national ID with a cryptographic token, and then leave it up to the executive to define the implementation. That's still too specific. "national ID with a cryptographic token" means that OpenID / Paypal-based single-sign on logins are illegal. Yeah, writing laws is hard as heck, and Congress is NOT the experts in the field of cryptography / login security. So Congress will get it wrong if they even tried to write the law in that manner. Executive Branch CAN hire experts (ie: 18f, NIST, etc. etc.) to define best practices. As such, the proper legislative solution would be to mandate "industry best practices of identity protection, as defined by (Insert Agency Here, maybe NIST)".
- jonlucc 8y ago> "national ID with a cryptographic token" means that OpenID / Paypal-based single-sign on logins are illegal. Why? Why doesn't it just mean that there's a canonical government system that doesn't touch PayPal or OpenID that can be used for stuff that would currently be tied to your social security number?
- dragontamer 8y agoPayPal touches your SSN, as it is tied to your bank account. (Bank accounts require a "Individual Taxpayer Identification Number", which is the SSN for any citizen. Non-citizens get a different ID, but really its the TIN that is the cause of all of these security issues). So yes, really, the proposed wording would probably make Paypal illegal. You have a point on OpenID, but my overall point is that OpenID would probably be sufficient for most financial transactions on today's internet. OpenID is basically equivalent to Paypal's security model. Neither Paypal nor OpenID require 2-factor or security tokens. I think they're an optional feature. But in any case, the Paypal / OpenID model of identification (Paypal controlled website verifies password, and sends a token to the 3rd party website) would be sufficient for today's security. ---------------- Of course, none of this even touches upon Equifax. Equifax uses SSNs to identify people, and often without their knowledge or consent. Equifax is a service to the financial industry, to help keep tabs on individual's history. So the Paypal model will NOT work with Equifax's use case, because the individuals don't always know when they are being tracked. Maybe it'd have to be something to OAuth's model. In any case, I'm not an expert either. I just appreciate the difficulty of this problem.