WEBVTT

00:00:00.000 --> 00:00:03.450 align:middle line:90%


00:00:03.450 --> 00:00:04.510 align:middle line:90%
Hi.

00:00:04.510 --> 00:00:07.770 align:middle line:84%
Welcome to this individual
lesson on Active Directory

00:00:07.770 --> 00:00:08.850 align:middle line:90%
Tiering.

00:00:08.850 --> 00:00:12.060 align:middle line:84%
This is the second video
in a series of two.

00:00:12.060 --> 00:00:15.420 align:middle line:84%
For the first part, we looked
at Active Directory Tiering

00:00:15.420 --> 00:00:17.230 align:middle line:90%
and the theory behind it.

00:00:17.230 --> 00:00:19.800 align:middle line:84%
While in this part, we'll look
into the actual implementation

00:00:19.800 --> 00:00:20.810 align:middle line:90%
of this.

00:00:20.810 --> 00:00:24.105 align:middle line:84%
I'll begin by a short
demonstration, or rather

00:00:24.105 --> 00:00:27.720 align:middle line:84%
a drawing, just to make sure
that the theory is understood

00:00:27.720 --> 00:00:28.710 align:middle line:90%
by everyone.

00:00:28.710 --> 00:00:30.660 align:middle line:84%
Then we can move
into the environment

00:00:30.660 --> 00:00:34.140 align:middle line:84%
and do the practical
implementation.

00:00:34.140 --> 00:00:36.450 align:middle line:84%
What we were discussing
in the previous video

00:00:36.450 --> 00:00:39.970 align:middle line:84%
is that we'll take the
Microsoft approach with having

00:00:39.970 --> 00:00:41.700 align:middle line:90%
three tiers by default.

00:00:41.700 --> 00:00:44.100 align:middle line:84%
I have seen an environment
where the tiers can

00:00:44.100 --> 00:00:48.720 align:middle line:84%
grow quite a bit of up to
20, and that's really a lot.

00:00:48.720 --> 00:00:49.830 align:middle line:90%
Although, it gains--

00:00:49.830 --> 00:00:53.910 align:middle line:84%
Or gives, rather, a
next level security

00:00:53.910 --> 00:00:57.390 align:middle line:84%
against potential theft, because
you have different accounts

00:00:57.390 --> 00:00:59.500 align:middle line:90%
for different kind of access.

00:00:59.500 --> 00:01:01.980 align:middle line:84%
But if we take the
three tiers, we'll

00:01:01.980 --> 00:01:04.769 align:middle line:90%
represent them by drawing them.

00:01:04.769 --> 00:01:10.780 align:middle line:84%
And we'll have tier two at
the bottom, then tier one,

00:01:10.780 --> 00:01:13.840 align:middle line:90%
and tier zero is on the top.

00:01:13.840 --> 00:01:20.710 align:middle line:84%
You can think of these tiers
as somewhat a military based

00:01:20.710 --> 00:01:23.800 align:middle line:84%
ranking where we have
the generals on top

00:01:23.800 --> 00:01:26.110 align:middle line:84%
and the lower ranks
on the bottom.

00:01:26.110 --> 00:01:28.420 align:middle line:84%
And by default,
lower ranks are not

00:01:28.420 --> 00:01:32.290 align:middle line:84%
going to be able to go above
and talk to the generals,

00:01:32.290 --> 00:01:34.090 align:middle line:84%
while the generals
can give commands

00:01:34.090 --> 00:01:36.130 align:middle line:90%
to everyone underneath.

00:01:36.130 --> 00:01:38.950 align:middle line:84%
So what will the different
tiers representing?

00:01:38.950 --> 00:01:43.720 align:middle line:84%
In tier two, we're going to
have our most untrusted devices

00:01:43.720 --> 00:01:44.650 align:middle line:90%
and users.

00:01:44.650 --> 00:01:48.100 align:middle line:84%
So that would be
our workstations,

00:01:48.100 --> 00:01:54.700 align:middle line:84%
our regular users, this
is our normal employees

00:01:54.700 --> 00:01:56.932 align:middle line:90%
and their accounts.

00:01:56.932 --> 00:01:58.390 align:middle line:84%
And the reason why
we had them here

00:01:58.390 --> 00:02:03.070 align:middle line:84%
is because these are the ones
that are primarily phished,

00:02:03.070 --> 00:02:07.270 align:middle line:84%
or those of the users who
download and then exploit

00:02:07.270 --> 00:02:10.070 align:middle line:90%
malicious files, and so on.

00:02:10.070 --> 00:02:13.240 align:middle line:84%
We also have this
tier, the level

00:02:13.240 --> 00:02:15.350 align:middle line:90%
of administrative accounts.

00:02:15.350 --> 00:02:17.680 align:middle line:84%
So that would be
tier two admins.

00:02:17.680 --> 00:02:21.770 align:middle line:90%


00:02:21.770 --> 00:02:27.480 align:middle line:84%
This is representing users
workstations and also groups.

00:02:27.480 --> 00:02:32.680 align:middle line:84%
So each tier will have this
representation within it.

00:02:32.680 --> 00:02:36.260 align:middle line:84%
Now, if we should move
further in tier one,

00:02:36.260 --> 00:02:40.310 align:middle line:84%
we will consider tier one
to be our normal member

00:02:40.310 --> 00:02:43.390 align:middle line:90%
servers in the domain.

00:02:43.390 --> 00:02:45.880 align:middle line:84%
That would be also
the users that

00:02:45.880 --> 00:02:51.560 align:middle line:90%
have access to those servers.

00:02:51.560 --> 00:02:53.290 align:middle line:90%
So that is tier one users.

00:02:53.290 --> 00:02:57.340 align:middle line:84%
And we're also going to have
a bunch of different groups

00:02:57.340 --> 00:02:59.740 align:middle line:84%
which are going to
represent certain access

00:02:59.740 --> 00:03:00.560 align:middle line:90%
to those servers.

00:03:00.560 --> 00:03:03.430 align:middle line:84%
So for example, some users
might need local admin rights,

00:03:03.430 --> 00:03:07.540 align:middle line:84%
others just might need
more privileged rights.

00:03:07.540 --> 00:03:13.010 align:middle line:84%
So I would just say that we also
have some groups in this tier.

00:03:13.010 --> 00:03:17.360 align:middle line:84%
And finally, in tier zero,
we'll have our crown jewels

00:03:17.360 --> 00:03:18.920 align:middle line:90%
of our environment.

00:03:18.920 --> 00:03:24.350 align:middle line:84%
And if we take it as a general
approach towards organizations,

00:03:24.350 --> 00:03:27.680 align:middle line:84%
this is going to contain
our domain controllers,

00:03:27.680 --> 00:03:30.590 align:middle line:84%
our PKI infrastructure,
there is going

00:03:30.590 --> 00:03:35.270 align:middle line:84%
to be a WSUS for updates
of tier zero, and so on.

00:03:35.270 --> 00:03:39.770 align:middle line:84%
It will contain our tier zero
accounts, tier zero users,

00:03:39.770 --> 00:03:44.660 align:middle line:84%
which are going to be users such
as domain admins, enterprise

00:03:44.660 --> 00:03:47.570 align:middle line:84%
admins, and those
really privileged groups

00:03:47.570 --> 00:03:53.150 align:middle line:84%
who should only be allowed
to access our most important

00:03:53.150 --> 00:03:54.960 align:middle line:90%
assets in the environment.

00:03:54.960 --> 00:03:57.870 align:middle line:84%
So we will also have
those privileged groups.

00:03:57.870 --> 00:04:01.820 align:middle line:84%
And I would just say, for
example, that be domain admins.

00:04:01.820 --> 00:04:05.130 align:middle line:90%


00:04:05.130 --> 00:04:08.850 align:middle line:84%
Now, what we're
trying to display here

00:04:08.850 --> 00:04:11.100 align:middle line:90%
is this kind of categorization.

00:04:11.100 --> 00:04:13.560 align:middle line:84%
Because the lies
that we just drew,

00:04:13.560 --> 00:04:15.510 align:middle line:84%
we haven't really
enforced anything.

00:04:15.510 --> 00:04:17.190 align:middle line:84%
Right now, we're
just categorizing

00:04:17.190 --> 00:04:20.190 align:middle line:84%
what do we want to consider
as a different tier.

00:04:20.190 --> 00:04:22.050 align:middle line:84%
And to enforce the
tiers, we're going

00:04:22.050 --> 00:04:24.330 align:middle line:84%
to implement technical
controls that

00:04:24.330 --> 00:04:27.720 align:middle line:84%
are going to forbid one
tier from interacting

00:04:27.720 --> 00:04:30.038 align:middle line:84%
in another tier unless
they're allowed to.

00:04:30.038 --> 00:04:31.830 align:middle line:84%
So what we're going to
forbid, for example,

00:04:31.830 --> 00:04:37.260 align:middle line:84%
is that tier two users will not
be able to connect to tier one,

00:04:37.260 --> 00:04:40.160 align:middle line:84%
and they will also not be
able to connect to tier zero.

00:04:40.160 --> 00:04:42.240 align:middle line:84%
We will have a
technical control which

00:04:42.240 --> 00:04:46.440 align:middle line:84%
forbids every tier two users
from performing this action.

00:04:46.440 --> 00:04:50.130 align:middle line:84%
While on the other
hand, tier zero users,

