Risk
11/1/2011
01:59 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

MDM: To Sandbox Or Not To Sandbox?

Mobile device management systems take different approaches to sandboxing. Is mobile virtualization the answer?

Most enterprises must make a tradeoff when it comes to mobile device management, or MDM, systems, because providers fall into one of two camps: those, like Good Technology, that provide a single sandbox where all corporate data goes, and those, such as MaaS360 or MobileIron, where the device has some sandboxing (for email) but most of the MDM client's work is done in conjunction with the operating system's apps and features.

The two approaches have pros and cons, and some organizations have a very difficult time deciding which route to go. Well, life is set to get a bit easier now that Verizon has partnered with VMware and AT&T has linked up with Enterproid's new Toggle to bring mobile virtualization to the market.

While sandboxing is traditionally done at the application level, the new technologies from VMware and Enterproid focus on creating partitions, using virtualization, to sandbox the entire mobile device. That allows a user to run two versions of a mobile operating system at the same time on the same phone: one for work, one for personal use.

In a video from the Qualcomm QPrize event demonstrating Entreproid's technology, you can see how a mobile user can seamlessly switch between the two "phones" and have full access to all 250,000+ real apps within each partition, as if they were the only apps on the device. We can finally allow Angry Birds to be installed in the personal partition and prevent it from running in the corporate partition. Huzzah!

While you can't get your hands on the tech until later this year, it has been discussed since 2009 and has been securing a very well-known user's mobile phone for over a year: President Barack Obama uses this type of virtualization technology on his BlackBerry to separate the highly secure apps he needs to run from the rest of the phone.

The benefits to enterprises are pretty compelling, too. Mobile virtualization provides all the advantages of sandboxing--mainly, full encryption of all corporate data and easy wiping of that data--as well as the benefits of non-sandbox-based approaches; for example, employees can use native mobile apps, such as the calendar and mail clients, without having to be retrained on a quirky interface from a vendor such as NitroDesk TouchDown or Good. There are new benefits, too, such as allowing an end user to upgrade to a new version of Android while the corporate partition stays at a corporate-enforced version.

We don't recommend you hold off on your MDM or mobile strategy until these technologies are available, since all the vendors we spoke with say that'll take a few months. But definitely keep it on your radar. I think that mobile virtualization will be a game changer for the enterprise if phone manufacturers provide devices that will support the technology. The holdup there is that the phone must have enough processor power and should be a dual-core device. Almost all the new Androids are dual-core, and this is something to consider if you provide stipends or guidance for users on device selection.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
J to the C
50%
50%
J to the C,
User Rank: Apprentice
11/4/2011 | 5:26:36 PM
re: MDM: To Sandbox Or Not To Sandbox?
I just read about 3LM. Looks like it takes Android to the iOS security level(s). Have you read about Mocana as well? Eventually BYOD will become BYOA (bring your own apps).
GrantMoerschel
50%
50%
GrantMoerschel,
User Rank: Apprentice
11/3/2011 | 11:13:32 AM
re: MDM: To Sandbox Or Not To Sandbox?
These are interesting developments. As I've learned more about the MDM space, I've come to the conclusion that Good-type solutions are typically going to be a dead end because user's will revolt if they can. In high security environment they can't revolt but in most others they can. Also it'll be interesting to see how standardized OS mods like those done by 3LM.com will play into hopefully normalizing the major flavors of droid so that they can be consistently controlled. Or will these VM's simply fix it all by giving people two completely different interfaces both of which are friendly and not restrictive.

Grant Moerschel, InformationWeek contributor
jrapoza
50%
50%
jrapoza,
User Rank: Apprentice
11/2/2011 | 11:14:03 PM
re: MDM: To Sandbox Or Not To Sandbox?
I agree. Mobile VMs will be the key to managing BYOB devices in a corporate environment. As pointed out, it is probably the cleanest and easiest to manage approach.

Jim Rapoza is an InformationWeek Contributing Editor
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.