The iPhone security model is broken ... can it be fixed?
Summary: User data is the new gold rush, and it's so easy to find and mine.
I like my iPhone. A lot. But I've not gotten to the point where I feel that the security model that Apple chose to implement in iOS is broken, and it's hard to see how it can be fixed in any useful or meaningful way.
How is the security model broken? Well, it's broken because the apps you install onto your iDevices are capable of accessing the user's address book and sending that data back to the company servers without you knowing that it's going on. Mobile social network Path was caught doing just that, and I'm sure that it's not the only one that's been up to this trick. User data is the new gold rush, and it's so easy to find and mine.
Note: Mac OS X offers developers easy access to the address book, and Apple hasn't done anything about this since the issue surfaced in 2006.
Now I'm going to assume for a moment that there are legitimate reasons for access user's address books and copying them, but what cannot be justified is doing this without user consent (and by consent I don't mean a small snippet of legalese buried in a ocean of legalese). Harvesting data without clearly informing the user of what's going to be done and what will happen to that data is at best a very bad business practice, and at worse it's malware-like behavior and a massive breach of trust.
So what should happen? Well, I have several ideas, but I must admit that I'm not in love any of them.
- Apple could ban apps that access the address book. This would be easy to do as Apple controls what APIs developers can use, and checks for developers breaking the rules. While Apple could do this easily, but it's not an ideal situation because some apps could have legitimate reasons for accessing this data.
- Apple could restrict how much data apps can access. Problem with this is that it doesn't give users much control. It's too blackbox and too opaque.
- Apple could put policies in place to force apps to use encryption when transmitting the data, but personally I'm more concerned about what happens to that data after transmission than during transmission.
- Apple could put a mechanism in place similar to that for Locations Services where apps would have to ask permission and users could revoke permission from the app later. Of all the options this seems like he best, but it does have a danger in that it could eventually mean that iOS users are faced with endless dialog boxes and a torrent of questions each time they install apps. This sort of security hasn't worked on any platform previously, and I'm not convinced that it would work on iOS.
As I said, none of these solutions are ideal, but in light of recent developments, it's clear that Apple can't just allow apps to have unfettered access to data stored on iOS devices. We're already sliding down a very slippery slope.
The best option in my opinion is to put the users in charge, but I see there being a giant gulf between giving the users choice, and the users making an informed choice. On platforms like Windows (and even on Mac) throwing endless dialog boxes at users quickly creates a fatigue where people don't really read (or even pay attention to) the information being put in front of them. Security turns from being a useful feature into something that's just standing between them and doing what they want.
These aren't new problems, but they're exaggerated by post-PC devices. In the PC world there's a huge amount of diversity when it comes to software. People could have their contacts in one (or many) of dozens of places (Outlook, Thunderbird, in the cloud, in a Notepad file ...), but on a device like the iPhone there's one place ... the Contacts app. Also, as our devices become more personal, they will contain more and more personal data (names, emails addresses, phone numbers, addresses, and so on).
All this makes the data easy pickings ... and this data is valuable stuff, so there are people who will grab it.
The move to the post-PC world is putting out personal data at risk, and no one has come up with a solution that protects us from the bad guys.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
I like Android's model in concept, but in practice I prefer Apple's. The problem with Android's model is it requires up front permissions. This is great in concept, as it gives the user an opportunity to avoid installing software for which they're not comfortable with permissions, but in practice, it's sometimes difficult to understand why the app needs certain permissions before you've actually used it. This is in part because sometimes the app descriptions are lacking, or it's simply complex enough that the user doesn't understand why it's needed or see the benefit. The end result is either users walking away from a good app or users just starting to blindly accept apps regardless of permissions required. Either way, it's a problem.
RE: The iPhone security model is broken ... can it be fixed?
On the one hand, I guess it's up to me to do a little work and figure it out - but on the other, I didn't feel like just then, so I cancelled the install.
But I'd rather be told and have the option to exercise if I can, than not to know at all.
Developer's good practices for iOS and Android
@piousmonk
RE: The iPhone security model is broken ... can it be fixed?
I don't disagree, but in practice, too often descriptions of what the app does, let alone why it needs certain permissions, is vague at best. In the case of malicious apps, I'm sure this is intentional. In the case of legit apps, it could simply be the case of the developer not being well suited for conveying technical details to a non-technical user. But either way, the end result is the same, and until addressed, many users will fall into one of the two camps I mentioned.
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
Pedantically, I'd just like to say that a spell check won't find any error with that sentence.
RE: The iPhone security model is broken ... can it be fixed?
I thought that spell checks were used by Harry Potter. Perhaps you mean a spelling checker?
RE: The iPhone security model is broken ... can it be fixed?
Don't think my "splitting of hairs" is any justification for inaction on Apple's part - it's actually quite the reverse: Apple CAN fix this problem, and now is the time to do so.
RE: The iPhone security model is broken ... can it be fixed?
"But I???ve not gotten to the point" which I believe should have said "now". Sort of changes the premise of the whole piece at the start.
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
Permission Flag
That's a great idea! When large amounts of users start flagging an app it would force honest developers to start explaining why the app accesses what it does.
RE: The iPhone security model is broken ... can it be fixed?
There IS some value in letting apps scan all my contacts (i.e. matching friends on Game Centre, LinkedIn and equivalents) - but this should be something that always prompts the user, and I'd say that accessing this API should require a higher level of certificate (which would trigger Apple into looking closely at the firm / what it does with the data).
Even better would be all the major vendors collaborating on some kind of standard for anonymised contact matching that worked by transmitting hashed contact data only.
I can't think of any legitimate situation where a server should have the email address and telephone numbers of my contacts.
but this should be something that always prompts the user
RE: The iPhone security model is broken ... can it be fixed?
I tend to come down on the side of user responsibility but have to admit that there are problems with this approach, not the least of which is the fact that insecure devices affect more that just the owner of that device. Zombies and botnets leap to mind. It is almost a public health metaphor. If you are allowed the freedom to forgo vaccinations, then to what extent are you responsible for communicable diseases that you might unknowingly spread?
It is a complex issue and way beyond a single vendor's control.
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
RE: The iPhone security model is broken ... can it be fixed?
I believe the EU is looking at this structure.