security risks. This security employs a variety of
authorization and access permissions. These may
include user authentication by logging-in to the
system as well as entering authentication codes for
particular documents.
Since mobile workers are not necessarily located
at a fixed site, content may be dynamic depending
on the worker’s location through the use of a global
positioning system (GPS) or navigation system.
AirWatch’s MCM application is called AirWatch
Secure Content Locker; this is a secure centralized
storage for all business content, files, and documents
with three storage options. The cloud storage option
can integrate with the most popular repositories such
as Google Drive, Office 365, SkyDrive, and
Amazon EC2. The on-premise option can integrate
with the host repositories as well as a secure access
to SharePoint without a VPN connection (AirWatch,
2013). The third is the hybrid option of the cloud
and on-premise. AirWatch’s MCM also facilitates
two-way synchronization of content from users’
desktops to mobile devices. So individual, user-
created content can be accessible to any device that
user owns. This option is exactly what the mobile
worker needs and expects when working within a
mobile-first environment. Again, the expectation is
that these documents are always available with any
device that is used to call it.
3.2 BYOD – A Decision Framework
The serious challenges in developing a BYOD
strategy and the consecutive framework for its
implementation is the impact BYOD can have on
individuals’ privacy, organizational security, and the
liability of both entities. The Gartner analysts Andy
and Nick Jones in their Checklist for Determining
Enterprise Readiness to Support Employee-Owned
Devices have analysed and defined a structured
approach in seven phases on the road to this
emerging trend (Rowsell-Jones, 2012).
For corporate IT structures embracing a BYOD
framework, the following key steps should be
considered:
Reasoning and deciding on a BYOD strategy –
identify corporate mobile needs; define
BYOD scope; shape sponsors’ and
stakeholders’ commitments and responses to a
BYOD program
Design BYOD program segmentation by
roles/needs/functions in the organization –
categorize internal and external support, the
range and type of access, and create packages
of Policies and Technologies for each group
Plan BYOD implementation by streamlining
tools and technologies, network infrastructure
and services, financing models, and exit
options such as:
classify and approve list of devices and
versions of mobile operating systems,
applications, and providers;
design uniform policies, to enable scalable
control and management of the user-
owned mobile device utilizing Mobile
Device Management (MDM), Mobile
Applications Management (MAM), and
Mobile Content/Document Management
(MCM) solutions;
acceptable use policy with user’s
responsibilities and organization’s rights
against user’s possession;
reimbursement plan options, total cost of
ownership, corporate/private ownership
separation, and list of approved exit
options.
Program setup and approval – complete internal
policy, procedures, contracts, agreements, and
training documents; educate stakeholders and
ensure their sign-off; gain sponsors’ budget
and program approval
Perform proof of concept by running a pilot
over selected BYOD segmentations – modify
procedure/policy/technologies based on the
feedback and lessons learned from the pilot
Program execution and evolution – periodic
review and update of the BYOD program with
current software versions, devices,
applications, and providers. Utilize and evolve
a mobile systems’ features/limitations
framework that supports the adopted corporate
mobile management system(s).
The early BYOD adoptions have already
experienced numerous concerns regarding losing
personal data and privacy as corporations took full
control over personal devices, applications, and
information by utilizing mobile device management
and device-level layer 3 VPNs. To address most of
those critical anxieties, instead of a full control of
the personal device, most corporations currently
focus on adopting a set of tools to enable IT
departments to wrap corporate applications in a
security layer and to make sure that the enterprise
control on the personally-owned device is limited
only to the corporate data and applications. This
actually shifts from MDM to MAM and from
device-level VPNs to explicit application-specific
VPNs involving technologies such as BIG-IP, APM,
AppTunnels and encrypted connection to specific
BYOD: The Next Wave of Consumerization of IT - The Impact of BYOD on the Enterprise IT Landscape
249