Skip to main content
Feb 26, 2013

Mobile Application Management vs. Containerization

The mobile management market is undergoing a metamorphosis. The focus is shifting away from devices to the use of the applications and the enterprise data they interact with; according to 451 Research. In today's enterprise landscape, two approaches to deliver enterprise data to mobile devices reign supreme; mobile application management (MAM) and containerization.

Containerization: Separate & Secure, But Still Attached to the Device Containerization is an approach used by companies to create a separate, encrypted environment for custom, in-house and third-party apps. It’s very similar to what BlackBerry is doing with their new BB10 – creating separate “home screens” for personal and business use. For instance; the container may contain a “third-party email client that is encrypted and separate from the native email client on the device, and can be provisioned and de-provisioned over the air by IT admins.” (451 Research) While the containerization approach protects corporate data and “separates” it from personal data, the user often has to work outside of native apps and enter separate credentials – which is not the most ideal circumstance. Users are looking for a seamless, convenient experience. Containerization may protect the corporate data, but it limits the convenience that makes BYOD so attractive to employees. As a recent ComputerWorld article praising this approach points out, containerization limits the protection of personal information on the device. “…As great as containment is for limiting corporate liability, it doesn't help any personal data that may be lost due to a wipe if the phone is lost or stolen.”

MAM: Secure, Simple – No Strings Attached to the Device Mobile application management or MAM takes a different approach. With MAM, the security and management happens at the app level – not inside a separate box. We like this approach because it keeps the focus on productivity and security. In most cases, these devices are the property of the employee and we respect that. Their stuff is theirs. When you drill down to managing the app security, usage and connections, it’s simpler to remove apps in the case of a lost device or suddenly departing employee. And IT never has to deal with “crossing the line” of personal devices. The best part of Mobile application management is that MAM is based on corporate mobile apps – making selecting apps a self-service operation. When users are empowered to install their own apps, they can be more productive and support costs stay down. Finally, the MAM approach allows IT to focus on delivering tools that keep your team productive and ahead of the competition.

Next Steps: Watch our on-demand Webcast outlining why MAM is a smarter approach to enabling the mobile workforce.

Apperian

More from the Blog
Feb 20, 2019

Part 4: App Security Should Be An Integral Part Of Your DevSecOps Process — Not An Afterthought

How Arxan can help streamline and optimize your DevSecOps process One of the most important factors to keep in mind when dep ...
Read more
Feb 13, 2019

Part 3: App Security Should Be An Integral Part Of Your DevSecOps Process — Not An Afterthought

Situations When DevSecOps Won’t Work Though DevSecOps is getting more popular by the day, and has many benefits to an organi ...
Read more
Feb 06, 2019

Part 2: App Security Should Be An Integral Part Of Your DevSecOps Process — Not an Afterthought

How to start implementing a DevSecOps process As you may have read in our
Read more