00:04:50.130 --> 00:04:56.530 align:middle line:84%
they will not be able to connect
to other tiers in this design,

00:04:56.530 --> 00:04:58.750 align:middle line:84%
but they will able to
control the other teachers.

00:04:58.750 --> 00:05:01.330 align:middle line:84%
So they have direct
control over the tiers.

00:05:01.330 --> 00:05:04.250 align:middle line:90%


00:05:04.250 --> 00:05:07.700 align:middle line:84%
And now because we're going
to deny this connection where

00:05:07.700 --> 00:05:10.640 align:middle line:84%
tier zero account is connecting
to tier one or tier two

00:05:10.640 --> 00:05:13.340 align:middle line:84%
systems, that
means the tier zero

00:05:13.340 --> 00:05:15.050 align:middle line:84%
account credentials
are not going

00:05:15.050 --> 00:05:19.400 align:middle line:84%
to be cached in any other
tier except tier zero.

00:05:19.400 --> 00:05:22.010 align:middle line:90%
So if one tier goes down--

00:05:22.010 --> 00:05:26.000 align:middle line:84%
Or rather, if you look
from a risk based approach

00:05:26.000 --> 00:05:28.040 align:middle line:84%
towards this tiering
design, we'll

00:05:28.040 --> 00:05:32.030 align:middle line:84%
see that a worst case
scenario that can occur

00:05:32.030 --> 00:05:36.450 align:middle line:84%
is that a highly privileged tier
based account is compromised.

00:05:36.450 --> 00:05:38.870 align:middle line:84%
So for example, a
tier two admin might

00:05:38.870 --> 00:05:42.272 align:middle line:84%
get compromised that has
access to big part of tier two.

00:05:42.272 --> 00:05:43.730 align:middle line:84%
But the worst case
scenario in here

00:05:43.730 --> 00:05:47.210 align:middle line:84%
would be that only
tier two can go down

00:05:47.210 --> 00:05:48.920 align:middle line:84%
while the rest of
our environment

00:05:48.920 --> 00:05:50.610 align:middle line:90%
is actually still standing.

00:05:50.610 --> 00:05:53.480 align:middle line:84%
And now it's working, we
can reduce from that point.

00:05:53.480 --> 00:05:58.060 align:middle line:84%
It's not like we are losing
our interactive directory.

00:05:58.060 --> 00:06:00.505 align:middle line:84%
And what is better
even is that we

00:06:00.505 --> 00:06:04.030 align:middle line:84%
will assume that at
least one of our devices

00:06:04.030 --> 00:06:05.800 align:middle line:90%
can get compromised.

00:06:05.800 --> 00:06:07.990 align:middle line:84%
But with all of the
active directory

00:06:07.990 --> 00:06:10.610 align:middle line:84%
checks that we have discussed
so far in the course,

00:06:10.610 --> 00:06:14.620 align:middle line:84%
we'll try to make sure that, if
one workstation is compromised,

00:06:14.620 --> 00:06:18.940 align:middle line:84%
then the damage, or rather the
impact towards our environment

00:06:18.940 --> 00:06:22.690 align:middle line:84%
will be limited only to
that one workstation.

00:06:22.690 --> 00:06:25.750 align:middle line:84%
And it's going to be very
hard, or nearly impossible

00:06:25.750 --> 00:06:28.300 align:middle line:84%
for an attacker to move
away or move laterally

00:06:28.300 --> 00:06:33.150 align:middle line:84%
from that workstation into other
assets into the environment.

00:06:33.150 --> 00:06:36.030 align:middle line:84%
And for this tier model
to work really well,

00:06:36.030 --> 00:06:39.750 align:middle line:84%
what is really important
is device hardening.

00:06:39.750 --> 00:06:41.130 align:middle line:90%
And I'll give you an example.

00:06:41.130 --> 00:06:43.800 align:middle line:84%
Let's take tier
two workstations.

00:06:43.800 --> 00:06:46.210 align:middle line:84%
I'll draw two different
workstations in here.

00:06:46.210 --> 00:06:50.760 align:middle line:84%
So we're going to have
workstation one and workstation

00:06:50.760 --> 00:06:51.870 align:middle line:90%
two.

00:06:51.870 --> 00:06:54.450 align:middle line:84%
Let's assume that an
attacker from the internet

00:06:54.450 --> 00:06:57.520 align:middle line:90%
compromises workstation one.

00:06:57.520 --> 00:07:00.480 align:middle line:84%
Now, we will have this attacker
living into the workstation

00:07:00.480 --> 00:07:04.170 align:middle line:84%
and having full control
over this one workstation.

00:07:04.170 --> 00:07:07.020 align:middle line:84%
But because of the hardening
that we have performed,

00:07:07.020 --> 00:07:09.570 align:middle line:84%
or that we should
have performed,

00:07:09.570 --> 00:07:12.780 align:middle line:84%
this attacker will be running
a slow, privilege-less user.

00:07:12.780 --> 00:07:15.130 align:middle line:84%
Even if the attacker
escalates their privileges,

00:07:15.130 --> 00:07:16.920 align:middle line:84%
there will be nothing
on this machine

00:07:16.920 --> 00:07:20.410 align:middle line:84%
that they can steal to move
laterally to other machines.

00:07:20.410 --> 00:07:23.280 align:middle line:84%
For example, the built-in
administrator accounts password

00:07:23.280 --> 00:07:26.530 align:middle line:84%
is going to be unique by
using Labs in our environment.

00:07:26.530 --> 00:07:29.850 align:middle line:84%
So each device will have
its unique Labs password.

00:07:29.850 --> 00:07:33.270 align:middle line:84%
Furthermore, what we could do
as an action, and something

00:07:33.270 --> 00:07:36.180 align:middle line:84%
that I usually recommend,
is that every workstation,

00:07:36.180 --> 00:07:41.240 align:middle line:84%
every device in tier two,
should have its built-in Windows

00:07:41.240 --> 00:07:44.800 align:middle line:84%
Firewall configured to
deny incoming connections

00:07:44.800 --> 00:07:47.820 align:middle line:84%
unless they're coming
from a management server,

00:07:47.820 --> 00:07:51.070 align:middle line:84%
or they can just deny all
connections completely.

00:07:51.070 --> 00:07:53.820 align:middle line:84%
So if we take workstation
two, for example,

00:07:53.820 --> 00:07:55.500 align:middle line:84%
what we could
perform, if we assume

00:07:55.500 --> 00:07:57.420 align:middle line:90%
that this is the firewall.

00:07:57.420 --> 00:08:00.030 align:middle line:84%
The firewall will
just simply block

00:08:00.030 --> 00:08:09.430 align:middle line:84%
connections that are over
SMB, over WMI, over PowerShell

00:08:09.430 --> 00:08:12.580 align:middle line:90%
Remoting, and over RDP.

00:08:12.580 --> 00:08:15.180 align:middle line:90%


00:08:15.180 --> 00:08:18.660 align:middle line:84%
So in the case of this,
even if an attacker

00:08:18.660 --> 00:08:21.360 align:middle line:84%
was to compromise
the privileged user,

00:08:21.360 --> 00:08:24.900 align:middle line:84%
they have no ability to move
laterally in the environment

00:08:24.900 --> 00:08:28.110 align:middle line:84%
because none of our devices
will accept that connection.

00:08:28.110 --> 00:08:31.740 align:middle line:84%
So just on network level
alone, even if an attacker

00:08:31.740 --> 00:08:33.829 align:middle line:84%
had those credentials,
they can't move laterally

00:08:33.829 --> 00:08:35.039 align:middle line:90%
in our workstations.

00:08:35.039 --> 00:08:38.100 align:middle line:84%
And this is where we can
really see how hardening

00:08:38.100 --> 00:08:39.960 align:middle line:90%
can shine to our workstations.

00:08:39.960 --> 00:08:43.230 align:middle line:84%
But if an attacker was to
compromise that workstation

00:08:43.230 --> 00:08:45.100 align:middle line:84%
and we have actual
logging on it,

00:08:45.100 --> 00:08:48.150 align:middle line:84%
we will be able to see that
the attacker is performing

00:08:48.150 --> 00:08:50.010 align:middle line:84%
all kind of
reconnaissance actions

00:08:50.010 --> 00:08:52.020 align:middle line:84%
that he's trying to
connect to workstations.

00:08:52.020 --> 00:08:55.140 align:middle line:84%
And even though that connections
will be unsuccessful,

00:08:55.140 --> 00:08:56.640 align:middle line:90%
we'll still be able to see that.

00:08:56.640 --> 00:08:58.320 align:middle line:84%
And that's going to
be a very easy way

00:08:58.320 --> 00:09:03.610 align:middle line:84%
for us to identify that there's
attackers into the environment.

00:09:03.610 --> 00:09:06.480 align:middle line:84%
And I hope that this tiering
model actually, really

00:09:06.480 --> 00:09:08.340 align:middle line:84%
starts to make sense
now, especially when we

00:09:08.340 --> 00:09:10.140 align:middle line:90%
can see it drawn like this.

00:09:10.140 --> 00:09:12.240 align:middle line:90%
It's a really simple concept.

00:09:12.240 --> 00:09:15.010 align:middle line:84%
But just the ability to
deny accounts to move around

00:09:15.010 --> 00:09:18.550 align:middle line:84%
different category
systems, for example,

