BYOD is Here to Stay. Take Device Lifecycle Into Account.

Friday, March 08, 2013

Michelle Drolet

E85787adcaf7bca10e799cfd1cfd08f1

It appears that BYOD, “Bring Your Own Device” to work, is beyond just being a growing trend if not currently a sanctioned practice within the corporate walls. It may seem that bowing to this desire on the parts of employees would have a lot to offer, not the least of which is a reduction in costs for employee-issued hardware. Unfortunately that is not entirely the case.

In fact, cost reduction should be the last reason for considering allowing BYOD.

Embracing this movement requires a well thought out policy that will be acceptable to both employees, who may want the convenience but fear privacy breaches, and the business, which must keep its own data and hardware safe from security threats while getting more productivity from its staff.

Employee concerns about privacy can be easily handled if the IT department has the right tools. But that is actually a smaller part of the issue. The larger element in determining BYOD policy must consider the entire life cycle of devices that are owned by private individuals and the impact on business security.

According to a survey by Cisco and Redshift Research, 48% of companies globally stated they would never authorize employees to BYOD. Contrast this to another finding in the survey: that 57% of companies state that some employees were doing it anyway without anyone’s consent.

Rather than continue to deny the trend, the best route to take is to put into place a policy that spells out what the concerns are from both sides of the aisle and how they will be addressed. Looking at privacy issues, employees tend to worry about:·        

  • Being tracked through mobile device management systems.
  • Employers viewing private information on their personal devices.
  • Deletion of personal information such as pictures, music, and email profile.
  • Employers viewing the websites visited during non-working hours.
  • Being required to allow access to installed personal applications.

Tools are being developed by mobile device manufacturers to address some of these concerns. The resolutions include a virtual wall between personal information and what the company can see or the capability of housing two personas on a single phone, one for business and one for personal use. Other tools include allowing IT to push and pull corporate information without being able to access private, personal information.

In addition to this, many mobile device management systems come with security options to protect against employer invasion of employee privacy. Unfortunately, these settings are often not used. A policy should spell these actions out.

Company Security

Businesses must be sure employees understand the risks from a corporate point of view. Part of the BYOD policy should include education for business users regarding how company information is to be accessed, how and when this information may be deleted from the device, and what to do when the device is no longer to be used for work. Emphasize the ease and invisibility of cybercrime.

The rest of the policy must address what IT must do when an employee:

  • Leaves employment, taking the device with him.
  • Decides to use the device only for personaal use.
  • Turns in a device for an upgrade.
  • Sells the device. 

Applications are another area that must be handled. The employee will not take kindly to being restricted in the applications he places on his own phone. Also, there is the possibility that the company may need to place a custom application on the phone for work purposes.

BYOD is here to stay. Prudent businesses are getting ahead of the curve by creating a policy that takes the entire device lifecycle into account.

(Note: We just released our eBook, "Beware BYOD." To download please visit http://www.towerwall.com.)

Possibly Related Articles:
10205
Policy General PDAs/Smart Phones
BYOD mobile
Post Rating I Like this!
F66c1a87a8db2cb584b4e06e93a84ce3
Mikko Jakonen With a great debate about BYOD and how much with is has gone and will go wrong, I do have to admit that this Michelle's writing carries the best (counter) arguments for second what to do with BYOD.

As it should be put in display, I do have my strict opinions about BYOD and how it goes wrong. Still, there is a clue within the article which I do support: Enforcement of operational security and not only that, a good governance over information assets life cycle -discipline.

When you outsource a business critical piece of process, you still do not outsource the risks. Barely move their place. The discussions what should take place is: What role this demonstrates in our end2end business processes and what are the real threats involved within.

The major reason (barely) NO organization is doing it is that they are UN-AWARE of the critical information assets they possess and where in the line of end2end architecture view they reside. Not even bringing in the 3rd parties involvement within the extended enterprise theme.

Unfortunately, there is no virtual wall as Michelle writes - the BYOD is a pancake, employee maneuvers it as most suitable for own needs - that is; not businesses needs.

As long as BYOD implements security solutions by the need, not by the basis we go wrong. By the way, same thing happens at the moment already with laptops etc. workforce environment even without 'BYOD'. @mikk0j
1363038425
The views expressed in this post are the opinions of the Infosec Island member that posted this content. Infosec Island is not responsible for the content or messaging of this post.

Unauthorized reproduction of this article (in part or in whole) is prohibited without the express written permission of Infosec Island and the Infosec Island member that posted this content--this includes using our RSS feed for any purpose other than personal use.