February 24, 2020

Whose Device Is It Anyway?

By txtsmarter-No Comment

Originally Posted by Chris Dritsas / July 22nd, 2014 / txtblog

Bringing your own mobile device to work is an extremely convenient option for an employee in almost any industry. According to a 2013 Gartner survey of CIO’s, over 50% of companies will actually require employees to bring their own mobile devices to work by 2017. However, this convenience is rarely shared by the employer and thus gives rise to a number of problematic situations in the workplace.

What many employees don’t understand is that any business-related data that’s transferred across an employee’s mobile device, still belongs to the company that they work for. Even if you don’t work at a company like NASA, whose BYOD policies are directly impacted by matters of national security there is a good chance your company considers data-security an important matter. That being said, destroying an employee’s personal mobile device because it is a company liability, is not always the best option. What’s a good alternative you ask? Mobile Workspace Management or “MWM”.

Applying an MWM strategy is efficient in limiting the company’s liability in a BYOD environment, while maximizing the employee’s sense of privacy. MWM’s are also known as containers because they successfully separate the user’s work-related data from their personal content and information. Considering a 2013 Coalfire survey, which found that 86% of employees use the same smartphone for personal and work usage – it becomes evident that deciphering between these two types of data is crucial. The fact is, the majority of employees are not willing to carry separate phones for work and personal use and thus a middle ground must be established. That middle ground needs to meet the security needs of the company while respecting the privacy of its employees. This text controversy will get louder and louder.

#intelligentcompliance #txtsmarter

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.