Dark Reading 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.

Endpoint

12/16/2013
07:10 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

How To Safely Retire Mobile Devices

Once employees bring their new iPads, Androids, to work after Christmas, their older mobile devices must be decommissioned to protect company data

One company destroyed an old server it had replaced by dousing it in Thermite and setting it ablaze in the company's parking lot.

"We lit it on fire and watched it [get destroyed]," says Tyler Shields, who witnessed the extreme data-wiping incident at one of his former employers. "That's one effective way to do it, certainly."

But unless your company's smartphones or tablets are used by the President of the United States or contain classified or highly sensitive information, pyrotechnics aren't necessary to ensure that older mobile devices don't leak data, says Shields, a senior analyst for security and risk management at Forrester Research.

Just how to properly purge employees' older smartphones and tablets when they return to work after Christmas with their new devices is a major holiday headache for IT and security teams. The number of employee-owned smartphones and tablets continues to skyrocket: The devices will number more than 1 billion by 2018, according to Juniper Research.

"Most people are working on their second or third generation of smartphone or tablet, so they're going to be disposing of them [in lieu of new ones]," says David Lingenfelter, information security officer at mobile device management firm Fiberlink. "A majority of them keep them, and 58 percent are going to keep them inactive. That's not bad, but that typically means they're being passed on to their children, and they will do something with them."

Lingenfelter says a Harris survey commissioned by Fiberlink last year found that 68 percent of the workforce does not professionally wipe or destroy their devices.

[With employees bringing their smartphones and tablets into the workplace, companies need to work to limit the threat posed by mobile applications. See 5 Steps To Managing Mobile Vulnerabilities .]

Here are some basic rules of thumb for users recycling or disposing of a smartphone or tablet:

Activate the factory wipe feature.
Before you hand down that tablet to your grade schooler, wipe it using, for example, the "factory data reset" function on an Android or the "Reset" function on an iPhone or iPad. That wipes all data and any apps you added from the device, which returns to its out-of-the-box unregistered setting.

"The little things you don't necessarily think of when you're passing the device on to your children -- children like to click on things, and they may make a mistake and adjust your finances" if you don't wipe the tablet, for instance, Lingenfelter says. "Go back to factory defaults, so the kids can set it up [for] themselves and your personal and corporate information is gone."

Sometimes going through the wipe process twice makes sense to ensure the device is clean, he says.

Don't forget to remove the SD card.
This is a common oversight: A user wipes the phone properly, but leaves the SD card in place, which may be storing data. The factory reset doesn't touch the card, security experts say. This is an issue with many Android devices. "You have to remember to take the card out," Lingenfelter says.

Some Android users configure their apps to save the SD card first, notes Forrester's Shields. "Pull the card and replace it with a new one. Then, A, you've got a backup copy of the data, and, B, you don't have to worry about any secure wipe technologies," he says.

And any SIM card also should be pulled out when you deactivate a phone, Lingenfelter says. "A lot of SIMs can keep a copy of your contact list," he says.

School your employees on your organization's decommissioning procedures.
Even when mobile device management (MDM) technology is in place, things can go awry when mobile devices are retired. "Once [the device] is disconnected from MDM, all is safe and secure is not always the case," Shields says. "People may be lulled into a false sense of security. The device now yours is not always 100 percent secure."

Organizations should consider a default factory reset wipe whenever a user or his or her device leaves the organization. "Then you make sure there are no fragments slipped outside the network," he says.

And be sure employees are educated on the procedures for retiring or recycling a personal mobile device. "A lot of companies now implement MDM, with containerization, where all enterprise software and data stays in one section [of the device] and is not able to be contacted by personal software or leaked out by Dropbox" or another app, says Lingenfelter.

Users should notify IT when they bring in their new Christmas iPads, for example. "If they are going to use it for work, you have to make sure they take the proper steps," he says.

But keep in mind that even the best decommissioning practices can be bypassed by clever hacks. "At the end of the day, you're never going to guarantee complete security when you're selling your phone. There are all sorts of extremely advanced attacks," Forrester's Shields says. "If you're paranoid about it, don't sell it. Destroy it."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
The Problem with Proprietary Testing: NSS Labs vs. CrowdStrike
Brian Monkman, Executive Director at NetSecOPEN,  7/19/2019
RDP Bug Takes New Approach to Host Compromise
Kelly Sheridan, Staff Editor, Dark Reading,  7/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-2873
PUBLISHED: 2019-07-23
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox...
CVE-2019-2874
PUBLISHED: 2019-07-23
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox...
CVE-2019-2875
PUBLISHED: 2019-07-23
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox...
CVE-2019-2876
PUBLISHED: 2019-07-23
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox...
CVE-2019-2877
PUBLISHED: 2019-07-23
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox...