WEBVTT

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


2
00:00.030 --> 00:01.863 align:middle line:90%
Now the last thing that
we're going to cover

3
00:01.863 --> 00:04.380 align:middle line:90%
isn't necessarily
an objective that we

4
00:04.380 --> 00:06.570 align:middle line:90%
have to know for an
exam environment.

5
00:06.570 --> 00:08.310 align:middle line:90%
But it's an
important one to know

6
00:08.310 --> 00:11.070 align:middle line:90%
if you're actually going to be
working for AMP for Endpoints.

7
00:11.070 --> 00:14.430 align:middle line:90%
This is where we
apply our intent

8
00:14.430 --> 00:15.840 align:middle line:84%
to the endpoints themselves.

9
00:15.840 --> 00:17.250 align:middle line:84%
This is the policies.

10
00:17.250 --> 00:19.440 align:middle line:90%
So we set up all of
the outbreak controls.

11
00:19.440 --> 00:23.040 align:middle line:90%
And then we need to push what
do we intend for our endpoints

12
00:23.040 --> 00:24.930 align:middle line:84%
to do via policies.

13
00:24.930 --> 00:28.443 align:middle line:90%
Let's explore how policies work
in the AMP for Endpoints board.

14
00:28.443 --> 00:30.360 align:middle line:90%
Now it's time for the
rubber to meet the road.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:28.443 --> 00:30.360 align:middle line:90%
Now it's time for the
rubber to meet the road.

15
00:30.360 --> 00:32.580 align:middle line:90%
We've gone through
outbreak controls.

16
00:32.580 --> 00:34.830 align:middle line:90%
We've talked about how
we can permit or deny

17
00:34.830 --> 00:39.010 align:middle line:90%
applications, as well as
files or even IP addresses.

18
00:39.010 --> 00:42.150 align:middle line:90%
How do we push this down
to the specific end users

19
00:42.150 --> 00:43.170 align:middle line:84%
that we care about?

20
00:43.170 --> 00:44.760 align:middle line:90%
What we're really
talking about here

21
00:44.760 --> 00:47.790 align:middle line:90%
is setting up groups
of users or endpoints

22
00:47.790 --> 00:51.600 align:middle line:90%
and then policies that encompass
all of these items together.

23
00:51.600 --> 00:54.360 align:middle line:90%
Let's explore how this
works from the portal.

24
00:54.360 --> 00:57.120 align:middle line:90%
What we're doing is we're going
into the Management section.

25
00:57.120 --> 01:00.270 align:middle line:90%
And the first thing that I want
to set up is the computers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:57.120 --> 01:00.270 align:middle line:90%
And the first thing that I want
to set up is the computers.

26
01:00.270 --> 01:04.739 align:middle line:90%
Computers are basically what
we install our application on.

27
01:04.739 --> 01:08.190 align:middle line:90%
When you install AMP for
Endpoints on a computer,

28
01:08.190 --> 01:09.660 align:middle line:84%
this is what it shows up as.

29
01:09.660 --> 01:11.070 align:middle line:84%
We see computers.

30
01:11.070 --> 01:13.980 align:middle line:90%
And we see different kinds
of computers here, don't we?

31
01:13.980 --> 01:15.510 align:middle line:90%
We can see the
little Apple symbol.

32
01:15.510 --> 01:16.960 align:middle line:84%
We can see the Windows symbol.

33
01:16.960 --> 01:19.170 align:middle line:90%
If I scroll down, we see
a little iPhone symbol.

34
01:19.170 --> 01:21.510 align:middle line:90%
And that denotes what
kind of operating systems

35
01:21.510 --> 01:22.740 align:middle line:84%
are we working in.

36
01:22.740 --> 01:25.620 align:middle line:90%
If I expand this down,
we can see specific info

37
01:25.620 --> 01:26.790 align:middle line:84%
about these computers.

38
01:26.790 --> 01:29.850 align:middle line:90%
We can see when was this
application installed?

39
01:29.850 --> 01:31.962 align:middle line:90%
What operating
system is it running?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.850 --> 01:31.962 align:middle line:90%
What operating
system is it running?

40
01:31.962 --> 01:33.420 align:middle line:90%
So the first thing
you need to know

