Mobility Device Management Strategy January 2013

idleheadedceleryΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 8 μήνες)

49 εμφανίσεις

INFORMATION TECHNOLOGY

Mobility Device Management Strategy

January

2013

By 2016, Cisco estimates …



There
will be
over seven
billion
additional wireless devices in the market
over the next
five years


These devices typically attach to a
network using a wireless connection



2

Strategic Goal

Enhance creative
and
responsible stewardship
;
educational excellence
and
community engagement
by
:



Providing cutting
-
edge technologies and services to
attract and retain the ‘best’ students in Kentucky


Expanding the
support
of mobile devices to increase
customer satisfaction


Ensuring access to technology services from mobile
devices, anywhere, anytime




3



Charge



Investigate and recommend a support
model for
pervasive use of mobile
devices accessing the
university’s technology services and
communications network



4

5

Wireless Devices at U of L

0
2000
4000
6000
8000
10000
Oct-12
Nov-12
Dec-12
Jan-13
U of L DEVICE COUNTS
BEFORE / AFTER HOLIDAY
2012
0
2000
4000
6000
8000
Nov-11
Dec-11
Jan-12
Feb-12
U of L DEVICE COUNTS
BEFORE / AFTER HOLIDAY
2011
Participants


Steering Committee



Jo Kaelin, Chair


Denita Campo


Brenda Gombosky


Sande
Johnson
-
Byers


Bo Lowrey


Deepak Sharma



Technical
Team



Bo Lowrey, Chair


Andrew Davis


Pam Frank


Trent Hurt


Scott
Owen


Michael
R
admacher


Dave Richards


6



Approach


Assessed current state of mobile technology at UofL


Performed a mobile application review


Reviewed customer satisfaction data


Surveyed benchmarks


Researched future trends and directions




7

Wireless Network



The Pervasive Wireless Project has achieved connectivity
to all university
buildings
and
outdoor areas




Implemented 802.11n standards with data rates up to
150 mbs (~6x faster than 802.11g)



ULsecure
-

Encrypted wi
-
fi access for students, faculty
and staff



ULopen



sponsored guest
wireless
network

Findings

8

Mobile Security



Virtual Private Network (VPN)
-

supports
Windows and Mac clients. Evaluating support for
Apple iOS and android clients due Q1 2013



Firewall
-

no special requirements needed to
support mobile devices



Findings
(continued…)


9

Mobile Security



Policy
Review





Information Security Policy and Standards

http://
security.louisville.edu/PolStds/ISO



UofL
Guidelines for Securing Mobile Devices with
Sensitive
Information



ISO policies 007, 012, and 018 pertain to all
equipment, including
mobile devices



Findings
(continued…)


10

Mobile Support



HelpDesk and iTechConnect support iOS
,
android
and
b
lackberry devices
-

mainly for wireless and email
configuration



Too
many
device types
and
OS versions
to
guarantee

support. Best effort is provided



Tier 1 community supports devices within their teams,
agree support cannot be
guaranteed

and also provide
their best effort

Findings
(continued…)


11

Mobile Applications



Blackberry:

(as
of
12/12/12)



173 registered
devices


74 users in the last
30 days


Estimated
< 100 active accounts


BlackBoard

has withdrawn Blackberry support for new
development (existing product is still supported)



Microsoft Active Sync (with
Exchange
2010)



Cannot manage 100
% of devices


Does not work the same for student Cardmail


Findings
(continued…)


12

Mobile Applications



S
upport for applications is provided if browser based and
web enabled



The
u
niversity
does
provide mobile applications through
vendor’s
“Apps Store”



ULMobile and CardSafety applications are current
offerings




Findings
(continued…)


13

Customer Satisfaction



2012 university
-
wide survey indicates



14

Findings
(continued…)


Students

Faculty & Staff


Mobile
Device
Support


84%


95%


Wireless
Network


89%


87%


Mobile
Device Support
:


U of L


Provides Best Effort Application Support (43%)

15

Findings
(continued…)


43%

21%

36%

Device Support

Best Effort
None Specified
Some Specific Application
Support
Benchmark Comparison


Security / Practice


U of L


Provides recommendations

and broad policy
covering all systems and data (36%)

16

Findings
(continued…)


36%

28%

36%

Security Policy or Recommendation

Have a Specific Policy
No Policy or
Recommendation
Recommended Measures
Benchmark Comparison


Wireless Access Policy


U of L


Provides staff
s
ponsored
g
uest accounts (21%)

17

Findings
(continued…)


79%

21%

Wireless Access Policy

Open or Self Provisioning
Staff Sponsored
Benchmark Comparison

Network



Increased access, more transparent join policy
-

we will
not know which provider network users are accessing



Diversity &

number of devices requiring connectivity is
increasing causing IP
address
exhaustion and density



W
ireless public
IP
addressing space was adjusted
before
end of 2012



Additional adjustments to be piloted Q1/ Q2 of this
year to provide additional address space (NAT / PAT)


Future
Trends

18

Network



IPv6 will become prevalent


Offers additional address space


Timing will be driven by internet adoption.



Network address translation will provide interim
solutions for address needs



Bandwidth needs will increase: 802.11AC


wireless
gigabit
-

will be a mainstream technology by 2015




19

Future
Trends
(continued…)

Security & Support



Risks
and vulnerabilities associated with desktops
today will
become evident on mobile
devices



Windows 8 and Surface are “tablet like




Devices are changing and will include unexpected forms
(e.g. Google glasses, watches, automobiles….)



Use of virtual
desktop
interfaces (VDI) will expand



Increased distance learning demands



Increased collaboration increases security risks



20

Future
Trends
(continued…)

General



Mobile support
should
focus

on the
data rather
than the
hardware or
devices



Application support requirements are minimized if browser
based.



A
pplications should be distributed through existing
mechanisms (
iStore
, Android Marketplace)



Applications developed that require access to Enterprise or
sensitive data should be approved by Enterprise Security and
the data owner


Recommendations


21

General


Additional
resources are needed
across
all
IT departments:



Mobile
devices available
to research
and

trial



Training for support
personnel



Monitoring
tools
for performance and device types



Increased
awareness of security
exposure



22

Recommendations
(continued…)


23

Recommendations
(continued…)


General


Increased budget for campus wi
-
fi and Internet
connectivity to accommodate traffic originating from
carrier networks
.



Clarify, communicate and document the role of vendors
Unit Business Managers and Tier
1 personnel in
the
provision of mobile device support



Create user self help web pages, allowing users to have
access to mobile device configuration information specific
to University systems.



Allow Blackberry devices and University supported
Blackberry resources to go “end of life”.


Wireless Network



I
ncrease satisfaction and ease of access by providing
self provisioning services



Implement plan
to provide
more
“open” wireless
network (reviewed
with
university legal counsel)



Purchase a device profiling network management tool
that allows discovery of device type
and
quantity
assessments


24

Recommendations
(continued…)


Mobile Security



Revise the University’s acceptable
u
se policy to explicitly
address
mobile
devices


Continue to invest in
needed in security
solutions


Recommend solutions (when available) for
device protection


Mobile
Support



Ensure customer facing areas are equipped to provide
comprehensive support for mobile devices



University web pages
will be
optimized for mobile device use as
a part of the PLONE4 upgrade



Continue investigation of VDI products, and apply where
appropriate






25

Recommendations
(continued
…)



Present
and receive leadership endorsement



Incorporate recommendations into unit strategic goals



Review support needs and realign resources



Develop timelines and budget requirements



Continue to monitor the technology and device landscape






Next Steps

26




27