Smartphone Kill-Switch Idea is DOA - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Mobile // Mobile Devices
News
4/7/2013
02:19 PM
Connect Directly
Twitter
Google+
RSS
E-Mail
50%
50%

Smartphone Kill-Switch Idea is DOA

An epidemic of stolen cell phones has San Francisco district attorney George Gascón demanding that handset companies put a remote "kill switch" into the devices. They're blowing him off. Experts say that there's little upside in the kill-switch for Apple, Samsung and the other handset makers and that the scheme is probably impractical.

A kill-switch, designed to make a phone inoperable if activated, is an expensive, unwieldy option with current technology, according to industry experts. The idea behind such technology is to discourage smart phone theft, a rampant problem in American cities.

San Francisco District Attorney George Gascón found out just how resistant device manufacturers were to the idea in a recent conversation with Apple. Gascón approached the hardware manufacturer after earlier talks with wireless providers went nowhere, according to Stephanie Stillman, Gascón's communications director.

Gascón's conversation with Apple did have an unlikely consequence: the news that Apple CEO, Steve Jobs, influenced the design of two forthcoming iPhone designs.

"He [Gascón] got frustrated on that conference call, because there was no will to make a kill switch," Stillman said regarding the conversations with carriers. Gascón told the SF Examiner that the "... apparent lack of interest in implementing kill-switch technology is fueled by profits."

It's no wonder the D.A. ran into trouble from the industry. "It's technically feasible, but the impact isn't high enough to drive anyone to do anything about it," said Ojas Rege, vice president of strategy at Mobile Iron.

"There's no competitive advantage to adding kill-switches," Rege said.

"I disagree with the opinion of the D.A.," Rege said, going on to explain that companies don't make money from stolen phones, they make money from new features.

Consumer and business markets are quite different, according to Rege. Unlike consumers, businesses will pay a premium for heightened security features. But what they're really concerned with isn't so much the device, but the data on the device. That's why they make sure they can wipe if a device is stolen.

The companies that work with Mobile Iron mostly use Apple devices, because that's what their employees ask for. "When the iPad came out in 2010, that was a huge shift," Rege said.

Consumers are also concerned with the data — which is why, Rege said, Apple and other manufacturers built remote wipe and tracking features. Samsung, for example, recently introduced wipe technology. But that's the most most people are willing to pay for.

"It's a demand driving economy, people buy new phones because of the cool new stuff," Rege said.

That means we're likely to see more megapixels before more security.

The practical way to go about mobile security is at the carrier level, according to Neil Shah senior analyst global wireless practice at Strategy Analytics. Although it would be a complex and difficult process, carrier-level protection using international mobile equipment identity numbers — IMEIs — would, in fact, be able to prevent stolen phones from activation. To get there, though, would require cooperation amongst carriers. Both Shah and Rege believe that to be a major challenge.

Cooperation would need to be on a global scale to prevent the resale of devices in other countries. Since there are more than 500 carriers worldwide, Shah said, that would require considerable effort. It could "slow down the [theft] process," Shah said.

Even if such a database existed, there would likely still be some countries with carriers that don't participate, making them destinations for stolen phones.

Enabling such a database, Shah said, could require a third party like a non-profit to study the problem. "They should have a solid business case," Shah told BYTE, "about what is the net impact on consumers and operators in terms of value lost [to theft]." Rege agrees with Shah that a database of stolen phones is probably the most effective way to combat the problem. But he too, acknowledged the carrier participation problem.

Until something changes, like kill-switches adding a "competitive advantage" to a smart phone, it's unlikely that D.A. Gascón's wish will be granted.

So until then, don't update your Facebook status on public transit.

Apple, LG, Samsung, Asus, and Nokia did not return BYTE's request for comment.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
News
How COVID is Changing Technology Futures
Jessica Davis, Senior Editor, Enterprise Apps,  7/23/2020
Slideshows
10 Ways AI Is Transforming Enterprise Software
Cynthia Harvey, Freelance Journalist, InformationWeek,  7/13/2020
Commentary
IT Career Paths You May Not Have Considered
Lisa Morgan, Freelance Writer,  6/30/2020
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Special Report: Why Performance Testing is Crucial Today
This special report will help enterprises determine what they should expect from performance testing solutions and how to put them to work most efficiently. Get it today!
Slideshows
PollQuery => select top 1 * from doc_documents inner join doc_sections on doc_section = section_id inner join informationweek.dbo.piddl_content piddl_content on piddlcontent_keyid = doc_id and piddlcontent_publication = 'informationweek' and piddlcontent_type = 'document' left join doc_editors on doc_author = doc_editors.doc_editor where doc_published <= getdate() and doc_pool in ('Public') and section_visible = 1 and section_id in (261) and doc_documents.doc_id in (select doc_id from doc_documentnodes where doc_documentnodes.node_id = 902) order by doc_published desc
Flash Poll