Risk
5/30/2008
10:41 AM
Keith Ferrell
Keith Ferrell
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Are Your Employee's Phones Secure? All Of Them? Really?

Can a single unsecured smartphone compromise your business's security? Looks that way -- and that should make you look hard at who's got phones in your company, and how they're using them.

Can a single unsecured smartphone compromise your business's security? Looks that way -- and that should make you look hard at who's got phones in your company, and how they're using them.Here we go again. As we've pointed out often, the explosion of powerful, capable consumer communication/IT devices holds a lot of risk for your company.

A long Informationweek look at the business dangers of rogue smartphones tells you why.

A rogue device is, in this context, one that an employee -- or, for that matter employer -- buys personally and then uses for business purposes.

In the case of smartphones, as the article points out, the devices' convenience, power and declining price makes them all but irresistible to road warriors, would-be road warriors and, increasingly, nearly everybody else.

And as employees lean more heavily on such devices, the devices become more and more filled with company data, company information, even company access codes.

All of which goes with the employee -- until the employee forgets the phone, loses the phone or has the phone stolen.

Or, assuming the person's at least cautious about keeping the phone physically close, holding it tightly when he or she uses it to pump company info through an unsecured public access point.

Time to put into place strict and inflexible security procedures and policies regarding employee use of personal mobile (and other) devices for company business.

Past time, really, and not getting any safer to wait, as Eric Zeman's article points out, with plenty of detail on just how to go about securing rogue devices.

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-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.