WEBVTT

1
00:00.000 --> 00:00.553 align:middle line:84%


2
00:00.553 --> 00:02.220 align:middle line:90%
In this video, I'd
like to chat with you

3
00:02.220 --> 00:04.830 align:middle line:90%
about the benefits of a
mobile device management,

4
00:04.830 --> 00:07.630 align:middle line:84%
or MDM policy for a network.

5
00:07.630 --> 00:12.230 align:middle line:90%
So MDM is an acronym for
mobile device management.

6
00:12.230 --> 00:15.050 align:middle line:90%
Because stuff that's not bolted
down can move around, like,

7
00:15.050 --> 00:16.129 align:middle line:84%
a wireless laptop.

8
00:16.129 --> 00:18.500 align:middle line:90%
And then, like everything
else, our smartphones

9
00:18.500 --> 00:20.420 align:middle line:90%
and other smart
devices that are being

10
00:20.420 --> 00:22.483 align:middle line:90%
used, whether they're
in the office being used

11
00:22.483 --> 00:23.900 align:middle line:90%
through the wireless
in the office

12
00:23.900 --> 00:27.420 align:middle line:90%
or they're connecting from
their homes, or other locations,

13
00:27.420 --> 00:28.430 align:middle line:84%
such as a hotel.

14
00:28.430 --> 00:31.460 align:middle line:90%
And as part of any good mobile
device management system,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:28.430 --> 00:31.460 align:middle line:90%
And as part of any good mobile
device management system,

15
00:31.460 --> 00:33.920 align:middle line:90%
we are going to have
an ability to onboard.

16
00:33.920 --> 00:36.440 align:middle line:90%
Now, onboard is just
simply introducing

17
00:36.440 --> 00:39.800 align:middle line:90%
or bringing on a mobile
device into our mobile device

18
00:39.800 --> 00:40.748 align:middle line:84%
management system.

19
00:40.748 --> 00:43.040 align:middle line:90%
And that leads to something
important called inventory.

20
00:43.040 --> 00:44.870 align:middle line:90%
So we know exactly,
or we're expecting

21
00:44.870 --> 00:46.760 align:middle line:90%
what is going to connect
and what's allowed

22
00:46.760 --> 00:48.020 align:middle line:84%
to connect to our network.

23
00:48.020 --> 00:49.700 align:middle line:90%
And after a device
has been onboarded,

24
00:49.700 --> 00:52.280 align:middle line:90%
it now becomes part of the
mobile device management

25
00:52.280 --> 00:53.000 align:middle line:84%
inventory.

26
00:53.000 --> 00:54.470 align:middle line:90%
So it's part of
the database, part

27
00:54.470 --> 00:57.170 align:middle line:90%
of the information about
what devices are expected

28
00:57.170 --> 00:58.730 align:middle line:84%
to connect to the network.

29
00:58.730 --> 01:01.010 align:middle line:90%
And that connection
could be local, on-prem,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
00:58.730 --> 01:01.010 align:middle line:90%
And that connection
could be local, on-prem,

30
01:01.010 --> 01:03.290 align:middle line:90%
or it could be
connecting with a VPN

31
01:03.290 --> 01:05.300 align:middle line:90%
from a remote network
such as the internet.

32
01:05.300 --> 01:09.140 align:middle line:90%
And with a good mobile device
management program or system,

33
01:09.140 --> 01:10.640 align:middle line:84%
here are a few of the benefits.

34
01:10.640 --> 01:12.910 align:middle line:90%
One would be
application protection.

35
01:12.910 --> 01:15.630 align:middle line:90%
So if a mobile device is
brought in by the user,

36
01:15.630 --> 01:18.230 align:middle line:90%
the user might have to agree to
have their device become part

37
01:18.230 --> 01:19.880 align:middle line:90%
of the mobile device
management system

38
01:19.880 --> 01:21.755 align:middle line:90%
so that they can have
some of these benefits,

39
01:21.755 --> 01:23.180 align:middle line:84%
like, application protection.

40
01:23.180 --> 01:26.330 align:middle line:90%
Or if the device is issued
by the company to the user,

41
01:26.330 --> 01:27.860 align:middle line:90%
then the company
has a better stance

42
01:27.860 --> 01:29.420 align:middle line:90%
because it's their
device in saying

43
01:29.420 --> 01:30.712 align:middle line:84%
this is what's going to happen.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:29.420 --> 01:30.712 align:middle line:84%
this is what's going to happen.

