Pros and cons of mobile tokens in authentication

Last updated: 21 March 2014

I recently discussed the future of the online banking industry and how the FFEIC should shape its next set of guidelines to ensure the safety of both banks and their customers in the years ahead. However, one area which I didn’t explore in that post is the mobile platform, and the role it has to play in the evolution of authentication. Symantec blogger Mike Jones recently put his neck on the line, saying that he believed mobile tokens were the future of the authentication industry – here are my thoughts on that.

I am a firm believer in convenience – in my eyes, the more convenient a security solution is, the more likely it is to be used, and this can only possibly be a good thing. And there is no better example of this than my smartphone. I have dozens of apps available at my fingertips and because they are so convenient to access, I use them for everything I possibly can. While we in the security space have an elevated awareness of security risks, your average consumer doesn’t even consider security on their smartphone, which is another argument for making security convenient.

Using this reasoning, one could argue that putting an authentication token on a mobile should represent the logical future of our industry. However, while mobile tokens are one option for multi-factor authentication, it is important to realize that the hardware components offer some basic benefits that phones do not – at least from a security perspective.

A mobile phone is a relatively new platform for commercial activity.  Its immaturity and the fact that it is rarely used for ‘high value’ activity (e.g. transactions or sharing of sensitive data) means that the phone as a platform has not been an attractive target for hackers.  But it has an operating system, and is potentially vulnerable to attack like any other.  If it were attacked, thanks to its persistent connectivity, any security tokens stored on that platform would be open to compromise from a distance.  A hardware token, isolated from any network, is not vulnerable to such an attack.

Hardware tokens are also self-contained – they are usually sealed at the factory, cannot be tampered with, and do not perform any other function.  They are simple, which seems limiting but, in fact, is perfect for their use.  Because I cannot manipulate the sealed environment of the hardware device, I cannot break it unintentionally (unless I physically break the device).  It is immune to software conflicts, version compliance and all manner of other issues which could affect a software platform.

Mobile tokens afford a level of convenience and cost-effectiveness that are perfectly suited to lower-end security needs, and can also be updated in the field.  However, where higher security is needed, hardware tokens still have their place.

In short, there is no one type of authentication device or software that will ever be truly universal, and this in itself brings a measure of security. With a more diverse selection of solutions on the market, those who seek to compromise them will be faced with an even greater challenge.

One thought on “Pros and cons of mobile tokens in authentication

  1. Adam,
    I quite agree with your excellent analysis. Smartphones are fantastic devices and a great way for companies to offer easily accessible ways to increase end-user security – like offering the possibility to add multi-factor authentication option for your webmail login etc.

    All modern operating systems come with at least rudimentary firewall enabled on first-boot, but there are very few Mobile operating systems that even offer firewalling possibilities out of the box. Trojans and other worms already exist in the wild and are coming up increasingly more innovating attack vectors.

    Perhaps one day the smartphones are ready for high-end transaction security, but I really wouldn’t trust my smartphone with my bank authenticator at the moment.

    The smartphone security market and the OS’es themselves are not mature enough.

Leave a Reply

Your email address will not be published. Required fields are marked *