00:09:18.550 --> 00:09:20.940 align:middle line:84%
from trusted to
non-trusted, it will really

00:09:20.940 --> 00:09:24.510 align:middle line:84%
prevent this from the credential
theft of privileged users.

00:09:24.510 --> 00:09:28.230 align:middle line:84%
Now, in order to achieve this
tiering, one way to do it

00:09:28.230 --> 00:09:30.420 align:middle line:84%
is by using Group
Policy Objects.

00:09:30.420 --> 00:09:33.540 align:middle line:84%
And that is probably the most
common way of seeing companies

00:09:33.540 --> 00:09:35.880 align:middle line:90%
doing it across the world.

00:09:35.880 --> 00:09:38.880 align:middle line:84%
But what we need to be aware
of is that, to achieve this,

00:09:38.880 --> 00:09:40.860 align:middle line:84%
we need to have some
kind of consistency

00:09:40.860 --> 00:09:43.260 align:middle line:90%
in our organizational units.

00:09:43.260 --> 00:09:47.580 align:middle line:84%
Because consistent OUs is going
to be much easier to actually

00:09:47.580 --> 00:09:50.860 align:middle line:84%
push and define
different things.

00:09:50.860 --> 00:09:53.580 align:middle line:84%
And one thing that I
really want to show now

00:09:53.580 --> 00:09:56.490 align:middle line:84%
is an example of
how we can structure

00:09:56.490 --> 00:10:02.640 align:middle line:84%
our organizational units to have
a predefined OUs and different

00:10:02.640 --> 00:10:04.920 align:middle line:84%
tiers and naming
conventions, so we

00:10:04.920 --> 00:10:06.750 align:middle line:84%
can follow all those
naming conventions

00:10:06.750 --> 00:10:09.380 align:middle line:90%
across the different tiers.

00:10:09.380 --> 00:10:12.080 align:middle line:84%
So let's just look
into tier two.

00:10:12.080 --> 00:10:14.080 align:middle line:84%
I'll just give this
example, and then we

00:10:14.080 --> 00:10:16.870 align:middle line:84%
can see the full
implementation once we

00:10:16.870 --> 00:10:18.230 align:middle line:90%
move on to the environment.

00:10:18.230 --> 00:10:21.460 align:middle line:84%
But this is just so you get the
brief overview before we just

00:10:21.460 --> 00:10:23.810 align:middle line:84%
start showing the
technical stuff behind it.

00:10:23.810 --> 00:10:26.020 align:middle line:84%
So if we look into
an OU, everything

00:10:26.020 --> 00:10:29.330 align:middle line:84%
that is rectangular in this
diagram is going to be an OU.

00:10:29.330 --> 00:10:34.650 align:middle line:84%
So we'll start by
looking at tier two OU.

00:10:34.650 --> 00:10:37.730 align:middle line:84%
So we're going to have
an OU called tier two.

00:10:37.730 --> 00:10:42.660 align:middle line:84%
And inside this tier two
OU, we can create a few more

00:10:42.660 --> 00:10:45.110 align:middle line:90%
OUs in the structure.

00:10:45.110 --> 00:10:49.620 align:middle line:84%
Where we're going
to have accounts,

00:10:49.620 --> 00:10:54.940 align:middle line:84%
we are going to
have also groups,

00:10:54.940 --> 00:11:01.710 align:middle line:84%
and we're also going to have
workstations for our devices.

00:11:01.710 --> 00:11:04.760 align:middle line:84%
Now, we can expand
this even further.

00:11:04.760 --> 00:11:09.650 align:middle line:84%
In accounts, we can have a
new OU for internal users.

00:11:09.650 --> 00:11:12.290 align:middle line:90%


00:11:12.290 --> 00:11:17.000 align:middle line:84%
Then we can have an
OU for external users.

00:11:17.000 --> 00:11:20.210 align:middle line:90%
Another one for disabled users.

00:11:20.210 --> 00:11:24.380 align:middle line:84%
And perhaps, one for
privileged users.

00:11:24.380 --> 00:11:29.450 align:middle line:84%
This would be privileged
users within tier two.

00:11:29.450 --> 00:11:32.390 align:middle line:84%
Then in our groups,
we will end up

00:11:32.390 --> 00:11:37.040 align:middle line:84%
having groups that are
defined for applications.

00:11:37.040 --> 00:11:40.250 align:middle line:84%
And this is rather
uncommon for tier two,

00:11:40.250 --> 00:11:41.840 align:middle line:84%
because we expect
our applications

00:11:41.840 --> 00:11:44.732 align:middle line:84%
to be running in tier one,
on our member servers.

00:11:44.732 --> 00:11:46.940 align:middle line:84%
But it could be the case
that we have something going

00:11:46.940 --> 00:11:48.315 align:middle line:84%
on the workstations,
and you want

00:11:48.315 --> 00:11:50.750 align:middle line:84%
to define it and
structure it in here.

00:11:50.750 --> 00:11:53.240 align:middle line:84%
For other groups, we will
also have groups that

00:11:53.240 --> 00:11:55.740 align:middle line:90%
provide local admin access.

00:11:55.740 --> 00:11:57.530 align:middle line:90%
So local admin.

00:11:57.530 --> 00:12:01.250 align:middle line:84%
This would be a unique
group for each workstation,

00:12:01.250 --> 00:12:03.533 align:middle line:90%
and this is easy to script.

00:12:03.533 --> 00:12:04.950 align:middle line:84%
But generally,
this is going to be

00:12:04.950 --> 00:12:07.220 align:middle line:84%
a unique group for each
workstation that is

00:12:07.220 --> 00:12:09.110 align:middle line:90%
managed from Active Directory.

00:12:09.110 --> 00:12:11.745 align:middle line:84%
Then you can manage
which local admin

00:12:11.745 --> 00:12:15.410 align:middle line:84%
on which device will cause
the entire environment, simply

00:12:15.410 --> 00:12:18.560 align:middle line:84%
from managing it only in
Active Directory itself.

00:12:18.560 --> 00:12:20.150 align:middle line:90%
So if you want to add someone--

00:12:20.150 --> 00:12:21.540 align:middle line:90%
Let's take an example.

00:12:21.540 --> 00:12:25.380 align:middle line:84%
If we have a device in our
environment called Workstation

00:12:25.380 --> 00:12:27.060 align:middle line:90%
001.

00:12:27.060 --> 00:12:29.400 align:middle line:84%
And then the group
under local admin

00:12:29.400 --> 00:12:33.145 align:middle line:84%
is going to be the host name of
the device underscore admins.

00:12:33.145 --> 00:12:36.000 align:middle line:90%


00:12:36.000 --> 00:12:39.870 align:middle line:84%
So if we want to add someone to
be local admin on Workstation

00:12:39.870 --> 00:12:43.440 align:middle line:84%
001, we simply have to modify
only this group and add

00:12:43.440 --> 00:12:44.700 align:middle line:90%
the user inside.

00:12:44.700 --> 00:12:48.210 align:middle line:84%
And we have the ability
to do this centrally.

00:12:48.210 --> 00:12:50.640 align:middle line:84%
And this is great, as
you will see later.

00:12:50.640 --> 00:12:53.190 align:middle line:84%
Now, under the new
OU of workstations,

00:12:53.190 --> 00:12:55.020 align:middle line:90%
we can create other OUs.

00:12:55.020 --> 00:12:57.180 align:middle line:84%
Depending on how big
our organization is,

00:12:57.180 --> 00:13:00.670 align:middle line:84%
we might need to even divide
this even further into say,

00:13:00.670 --> 00:13:02.100 align:middle line:90%
for example, countries.

00:13:02.100 --> 00:13:06.420 align:middle line:84%
So we can have Denmark,
we can have UK, and so on.

00:13:06.420 --> 00:13:07.860 align:middle line:90%
U.S.

00:13:07.860 --> 00:13:09.660 align:middle line:84%
And if our organization
is that big,

00:13:09.660 --> 00:13:12.750 align:middle line:84%
we might also need to split
our internal employees

00:13:12.750 --> 00:13:14.070 align:middle line:90%
based on countries.

00:13:14.070 --> 00:13:17.010 align:middle line:84%
And doing this will
give us the ability

00:13:17.010 --> 00:13:21.060 align:middle line:84%
to push out certain GPO
restrictions per country.

00:13:21.060 --> 00:13:24.150 align:middle line:84%
It all depends on how deep
we want to go with this.

00:13:24.150 --> 00:13:29.620 align:middle line:84%
But good structure
is always beneficial.

00:13:29.620 --> 00:13:32.800 align:middle line:84%
Now, with similar approach
towards organizing

00:13:32.800 --> 00:13:33.920 align:middle line:90%
our environment--

00:13:33.920 --> 00:13:35.860 align:middle line:84%
I'll move into the
environment, just

00:13:35.860 --> 00:13:39.875 align:middle line:84%
to show you an example of how
I have created a organization

00:13:39.875 --> 00:13:44.500 align:middle line:84%
ability structure, and then how
I have implemented the tiering

00:13:44.500 --> 00:13:48.730 align:middle line:84%
so we can prevent and allow
access to certain users

00:13:48.730 --> 00:13:51.320 align:middle line:90%
across different tiers.

00:13:51.320 --> 00:13:51.820 align:middle line:90%
All right.

00:13:51.820 --> 00:13:54.440 align:middle line:84%
So now I'm connected
to our environment.