44
01:30.712 --> 01:32.305 align:middle line:90%
And as far as
application protection,

45
01:32.305 --> 01:34.430 align:middle line:90%
we can specify through our
mobile device management

46
01:34.430 --> 01:38.600 align:middle line:90%
system what applications are
allowed to run on that device.

47
01:38.600 --> 01:40.460 align:middle line:90%
And that way we can
lock applications down

48
01:40.460 --> 01:43.280 align:middle line:90%
to a specific list and
only those applications

49
01:43.280 --> 01:45.390 align:middle line:84%
can run on that mobile device.

50
01:45.390 --> 01:48.500 align:middle line:90%
Another benefit of a good
MDM is data protection.

51
01:48.500 --> 01:50.900 align:middle line:90%
We can enforce through
a policy that there's

52
01:50.900 --> 01:52.640 align:middle line:90%
encryption involved,
and that when

53
01:52.640 --> 01:55.850 align:middle line:90%
data is being stored,
especially if this is Bob here,

54
01:55.850 --> 01:58.820 align:middle line:90%
and Bob has VPNed in
and he's accessing data

55
01:58.820 --> 02:00.840 align:middle line:90%
and it's stored on
his mobile device,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
01:58.820 --> 02:00.840 align:middle line:90%
and it's stored on
his mobile device,

56
02:00.840 --> 02:03.200 align:middle line:90%
we can specify through
policy on that device

57
02:03.200 --> 02:05.450 align:middle line:90%
that the location where
that's being stored

58
02:05.450 --> 02:06.710 align:middle line:84%
is being encrypted.

59
02:06.710 --> 02:10.160 align:middle line:90%
Another benefit of a good
MDM system would be malware--

60
02:10.160 --> 02:12.170 align:middle line:84%
and I'll include in that virus--

61
02:12.170 --> 02:15.500 align:middle line:90%
protection that can be
enforced via the policy.

62
02:15.500 --> 02:18.710 align:middle line:90%
Another benefit is identity
management, both the identity

63
02:18.710 --> 02:21.560 align:middle line:90%
of that mobile device based
on certain characteristics

64
02:21.560 --> 02:24.320 align:middle line:90%
as it connects, including the
identity of the user using it.

65
02:24.320 --> 02:27.350 align:middle line:90%
Perhaps part of our policy is
multifactor authentication.

66
02:27.350 --> 02:29.240 align:middle line:90%
And with a smart
device, the user

67
02:29.240 --> 02:32.750 align:middle line:90%
can provide two different
factors, such as their password
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:29.240 --> 02:32.750 align:middle line:90%
can provide two different
factors, such as their password

68
02:32.750 --> 02:34.512 align:middle line:90%
and also a picture
of their face,

69
02:34.512 --> 02:35.720 align:middle line:84%
which is something they have.

70
02:35.720 --> 02:38.540 align:middle line:90%
We'll take a closer look at
multifactor authentication

71
02:38.540 --> 02:39.433 align:middle line:84%
in a separate video.

72
02:39.433 --> 02:40.850 align:middle line:90%
And the great news
here is that we

73
02:40.850 --> 02:43.800 align:middle line:90%
can enforce that via our mobile
device management system.

74
02:43.800 --> 02:45.890 align:middle line:90%
Another great option
is provisioning.

75
02:45.890 --> 02:47.348 align:middle line:90%
If you've ever set
up a new device,

76
02:47.348 --> 02:49.390 align:middle line:90%
there's a lot of things
that can be gone through,

77
02:49.390 --> 02:51.060 align:middle line:90%
a lot of choices
that have to be made.

78
02:51.060 --> 02:53.180 align:middle line:90%
And if we have a mobile
device management system,

79
02:53.180 --> 02:55.370 align:middle line:90%
the provisioning based
on our security policies

80
02:55.370 --> 02:56.845 align:middle line:84%
can be automated and routine.

81
02:56.845 --> 02:58.220 align:middle line:90%
And that way we're
not forgetting

82
02:58.220 --> 02:59.510 align:middle line:84%
this step or that step.

83
02:59.510 --> 03:02.180 align:middle line:90%
And we're locking down
the more risky apps
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
02:59.510 --> 03:02.180 align:middle line:90%
And we're locking down
the more risky apps

84
03:02.180 --> 03:03.560 align:middle line:84%
or the risky services.

85
03:03.560 --> 03:06.500 align:middle line:90%
And we're forcing consistently
the options such as encryption

86
03:06.500 --> 03:07.730 align:middle line:84%
for the data protection.

