Perimeter
4/22/2011
01:21 PM
Rob Enderle
Rob Enderle
Commentary
50%
50%

What's Good About iPhone's Location Tracking

The iPhone tracking disclosure this week showcases an unfortunate tendency for device manufacturers to focus excessively on their needs and forget those of their users

Over the past week there has been a lot of time spent by seemingly outraged people finding that the iPhone tracks and records the user's location. The problem, as I see it, is that the file isn’t secure -- not that Apple was misusing the information, but there has yet been no identification of anyone misusing that information yet. Granted, now that folks know it is there, that will likely change.

I think the real problem with this capability whether it is found in an Apple or Android device (Android phones have this capability built in as well, and you can generally turn it off) is that it isn’t overt and used for our benefit. If it were, then it not only could be better protected but we might find the rewards greater than the risks. Let me explain.

I’ve actually been a big believer in location-tracking but that is because I’m concerned about protecting loved ones and getting help should I need it quickly. We’ve had a rash of kidnappings for adults and children that could have likely been partially mitigated if these people could be more quickly and easily tracked. In addition, as we age we are at increased risk of heart attack and any of us could have an accident or be attacked where we are away from folks that could hear our cries for help.

A phone that ether had an emergency button which would send our location and our immediate need for assistance would be a life saver. And simply allowing parents to constantly be aware of where their children are would give them piece of mind, and for those watching, a better opportunity to come to the child’s assistance.

But these positive uses of location tracking are rarely implemented: instead, they are used so that advertisers can better target us with sales opportunities. While I don’t see that as particularly evil, neither is it something I want so badly I’m going to risk a predator knowing where my kid is, particularly if I don’t.

I think the general problem here is that there is so much effort to find new and creative ways to monetize personal information that people are forgetting there are real user needs for this information as well.

Thus the vendors conceal, intentionally or not, the collection of this information because they rightly expect we’ll get upset if we find out they are capturing it. If they worked harder to find ways we could use this information for our own benefit, then it would be more overt, and we’d likely have in place rules as to how it needs to be protected, and they could still get the majority of the benefit they initially wanted.

The problem is vendors get so blinded by greed they forget there are real people buying these phones and increasing the efforts to protect these customers might result in a better, and less contentious, solution for everyone.

--Rob Enderle is president and founder of The Enderle Group. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?