41
01:33.420 --> 01:37.170 align:middle line:90%
is we need to just install AMP
for Endpoints on computers.

42
01:37.170 --> 01:39.240 align:middle line:90%
And then they report
back to our portal,

43
01:39.240 --> 01:42.720 align:middle line:90%
showing up as a computer that
we can push policies down to.

44
01:42.720 --> 01:45.540 align:middle line:90%
Next, we need to
have groups of users.

45
01:45.540 --> 01:47.880 align:middle line:90%
For instance, which
users are going

46
01:47.880 --> 01:49.410 align:middle line:84%
to be using which computer?

47
01:49.410 --> 01:50.982 align:middle line:84%
Now, groups can be nested.

48
01:50.982 --> 01:52.440 align:middle line:90%
And that's what
you're seeing here.

49
01:52.440 --> 01:55.890 align:middle line:90%
We have this total Company
ABC end user group.

50
01:55.890 --> 01:57.570 align:middle line:90%
And if I expand
the child groups,

51
01:57.570 --> 02:00.810 align:middle line:90%
we see we've got marketing
users, engineering users,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:57.570 --> 02:00.810 align:middle line:90%
we see we've got marketing
users, engineering users,

52
02:00.810 --> 02:03.210 align:middle line:90%
management users, the
domain controllers.

53
02:03.210 --> 02:04.320 align:middle line:84%
You get the idea.

54
02:04.320 --> 02:07.560 align:middle line:90%
When I click on marketing
users here, I can scroll down.

55
02:07.560 --> 02:10.889 align:middle line:90%
And I can see these
three computers

56
02:10.889 --> 02:13.420 align:middle line:84%
belong to marketing users.

57
02:13.420 --> 02:18.540 align:middle line:90%
So when I want to push my intent
down to my specific end users

58
02:18.540 --> 02:20.760 align:middle line:90%
like the marketing
users, that's going

59
02:20.760 --> 02:24.570 align:middle line:90%
to be pushing these restrictions
and outbreak control

60
02:24.570 --> 02:28.080 align:middle line:90%
items that we configured down
to these three computers.

61
02:28.080 --> 02:32.050 align:middle line:90%
Now, the glue that brings all
of this together is the policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:28.080 --> 02:32.050 align:middle line:90%
Now, the glue that brings all
of this together is the policy.

62
02:32.050 --> 02:34.450 align:middle line:90%
This is where everything
can go, oh, OK.

63
02:34.450 --> 02:35.190 align:middle line:84%
I get it.

64
02:35.190 --> 02:38.640 align:middle line:90%
Let's take a look at the
info policy item right here.

65
02:38.640 --> 02:41.040 align:middle line:90%
When I expand this
down, this is where

66
02:41.040 --> 02:42.850 align:middle line:84%
you can see what's going on.

67
02:42.850 --> 02:45.720 align:middle line:90%
The first thing to draw
your attention to is groups.

68
02:45.720 --> 02:48.270 align:middle line:90%
We see we've got our
marketing users, which

69
02:48.270 --> 02:50.160 align:middle line:84%
contains three computers.

70
02:50.160 --> 02:52.740 align:middle line:90%
Engineering users
contains two computers.

71
02:52.740 --> 02:54.570 align:middle line:84%
The end users contains 10.

72
02:54.570 --> 02:56.670 align:middle line:84%
Management users contains 11.

73
02:56.670 --> 03:01.500 align:middle line:90%
So this policy is going to
impact these groups of users
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:56.670 --> 03:01.500 align:middle line:90%
So this policy is going to
impact these groups of users

74
03:01.500 --> 03:02.940 align:middle line:84%
and those computers.

75
03:02.940 --> 03:04.800 align:middle line:84%
And what does this policy do?

76
03:04.800 --> 03:05.370 align:middle line:84%
Well, look.

77
03:05.370 --> 03:07.740 align:middle line:90%
Here's the outbreak
control section.

78
03:07.740 --> 03:12.120 align:middle line:90%
We have our simple detection
right here, a quarantine list.

79
03:12.120 --> 03:14.700 align:middle line:90%
We have advanced
detections here.

