“Look what I got for Christmas!”
Although the holidays are long gone, those six words are still affecting IT managers months into the new year. Then come the next eight words “When can you connect it to our network?” - turning the awe factor into a network nightmare. The excitement surrounding the latest cool gadget quickly dissolves into concerns of security, compliance, control, support, and “will this thing even work?”
The long awaited (and dreaded) day of Bring Your Own Device (BYOD) is upon us and it is here to stay. The concept is not new even if the practice is in its infancy. The recent explosion in smart phones, pads, and tablet computers has thrust these issues to the forefront of all organizations. In fact, by 2014 Gartner predicts, “90 percent of all organizations will support corporate applications on personal devices.” Not so long ago, IT was able to dictate systems and software used in business in an effort to set standards for security, compliance, control, and support which helped to control cost. BYOD is a game changer for this model.
The New Model
A current trend driving BYOD is organizations giving their employees a budget to purchase their own device. This places the responsibility on the IT Team to ensure it will work with the company systems. IT can either fight BYOD or embrace it. Even if IT chooses to rebel against BYOD, end users have multiple cloud options for storage and collaboration and may choose to circumvent policies, opening up the company to unknown risk. If IT chooses to embrace BYOD, they will see that their end users fall right inline and essentially cooperate when they see that their needs being met. As time progresses, BYOD will become commonplace - the question remains, will your IT department be proactive or reactive?
If your organization is thinking about implementing or transitioning to a BYOD program, here are some points to think about when developing a BYOD strategy.
Implement Network Access Control (NAC) Having NAC technology in place implements a certain set of protocols to address endpoints (computers, tablets, mobile devices) before they can access the network. In a nutshell, NAC will not allow any endpoint to access the network unless it complies with the predefined policy. Typical NAC policies include anti-virus protection level, system update level, employee credentials and configuration. For example, if you were an accountant trying to access client files from your company database, NAC would evaluate your current anti-virus level and employee credentials before allowing you to access the shared company database. The value NAC brings is allowing more control over endpoints that may lack updated anti-virus, patches and other host intrusion software that could place more vulnerability on the network.
Develop and Communicate Security Standards Clearly define and communicate the security requirements for individual devices, pre-approved configuration policies, and most importantly the steps employees need to take in order to properly connect their device to the network. This will help the IT Team keep track of the devices and let employees know what is and is not acceptable.
Examples of Security Standards:
- Users may not store company data through cloud services on personal devices (i.e. Drop box, iCloud, etc).
- Personal devices must have a screen lock password and must time out or go inactive after not being used for 15 minutes.
- Company may remotely wipe the personal device if the device is lost, stolen or if the employee departs the company (voluntarily or involuntarily).
Responsibility Think of BYOD as a partnership between the company and the employee with both parties have different end goals and responsibilities. Dave Merrill, IBM Endpoint Security Strategist points out “while technologies can play the enforcement role by ensuring that all enterprise data is protected per security requirements, a successful BYOD program requires that employees acknowledge and embrace the need for controls that are now enforced on their devices.” Although this part is not easy, employee buy-in is vital when implementing a BYOD program.
Read more from Dave on BYOD via his post Things that matter: BYOD and the Enterprise on the IBM Institute for Advanced Security blog.
It’s time for you weigh in: To BYOD? Or not to BYOD?