THE CONNECTED ENTERPRISE
SPECIAL REPORT
::
JULY 2011
3 www.networkworld.com • tHe connected enterPrISe
INSIDER
NetworkWorld
Four keys to successful BYOD
process beyond the iTunes and Android store
approach, in an effort to define strict coding
practices for an in-house apps store. There
is huge momentum around BYOD, and Kad-
rich acknowledges that one day it is likely to
be a component in Kaiser Permanente’s IT
strategy.
Like Kaiser Permanente, a number of
IT consultancies have expressed doubts
about whether BYOD is truly cost-effec-
tive. Although it may look at first glance as
though a company is saving money by hav-
ing employees buy their own mobile devices,
perhaps with a corporate stipend, there are
management costs that may not work out to
the company’s advantage. Aberdeen analyst
Hyoun Park, for instance, notes that telecom
rate plans, for example, cost less through tra-
ditional contract negotiations than through
individual contracts.
As far as cost-savings go, “the jury is
still out on BYOD,” says Joe Nocera, prin-
cipal in the IT security risk practice at
PricewaterhouseCoopers. He thinks the
BYOD “promise of cost-savings” is largely
“unrealized” today.
BYOD raises questions about security
controls and how forensics will be done on a
device owned not by the company but by the
employee, Nocera notes. He also is skeptical
about how far MDM software goes today to
meet strict security requirements. “Its func-
tionality is very limited,” he says of current
MDM packages. “All they do is secure email
fairly well.”
The main goal has to be securing the data
on the device and having a way to validate
it through risk assessments, he says. In
regulated industries, such as healthcare and
finance, there are going to be audits of these
BYOD mobile devices and the apps that are
used, Nocera points out. Unfortunately, in too
many cases, businesses are thinking about
these questions only after they’ve rolled out
BYOD practices.
Some user discussion groups have taken
up the topic of BYOD so that IT and security
managers can share ideas. Austin-based
Wisegate IT community, for example, a group
in which Kadrich participates, recently pub-
lished a report titled, “IT Peers Share Advice
on Effective ‘Bring Your Own Device’ Strate-
gies.” The upshot: There appears to be little
consensus so far.
Some 27% in the survey on BYOD said
they’ll only allow “fully managed and secured
devices to utilize corporate services,” while
24% said, “We are moving from a ‘device
centric’ strategy to a ‘user centric’ strategy
and don’t think that devices can be fully
secured. We focus on securing the sensitive
transactions.” Another 20% claimed to have
a “hybrid approach” in which more secured
devices get more access and less secured/
managed get less access.
Tellingly, 6% revealed how painful dealing
with BYOD is by answering, “This issue just
gives me a headache, and I’d really like it to
go away.” n
By Eric VandErBurg, spEcial to
nEtwork world
V
anderburg is a CISSP, and director
of Information Systems and Secu-
rity at consultancy JurInnov. This
vendor-written tech primer has
been edited by Network World to
eliminate product promotion, but readers should
note it will likely favor the submitter’s approach.
The bring your own device (BYOD) move-
ment formally advocates use of personal
equipment for work and obligates IT to
ensure jobs can be performed with an accept-
able level of security, but how can risks be
addressed given the range of devices used and
the fact that you lack control of the end point?
Companies looking to embrace BYOD --
44% of firms surveyed by Citrix say they have
a BYOD policy in place and 94% plan to imple-
ment BYOD by 2013 -- need to address four
key areas: 1) standardization of service, not
device, 2) common delivery methods, 3) intel-
ligent access controls and 4) data containment.
1. Standardization of service
Standardization is necessary to implement
a consistent set of security controls across dif-
ferent platforms while providing the same
level of service. Lack of compatibility with
security controls can deny legitimate users
access to information services and hurt pro-
ductivity. Solving this issue by adding more
access methods can result in weaker security
and make the environment more difficult to
manage. Instead, companies can give users
the service they expect through desktop and
application virtualization technologies and
terminal servers.
Virtual desktops are hosted on a remote
server and emulate a desktop computer to
provide access to IT services, including appli-
cations and tools users need to do their job. As
long as they can connect to the server, users
can access their virtual desktop.
Through application virtualization, soft-
ware is streamed from a server to the end
users device, enabling users to access their
core business applications from a variety of
devices. Application virtualization does not
require software installation and applica-
tions can be upgraded from the server without
interfacing with remote or mobile devices. In
some cases, the application can be cached on
the device so it will function even when a con-
nection to the server does not exist.
Both virtualization options use termi-
nal server connections to access the remote
virtual desktop or application but terminal
servers can be used alone to provide consis-
tent access to IT services similar to desktop
virtualization. It differs from desktop virtual-
ization, however, in that the applications run
on the server operating system instead of a
virtualized one. Terminal servers are limited
in the services they can provide because not
all applications support terminal access and
some may behave differently on a terminal
than they would on a virtual desktop.
None of these solutions are new so their
security models are mature enough to be
relied upon for IT services. In fact, these tools
return control of end user devices to security
practitioners. Restrictions can be placed on
systems so the user can neither install other
applications nor change the system to intro-
duce vulnerabilities. Since all the activity is
performed remotely, the device used to con-
nect does not matter so employees can do their
job even if their primary computer is unavail-
able. Both terminal server and virtualization