- If your AI-generated code becomes faulty, who faces the most liability exposure?
- These discoutned earbuds deliver audio so high quality, you'll forget they're mid-range
- This Galaxy Watch is one of my top smartwatches for 2024 and it's received a huge discount
- One of my favorite Android smartwatches isn't from Google or OnePlus (and it's on sale)
- The Urgent Need for Data Minimization Standards
Why 2FA is failing and what should be done about it
Jack Wallen details a recent hack and why he believes one aspect of two-factor authentication is part of the problem.
Recently, my PayPal account was hacked, and it’s not the first or second time it’s happened. Fortunately, I have enough alerts set up to catch these things fairly quickly and act on them, but that doesn’t mean all is well. It’s not. I know it’s only a matter of time before another account is hacked.
SEE: Password breach: Why pop culture and passwords don’t mix (free PDF) (TechRepublic)
At this point, you’re probably thinking: “Why doesn’t he use a strong password and two-factor authentication on those accounts?” My answer: I do. All of my accounts are protected by passwords I couldn’t even think about memorizing, generated by a random password generator. Every account I use has 2FA enabled.
But not all 2FA setups are built the same. Let me explain: Of all the accounts I have — and, like you, they are many — only one configuration ever gets hacked. That configuration is 2FA sent over SMS. The accounts using 2FA via a password app like Authy or Google’s Authenticator have never had any problems.
But those SMS 2FA accounts have been nothing but problems. Why is this an issue? Simply put, when those 2FA codes are submitted via SMS text, they can be intercepted by the wrong people. If they already have your login credentials, the SMS text is the missing piece. Once they can intercept that code, they have the keys to the kingdom and lay waste to all that awaits them.
2FA via an authenticator app isn’t nearly as simple to crack. The problem is that a lot of institutions — especially banks — fail to see this vulnerability and continue going about the business of using an inferior security mechanism.
Believe it or not, I get it. Many organizations understand that getting users to enable 2FA is already a losing proposition. Most consumers don’t want to have to deal with the fiddly bits of requesting a code, waiting and then typing it. These are the same people still using “password123” for their login because they want everything to be as simple as possible.
Again, I understand: Life is already complicated enough without having to jump through even more hoops to do something that should be simple. But if you want to keep your data and money safe from those whose only task is to take it, strong passwords and added security are a must. It’s just so disheartening to know that many important institutions are still relying on less-than-secure technology.
An interesting and important position
The thing is, these organizations are in a rather interesting and important position. Say, for example, that Bank X decides it’s had enough of accounts being hacked and put in place two things: Strong password requirements and authenticator app-style 2FA. Any customer of that bank would have to implement those two things immediately. Yes, there would be a kerfuffle over the change, but eventually, everyone would accept it and move on with the improved security. Soon enough, the ritual of logging in to an account would become second nature and the complaints would cease.
Bank X would have successfully helped its customers understand that a couple of extra steps are worth the added security. By leveraging auth apps over SMS codes, the bank heightens the security of their organization and hopefully slows down the number of hacks that occur.
No, it’s not perfect, and even authy-type 2FA can be hacked, but they aren’t hacked at nearly the level of SMS 2FA. Knowing that, it never ceases to amaze me that so many websites and services still depend on SMS 2FA codes.
It’s time banks and other important services dropped SMS 2FA codes and migrated users to authorization app-type 2FA.
What should consumers do?
As far as consumers and users are concerned, if given the option between SMS and app-based 2FA, always go with the app-based option. By going that route, you don’t have to worry that your time-based 2FA code will be transmitted across the ether for someone to snoop on and use against you.
This should be instituted across the board with zero exceptions — at least until someone comes up with a more reliable, secure form of multi-factor authentication. Otherwise, accounts are going to continue to be hacked at an increasingly alarming rate.
To every bank, service and social networking site I would say this: It’s long past time for you to institute better security. Yes, there is a steeper learning curve to app-based 2FA codes, but most consumers and users would acclimate fairly quickly to the method if given a reason. And if any bank thinks a consumer is going to leave your institution because of an improved security policy, you’ve clearly never moved from one bank to another.
Subscribe to TechRepublic’s How To Make Tech Work on YouTube for all the latest tech advice for business pros from Jack Wallen.