Risk
1/16/2013
04:10 PM
Connect Directly
RSS
E-Mail
50%
50%

Close The BYOD Security Hole

A bring-your-own-device policy it a low-cost way to use Apple devices without spending a lot of money, but don’t forget security.

A bring-your-own-device policy is a low-cost way to let employees use Apple devices without a huge capital investment. But the downside is security. In a recent Virgin Media Business survey of 500 British CIOs, more than half reported network breaches from employee-owned devices accessing the network. Dartmouth-Hitchcock Medical Center, a major northern New England healthcare provider with nearly 8,500 employees, has policies and processes that let its staff use Apple devices on the network securely, without having to manage them centrally.

Lessons Learned

>> Know that management will be an issue. Windows PCs continue to be the medical center's only centrally purchased and supported systems, in part due to the difficulties it has had centrally managing Macs. Macs don't have full Active Directory support, among other things, says Bill Weyrick, senior manager of information systems.

>> Set up a separate guest WLAN. Dartmouth-Hitchcock's first and most fundamental level of security has been to provide a guest Wi-Fi network with a completely separate IP space and service provider, and to configure business-critical apps so they can't run from that address space. This approach provides basic BYOD network access, including for patient and guest devices, without compromising network security.

>> Write a policy for employee-owned devices that has teeth. Dartmouth-Hitchcock lets employees use personally owned Apple devices to access email and enterprise apps that don't involve medical records. Employees must have device-level authentication and let IT verify they're using a password and encrypting certain data, and allow remote wipe if the device is lost. The hospital doesn't allow Android devices because the policy-level security it's using can't monitor security status with the same level of confidence that it has with the iPhone.

>> OS X is out for certificate-level authentication. Only Windows devices can be used for the most secure level of access, since Dartmouth-Hitchcock requires those devices to be certificate-authenticated and centrally managed.

>> Explore thin client. Dartmouth-Hitchcock uses Citrix to securely serve mission-critical apps to both Macs and PCs, keeping patient data off the client.

>> Consider outsourced support. Dartmouth-Hitchcock limits iPad use to projects funded and supported by nonstandard means, such as loaner iPads for kids in the children's hospital and devices used by the hospital's Boards of Trustees to access meeting materials. Outsourcers manage both projects.

Go to the main story:
Why Apple Is IT's Arch Frenemy

Continue to the sidebar:
Apple Doesn’t Rule The School

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio