Vulnerabilities / Threats
02:14 PM

Beware Smartphone Lurkers: Cloud Storage File Remnants

Security investigators recovered Box, Dropbox and SugarSync files and unique file IDs, via forensic dump of iPhone and Android smartphone memory.

What are the implications of these findings? As more people use smartphones, digital forensic investigators -- including police departments and law enforcement agencies -- are increasingly looking at such devices to recover usable evidence. Last year, for example, police in London announced that they were testing mobile phone data extraction devices to allow specialist teams to access, study and save any data stored on a suspect's mobile device. In the future, however, they may need to study not one device, but many, given the extent to which many people now own multiple devices.

On that front, the Glasgow researchers said they're now continuing their study to cross-reference forensic examinations of multiple devices used by the same person. "The very nature of the cloud environment encourages users to access data through multiple devices," they said, noting that they already have an experiment underway "to access residual artifacts from Gmail, Mozy, Ubuntu One and Evernote on end devices connected to these services." Their question is whether conducting a forensic analysis of multiple devices used by the same user will yield a greater number of recoverable files and artifacts.

"The first step was to say, is this an idea that's going to work, then we can say, in future research, how do we use this data to say something useful for a forensic investigator, in terms of merging evidence from different proxies into a single data set?" said paper co-author Tim Storer, speaking by phone. For example, if part of an Excel spreadsheet is found on one device, but not another two devices used by the same user, should it count as evidence? "There's often a tendency by forensic investigators to conflate data and evidence," he said, when a higher threshold is called for.

Going forward, the researchers said in their paper that they hope to detail "the data leakage risk that cloud applications introduce to corporate environments" in greater detail, as well as to "propose a set of security measures for both cloud providers and smartphone users to mitigate the potential risk of data leakage."

"These services are being used in corporate environments more and more ... so it's a potential source of risk for an organization," said Storer. "Sensitive documents may end up on someone's device that's subject to analysis." But businesses might minimize those types of risks by steering their employees to use devices from which it's more difficult to recover usable information, forensically speaking. Likewise, cloud service providers could offer their corporate customers specialized services that scrubbed all data stored by their mobile apps, once a user no longer needed to view it.

2 of 2
Comment  | 
Print  | 
More Insights
Threaded  |  Newest First  |  Oldest First
Andrew Hornback
Andrew Hornback,
User Rank: Apprentice
3/22/2013 | 4:28:13 AM
re: Beware Smartphone Lurkers: Cloud Storage File Remnants
From my point of view, this makes the use of an appropriate MDM solution all that much more important in an organization with a BYOD policy that also leverages these kinds of cloud services. Being able to do a full out "device nuke" in the event of a device loss becomes critical in light of these findings.

Andrew Hornback
InformationWeek Contributor
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-05
system/session/drivers/cookie.php in Anchor CMS 0.9.x allows remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via a crafted serialized object in a cookie.

Published: 2015-10-05
The Secure Meeting (Pulse Collaboration) in Pulse Connect Secure (formerly Juniper Junos Pulse) before 7.1R22.1, 7.4, 8.0 before 8.0R11, and 8.1 before 8.1R3 provides different messages for attempts to join a meeting depending on the status of the meeting, which allows remote attackers to enumerate ...

Published: 2015-10-05
The Secure Meeting (Pulse Collaboration) in Pulse Connect Secure (formerly Juniper Junos Pulse) before 7.1R22.1, 7.4, 8.0 before 8.0R11, and 8.1 before 8.1R3 allows remote authenticated users to bypass intended access restrictions and log into arbitrary meetings by leveraging a meeting id and meetin...

Published: 2015-10-05
Heap-based buffer overflow in the parse_string function in libs/esl/src/esl_json.c in FreeSWITCH before 1.4.23 and 1.6.x before 1.6.2 allows remote attackers to execute arbitrary code via a trailing \u in a json string to cJSON_Parse.

Published: 2015-10-05
Unrestricted file upload in GLPI before 0.85.3 allows remote authenticated users to execute arbitrary code by adding a file with an executable extension as an attachment to a new ticket, then accessing it via a direct request to the file in files/_tmp/.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.