Making the Case for Containment With WIP

November 9, 2017
| |
3 min read

It seems all too common today to hear about a sensitive data breach or a rogue employee who is up to no good. There are many security solutions on the market, and containment is the most popular for the enterprise.

Since its release, Windows 10 has been integrating its own secure system, Windows Information Protection (WIP), with these solutions to ensure compatibility.


The Case for Containment in Windows 10

The Microsoft Windows operating system (OS) has been an industry standard for decades. Unlike iOS and Android, Microsoft’s decision to develop a relatively seamless OS across multiple device types is an ingenious way to ensure consistency and improve adoption rates. In today’s market, consumers want devices that work for them, whether for business or personal use. That means enterprises need an all-encompassing solution that is easy to use, provides a pleasant overall experience and, most importantly, delivers robust security.

The case for a containment for Windows 10 is compelling, since Microsoft has already implemented WIP. Data containment is a way to house sensitive information on a device in a secure manner. Usually, with a unified endpoint management (UEM) solution, rules are pushed down from an IT administrator to ensure that enterprise data stays safe. With a robust policy and deep integration, you might wonder whether a third-party container is even necessary.

Integrating UEM With WIP

Compared to Windows 7 and Windows 8, the management capabilities for Windows 10 far exceed those of the previous operating systems. The default policy is on par with the capabilities of other mobile device platforms in terms of security, restrictions and compliance. At the moment, there is no third-party container for Windows 10 laptops and desktops that supports email, chat and documents.

The policies that Microsoft released for UEM solutions also include complete integration with WIP through the default policy. In essence, it acts as its own container and maintains a native experience for the user.

Unless the market changes, there is no foreseeable need to develop a containment solution for Windows 10 computers. However, that doesn’t mean it is completely off the table. If there is a demand for it, software development teams will create a container for Windows 10. The idea is to trim the excess and keep it simple so there will be less to worry about.

In bring-your-own-device (BYOD) environments, it’s fair to assume that containment is the best course of action for smartphones and tablets. However, once the default Windows 10 policy is published, it leverages the need for a container. WIP integrates directly into the UEM policy so any information or settings pushed from the UEM solution can be removed from the device remotely via a selective wipe.

See a Need, Fill a Need

With WIP, it is not necessary to develop an entire suite of additional apps and features because everything is already being managed in the policy. As time goes on, software companies such as Microsoft, Apple and Google will add more features for better integration. A container app may be optional or even necessary in future iterations of Windows laptops and desktops. Until then, the possibilities depend on IT trends and demand. But on the bright side, the sky’s the limit.

To learn more, view our on-demand webcast, “The Seven Wonders of Windows 10,” which features a demo of IBM MaaS360 with Watson for Windows 10.

Dan Cheuvront
MaaS360 Product Marketing Professional, IBM

Dan's career has been primarily IT-based, starting at Apple Inc. as a Mac Genius, moving on to Flextronics, and is now on the Product Marketing Team at IBM f...
read more