00:13:54.440 --> 00:13:57.310 align:middle line:84%
And in this case, I am
assuming that our environment

00:13:57.310 --> 00:13:58.040 align:middle line:90%
is brand new.

00:13:58.040 --> 00:14:00.400 align:middle line:84%
We're building it from scratch,
which is most likely not

00:14:00.400 --> 00:14:01.810 align:middle line:90%
going to be the case with you.

00:14:01.810 --> 00:14:03.610 align:middle line:84%
So to accommodate
with that, I have

00:14:03.610 --> 00:14:07.750 align:middle line:84%
started to create a new OU on
the top of the domain called

00:14:07.750 --> 00:14:08.748 align:middle line:90%
Tiers.

00:14:08.748 --> 00:14:10.540 align:middle line:84%
And this is something
that you can actually

00:14:10.540 --> 00:14:13.720 align:middle line:84%
use in a environment
which already exists.

00:14:13.720 --> 00:14:16.480 align:middle line:84%
But to achieve this, you have
to move your Active Directory

00:14:16.480 --> 00:14:18.520 align:middle line:84%
objects into the
right containers

00:14:18.520 --> 00:14:20.500 align:middle line:84%
that we have created
for them now.

00:14:20.500 --> 00:14:22.090 align:middle line:84%
And that might be
problematic based

00:14:22.090 --> 00:14:24.070 align:middle line:84%
on certain GPOs
or other settings

00:14:24.070 --> 00:14:25.420 align:middle line:90%
that you might be pushing out.

00:14:25.420 --> 00:14:27.250 align:middle line:84%
So you have to be
very careful if you

00:14:27.250 --> 00:14:30.370 align:middle line:84%
start moving your current
infrastructure and the OUs

00:14:30.370 --> 00:14:32.740 align:middle line:84%
that you have, into
these new layers,

00:14:32.740 --> 00:14:35.530 align:middle line:84%
because you have to test
them before moving something

00:14:35.530 --> 00:14:37.780 align:middle line:90%
without testing before that.

00:14:37.780 --> 00:14:41.320 align:middle line:84%
Now into the Tiers OU, I
have three different tiers

00:14:41.320 --> 00:14:43.420 align:middle line:84%
representing the
default three tiers

00:14:43.420 --> 00:14:45.580 align:middle line:90%
that Microsoft recommends.

00:14:45.580 --> 00:14:49.900 align:middle line:84%
The most I have seen is
18 years of a company.

00:14:49.900 --> 00:14:52.300 align:middle line:84%
And that's because
their administrators

00:14:52.300 --> 00:14:55.720 align:middle line:84%
were really afraid that a
compromised administrator

00:14:55.720 --> 00:14:59.270 align:middle line:84%
account might lead to
compromise of many devices.

00:14:59.270 --> 00:15:02.503 align:middle line:84%
So what it did is,
basically every single type

00:15:02.503 --> 00:15:04.170 align:middle line:84%
of application they
had, they considered

00:15:04.170 --> 00:15:06.280 align:middle line:90%
that a whole separate tier.

00:15:06.280 --> 00:15:10.000 align:middle line:84%
But their administrators ended
up with 20 different accounts.

00:15:10.000 --> 00:15:12.280 align:middle line:84%
And that might be
too much for some,

00:15:12.280 --> 00:15:17.110 align:middle line:84%
but the minimum that you
should aim for is at least 3.

00:15:17.110 --> 00:15:21.760 align:middle line:84%
So in our tier two structure,
we have the same OUs,

00:15:21.760 --> 00:15:23.620 align:middle line:84%
which I was just
showing on the slides.

00:15:23.620 --> 00:15:25.630 align:middle line:84%
You have the accounts,
computers and groups.

00:15:25.630 --> 00:15:30.280 align:middle line:84%
So under accounts, we will have
disabled, external, internal

00:15:30.280 --> 00:15:31.930 align:middle line:90%
and privileged users.

00:15:31.930 --> 00:15:33.595 align:middle line:84%
And then for each
of the users, we

00:15:33.595 --> 00:15:36.650 align:middle line:84%
will, again, have
different countries.

00:15:36.650 --> 00:15:38.230 align:middle line:90%
As you can see here.

00:15:38.230 --> 00:15:44.020 align:middle line:84%
Now, it's very important to have
a really good naming convention

00:15:44.020 --> 00:15:46.033 align:middle line:90%
across your entire domain.

00:15:46.033 --> 00:15:47.200 align:middle line:90%
So if we take, for example--

00:15:47.200 --> 00:15:48.950 align:middle line:84%
I'll be showing this
across different tiers,

00:15:48.950 --> 00:15:50.230 align:middle line:90%
so you can see the difference.

00:15:50.230 --> 00:15:52.030 align:middle line:90%
Let's take our regular users.

00:15:52.030 --> 00:15:54.670 align:middle line:84%
Our naming convention
for regular users

00:15:54.670 --> 00:15:57.190 align:middle line:84%
is that we'll simply
use the first two

00:15:57.190 --> 00:15:59.740 align:middle line:90%
letters of their name.

00:15:59.740 --> 00:16:03.900 align:middle line:84%
First name, and the first
letters of their last name.

00:16:03.900 --> 00:16:08.430 align:middle line:84%
And this is going to be across
all our users of tier two.

00:16:08.430 --> 00:16:11.340 align:middle line:84%
So everything that has
four character user name

00:16:11.340 --> 00:16:14.840 align:middle line:90%
will be regular tier two user.

00:16:14.840 --> 00:16:17.180 align:middle line:84%
That will be the same
for Johnny Johnson.

00:16:17.180 --> 00:16:21.990 align:middle line:84%
In this case, the username
is going to be JoJo.

00:16:21.990 --> 00:16:26.250 align:middle line:84%
Now, if we move forward, we
will have privileged users.

00:16:26.250 --> 00:16:28.470 align:middle line:84%
And the name recognition
for privileged users

00:16:28.470 --> 00:16:33.870 align:middle line:84%
is tier two underscore
the first two

00:16:33.870 --> 00:16:36.180 align:middle line:84%
letters from the first
name and the first two

00:16:36.180 --> 00:16:37.200 align:middle line:90%
from the last name.

00:16:37.200 --> 00:16:39.300 align:middle line:84%
And then this becomes
really consistent,

00:16:39.300 --> 00:16:42.420 align:middle line:84%
because now we can
also trace users

00:16:42.420 --> 00:16:45.518 align:middle line:84%
that have user accounts
in different tiers.

00:16:45.518 --> 00:16:47.310 align:middle line:84%
And one thing that we
can achieve from this

00:16:47.310 --> 00:16:49.680 align:middle line:84%
is, we can later on
check whether users

00:16:49.680 --> 00:16:52.260 align:middle line:84%
in different tiers had
the same passwords.

00:16:52.260 --> 00:16:55.880 align:middle line:84%
Because giving an
administrator account 10 users,

00:16:55.880 --> 00:16:58.320 align:middle line:84%
but if he's using the same
password on all of them,

00:16:58.320 --> 00:17:01.568 align:middle line:84%
he's essentially bypassing the
added security from all tiers.

00:17:01.568 --> 00:17:03.360 align:middle line:84%
So it's very important
for us to have a way

00:17:03.360 --> 00:17:06.000 align:middle line:84%
to verify that the
same user is not

00:17:06.000 --> 00:17:08.700 align:middle line:84%
using the same password across
all the different accounts.

00:17:08.700 --> 00:17:11.010 align:middle line:84%
But generally, this
consistency will

00:17:11.010 --> 00:17:13.810 align:middle line:84%
help into automating
most of this tiering.

00:17:13.810 --> 00:17:19.450 align:middle line:84%
It can be really easy to
achieve if we have consistency.

00:17:19.450 --> 00:17:22.047 align:middle line:84%
If we look at the workstations,
or under our computers,

00:17:22.047 --> 00:17:23.839 align:middle line:84%
again, we will have
the different countries

00:17:23.839 --> 00:17:28.569 align:middle line:84%
so it matches with our
design for the users.

00:17:28.569 --> 00:17:31.610 align:middle line:84%
And our naming convention for
workstations is very simple.

00:17:31.610 --> 00:17:35.320 align:middle line:90%
It's just WS10-001.

00:17:35.320 --> 00:17:39.040 align:middle line:84%
And for each other workstation,
we just increase this number.

00:17:39.040 --> 00:17:41.740 align:middle line:84%
Of course, this can
be whatever you like,

00:17:41.740 --> 00:17:44.170 align:middle line:84%
as long as there's
consistency behind it.

00:17:44.170 --> 00:17:48.100 align:middle line:84%
And now, the good thing
about having this consistency

00:17:48.100 --> 00:17:50.740 align:middle line:84%
in workstations, is
that we can achieve

00:17:50.740 --> 00:17:55.870 align:middle line:84%
creating this group, which is
SG, which stands for Security

00:17:55.870 --> 00:17:59.380 align:middle line:84%
Group, underscore the
hostname for our workstation,

00:17:59.380 --> 00:18:00.940 align:middle line:90%
underscore admins.

00:18:00.940 --> 00:18:03.980 align:middle line:84%
Now, if you want to control who
should be admin to workstation

00:18:03.980 --> 00:18:07.150 align:middle line:84%
10 001, you simply have to
modify this group in Active

