Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

9/15/2013
08:19 PM
Dark Reading
Dark Reading
Quick Hits
50%
50%

Ten Things To Consider When Developing An Enterprise BYOD Security Policy

Is there a safe way to let employees access corporate data from their own mobile devices? Here are some things to think about

[The following is excerpted from "Ten Things to Consider When Developing BYOD Policy," a new report posted this week on Dark Reading's Mobile Security Tech Center.]

BYOD, or bring-your-own-device, is a trend that is not going away. In InformationWeek's 2013 State of Mobile Security report, based on a survey of 424 business technology professionals, 68% of respondents said their mobility policy allows employees to use personal mobile for work, with 20% saying they are developing such a policy.

In fact, BYOD can hardly be called a trend anymore: The model is here to stay in the enterprise, and it's expanding to include all manner of employee-owned technology (including bring your own apps, bring your own private clouds and bring your own WLANs). Organizations, therefore, must do more than just bless the concept; they must proactively set out guidelines that tell users what they can and cannot do, and that describe the role IT will and will not play in the management, support and security of employee-owned devices.

"In today's always-connected society, organizations can no longer let mobile device adoption in the workplace simply run its course," says Steve Durbin, global VP of the nonprofit Information Security Forum.

"By putting the right usage policies in place, businesses can benefit from the returns that mobile devices can bring to the workplace while limiting exposure to potential security risks," Durbin says. "If executed poorly, a personal device strategy in the workplace could face unintentional leaks due to a loss of boundaries between work and personal data and more business information being held in an unprotected manner on consumer devices."

One of the biggest challenges with BYOD is the ambiguity that often surrounds the concept, especially when it comes to security. For example, when the employee owns the device, who owns the data on the device when it's being used to access corporate networks and data? To what extent can IT dictate the level of security an employee-owned device must have?

These are just a few of the questions organizations are dealing with, which is all the more reason for companies to develop a firm policy, says Forrester analyst Christian Kane, whose research is focused on desktop and mobile strategies, including BYOD.

"The biggest reason [to develop BYOD policy] is that there is so much gray area in this topic," says Kane. "Many companies have built their mobile strategies around the fact that they owned the devices and could dictate what happens on them. So a big part of having a BYOD policy in place really has to do with things that are ambiguous: What can I do and what can't I do? What's the right kind of usage, and how does the company feel about that?"

Research from the SANS Institute indicates a bit of a Catch-22 when it comes to BYOD policy: The complexities of BYOD increase the need for policy, but BYOD complexity makes it challenging to develop policy.

"With such complex issues to address, it's no wonder that 50% of survey respondents either don't have policies to support BYOD devices or they depend on the user to comply with corporate policy for securing these personally owned devices," the March 2012 SANS report "SANS Mobility/BYOD Security Survey" states. "Only 41% feel strongly that they have policies to support BYOD, of which 17% are standalone policies and 24% are integrated as an aspect to their overall security policies.”

To find out more about what enterprises are doing to facilitate BYOD -- and for the full list of 10 points to consider when writing your own policy -- download the free report.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5783
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the login functionality does not contain any CSRF protection mechanisms.
CVE-2020-11031
PUBLISHED: 2020-09-23
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library c...
CVE-2020-5781
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the langSelection parameter is stored in the luci configuration file (/etc/config/luci) by the authenticator.htmlauth function. When modified with arbitrary javascript, this causes a denial-of-service condition for all other users.
CVE-2020-5782
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, if a user logs in and sets the ‘wan_type’ parameter, the wan interface for the device will become unreachable, which results in a denial of service condition for devices dependent on this connection.
CVE-2020-24213
PUBLISHED: 2020-09-23
An integer overflow was discovered in YGOPro ygocore v13.51. Attackers can use it to leak the game server thread's memory.