{"id":2953,"date":"2017-03-16T16:59:09","date_gmt":"2017-03-16T16:59:09","guid":{"rendered":"https:\/\/www.peeriosity.com\/shared-services\/articles\/?p=2953"},"modified":"2022-09-06T22:27:47","modified_gmt":"2022-09-06T22:27:47","slug":"the-benefits-and-risks-of-a-bring-your-own-device-byod-policy","status":"publish","type":"post","link":"https:\/\/www.peeriosity.com\/shared-services\/articles\/2017\/03\/the-benefits-and-risks-of-a-bring-your-own-device-byod-policy\/","title":{"rendered":"The Benefits and Risks of a Bring Your Own Device (BYOD) Policy"},"content":{"rendered":"

In a world of heightened security, where any access to a company\u2019s systems risks introducing security breaches or viruses, carefully evaluating and setting a policy for the authorized use of employee-owned devices isn\u2019t a trivial exercise.\u00a0 A decision to allow personal devices triggers a series of additional decisions, including what systems or applications to make accessible, password format requirements, and helpdesk support<\/a> that may be required when employees have problems with their personal devices.<\/span><\/p>\n

One particularly complex issue related to BYOD policies is what will take place when an employee leaves the company, and you need to eliminate systems access capabilities and ensure the removal of sensitive company information.\u00a0 With company-issued devices, this is not a problem, since the company simply takes possession of the device.\u00a0 With employee-owned devices the employee retains possession, and changes to the device may be required prior to the employee leaving the company.\u00a0<\/span><\/p>\n

Recently, Peeriosity\u2019s iPollingTM<\/sup> was used by the Vice President of Shared Services<\/a> at one of our member companies to better understand the policies other companies have in place that cover employee-owned devices.\u00a0 Here\u2019s the background information that was submitted when the poll was created: \u201cOur organization is in the process of developing a BYOD policy to allow employee-owned devices to access company systems.\u00a0 We would find input from other companies very valuable in creating something that is flexible for the employees<\/a>, but also ensures that our systems and data integrity are not put at risk.\u201d<\/span><\/p>\n

Once the poll was released by Peeriosity, responses were posted in real-time, with visibility to company responses available to all Peeriosity members, allowing for direct communication with peers using Peeriosity\u2019s integrated Peer MailTM<\/sup> capabilities, including following up to ask about specific policy examples.<\/span><\/p>\n

The first poll question asked about the status of developing a Bring Your Own Device (BYOD) policy for employee-owned smartphones, tablets, and other devices.\u00a0 Interestingly, 54% of responding companies indicated that they have implemented, with an additional 14% currently evaluating options for doing so.\u00a0 Only 11% of responding companies considered the opportunity and decided not to provide access, and, somewhat surprisingly, 21% haven\u2019t yet evaluated the issue.\u00a0<\/span><\/p>\n

Here are the details:<\/span><\/p>\n

\"iPolling:<\/p>\n

For companies that do have a BYOD policy in place, a follow-up question examined the level of employees who would qualify under the policy.\u00a0 In 60% of companies with a current policy, all employees qualify, with 7% restricting the program to Directors and above, and 13% restricted to supervisory level and above.\u00a0 In another 13% of companies, the policy is administered based on the role of the employee, and not their job level.<\/span><\/p>\n

\"iPolling:<\/p>\n

Unlike traditional benchmarking, Peeriosity\u2019s iPollingTM<\/sup> capabilities allow members to very quickly examine this issue in detail, providing a range of experiences and viewpoints that can be reviewed to develop an appropriate and workable answer.\u00a0 Tapping into the experience of peers eliminates guesswork and allows members to quickly access the collective experiences of a large community of users who are facing the same challenges.<\/span><\/p>\n

Here are a few of the comments from responding companies:<\/span><\/p>\n