00:18:07.150 --> 00:18:09.775 align:middle line:84%
Directory, and it will
give access that user,

00:18:09.775 --> 00:18:10.870 align:middle line:90%
administrative access.

00:18:10.870 --> 00:18:13.090 align:middle line:84%
Then we can remove
it from here as well.

00:18:13.090 --> 00:18:17.080 align:middle line:84%
To push out this groups into
each of the workstations,

00:18:17.080 --> 00:18:18.820 align:middle line:90%
we have a very unique way.

00:18:18.820 --> 00:18:22.150 align:middle line:84%
Because in a Group
Policy Object,

00:18:22.150 --> 00:18:25.000 align:middle line:84%
we can push exactly
this line that

00:18:25.000 --> 00:18:27.370 align:middle line:84%
will resolve the hostname
and the domain name

00:18:27.370 --> 00:18:28.810 align:middle line:90%
to the current one.

00:18:28.810 --> 00:18:31.360 align:middle line:84%
But it's only going to
append the admins to the end.

00:18:31.360 --> 00:18:33.160 align:middle line:84%
So for each
workstation, it's going

00:18:33.160 --> 00:18:34.840 align:middle line:90%
to resolve its own hostname.

00:18:34.840 --> 00:18:38.950 align:middle line:84%
So one single command will
hit all our workstations

00:18:38.950 --> 00:18:41.842 align:middle line:84%
and servers, and resolve the
correct values for all of them

00:18:41.842 --> 00:18:42.550 align:middle line:90%
at the same time.

00:18:42.550 --> 00:18:46.150 align:middle line:90%


00:18:46.150 --> 00:18:49.420 align:middle line:84%
With the same consistency, we
can go forward into tier one.

00:18:49.420 --> 00:18:52.305 align:middle line:84%
Again, we have accounts,
groups and servers.

00:18:52.305 --> 00:18:54.550 align:middle line:84%
And for expansion
into Accounts, we'll

00:18:54.550 --> 00:18:58.270 align:middle line:84%
see similar OUs as
previously, while now we'll

00:18:58.270 --> 00:19:00.040 align:middle line:90%
have also Service Accounts.

00:19:00.040 --> 00:19:03.460 align:middle line:84%
For internal users, we have
a new naming convention,

00:19:03.460 --> 00:19:06.535 align:middle line:84%
which is going to be
tier one underscore--

00:19:06.535 --> 00:19:09.670 align:middle line:84%
And again, using the first
two letters of the first name

00:19:09.670 --> 00:19:12.610 align:middle line:84%
and the first two letters
of the second name.

00:19:12.610 --> 00:19:15.190 align:middle line:84%
Again, we're keeping
the consistency.

00:19:15.190 --> 00:19:20.044 align:middle line:84%
For service accounts, we'll name
all service accounts with svc

00:19:20.044 --> 00:19:24.130 align:middle line:84%
underscore the server that
they're being used for

00:19:24.130 --> 00:19:26.560 align:middle line:84%
and what is the application
that they're running.

00:19:26.560 --> 00:19:29.660 align:middle line:84%
You can go forward and
also add additional data.

00:19:29.660 --> 00:19:33.400 align:middle line:84%
For example, if this is a read
user, you can at sql read.

00:19:33.400 --> 00:19:35.450 align:middle line:84%
In our case, it
is an admin user,

00:19:35.450 --> 00:19:36.850 align:middle line:90%
and we only have admin user.

00:19:36.850 --> 00:19:40.310 align:middle line:84%
So it was not necessary to
create more explanation.

00:19:40.310 --> 00:19:42.970 align:middle line:84%
But the username
itself, will give us

00:19:42.970 --> 00:19:45.550 align:middle line:84%
the information of where
this user is being used,

00:19:45.550 --> 00:19:48.940 align:middle line:84%
what it's being used for, and
most importantly, that this

00:19:48.940 --> 00:19:51.040 align:middle line:90%
is a service account.

00:19:51.040 --> 00:19:53.650 align:middle line:84%
And again, having
this consistency,

00:19:53.650 --> 00:19:55.930 align:middle line:84%
we can put restrictions
on service accounts

00:19:55.930 --> 00:19:57.590 align:middle line:90%
as we go forward.

00:19:57.590 --> 00:20:01.150 align:middle line:84%
Where we can add service
account into different groups

00:20:01.150 --> 00:20:04.180 align:middle line:84%
as we go forward, because we
have this naming convention

00:20:04.180 --> 00:20:06.970 align:middle line:90%
that we can use all across.

00:20:06.970 --> 00:20:09.600 align:middle line:84%
And, I think, this is the
moment to mention group managed

00:20:09.600 --> 00:20:12.360 align:middle line:84%
service accounts,
which is a concept that

00:20:12.360 --> 00:20:17.802 align:middle line:84%
exists since Windows 2012,
the main functional level.

00:20:17.802 --> 00:20:19.260 align:middle line:84%
And that's something
that Microsoft

00:20:19.260 --> 00:20:22.830 align:middle line:84%
created as Active Directory
managed service account.

00:20:22.830 --> 00:20:25.950 align:middle line:84%
And the difference is that
that service accounts password

00:20:25.950 --> 00:20:28.020 align:middle line:84%
is going to be managed
by Active Directory.

00:20:28.020 --> 00:20:30.360 align:middle line:84%
You, as an admin, you'll
never have to know it.

00:20:30.360 --> 00:20:32.530 align:middle line:84%
And Active Directory
will automatically

00:20:32.530 --> 00:20:34.650 align:middle line:84%
rotates the password
without breaking

00:20:34.650 --> 00:20:35.910 align:middle line:90%
the way that services work.

00:20:35.910 --> 00:20:38.490 align:middle line:84%
It will ultimately also
update things with services

00:20:38.490 --> 00:20:40.560 align:middle line:84%
that the service accounts
are being used for.

00:20:40.560 --> 00:20:42.840 align:middle line:84%
Unfortunately, there are
some limitations with this.

00:20:42.840 --> 00:20:45.220 align:middle line:84%
And that is primarily
that this group

00:20:45.220 --> 00:20:47.580 align:middle line:84%
managed service
accounts will work only

00:20:47.580 --> 00:20:49.930 align:middle line:90%
with Microsoft services.

00:20:49.930 --> 00:20:52.920 align:middle line:84%
So if you have services, such
as external tools that you might

00:20:52.920 --> 00:20:55.330 align:middle line:84%
have purchased in
your organization,

00:20:55.330 --> 00:20:58.890 align:middle line:84%
you might have to go back to
the traditional way of having

00:20:58.890 --> 00:21:00.430 align:middle line:90%
these service user accounts.

00:21:00.430 --> 00:21:02.430 align:middle line:84%
But what is important for
them is that they need

00:21:02.430 --> 00:21:03.930 align:middle line:90%
to have very strong password.

00:21:03.930 --> 00:21:09.340 align:middle line:84%
And we'll talk about
passwords in upcoming video.

00:21:09.340 --> 00:21:14.410 align:middle line:84%
For our groups, again, we have
the same naming convention

00:21:14.410 --> 00:21:16.600 align:middle line:90%
for server admins.

00:21:16.600 --> 00:21:19.720 align:middle line:84%
So for each server object,
for each computer server

00:21:19.720 --> 00:21:23.080 align:middle line:84%
object in our environment, we
will have this security group,

00:21:23.080 --> 00:21:25.210 align:middle line:84%
the hostname of the
server underscore admins.

00:21:25.210 --> 00:21:27.340 align:middle line:90%
Then we can control host admins.

00:21:27.340 --> 00:21:29.890 align:middle line:84%
And actually, in this case,
I'm only showing admins.

00:21:29.890 --> 00:21:32.590 align:middle line:84%
But what could be really
nice to have as well,

00:21:32.590 --> 00:21:35.990 align:middle line:84%
is the same group or the same
style, but for RDP access.

00:21:35.990 --> 00:21:38.230 align:middle line:84%
So for each server, we
have the same group,

00:21:38.230 --> 00:21:42.340 align:middle line:84%
we'll give RDP access
to that server.

00:21:42.340 --> 00:21:45.310 align:middle line:84%
Because not every user connected
to a server requires local

00:21:45.310 --> 00:21:46.930 align:middle line:90%
underwrites.

00:21:46.930 --> 00:21:50.530 align:middle line:84%
RDP rights might be
more than enough.

00:21:50.530 --> 00:21:54.550 align:middle line:84%
For the servers, we'll
have multiple OUs again.

00:21:54.550 --> 00:21:56.320 align:middle line:84%
And the OUs are going
to be structured

00:21:56.320 --> 00:22:00.143 align:middle line:84%
based on the application
that the servers are hosting.

00:22:00.143 --> 00:22:02.560 align:middle line:84%
And this is usually good when
you have hardening in place,

00:22:02.560 --> 00:22:05.440 align:middle line:84%
because you can push
out different hardening

00:22:05.440 --> 00:22:07.270 align:middle line:84%
policies depending
on the application

00:22:07.270 --> 00:22:09.300 align:middle line:90%
that you're hardening.

00:22:09.300 --> 00:22:12.150 align:middle line:84%
Because certain features
might break one application,

00:22:12.150 --> 00:22:14.020 align:middle line:84%
but it might be just
fine with another one.

00:22:14.020 --> 00:22:17.610 align:middle line:84%
So instead of having to live
with not hardening something

