10:41 AM
Keith Ferrell
Keith Ferrell
Connect Directly

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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio