WEBVTT

00:00.210 --> 00:07.560
If I as an organization have tens hundreds thousands of mobile devices under my control I can use something

00:07.560 --> 00:10.230
known as mobile device management.

00:10.320 --> 00:17.340
Every mobile operating system has built into its core the ability to listen to a single control source

00:17.640 --> 00:21.950
to be able to do just about anything you want to a mobile device.

00:22.140 --> 00:25.950
So for example I can define what applications you can install.

00:25.980 --> 00:32.940
I can even decide what kind of backgrounds you have and what type of wallpapers you use and I can even

00:32.940 --> 00:36.030
set it up so that you can't take pictures unless I want you to.

00:36.030 --> 00:39.480
Now if this sounds a little bit Big Brother it is.

00:39.570 --> 00:44.090
But there's a wonderful granularity to mobile device management.

00:44.100 --> 00:49.890
Now as you can imagine there are thousands of things we can cover but for the exam there's a very specific

00:49.890 --> 00:50.270
list.

00:50.280 --> 00:52.810
And I would just want to run through these really quick.

00:52.830 --> 00:54.380
First is content management.

00:54.390 --> 00:58.270
Now that certainly are applications but it goes a lot deeper than that.

00:58.320 --> 01:01.440
For example our applications need databases.

01:01.440 --> 01:06.210
Our nurses are going to need databases that are up to date for the different types of patients on the

01:06.210 --> 01:07.080
floor.

01:07.230 --> 01:11.670
Our sales people are going to have to have databases that showed the current sales that are taking place

01:11.910 --> 01:14.610
for the customer and he's right in front of right now.

01:14.700 --> 01:19.680
Also things like documents if I've got an engineer out in the field and he's referencing some type of

01:19.680 --> 01:26.000
documentation I want to make sure that my content management keeps all of this up to date.

01:26.100 --> 01:27.650
Next is geo location.

01:27.690 --> 01:33.330
Pretty common stuff letting us know where somebody is at this very moment.

01:33.540 --> 01:40.950
But as a corollary to that is geo fencing jeel fencing is geo location but with a trigger the moment

01:40.950 --> 01:47.070
that truck comes into the yard I want the loader guys to know that it's coming and they need to be ready

01:47.070 --> 01:47.650
for it.

01:49.350 --> 01:55.770
Also push notification services it's very convenient for us to have our applications put push notifications

01:56.070 --> 02:02.310
up on the screen but we don't want a casual push notification to come up when our charge nurse is working

02:02.310 --> 02:03.580
on a critical patient.

02:04.710 --> 02:06.540
Next our passwords and pins.

02:06.540 --> 02:12.360
Not only do we require passwords and pins but more importantly if someone forgets one or if there's

02:12.360 --> 02:18.840
an issue we have the ability from remote management to be able to take care of those types of problems.

02:19.700 --> 02:26.990
On top of that are biometrics fingerprint facial recognition even voice are common on most mobile devices

02:26.990 --> 02:28.190
these days.

02:28.190 --> 02:33.740
What's interesting is not only can we use this to lock or unlock a device but we can actually configure

02:33.740 --> 02:35.140
applications today.

02:35.180 --> 02:40.190
You may be on the device but if you want to use a particular application you're going to have to use

02:40.190 --> 02:45.980
one of these biometrics just to get to that next our screen locks.

02:45.980 --> 02:50.250
We want to make sure that people have their screens locked when they're not in use.

02:50.270 --> 02:54.820
And these are one things that mobile device management can easily enforce.

02:54.980 --> 03:01.130
And last unfortunately we do have users who lose devices and the convenience of a remote wipe from a

03:01.130 --> 03:04.730
central location is a powerful MTM tool.

03:04.730 --> 03:09.980
Now there's a lot of situations in mobile device management where we're really kind of transcending

03:09.980 --> 03:16.130
the device itself and instead we're concentrating on the applications on this device.

