Google has added two-step authentication to a variety of its accounts, such as the basic Google account and its Gmail services. While this is an extra security step in the right direction, it is not as secure as people may think.
Many users will simply ignore this extra layer of annoyance, as they see it, and some of those who use it will not think through the process and just accept it as a cast iron security improvement.
Two-factor authentication is based on the principle that you have your primary sign-on user name and a password (the first factor). Following this step, another password, known as a verification code, dispatched by the service supplier through your mobile phone SMS service (the second factor), must be entered. The process is summed up in the phrase: something you know (your password) and something you have (your mobile phone).
The problem is that it does not act as a safeguard against “man in the middle” phishing scams where spam emails contain links to fake sites, usually spoofed banking sites. It also does not allow for the march of technology.
In its original concept, the two-step method relied on the fact that users would browse the web from their laptop or desktop PC. Sending a validation code to an independent device – the phone – meant that online hackers could not intercept the code in transit. It also meant that a thief would have to have access both to the user’s computer and their phone. The phone was known as an out-of-band device.
Today, it is more likely that the mobile browsing device and the phone are one in the same device, or in-band, which weakens two-factor SMS systems. Although the remote hacker is still blocked, the thief who steals, or finds, a phone has effective access to both devices. The extra layer of security becomes a chocolate fireguard – a sight to behold but actually useless.
Owners of iPhone, Android and BlackBerry smartphones may even have downloaded an app which automatically generates the validation code, further aiding the thief.
Graham Cluley, senior technology consultant at Sophos, agreed: “Yes, it’s a good step from Google… but if it’s your phone that you’re using to access your web-based accounts, it’s not going to be that much help. Many users use their smartphone as a browser and, when asked for a number, without thinking, will supply the number of the very device they are browsing from rather than a secondary phone.”
The problem does not stop there. Once in possession of the phone, the thief can cause so many other problems for the careless or luckless user.
“Mind you, many people don’t have their smartphones protected by a PIN code,” Cluley added, “even though they have them automatically remember all of their web-based passwords, so there are lots of problems in this area.”
Another danger is in the increasing number of Trojan horse apps with malicious code hidden inside. This is mainly a concern for smartphones that have unregulated download marketplaces. It would be simple to write a Trojan that allows a remote hacker to piggy-back on a user’s sessions.
This would mean that the hacker would be alerted once the validation is complete and would then be able to covertly insert their own transactions into the session.
Barclays, and some other banks, provide online customers with a validation device that requires a credit card to be inserted and PINned to generate a passcode. The user has their own bank-issued ID, and the separately-created validation code adds a true layer of added security.
The token-generating device still has its failings but is less vulnerable than SMS-based two-step security.
Google gives the impression that its latest move is a large step towards safeguarding user accounts but that’s just the marketing hype. Times change, and security systems have to respond to this march. Simple locks in the middle ages gradually evolved into the tumbler locks seen everywhere today, the increasing number of PIN-coded electronic locks, and the future use of palmprint or fingerprint locks.
Google is to be applauded for making its accounts a little more secure. It has shown that, like Facebook, it is taking the issue seriously, though Facebook has a lot to learn in overall security. But let’s not allow all this door-locking to go to our heads. More secure is not the same as strongly secured and the days of phone-based authentication started to fade when the first browser appeared on a mobile phone.
Suspended prison sentence for Craig Wright for “flagrant breach” of court order, after his false…
Cash-strapped south American country agrees to sell or discontinue its national Bitcoin wallet after signing…
Google's change will allow advertisers to track customers' digital “fingerprints”, but UK data protection watchdog…
Welcome to Silicon In Focus Podcast: Tech in 2025! Join Steven Webb, UK Chief Technology…
European Commission publishes preliminary instructions to Apple on how to open up iOS to rivals,…
San Francisco jury finds Nima Momeni guilty of second-degree murder of Cash App founder Bob…
View Comments
good article. we are in this business and what google has rolled out is good enough but still not up to mark for today's and future attacks.
we need to have strong authentication that includes mutual authentication, device profiling, digital signatures, and geo location to give solid multi layered authentication.
we are coming up with something for Google Apps with 4 folds of protection. If you are interested then once it is live then we will gld to you and get your feedback.
Once again, great artcile.
regards,
vikram
I just implemented Google's two-step authentication for my phone, desktops, and notebooks. I suspect a vast majority of users will find it too complex and will either simply not use it or attempt setup, get frustrated and abandon it. Regardless, as Mr. Doyle says it is a step in the right direction as was Google's HTTPS "incentive" way back when.
Now if we could just get them to jump on board the "DO NOT TRACK" bandwagon !