Analytics
1/15/2010
03:12 PM
50%
50%

Tech Insight: Tools For Securing Your Smartphones

What major smartphone vendors provide from a security standpoint

The growing popularity of smartphones in the enterprise requires that companies extend similar data protection policies to their smartphones as they use for their computer systems. But smartphones pose slightly different threats: While malware is still a threat, the likelihood of the mobile device being lost or stolen is much more likely because of its small size and portability.

Encryption is a way to lock down smartphones. But to date, it's not widely adopted across enterprise mobile devices. According to a recent Ponemon Institute report, "2009 Annual Study: U.S. Enterprise Encryption Tools," 59 percent of enterprises surveyed rated the data on mobile devices used by employees as important to very important. Just how many organizations actually encrypt the data on smartphones, however, was low: Only 26 percent said they encrypt data on mobile devices most of the time, while 51 percent said they never do, according to the survey, which was commissioned by PGP.

It might seem the amount of data loss from a mobile device would be insignificant. But 16 gigabytes isn't uncommon for a smartphone today, and that's a substantial amount of potential data. Additionally, there's the high likelihood that corporate smartphones can check corporate e-mail without needing a password. They also can access an internal network via VPN, and custom ERP, sales, or similar applications -- allowing access to sensitive data. Add that all together, and you have the clear potential for a major data breach.

The two major platforms for reining in control of smartphones are BlackBerry Enterprise Server and Microsoft Exchange ActiveSync. Both are well-established and have extensive support for managing policies, such as encryption, password complexity, account lockout, and remote wipe. But they have their pros and cons, including vendor lock-in versus multivendor device support and granularity of endpoint control. And there's always the competitors looking to supplant both platforms with one single unified platform supporting BlackBerry, Windows Mobile, Palm, and iPhone.

RIM's BlackBerry has dominated the enterprise smartphone arena for years because of its extensive policy management capabilities, built-in security features, and ease of use for users. BlackBerry offers more than 400 policy settings for making sure smartphones are adequately protected from unauthorized access. And devices can be deployed without the need for a third-party encryption solution to handle data at rest and in transit because they include out-of-the-box support for encrypted communications back to the enterprise server, intranet services, and encrypted storage.

Microsoft's Exchange ActiveSync also comes with some strong security tools for enterprises. Encryption for data at rest is weak compared with the BlackBerry's, and the available policies pale in comparison by number, but important options in password settings, recovery, and remote wipe are there. As expected, there is tight integration with Windows Mobile-based devices, but support doesn't stop at Windows-based smartphones. Other smartphone vendors have implemented management tie-ins for remote management via ActiveSync, although several of the implementations are lacking in completeness. With each new OS released for the Apple iPhone, Apple has taken steps to implement more ActiveSync functionality, while current support within the Motorola Droid is weak.

Companies using smartphones from various vendors have options, too. The growing need to manage a largely heterogeneous smartphone environment with a mixture of Palm, iPhone, BlackBerry, and Windows Mobile has created a market of promising players. Third-party offerings add the ability to now manage many disparate devices that all have varying levels of support for various policy settings and features within a unified interface. The offerings here include enterprise management solutions from BoxTone, Trust Digital, MobileIron, and GuardianEdge. At the very least, all of the vendors support the platforms mentioned above, several include support for Symbian, and some are adding support for Google Android devices.

Native and third-party management solutions provide support to configure encryption for data at rest, and SSL is typically used for data in-transit.

So why don't many enterprises deploy these tools for securing their smartphones? The sad fact is it may take a few lost or stolen smartphones to get enterprises to move from the "it's important to me" category to actually adopting these tools.

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

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.