1. Supporting BYOD Dennis Cromwell dcromwel@iu.edu

2. Supporting BYOD  CISCO Study – 15B devices capable of connecting to a network by 2015  The Consumerization of IT

3. Two fundamental items Support Security

4. We have done this for years. Right?

5. The Problem – The Device

6. The device type presents its own problem  Laptop/Desktop computers are somewhat easier – known issues and good solutions.  Tablets and smart phones

7. The problem – The embedded Cloud

8. The Problem – Security  It’s about the data

9. The Problem – The applications and user expectations

10. The Problem – the network  The carrier and you!

11. Lessons learned from years of student BYOD The devices run consumer OS and not Enterprise = they are unmanaged They have viruses They are not patched They need to be registered They will not practice safe computing by default They will expect THEIR device to work and work now

12. IU Get Connected – Poor Man’s Network Access Control  Written for students  Started when connecting to the network was difficult  Morphed to a product to protect user and University  Started with Windows, but now has a MAC version  Supports various OS versions  Use of this type of tool being limited as vendors tighten security Configures network connections Registers device to user Checks for anti-virus software Checks for updates Turns on automatic updates Installs some useful applications

13. Network Access Control

14. Policy and guidelines are important  Data Restrictions  Public, University Internal, Restricted, Critical  Storage of data on mobile devices  Mobile services  Encryption  Tracking services  Remote wipe  Cloud resources – better embrace this rather than fight it

15. Applications – There’s an App for that!  Device specific vs. device agonistic  The Case for Generic   HTML5 & CSS3 & javascript - When people say HTML5, they mean this combination.  HTML5 provides access to many native features. Need to wait for browsers to implement these features. GPS and device orientation/rotation was first, Apple just added access to camera and photo libraries in iOS 6 Beta. This trend truly makes PhoneGap just a narrowing gap  Much easier skill to learn and find, so this point alone is a big advantage of native development.  Write once, run anywhere solution as opposed to the native platforms where you might even need a different OS to write and compile the mobile software.

16. Network Access - Can you hear me now?  We used to call wireless LAN a network of convenience…..when did that change?  Cell coverage and capacity are important  Higher Ed generally has the worst possible situation for wireless networks  High usage areas  Large number of roaming users  Restricted budgets limit “over provisioning”  Large buildings with steel and stone  New buildings with energy efficient glass

17. Virtualization  Application and desktop virtualization – Citrix or VMWare  Web delivered apps – Office 365

18. Laws – Do I really have to meet with Counsel again?  We all know about data breach laws  How does open record laws apply to BYOD?  Who is responsible for discovery?

19. Closing thoughts  This is inevitable  This will cause you problems  Do things now to prepare 1.Get your policies updated 2.Establish guidelines – if you are going to access our network, connect to our email, use applications “You must…” “You are encouraged…” 3.Invest in technology 4.Establish an application standard 5.Wireless networks are not optional and carriers will need to be part of the strategy 6.Yes, meet with Counsel again.