Security? I highly doubt that this can be an issue here and I cannot follow that logic of yours, to be honest.
Unfortunately, it seems, the opposite is true: Rooting is often one of the "checklist" kind of things that you see on many misled Android forums, and it seems that many users do it...just because.
And now they have a platform that is often significantly more vulnerable.
I completely understand why services would block this -- it fundamentally breaks the protections of the device. Many widely referenced vulnerabilities of Android only apply to rooted devices.
To see how an apparently trivial peripheral vulnerability can bring down an entire network, look at how Target was successfully attacked, step by step, from the outside in:
http://www.aorato.com/blog/untold-story-target-attack-step-s...
Don't get me wrong. All my Android devices are rooted, but I can see the logic behind the policy.
Indeed, it is. Do most corporate users run with admin accounts? Home users? In both cases, while the answer is unfortunately sometimes yet, it should always be no -- they are one confirmation away from significant peril.
> A rooted phone is not a stable environment for Barclays to run their software - it could have been changed in any number of ways
This means it could be less stable, but I don't see how it would affect the possibility of a "security breach". You are talking about two different kind of issues as if they are related. Could you clarify?
Ordinarily no one would care if a phone has been rooted or not. It's not important. But the point here is that allowing an app that has access to your bank account to run on a rooted device is assuming that the device was intentionally rooted by it's owner. For a bank that should be assuming far too much.
Besides, even if the malware really needed to "root" the device, it could just use the same process has RootCloak[1] to hide that fact.
There's no valid security explanation; the app must designed assuming it's running on an insecure system, because there's no way of knowing if the system isn't lying.
Local app exploit that messes with the bank app only will not be detectable by the bank app.
This seem highly unlikely. In fact, I've never heard of it. And, add to that the serious hurdles I had to go through to root all the phones I ever rooted (3).
Your statements amount, to me, to overblown risk.
The type of person who roots their phone is almost always going to be technologically experienced, or at least idea of dealing with money through technology.
On the other hand, though, Pingit is new technology and is actually scary for some people. When I enabled it in-branch, the advisor was surprised - even she said she'd never trust it!
I imagine that internally for Barclays it's a big move and a sensitive one. A security breach in the early stages would be catastrophic for the service and their brand. They need security, and for that they need stability.
A rooted phone is not a stable environment for Barclays to run their software - it could have been changed in any number of ways. It's a logical decision for them to increase stability by removing the wildcard platforms where they can't be sure what's going on.