87
03:07.730 --> 03:10.310 align:middle line:90%
And one of the benefits
of having a system

88
03:10.310 --> 03:12.200 align:middle line:90%
is that we can have
templates, which

89
03:12.200 --> 03:14.840 align:middle line:90%
is a generic concept for
doing something the same way

90
03:14.840 --> 03:15.990 align:middle line:84%
every single time.

91
03:15.990 --> 03:19.400 align:middle line:90%
So if we have a platform
service policy that

92
03:19.400 --> 03:21.740 align:middle line:90%
says every iPhone
gets treated this way,

93
03:21.740 --> 03:23.810 align:middle line:90%
every Android device
gets treated that way,

94
03:23.810 --> 03:25.910 align:middle line:90%
every tablet gets
treated the other way,

95
03:25.910 --> 03:28.070 align:middle line:90%
by using the same
templates, the same config

96
03:28.070 --> 03:30.740 align:middle line:90%
and having the same consistent
policy across the same type
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:28.070 --> 03:30.740 align:middle line:90%
and having the same consistent
policy across the same type

97
03:30.740 --> 03:33.082 align:middle line:90%
of devices, that's going to
help not only our security,

98
03:33.082 --> 03:35.540 align:middle line:90%
but it's also going to help in
the support of those devices

99
03:35.540 --> 03:37.880 align:middle line:90%
because they're all acting
and behaving the same way.

100
03:37.880 --> 03:41.120 align:middle line:90%
And I did a Google search
for MDM platform comparison.

101
03:41.120 --> 03:43.100 align:middle line:90%
And there's lots of
hits that came up,

102
03:43.100 --> 03:44.542 align:middle line:84%
including a lot of ads.

103
03:44.542 --> 03:47.000 align:middle line:90%
Here's one from TrustRadius
that I thought was interesting.

104
03:47.000 --> 03:49.650 align:middle line:90%
So if we scroll
down to products,

105
03:49.650 --> 03:52.130 align:middle line:90%
here's a list of vendors that
do mobile device management.

106
03:52.130 --> 03:54.770 align:middle line:90%
So as we scroll down,
here's a very popular one,

107
03:54.770 --> 03:57.620 align:middle line:90%
Microsoft's Intune, in
conjunction with System Center

108
03:57.620 --> 03:58.640 align:middle line:84%
Configuration Manager.

109
03:58.640 --> 04:02.360 align:middle line:90%
And as we scroll down,
here's AirWatch by VMware.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
03:58.640 --> 04:02.360 align:middle line:90%
And as we scroll down,
here's AirWatch by VMware.

110
04:02.360 --> 04:04.010 align:middle line:84%
There's a solution from IBM.

111
04:04.010 --> 04:06.770 align:middle line:90%
There's a solution from Cisco
as part of their Meraki suite,

112
04:06.770 --> 04:08.840 align:middle line:90%
called the Meraki
Systems Manager.

113
04:08.840 --> 04:10.167 align:middle line:84%
And the list goes on.

114
04:10.167 --> 04:11.750 align:middle line:90%
In this video, we
took a look at a few

115
04:11.750 --> 04:14.485 align:middle line:90%
of the benefits of a mobile
device management system,

116
04:14.485 --> 04:16.519 align:middle line:90%
including on these
smart devices that

117
04:16.519 --> 04:19.150 align:middle line:90%
have the ability to use a
camera to do multifactor

118
04:19.150 --> 04:19.775 align:middle line:84%
authentication.

119
04:19.775 --> 04:20.870 align:middle line:84%
And you know what?

120
04:20.870 --> 04:22.970 align:middle line:90%
In the next video, let's
take a little bit more

121
04:22.970 --> 04:24.710 align:middle line:90%
time and confirm
that we understand

122
04:24.710 --> 04:27.200 align:middle line:90%
what that is, what is
multifactor authentication,

123
04:27.200 --> 04:29.180 align:middle line:90%
and how we can
leverage it to improve

124
04:29.180 --> 04:32.070 align:middle line:90%
the security of our
endpoints in our networks.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
04:29.180 --> 04:32.070 align:middle line:90%
the security of our
endpoints in our networks.

125
04:32.070 --> 04:34.530 align:middle line:90%
So I'll see you in that
next video in just a moment.

126
04:34.530 --> 04:36.890 align:middle line:90%
Meanwhile, I hope this has
been informative for you.

127
04:36.890 --> 04:40.300 align:middle line:90%
And I'd like to thank
you for viewing.