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.

Risk

2/25/2013
06:06 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Smartphones, Foolish Security Choices

One quarter of smartphone users store "intimate" images on their mobile devices, says security vendor AVG.

10 Best Android Apps Of 2012
10 Best Android Apps Of 2012
(click image for larger view and for slideshow)
People with smartphones could be smarter in their security practices. One smartphone user in every four, according to security firm AVG Technologies, stores intimate photos on a smartphone or tablet, a practice that makes a lost or stolen device a potential privacy problem.

AVG didn't specifically define "intimate" in its survey. "The mobile survey asks whether or not people have intimate photos of themselves on their smartphone or tablet, allowing the definition of 'intimate' to be purely up to the respondents' interpretation of that word," a company spokeswoman said in an email.

In other words, among the intimate photos said to reside on a quarter of respondents' mobile devices, not every image is likely to deserve an "X" rating. Some might not even qualify for an R or PG-13. Even so, the finding suggests that a significant percentage of smartphone users have some security and privacy blind spots.

[ Will Firefox OS phones rock the market? Read Mozilla Firefox OS Ignites Carrier Rebellion. ]

AVG surveyed 5,000 smartphone users in U.K., U.S., France, Germany and Brazil about the kinds of data kept on mobile devices. The company says that although respondents were "acutely aware" of data threats -- 50% of respondents recognized that mobile devices are less secure than computers -- they missed potential privacy implications.

JR Smith, CEO of AVG, said in a statement that the survey demonstrates consumer confusion about safe usage of mobile devices and urged companies to do more to educate consumers about privacy and security.

So, while we wait for the inevitable launch of Fruit of the Loom briefs stitched with, "No Cameras Beyond This Point," AVG has some modest advice to help those who don't recognize the privacy and security implications of carrying a phone loaded with potential blackmail material.

-- Don't install (Android) apps from outside the Google Play store.

-- Don't install anything that sounds too good to be true, such as "free ringtones" or "free wallpaper."

-- Keep your phone's operating system up-to-date, even if mobile carriers don't necessarily make this easy.

-- Install an anti-virus app on your phone -- not exactly surprising advice from a company that makes an anti-virus app.

AVG neglects to mention the most obvious way to protect one's privacy: Don't store intimate photos on your phone.

Attend Interop Las Vegas, May 6-10, and attend the most thorough training on Apple Deployment at the NEW Mac & iOS IT Conference. Use Priority Code DIPR02 by March 2 to save up to $500 off the price of Conference Passes. Join us in Las Vegas for access to 125+ workshops and conference classes, 350+ exhibiting companies, and the latest technology. Register for Interop today!

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Ninja
2/26/2013 | 9:50:55 PM
re: Smartphones, Foolish Security Choices
So where should people store their intitmate photos? In the cloud? Is that really going to be any safer? On their home PC? Same deal. Might as well roll the dice with the phone. Or follow Tom's advice, which is probably best of all: don't take "intimate" pictures.

Drew Conry-Murray
Editor, Network Computing
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...