80
03:14.700 --> 03:16.380 align:middle line:90%
We have the
application controls.

81
03:16.380 --> 03:18.750 align:middle line:84%
We see putty is blocked.

82
03:18.750 --> 03:22.830 align:middle line:90%
And then we see the IP addresses
that are blocked or allowed

83
03:22.830 --> 03:23.740 align:middle line:84%
right here.

84
03:23.740 --> 03:25.710 align:middle line:90%
So for instance,
engineering users

85
03:25.710 --> 03:29.760 align:middle line:90%
will not be able to access
the GUI front end of CUCM.

86
03:29.760 --> 03:32.220 align:middle line:90%
And I can do things
like click Edit here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:29.760 --> 03:32.220 align:middle line:90%
And I can do things
like click Edit here.

87
03:32.220 --> 03:34.710 align:middle line:90%
And we can jump into
outbreak control

88
03:34.710 --> 03:37.740 align:middle line:90%
and change the outbreak
control to my CBT demo,

89
03:37.740 --> 03:41.220 align:middle line:90%
so that it blocked my
nuclear virus Excel file.

90
03:41.220 --> 03:42.600 align:middle line:84%
And I'll click Save.

91
03:42.600 --> 03:44.190 align:middle line:90%
Now, the big thing
to note there is I

92
03:44.190 --> 03:46.770 align:middle line:90%
can't select multiple
outbreak controls.

93
03:46.770 --> 03:49.110 align:middle line:90%
We'd have to duplicate
other policies

94
03:49.110 --> 03:50.850 align:middle line:84%
if we want to add on to it.

95
03:50.850 --> 03:53.550 align:middle line:90%
But now when I go back
into info policy two,

96
03:53.550 --> 03:57.060 align:middle line:90%
I see that this policy right
here is being pushed down

97
03:57.060 --> 03:58.600 align:middle line:84%
to these end users.

98
03:58.600 --> 04:00.540 align:middle line:90%
This is my outbreak
control that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
03:58.600 --> 04:00.540 align:middle line:90%
This is my outbreak
control that's

99
04:00.540 --> 04:03.450 align:middle line:90%
now CBT demo, which is
my nuclear virus item.

100
04:03.450 --> 04:06.510 align:middle line:90%
And I still maintain the exact
same other outbreak controls

101
04:06.510 --> 04:07.920 align:middle line:84%
that we specified above.

102
04:07.920 --> 04:10.420 align:middle line:90%
So this is where the
rubber meets the road.

103
04:10.420 --> 04:14.460 align:middle line:90%
We can say when certain end
users meet a certain profile,

104
04:14.460 --> 04:18.120 align:middle line:90%
like Windows devices, this
is the policies or outbreak

105
04:18.120 --> 04:20.100 align:middle line:90%
control items that
they should have.

106
04:20.100 --> 04:21.899 align:middle line:90%
If a different
group of end users

107
04:21.899 --> 04:24.450 align:middle line:90%
are using different
objects or items,

108
04:24.450 --> 04:28.900 align:middle line:90%
like engineering users are using
iPhones or Android devices,

109
04:28.900 --> 04:32.790 align:middle line:90%
this is the group of outbreak
controls that they should have.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
04:28.900 --> 04:32.790 align:middle line:90%
this is the group of outbreak
controls that they should have.

110
04:32.790 --> 04:34.860 align:middle line:90%
It's very granular,
and we have a lot

111
04:34.860 --> 04:37.020 align:middle line:90%
of control over
how we can protect

112
04:37.020 --> 04:39.210 align:middle line:90%
all of the various
types of endpoints

113
04:39.210 --> 04:40.870 align:middle line:84%
within our environment.

114
04:40.870 --> 04:44.010 align:middle line:90%
So that's been introducing
how we can actually push down

115
04:44.010 --> 04:47.160 align:middle line:90%
all of these outbreak controls
using computers, groups,

116
04:47.160 --> 04:48.002 align:middle line:84%
and policies.

117
04:48.002 --> 04:49.710 align:middle line:90%
I hope this has been
informative for you,

118
04:49.710 --> 04:52.130 align:middle line:90%
and I'd like to thank
you for viewing.