Now the last thing that we're going to cover
isn't necessarily an objective that we
have to know for an exam environment.
But it's an important one to know
if you're actually going to be working for AMP for Endpoints.
This is where we apply our intent
to the endpoints themselves.
This is the policies.
So we set up all of the outbreak controls.
And then we need to push what do we intend for our endpoints
to do via policies.
Let's explore how policies work in the AMP for Endpoints board.
Now it's time for the rubber to meet the road. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now it's time for the rubber to meet the road.
We've gone through outbreak controls.
We've talked about how we can permit or deny
applications, as well as files or even IP addresses.
How do we push this down to the specific end users
that we care about?
What we're really talking about here
is setting up groups of users or endpoints
and then policies that encompass all of these items together.
Let's explore how this works from the portal.
What we're doing is we're going into the Management section.
And the first thing that I want to set up is the computers. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the first thing that I want to set up is the computers.
Computers are basically what we install our application on.
When you install AMP for Endpoints on a computer,
this is what it shows up as.
We see computers.
And we see different kinds of computers here, don't we?
We can see the little Apple symbol.
We can see the Windows symbol.
If I scroll down, we see a little iPhone symbol.
And that denotes what kind of operating systems
are we working in.
If I expand this down, we can see specific info
about these computers.
We can see when was this application installed?
What operating system is it running? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
What operating system is it running?
So the first thing you need to know
is we need to just install AMP for Endpoints on computers.
And then they report back to our portal,
showing up as a computer that we can push policies down to.
Next, we need to have groups of users.
For instance, which users are going
to be using which computer?
Now, groups can be nested.
And that's what you're seeing here.
We have this total Company ABC end user group.
And if I expand the child groups,
we see we've got marketing users, engineering users, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we see we've got marketing users, engineering users,
management users, the domain controllers.
You get the idea.
When I click on marketing users here, I can scroll down.
And I can see these three computers
belong to marketing users.
So when I want to push my intent down to my specific end users
like the marketing users, that's going
to be pushing these restrictions and outbreak control
items that we configured down to these three computers.
Now, the glue that brings all of this together is the policy. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, the glue that brings all of this together is the policy.
This is where everything can go, oh, OK.
I get it.
Let's take a look at the info policy item right here.
When I expand this down, this is where
you can see what's going on.
The first thing to draw your attention to is groups.
We see we've got our marketing users, which
contains three computers.
Engineering users contains two computers.
The end users contains 10.
Management users contains 11.
So this policy is going to impact these groups of users WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this policy is going to impact these groups of users
and those computers.
And what does this policy do?
Well, look.
Here's the outbreak control section.
We have our simple detection right here, a quarantine list.
We have advanced detections here.
We have the application controls.
We see putty is blocked.
And then we see the IP addresses that are blocked or allowed
right here.
So for instance, engineering users
will not be able to access the GUI front end of CUCM.
And I can do things like click Edit here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I can do things like click Edit here.
And we can jump into outbreak control
and change the outbreak control to my CBT demo,
so that it blocked my nuclear virus Excel file.
And I'll click Save.
Now, the big thing to note there is I
can't select multiple outbreak controls.
We'd have to duplicate other policies
if we want to add on to it.
But now when I go back into info policy two,
I see that this policy right here is being pushed down
to these end users.
This is my outbreak control that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This is my outbreak control that's
now CBT demo, which is my nuclear virus item.
And I still maintain the exact same other outbreak controls
that we specified above.
So this is where the rubber meets the road.
We can say when certain end users meet a certain profile,
like Windows devices, this is the policies or outbreak
control items that they should have.
If a different group of end users
are using different objects or items,
like engineering users are using iPhones or Android devices,
this is the group of outbreak controls that they should have. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this is the group of outbreak controls that they should have.
It's very granular, and we have a lot
of control over how we can protect
all of the various types of endpoints
within our environment.
So that's been introducing how we can actually push down
all of these outbreak controls using computers, groups,
and policies.
I hope this has been informative for you,
and I'd like to thank you for viewing.