03:16.130 --> 03:22.430
Now this is particularly true when we get into the b y O.D. kind of scenario because what we're talking

03:22.430 --> 03:26.920
about now is that we have a person's personal device.

03:27.140 --> 03:30.850
But we're going to apply applications to this device.

03:31.010 --> 03:36.480
So we have to be sensitive to the fact that it's their device and they need access to their stuff.

03:36.650 --> 03:42.020
Yet on the same token we need to provide strong control and security for our stuff.

03:42.020 --> 03:49.490
So let's go through different aspects of mobile application management first is application management.

03:49.490 --> 03:54.650
Now I know just a moment ago I said that content management was a part of NDA.

03:54.770 --> 04:00.380
But when we're talking about application management here we're talking about versioning updates patches

04:00.620 --> 04:04.530
things that are specific to the application that you're managing.

04:04.670 --> 04:12.470
Next is context aware authentication instead of just counting on things like passwords or fingerprints.

04:12.500 --> 04:14.300
We can add context.

04:14.300 --> 04:16.330
Where are they right now.

04:16.520 --> 04:22.730
What operating system are they using what time of day are they trying to authenticate these context

04:22.760 --> 04:26.230
aware authentication tools can be incredibly powerful.

04:27.240 --> 04:30.120
Next is storage segmentation.

04:30.120 --> 04:35.940
Now when I talk about storage segmentation I'm talking about dedicating a separate piece of the storage

04:36.000 --> 04:42.550
of the mobile device just for our application keeping it totally separate from the user's personal stuff.

04:43.690 --> 04:50.290
Another big one is full device encryption where we literally encrypt the entire storage of the mobile

04:50.290 --> 04:55.250
device to make sure that if it falls in the wrong hands they're not going to get any information.

04:56.160 --> 05:01.250
As to something interesting and we call this containerization Let's talk about that for a minute.

05:05.690 --> 05:07.990
Containers are really really popular.

05:07.990 --> 05:11.540
We see people for example who do web apps here total seminars.

05:11.570 --> 05:14.910
We live in the world of doctor for our web app development.

05:14.960 --> 05:23.300
However it's also great when it comes to mobile devices both iOS and Android.

05:23.300 --> 05:29.210
We're great with containers and it's a super way if you have a particular application or more than that

05:29.210 --> 05:33.680
an application with all its support deals and all the other documents and everything.

05:33.680 --> 05:37.660
Well with one container you can do all kinds of amazing updates.

05:37.980 --> 05:38.630
OK.

05:38.750 --> 05:45.920
So in the end mam's sound great and I can just throw some pretty words up on the screen but you really

05:45.920 --> 05:48.310
need to see it in action to see how this works.

05:48.410 --> 05:54.920
Now there are literally hundreds of different companies that provide MDMA type solutions out there so

05:55.250 --> 05:59.170
I chose one in particular that actually comes directly from Google.

05:59.570 --> 06:04.910
Google does MTM through a very very powerful system in this particular case.

06:04.910 --> 06:09.370
They provide a wonderful little demo and it's great for a course like this.

06:09.380 --> 06:12.170
So let's take a look what's up on my screen.

06:12.170 --> 06:14.290
So what I've got is an Indian solution.

06:14.300 --> 06:20.060
This is a demo so it's not a complete product from Google so I want to go through and just give you

06:20.060 --> 06:22.920
some idea of some of the management stuff we'd want to see.

06:23.030 --> 06:29.690
First of all we'd have to decide on our users so here's me and one device and it's the Android I've

06:29.690 --> 06:38.870
actually got sitting right in front of me right here so it is a managed device so we can also define

06:38.870 --> 06:40.520
things like for example apps.

06:40.520 --> 06:44.270
Now right now I have three apps that my users are going to use.

06:44.270 --> 06:48.890
Now if you're looking at this you're going to go well what if I already have Chrome browser or what

06:48.890 --> 06:52.610
if I already have Dropbox hang on a sec I'll show you it's really cool.