00:22:17.610 --> 00:22:20.700 align:middle line:84%
because of one application,
while the rest 200 applications

00:22:20.700 --> 00:22:22.770 align:middle line:84%
are just fine with it,
you can have this approach

00:22:22.770 --> 00:22:24.930 align:middle line:84%
to take the different
applications

00:22:24.930 --> 00:22:29.190 align:middle line:84%
and make sure that they'll
support what they need.

00:22:29.190 --> 00:22:34.200 align:middle line:84%
For tier zero, we'll have pretty
much exactly the same structure

00:22:34.200 --> 00:22:36.060 align:middle line:90%
with our accounts.

00:22:36.060 --> 00:22:39.397 align:middle line:84%
Now, we have Martin Rollin
account again in here.

00:22:39.397 --> 00:22:40.980 align:middle line:84%
The naming convention
though, is going

00:22:40.980 --> 00:22:42.630 align:middle line:90%
to be tier zero underscore.

00:22:42.630 --> 00:22:44.820 align:middle line:84%
And now, we have a
naming convention

00:22:44.820 --> 00:22:49.020 align:middle line:84%
which is going to be unique
but the same for each tier.

00:22:49.020 --> 00:22:51.990 align:middle line:84%
Unique, because we have
the tier zero, tier one,

00:22:51.990 --> 00:22:56.490 align:middle line:84%
tier two underscore, but the
username persists the same

00:22:56.490 --> 00:22:58.170 align:middle line:90%
across all tiers.

00:22:58.170 --> 00:23:01.630 align:middle line:84%
And the regular user is
going to be just maro.

00:23:01.630 --> 00:23:04.330 align:middle line:90%


00:23:04.330 --> 00:23:08.290 align:middle line:84%
Service accounts will contain
the same naming convention.

00:23:08.290 --> 00:23:11.140 align:middle line:84%
We want to give them svc
underscore, to recognize

00:23:11.140 --> 00:23:13.150 align:middle line:90%
this is a service account.

00:23:13.150 --> 00:23:16.030 align:middle line:84%
External users are interesting,
because occasionally we

00:23:16.030 --> 00:23:18.700 align:middle line:84%
need to have consultants
or other parties that

00:23:18.700 --> 00:23:19.750 align:middle line:90%
are helping us.

00:23:19.750 --> 00:23:22.600 align:middle line:84%
So our naming convention
for them is also important.

00:23:22.600 --> 00:23:24.910 align:middle line:84%
In this case, my
suggestion is that we

00:23:24.910 --> 00:23:29.170 align:middle line:84%
have ex underscore the tier
that the account should operate

00:23:29.170 --> 00:23:31.210 align:middle line:84%
in, and then again,
the first two

00:23:31.210 --> 00:23:33.970 align:middle line:84%
characters of the first
name and the first two

00:23:33.970 --> 00:23:37.390 align:middle line:90%
characters of the last name.

00:23:37.390 --> 00:23:39.570 align:middle line:84%
Now, moving forward,
we will have

00:23:39.570 --> 00:23:41.760 align:middle line:84%
groups for local
admin servers again

00:23:41.760 --> 00:23:43.620 align:middle line:90%
and different applications.

00:23:43.620 --> 00:23:46.470 align:middle line:84%
We will have our
servers in tier zero.

00:23:46.470 --> 00:23:49.920 align:middle line:84%
And we will also have previous
accessed workstations.

00:23:49.920 --> 00:23:52.860 align:middle line:84%
This is a concept we have not
discussed yet in the course,

00:23:52.860 --> 00:23:54.660 align:middle line:90%
but we'll get into this shortly.

00:23:54.660 --> 00:23:56.760 align:middle line:84%
But these are essentially
the workstations

00:23:56.760 --> 00:24:00.270 align:middle line:84%
that we need to use to
access a tier zero system.

00:24:00.270 --> 00:24:02.970 align:middle line:84%
Because tier zero system
is the core infrastructure

00:24:02.970 --> 00:24:04.020 align:middle line:90%
of our environment.

00:24:04.020 --> 00:24:06.690 align:middle line:84%
It is so critical,
you want to have

00:24:06.690 --> 00:24:10.320 align:middle line:84%
different device that
is the only device which

00:24:10.320 --> 00:24:11.760 align:middle line:90%
can access this tier.

00:24:11.760 --> 00:24:13.140 align:middle line:84%
Or, in many cases,
this of course

00:24:13.140 --> 00:24:15.240 align:middle line:90%
can be devices for redundancy.

00:24:15.240 --> 00:24:17.800 align:middle line:84%
It doesn't make sense
to be only one device.

00:24:17.800 --> 00:24:20.040 align:middle line:84%
Now, we have this
tiering model, but how do

00:24:20.040 --> 00:24:24.690 align:middle line:84%
we control who can access
what, and who can control what?

00:24:24.690 --> 00:24:29.130 align:middle line:84%
That brings us into our group
policy tiering that we're

00:24:29.130 --> 00:24:30.630 align:middle line:90%
going to present now.

00:24:30.630 --> 00:24:34.230 align:middle line:84%
I have already applied
Group Policy Objects

00:24:34.230 --> 00:24:37.020 align:middle line:84%
to the different
tiers for the servers,

00:24:37.020 --> 00:24:42.000 align:middle line:84%
where I am applying different
user right assignments for all

00:24:42.000 --> 00:24:43.140 align:middle line:90%
the different tiers.

00:24:43.140 --> 00:24:45.140 align:middle line:84%
And that is exactly
what you can see now

00:24:45.140 --> 00:24:49.930 align:middle line:84%
as I am expanding through the
different organizational units.

00:24:49.930 --> 00:24:51.775 align:middle line:90%
Now, let's start with tier two.

00:24:51.775 --> 00:24:54.150 align:middle line:84%
Let's look at the settings
which are currently configured

00:24:54.150 --> 00:24:56.410 align:middle line:90%
in this organizational unit.

00:24:56.410 --> 00:24:59.140 align:middle line:84%
What we are going
to see is that, when

00:24:59.140 --> 00:25:03.040 align:middle line:84%
we come into the
allow and deny access,

00:25:03.040 --> 00:25:05.830 align:middle line:84%
we'll see that in
Allow log on locally,

00:25:05.830 --> 00:25:09.880 align:middle line:84%
we're allowing users and
administrators to login.

00:25:09.880 --> 00:25:13.510 align:middle line:84%
But also, at the same time, if
we look at Deny log on locally,

00:25:13.510 --> 00:25:16.100 align:middle line:90%
we're explicitly denying log on.

00:25:16.100 --> 00:25:17.920 align:middle line:84%
We'll see that we
have actually listed

00:25:17.920 --> 00:25:20.860 align:middle line:84%
all the privileged groups and
all the tier zero accounts,

00:25:20.860 --> 00:25:23.630 align:middle line:84%
all the tier one
accounts, and so on.

00:25:23.630 --> 00:25:28.180 align:middle line:84%
So, Account Operators, Backup
Operators Cryptographic

00:25:28.180 --> 00:25:32.140 align:middle line:84%
Operators, Distributed COM
Users, Print Operators,

00:25:32.140 --> 00:25:36.640 align:middle line:84%
Domain Admins, Enterprise
Admins, all of our tier zero

00:25:36.640 --> 00:25:39.760 align:middle line:84%
accounts, all of our tier
zero service accounts,

00:25:39.760 --> 00:25:43.330 align:middle line:84%
all of our tier one accounts,
all of our tier one service

00:25:43.330 --> 00:25:45.700 align:middle line:90%
accounts, and Server Operators.

00:25:45.700 --> 00:25:50.080 align:middle line:84%
They are explicitly being denied
to access this workstation.

00:25:50.080 --> 00:25:54.460 align:middle line:84%
So privileged users cannot
login to this workstation.

00:25:54.460 --> 00:26:00.370 align:middle line:84%
So this immediately tells
us that users from tier zero

00:26:00.370 --> 00:26:03.960 align:middle line:84%
and tier one cannot
login to tier two.

00:26:03.960 --> 00:26:08.340 align:middle line:84%
And that is the case, not
just the physical login,

00:26:08.340 --> 00:26:11.050 align:middle line:90%
but with login as a batch.

00:26:11.050 --> 00:26:14.790 align:middle line:84%
So these users cannot access
this machine by running

00:26:14.790 --> 00:26:15.690 align:middle line:90%
a scheduled task.

00:26:15.690 --> 00:26:17.820 align:middle line:84%
They cannot be
running a service.

00:26:17.820 --> 00:26:20.520 align:middle line:84%
They cannot login
through RDP either.

00:26:20.520 --> 00:26:24.030 align:middle line:84%
And what is more, in fact,
is that these users will not

00:26:24.030 --> 00:26:27.540 align:middle line:84%
be able to access our
workstation over the network

00:26:27.540 --> 00:26:28.150 align:middle line:90%
as well.

00:26:28.150 --> 00:26:31.420 align:middle line:84%
So SMB, VMI, all
these protocols,

00:26:31.420 --> 00:26:34.540 align:middle line:84%
they're not going to be allowed
for our privileged users.

00:26:34.540 --> 00:26:37.320 align:middle line:84%
And this is how we deny access
to our privileged accounts

00:26:37.320 --> 00:26:41.460 align:middle line:84%
from accessing workstations
in the environment.

00:26:41.460 --> 00:26:43.650 align:middle line:84%
Now, I'm already
mentioning groups

