Security "Bits"

Next-Gen BYOD Requirement 6 of 6: Can I Get Some Privacy in Here?

By Rich Campagna | April 18, 2014 at 6:35 AM

I’m starting to see a lot more mixed-use applications in our customer base. By mixed-use, I mean the same applications deployed by corporate IT are being used by employees for personal use. We see Google Apps very often in the mid-market, and of course just about everyone has a personal Gmail account. We also see a lot of file sharing applications like Box and Dropbox used for both corporate and personal use.  I still have yet to encounter anyone using in their personal life, but I’m sure they’re out there somewhere…

The point is that there are a lot of mixed-use devices out there, and an increasing number of mixed-use applications. Most of the corporate security infrastructure that we have deployed to date makes no such distinction – data is data, and so it is all treated as data that should be inspected and secured. The rationale behind this was sound – all of this data is travelling from a corporate device to a corporate app over a corporate network, so it should be secured.

That’s not the case anymore. Data is now traveling from a personally-owned device, over a public network, to a third-party application, and only some of that data belongs to the corporation. The rest of that data belongs to the employee, and corporate IT has no business inspecting it or “securing” it. For a next-generation solution to work, it must respect the employee’s personal privacy without sacrificing security.


Next-generation BYOD security requirement #6
Secure ONLY corporate data; respect employee privacy.


Get the Bitglass BYOD Security datasheet to learn more:

Download the Datasheet


This is post 7 in a 7-part series on next-generation BYOD requirements. Read the prior posts here:



see all