06:52.640 --> 06:55.390
So what we can say is we can auto install.

06:55.400 --> 06:59.800
So basically the moment this person logs in they're going to get these programs.

06:59.870 --> 07:05.750
But I can even add more stuff for example if I want to I can add this painting program I'm going to

07:05.750 --> 07:10.040
go ahead and prove that.

07:10.290 --> 07:14.730
And what I've done is I've added this particular program I'm going to show you where this comes into

07:14.730 --> 07:16.000
play in just a second.

07:16.810 --> 07:22.310
Next we can apply some policies for example here I can disable screen capture in this case.

07:22.450 --> 07:28.360
I've got it turned off so my individual computers can still go ahead and do screen captures disable

07:28.360 --> 07:29.270
copy and paste.

07:29.270 --> 07:32.290
What an interesting thing to disable as a policy.

07:32.290 --> 07:37.860
You don't want people copying and pasting from some important application and putting it in their notepad.

07:37.860 --> 07:43.450
I can require a screen lock with a pin if I want I can have runtime permissions basically when they

07:43.450 --> 07:48.070
come up to run a particular app I could require them to do a username and password if I want.

07:48.070 --> 07:50.880
I can even in this one little simple demo.

07:51.070 --> 07:54.440
Force them to use a particular Wi-Fi configuration.

07:54.570 --> 07:54.860
OK.

07:54.860 --> 08:02.230
Now understand right now folks this is a demo tool so it is extremely limited but it's designed to show

08:02.230 --> 08:07.380
you I think Google does a good job of giving you an idea of what MTM can really do.

08:07.390 --> 08:10.470
Now the interesting part is over here on my screen.

08:10.480 --> 08:17.420
So what I want you to look at and you'll see if there I have contacts and this is just my personal contacts.

08:17.760 --> 08:20.430
And you can see it says Mike at play.

08:20.430 --> 08:24.870
Now what I'm going to do right now is I'm going to go this new folder and you'll see it has a little

08:24.930 --> 08:26.180
icon on there.

08:26.190 --> 08:31.210
This is the work folder that's been put in through this management tool.

08:31.230 --> 08:32.670
You can see I've got contacts here.

08:32.670 --> 08:34.640
Now watch what happens when I click on this.

08:34.680 --> 08:36.560
Now you see it says Mike at work.

08:36.570 --> 08:41.500
So really what's happening is I have two completely separate sets of contacts here.

08:42.830 --> 08:48.940
One for work and one for play The other interesting part is right up here.

08:49.040 --> 08:55.010
So you'll see that I have installed programs I've got Dropbox chrome and the show pad which are the

08:55.010 --> 08:58.180
three that were in there but I want to install that paint program.

08:58.310 --> 09:01.090
So what I can do now is go into Google store.

09:01.220 --> 09:03.750
However this is not the Google store that you and I know.

09:03.770 --> 09:07.120
Notice it only has four applications for me to choose from.

09:07.340 --> 09:12.830
So I could if I want to go ahead and install that one particular application.

09:12.890 --> 09:18.800
The cool part to this little demo tool is that it really makes two of everything.

09:18.800 --> 09:24.740
So if you have to have everything in many of these endian solutions what you'll see is that they take

09:24.830 --> 09:31.730
your system and they segregate your storage so that some of the storage is for your stuff and some is

09:31.730 --> 09:36.620
dedicated to the applications that you need to get your job done.

09:36.650 --> 09:41.870
In fact not only does it segregate it but it will actually go through an encryption process to really

09:41.870 --> 09:43.450
really lock that stuff down.

09:44.850 --> 09:52.920
Mobile device management is absolutely amazing and it is becoming more and more accomplished and powerful

09:53.130 --> 09:54.600
as the years progressed.

09:54.750 --> 09:59.970
I think it will be interesting to see in the not too distant future what some of the amazing opportunities

09:59.970 --> 10:15.080
can take place within the world of mobile device management.