00:26:43.650 --> 00:26:47.670 align:middle line:84%
that are showing all our
tier zero accounts and all

00:26:47.670 --> 00:26:49.230 align:middle line:90%
our tier one accounts.

00:26:49.230 --> 00:26:53.187 align:middle line:84%
These groups I had already
created in our structure,

00:26:53.187 --> 00:26:54.270 align:middle line:90%
which you might have seen.

00:26:54.270 --> 00:26:57.360 align:middle line:84%
They are located under
the groups OU for each

00:26:57.360 --> 00:26:58.680 align:middle line:90%
of the different years.

00:26:58.680 --> 00:27:01.750 align:middle line:84%
Here I have SG All
Tier zero Accounts,

00:27:01.750 --> 00:27:04.740 align:middle line:84%
which will contain all
our tier zero accounts.

00:27:04.740 --> 00:27:06.365 align:middle line:84%
So we can put a
restriction to all tier

00:27:06.365 --> 00:27:10.183 align:middle line:84%
zero accounts immediately, just
by referring to this group.

00:27:10.183 --> 00:27:11.850 align:middle line:84%
Now, there are multiple
ways to maintain

00:27:11.850 --> 00:27:13.380 align:middle line:90%
the membership of this group.

00:27:13.380 --> 00:27:15.210 align:middle line:84%
Something that is
automated is that you

00:27:15.210 --> 00:27:18.870 align:middle line:84%
can create a PowerShell script,
which runs every six minutes,

00:27:18.870 --> 00:27:22.770 align:middle line:84%
say, every 5, or 10 minutes, or
15 minutes in your environment.

00:27:22.770 --> 00:27:26.295 align:middle line:84%
Checks that, if an account
starts with tier zero

00:27:26.295 --> 00:27:30.420 align:middle line:84%
underscore, or X tier
zero underscore, then

00:27:30.420 --> 00:27:32.100 align:middle line:84%
that account will
automatically be added

00:27:32.100 --> 00:27:33.308 align:middle line:90%
to be a member of this group.

00:27:33.308 --> 00:27:36.270 align:middle line:84%
And that's how the consistency
that we were talking about

00:27:36.270 --> 00:27:38.730 align:middle line:84%
before is becoming
really helpful for us.

00:27:38.730 --> 00:27:41.820 align:middle line:84%
Because we can automate
maintaining this membership

00:27:41.820 --> 00:27:43.780 align:middle line:84%
and applying our
different tiering

00:27:43.780 --> 00:27:46.750 align:middle line:90%
restrictions to our accounts.

00:27:46.750 --> 00:27:49.660 align:middle line:84%
And now, similarly,
for tier two accounts--

00:27:49.660 --> 00:27:51.370 align:middle line:84%
Sorry, for tier
one accounts, we'll

00:27:51.370 --> 00:27:52.990 align:middle line:90%
have the same restrictions.

00:27:52.990 --> 00:27:57.190 align:middle line:84%
But the difference now, is going
to be that we have now tier two

00:27:57.190 --> 00:28:00.490 align:middle line:84%
accounts and tier zero accounts
that cannot access tier one.

00:28:00.490 --> 00:28:02.680 align:middle line:84%
And, of course, that just
makes sense to everything

00:28:02.680 --> 00:28:05.100 align:middle line:84%
that we have been
discussing so far.

00:28:05.100 --> 00:28:08.130 align:middle line:84%
Similarly, tier one
will have the same,

00:28:08.130 --> 00:28:10.410 align:middle line:84%
but now the previous
groups are gone.

00:28:10.410 --> 00:28:14.330 align:middle line:84%
We allow the previous groups
to actually access tier zero.

00:28:14.330 --> 00:28:16.080 align:middle line:84%
There are some privileged
groups we simply

00:28:16.080 --> 00:28:18.300 align:middle line:84%
don't allow, because these
groups should just not

00:28:18.300 --> 00:28:19.630 align:middle line:90%
be used at all.

00:28:19.630 --> 00:28:22.530 align:middle line:84%
But if you look into domain
admins and enterprise admins,

00:28:22.530 --> 00:28:26.850 align:middle line:84%
we allow those groups to connect
to our tier zero systems.

00:28:26.850 --> 00:28:29.740 align:middle line:90%


00:28:29.740 --> 00:28:31.840 align:middle line:84%
And, of course, it's
highly recommended

00:28:31.840 --> 00:28:34.900 align:middle line:84%
to create your own
custom groups that

00:28:34.900 --> 00:28:38.110 align:middle line:84%
will provide only the
access that you may need,

00:28:38.110 --> 00:28:39.850 align:middle line:84%
instead of using
the default groups.

00:28:39.850 --> 00:28:42.790 align:middle line:84%
Because the default groups
are just way too privileged.

00:28:42.790 --> 00:28:44.770 align:middle line:84%
There's many hidden
privileges that you're not

00:28:44.770 --> 00:28:46.930 align:middle line:84%
aware of when you
assign someone.

00:28:46.930 --> 00:28:49.510 align:middle line:84%
Let's take, for example,
the Account Operators look.

00:28:49.510 --> 00:28:51.430 align:middle line:84%
I hear many
administrators saying

00:28:51.430 --> 00:28:54.700 align:middle line:84%
that account operators is
a good group because they

00:28:54.700 --> 00:28:56.800 align:middle line:84%
can go and reset the
password to many users

00:28:56.800 --> 00:28:58.900 align:middle line:84%
and they'll just
inherit that right.

00:28:58.900 --> 00:29:01.210 align:middle line:84%
But, while that is
true, they will also

00:29:01.210 --> 00:29:04.870 align:middle line:84%
inherit the right to
modify all the users which

00:29:04.870 --> 00:29:08.680 align:middle line:84%
are located under this
Users organizational unit.

00:29:08.680 --> 00:29:11.170 align:middle line:84%
And that is crazy, if
you think about it.

00:29:11.170 --> 00:29:12.640 align:middle line:84%
Because account
operators will be

00:29:12.640 --> 00:29:15.730 align:middle line:84%
able to change now the password
for the account administrator

00:29:15.730 --> 00:29:18.190 align:middle line:84%
as well, which is
placed here by default,

00:29:18.190 --> 00:29:21.610 align:middle line:84%
or the MSO account,
which is the default

00:29:21.610 --> 00:29:25.270 align:middle line:84%
account for performing password
synchronization with Azure AD.

00:29:25.270 --> 00:29:29.050 align:middle line:84%
And this account has the ability
to act as a domain controller,

00:29:29.050 --> 00:29:30.520 align:middle line:90%
it can do [INAUDIBLE].

00:29:30.520 --> 00:29:32.230 align:middle line:84%
So an account operator
has the ability

00:29:32.230 --> 00:29:34.180 align:middle line:84%
to change the password
on this account,

00:29:34.180 --> 00:29:37.390 align:middle line:84%
and essentially steal your
entire Active Directory.

00:29:37.390 --> 00:29:39.880 align:middle line:84%
And this doesn't make sense
because account operators are

00:29:39.880 --> 00:29:42.530 align:middle line:84%
not as privileged as
domain administrators,

00:29:42.530 --> 00:29:44.680 align:middle line:84%
but they can gain this
right, and essentially

00:29:44.680 --> 00:29:47.930 align:middle line:90%
breach our tiering model.

00:29:47.930 --> 00:29:50.570 align:middle line:84%
The last thing that I wanted
to mention here and discuss

00:29:50.570 --> 00:29:52.820 align:middle line:84%
with you, is that now
we have the ability

00:29:52.820 --> 00:29:55.700 align:middle line:84%
to use this Group
Policy Object to manage

00:29:55.700 --> 00:29:58.490 align:middle line:84%
who is local administrator
on our devices.

00:29:58.490 --> 00:30:04.430 align:middle line:84%
And in this case, we can set the
built-in administrators group

00:30:04.430 --> 00:30:08.000 align:middle line:84%
to have all its members deleted,
whether the member is currently

00:30:08.000 --> 00:30:10.700 align:middle line:84%
a user or groups, and
then set new members who

00:30:10.700 --> 00:30:13.760 align:middle line:84%
should be local
administrators on our devices.

00:30:13.760 --> 00:30:17.970 align:middle line:84%
And in this case, we're
setting that SG underscore

00:30:17.970 --> 00:30:20.720 align:middle line:84%
computer name underscore
admins, should

00:30:20.720 --> 00:30:22.520 align:middle line:90%
be set to all workstations.

00:30:22.520 --> 00:30:24.410 align:middle line:84%
And again, the great
thing about this comment

00:30:24.410 --> 00:30:26.600 align:middle line:84%
is that computer
name will get result

00:30:26.600 --> 00:30:28.290 align:middle line:90%
to the hostname of the machine.

00:30:28.290 --> 00:30:32.210 align:middle line:84%
So each machine will
dynamically assign its own group

00:30:32.210 --> 00:30:33.770 align:middle line:90%
to be local administrator.

00:30:33.770 --> 00:30:36.740 align:middle line:84%
And this is
absolutely fantastic.

00:30:36.740 --> 00:30:40.820 align:middle line:84%
Then we have the group
SG LA All Tier Two.

00:30:40.820 --> 00:30:43.340 align:middle line:84%
This group is going
to be set to be

00:30:43.340 --> 00:30:45.500 align:middle line:84%
local administrator
on all workstations

