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-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.