Perimeter
4/22/2011
01:21 PM
Rob Enderle
Rob Enderle
Commentary
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3594
Published: 2014-08-22
Cross-site scripting (XSS) vulnerability in the Host Aggregates interface in OpenStack Dashboard (Horizon) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-3 allows remote administrators to inject arbitrary web script or HTML via a new host aggregate name.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.