Embedded Security for Mobile Applications . . . Way Cool!
I’m going to start this blog off by sounding like a corporate hack! Ok, I know, as a marketing person, I’m supposed to be kind of a corporate hack; but I don’t generally act like one, I certainly don’t dress like one, and I try not to sound like one. But today Entrust dropped a press release about a new product that enables organizations to embed security into their mobile applications. This is very cool! What this means, in a nut shell, is that developers of mobile applications can add security natively into the application – and while it doesn’t have to be – and in some instances they won’t want it to be, they’ll have the ability to make that security entirely transparent to the users.
So why is this important?
Well, here I’m going to digress. The other night I was in a pub with a couple of friends, sharing some stories over a pint or two, and there was a particularly attractive young woman beside me and she was clicking away on her Blackberry. . . she was twenty-something. . . and I fancied my chances! So I leaned over to her and asked her why she was using a Blackberry and not an iPhone. Ok, criticize me for my approach, but a part of me was genuinely interested. Interrupted, but not wanting to seem rude (it’s been a week and I’ve had time to reflect), she looked at me and answered my question: ”Because I have long nails – and it’s hard to use a touch screen with long nails!”
And with that, the price of Apple shares drop like a stone!
Now, perhaps it’s just me – I don’t have empirical data to back this up – but I figure if you can’t use a touch screen ‘cause your nails are too long, you’re not going to be keen about having to type a series of numbers (a one-time passcode) into some application so you can check your bank balance on that device. . . even if it has a keypad. And the idea of opening up a second app on the device, in addition to your banking app, just to have stronger security? Right!!
And this is the thing with security for consumer-facing financial applications: it needs to be “like. . . totally easy to use” – no disruption to the user – and it needs to be secure. “Bitchin’!”