Home' Defense Systems : June and July 2013 Contents MOBILE
MOBILE DEVICE MANAGEMENT
12 JUNE/JULY 2013 | DefenseSystems.com
Guard, National Guard, reserves and
possibly more components in the fu-
ture. e objective of the enterprise
MAS is to optimize the functional-
ity and distribution of mobile apps
to mobile devices while minimizing
replication, cost and downtime.
"As end-user dependence on mo-
bile devices rises, enterprise man-
agement implemented via an MDM
becomes necessary to ensure secure
mobile device operation and main-
tenance in a cost-e cient manner,"
the Commercial Mobile Device Implementation Plan states.
Furthermore, MDM capabilities "ensure [that] the security
of the entire user community is not compromised by an im-
properly con gured or operated device."
However, the plan also states that "until the development
of multi-level security is a viable construct," separate MDM
systems in the classi ed and unclassi ed DOD information
domains will be implemented. An enterprise-level service
capability for unclassi ed information processing will be
accomplished by an MDM system, with an enterprise MAS
that will deliver, update and delete applications on mobile
devices without the user having to return the device for
"On the unclassi ed side, that mobile application store
will include commercial apps, as well as government-
developed apps, and the review of the code and how we put
those apps out, as well as the licenses that we procure for
some of the enterprise capability," Hickey said. "We have to
maintain control of the number of devices that use those
applications, much like a commercial environment."
An enterprise-level service capability for unclassi ed
information processing will be accomplished by an MDM
system with an enterprise MAS. e MDM system will be
a decentralized capability hosted at several DISA Defense
Enterprise Computing Centers.
"Right now, we don t have an MDM on the classi ed [side],
but we re working with [the National Security Agency] on
what could meet our very unique security requirements,"
Hickey said. "We re in the planning stages right now."
DISA s objective is to establish an enterprise mobility ar-
chitecture that will provide secure delivery of email, mobile
applications, voice services and other data services, includ-
ing initial network operations and reporting capabilities.
DISA will implement the MDM and MAS in three phases.
Phase 1, which includes the purchase of 1,500 devices,
will deploy voice and data services via a commercial wire-
less network and award a contract for the initial MDM and
MAS. Phase 2 will provide the capability to manage as many
as 5,000 devices. Phase 3 is an operational capability that
will be o ered as a subscription-based service to support
"We re looking to have 5,000 devices by the end of this
scal year ," Hickey said. "With Android, Apple,
BlackBerry and Windows, we see demand from all over for
di erent mobile devices."
"Our goal is to be device-agnostic," he added. " at s what
we ve said all along to create competition in this space, lower
our overall costs and improve the capability. DISA is not in
the business of trying to determine a speci c device [for ev-
eryone to use]. at is up to DOD users to decide. We re
providing a service."
MOBILITY PILOTS, SPIRAL DEVELOPMENT
Currently, DISA is conducting both unclassi ed and classi-
ed operational pilot projects to test existing mobile tech-
nologies. e projects evaluate select mobile capabilities,
including information assurance, security, logistics and
performance. is series of pilots will incorporate lessons
learned, ensure interoperability, re ne technical require-
ments, in uence commercial standards and create opera-
tional e ciencies, o cials said.
" e biggest di erence between unclassi ed and classi-
ed [devices] is that we require a second layer of encryp-
tion on the classi ed device, as well as we route all the tra c
through what we call a mobile gateway," Hickey said. " at
provides us with the capability to look at the information
that is inbound and outbound. And it ties back into our se-
cure voice-over-IP network."
In May 2012, DISA began its mobility pilot activities to
build an enterprise mobile capability that is the wireless
The goal of the DOD CIO is
to make sure that pilots are
innovative and that we don't
hamper the good ideas and
development that can happen
at various levels.
--- JOHN HICKEY, DISA
Links Archive April and May 2013 August and September 2013 Navigation Previous Page Next Page