3 ms·
I'm of the opinion that the accelerant for this dumpster fire is that companies are allowed to define "two-factor authentication". Security questions? Nope. "Ch
by mikestew 9y ago
I'm of the opinion that the accelerant for this dumpster fire is that companies are allowed to define "two-factor authentication". Security questions? Nope. "Choose the picture"? Nope. SMS? Again, close but nope. But because we sadly let just about anything beyond UID/PWD under the 2FA tent, that's what we ended up with.
The article identifies 2012 as when the mess started. Oh, no, it goes back at least five years prior. I worked at a company implementing biometrics as an authentication factor. The Feds had just mandated 2FA for banks and the like. Man, we're all going to be rich soon! Nope, I never made a dime off those options, and last I checked the company has pivoted twice and may not even be in business anymore. What happened, we were practically handed a money printing press? What happened was that banks and the like were allowed to use those half-assed implementations like security questions. Yes, security questions counted as 2FA. The "choose a picture" was allowed. So our relatively expensive system was rejected in favor of the less expensive, half-assed systems. And ten years later, here we are, with a bunch of security questions that can be answered by anyone you've friended on Facebook, and SMS that can be social-engineered.
From where I stand, it comes down to money (doesn't it always?). RSA fobs, biometric systems, they all cost money and have high support costs. Because that's what security is: it costs money, and it adds inconvenience. Well, we can't have that, so we'll implement a JS library we found on github, reset passwords over the phone for anyone that says the right things, and we save money.