00:30:45.500 --> 00:30:47.150 align:middle line:90%
across the entire environment.

00:30:47.150 --> 00:30:49.700 align:middle line:84%
And I don't really
recommend using this group,

00:30:49.700 --> 00:30:53.130 align:middle line:84%
it's only really for
emergency purpose.

00:30:53.130 --> 00:30:54.650 align:middle line:84%
For example, if you
get compromised,

00:30:54.650 --> 00:30:56.930 align:middle line:84%
or if you need some kind
of disaster recovery

00:30:56.930 --> 00:30:59.720 align:middle line:84%
team on your workstations
and you need access

00:30:59.720 --> 00:31:02.570 align:middle line:84%
to many workstations at the
same time simultaneously,

00:31:02.570 --> 00:31:04.940 align:middle line:84%
you can add yourself to
be a member of this group

00:31:04.940 --> 00:31:08.210 align:middle line:84%
and gain that access
for a limited time.

00:31:08.210 --> 00:31:11.900 align:middle line:84%
What I also recommend is
that you add this group,

00:31:11.900 --> 00:31:14.720 align:middle line:84%
so that members of
this group are not

00:31:14.720 --> 00:31:16.850 align:middle line:84%
allowed to access
workstations remotely.

00:31:16.850 --> 00:31:18.680 align:middle line:84%
They have to be
physically in the machine

00:31:18.680 --> 00:31:28.160 align:middle line:84%
or utilize a tool, such
as a Team Viewer or one

00:31:28.160 --> 00:31:29.990 align:middle line:84%
of the other tools
that has this ability,

00:31:29.990 --> 00:31:32.690 align:middle line:84%
and can let you
perform local login,

00:31:32.690 --> 00:31:35.660 align:middle line:84%
even though you're
coming from the network.

00:31:35.660 --> 00:31:39.690 align:middle line:84%
So let's demonstrate
our tiering in action.

00:31:39.690 --> 00:31:42.178 align:middle line:84%
I will connect now
to workstation--

00:31:42.178 --> 00:31:43.720 align:middle line:84%
I want demonstrate
in the workstation

00:31:43.720 --> 00:31:47.540 align:middle line:84%
because it should be sufficient
to showcase how this works.

00:31:47.540 --> 00:31:49.570 align:middle line:84%
So what I'm going to
do first is that I

00:31:49.570 --> 00:31:51.610 align:middle line:84%
will try to log in
with the administrator

00:31:51.610 --> 00:31:53.870 align:middle line:90%
account of the domain.

00:31:53.870 --> 00:31:58.990 align:middle line:84%
So that would be
prod/administrator.

00:31:58.990 --> 00:32:02.560 align:middle line:84%
Now, this account is a member
of the group domain admins,

00:32:02.560 --> 00:32:04.570 align:middle line:84%
and that means this
account should not

00:32:04.570 --> 00:32:06.680 align:middle line:90%
be allowed to log in.

00:32:06.680 --> 00:32:11.510 align:middle line:84%
So if you try to log in, you
will immediately get an error.

00:32:11.510 --> 00:32:14.720 align:middle line:84%
This sign-in method you're
trying to use is not allowed.

00:32:14.720 --> 00:32:15.410 align:middle line:90%
And that'd it.

00:32:15.410 --> 00:32:17.840 align:middle line:84%
They simply cannot
access the workstation.

00:32:17.840 --> 00:32:21.290 align:middle line:84%
The workstation will deny
access to the account,

00:32:21.290 --> 00:32:23.027 align:middle line:84%
even though this
account is domain admin.

00:32:23.027 --> 00:32:25.610 align:middle line:84%
And this is how we can enforce
that this account, essentially,

00:32:25.610 --> 00:32:29.710 align:middle line:84%
doesn't get used on our
one privileged devices.

00:32:29.710 --> 00:32:32.590 align:middle line:84%
Now, let's use a
regular user and try

00:32:32.590 --> 00:32:34.840 align:middle line:90%
to login as this account.

00:32:34.840 --> 00:32:38.860 align:middle line:84%
I wanted to show you
how our GPO has applied

00:32:38.860 --> 00:32:43.450 align:middle line:84%
across the workstation, and
has also taken into effect

00:32:43.450 --> 00:32:46.060 align:middle line:84%
the different local
admin groups, which

00:32:46.060 --> 00:32:49.390 align:middle line:90%
we want to be assigned here.

00:32:49.390 --> 00:32:51.400 align:middle line:84%
One thing which I
didn't mention before

00:32:51.400 --> 00:32:54.520 align:middle line:84%
is that the account
administrator will always

00:32:54.520 --> 00:32:56.380 align:middle line:84%
be a member of this
group, regardless

00:32:56.380 --> 00:32:59.920 align:middle line:84%
of whether we define that
account in the Group Policy

00:32:59.920 --> 00:33:00.910 align:middle line:90%
Object or not.

00:33:00.910 --> 00:33:03.640 align:middle line:84%
We did not define the
accounts explicitly,

00:33:03.640 --> 00:33:07.270 align:middle line:84%
but it's implicitly being
a local admin group.

00:33:07.270 --> 00:33:14.930 align:middle line:84%
So if I run the command net
localgroup administrators,

00:33:14.930 --> 00:33:17.740 align:middle line:84%
I get a list of the
users and groups

00:33:17.740 --> 00:33:20.330 align:middle line:84%
who are members of the
local built administrators

00:33:20.330 --> 00:33:22.690 align:middle line:90%
group on this workstation.

00:33:22.690 --> 00:33:27.400 align:middle line:84%
Running the command, I will get
Administrator, our workstation

00:33:27.400 --> 00:33:29.680 align:middle line:84%
specific group,
and the group that

00:33:29.680 --> 00:33:33.590 align:middle line:84%
is local admin on
our workstations.

00:33:33.590 --> 00:33:38.180 align:middle line:84%
And this really works the
way we expect it to do.

00:33:38.180 --> 00:33:39.930 align:middle line:84%
And that's fantastic,
because now we

00:33:39.930 --> 00:33:41.660 align:middle line:90%
can manage local admin groups.

00:33:41.660 --> 00:33:44.600 align:middle line:84%
And even if someone
escalates and adds themselves

00:33:44.600 --> 00:33:50.420 align:middle line:84%
to this group, next time
Group Policy Objects runs,

00:33:50.420 --> 00:33:51.740 align:middle line:90%
they'll get deleted.

00:33:51.740 --> 00:33:53.930 align:middle line:84%
And the built-in
administrator account,

00:33:53.930 --> 00:33:56.150 align:middle line:84%
even if someone obtains the
password, or the password

00:33:56.150 --> 00:33:59.120 align:middle line:84%
hash for this account, if
we're managing this with Laps,

00:33:59.120 --> 00:34:01.370 align:middle line:84%
the password will be
protected automatically.

00:34:01.370 --> 00:34:04.490 align:middle line:84%
And they usually recommend
that the password of Laps

00:34:04.490 --> 00:34:08.030 align:middle line:90%
is rotated every day.

00:34:08.030 --> 00:34:10.130 align:middle line:84%
It could be the case
with you that you

00:34:10.130 --> 00:34:13.219 align:middle line:84%
might want to have more
local admin groups,

00:34:13.219 --> 00:34:15.070 align:middle line:90%
or they could be different.

00:34:15.070 --> 00:34:17.090 align:middle line:84%
For example, if you
have workstations

00:34:17.090 --> 00:34:19.310 align:middle line:84%
across different
countries, and helpdesk

00:34:19.310 --> 00:34:21.350 align:middle line:84%
for each of the
countries, then you

00:34:21.350 --> 00:34:25.010 align:middle line:84%
want that helpdesk to have
local admin rights, perhaps,

00:34:25.010 --> 00:34:26.447 align:middle line:90%
only for that country.

00:34:26.447 --> 00:34:28.489 align:middle line:84%
So you can define the
group only for the country,

00:34:28.489 --> 00:34:30.170 align:middle line:84%
and it's going to
be applied only

00:34:30.170 --> 00:34:32.179 align:middle line:90%
on computers in that country.

00:34:32.179 --> 00:34:34.760 align:middle line:84%
And applying these GPOs
is going to be very easy

00:34:34.760 --> 00:34:38.179 align:middle line:84%
because we have that consistency
across the naming convention,

00:34:38.179 --> 00:34:40.460 align:middle line:90%
but also we have defined the--

00:34:40.460 --> 00:34:42.590 align:middle line:84%
Or we have structured
our organizational units

00:34:42.590 --> 00:34:44.330 align:middle line:84%
in a way that is
going to be very

00:34:44.330 --> 00:34:48.739 align:middle line:84%
easy to apply certain GPOs to
the different organizational

00:34:48.739 --> 00:34:50.120 align:middle line:90%
units.

00:34:50.120 --> 00:34:53.719 align:middle line:84%
This is pretty much all
there is behind tiering.

00:34:53.719 --> 00:34:57.290 align:middle line:84%
The concept is very easy, but
yet, it's a very effective

00:34:57.290 --> 00:35:00.120 align:middle line:84%
to prevent privileged
users from accessing

00:35:00.120 --> 00:35:03.230 align:middle line:84%
non-privileged devices,
caching their credentials,

00:35:03.230 --> 00:35:08.320 align:middle line:84%
and then allowing attackers to
abuse those cached credentials.