WEBVTT

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


00:00:02.900 --> 00:00:03.630 align:middle line:90%
Hi.

00:00:03.630 --> 00:00:05.660 align:middle line:84%
Welcome to this
video lesson in which

00:00:05.660 --> 00:00:09.490 align:middle line:84%
we're going to talk about
the Protected Users Group.

00:00:09.490 --> 00:00:11.290 align:middle line:84%
Once we discuss the
protected users,

00:00:11.290 --> 00:00:15.220 align:middle line:84%
we'll actually show a small
demonstration that demonstrates

00:00:15.220 --> 00:00:17.770 align:middle line:84%
a problem or rather
a feature, it's

00:00:17.770 --> 00:00:23.080 align:middle line:84%
an expected behavior that occurs
for members of this group.

00:00:23.080 --> 00:00:26.410 align:middle line:84%
But what I've seen across
different environments

00:00:26.410 --> 00:00:28.360 align:middle line:84%
is that it's causing
a lot of troubles,

00:00:28.360 --> 00:00:30.800 align:middle line:84%
and we'll look into
that afterwards.

00:00:30.800 --> 00:00:34.090 align:middle line:84%
So the protected users
group as stated by Microsoft

00:00:34.090 --> 00:00:37.120 align:middle line:84%
was designed as a
part of a strategy

00:00:37.120 --> 00:00:40.600 align:middle line:84%
to manage credential exposure
and minimize that, essentially,

00:00:40.600 --> 00:00:42.370 align:middle line:90%
in the entire environment.

00:00:42.370 --> 00:00:44.410 align:middle line:84%
Every member of this
group automatically

00:00:44.410 --> 00:00:47.320 align:middle line:84%
inherits certain
protections that

00:00:47.320 --> 00:00:50.410 align:middle line:84%
will prevent these accounts
from caching credentials

00:00:50.410 --> 00:00:54.550 align:middle line:84%
and essentially reducing the
ability of an attacker to still

00:00:54.550 --> 00:00:58.160 align:middle line:90%
produce users' credentials.

00:00:58.160 --> 00:01:05.090 align:middle line:84%
Now, the group originally
came with those domains 2012R2

00:01:05.090 --> 00:01:09.140 align:middle line:84%
and later it was
backported to 2008R2.

00:01:09.140 --> 00:01:12.680 align:middle line:84%
Even though it was backported,
some of the functionality

00:01:12.680 --> 00:01:19.670 align:middle line:84%
is just partially there,
it's not as good as in 2012.

00:01:19.670 --> 00:01:25.160 align:middle line:84%
When we talk about protection
by the protected users group,

00:01:25.160 --> 00:01:29.180 align:middle line:84%
this protection is divided
into different categories

00:01:29.180 --> 00:01:34.310 align:middle line:84%
or domains, that would be
protection at the host device

00:01:34.310 --> 00:01:36.930 align:middle line:90%
and protection at domain level.

00:01:36.930 --> 00:01:39.800 align:middle line:84%
Now, I'll go through
these two domains

00:01:39.800 --> 00:01:42.110 align:middle line:84%
just to show you the
actual protection

00:01:42.110 --> 00:01:44.240 align:middle line:90%
that the group provides.

00:01:44.240 --> 00:01:47.870 align:middle line:84%
So from a host
protection perspective

00:01:47.870 --> 00:01:50.840 align:middle line:84%
the credential
delegation, CredSSP,

00:01:50.840 --> 00:01:54.740 align:middle line:84%
will no longer cache plain
text credentials of users

00:01:54.740 --> 00:01:57.450 align:middle line:84%
at the endpoint, which
was the case before.

00:01:57.450 --> 00:02:00.800 align:middle line:84%
So if a user RDP's
into a server,

00:02:00.800 --> 00:02:04.520 align:middle line:84%
the credentials will be
cached in plain text.

00:02:04.520 --> 00:02:07.070 align:middle line:84%
Right now if a
user RDP's, nothing

00:02:07.070 --> 00:02:09.430 align:middle line:84%
is going to be cached
at the LSASS process.

00:02:09.430 --> 00:02:11.600 align:middle line:84%
So tools like Mimikatz,
they should not

00:02:11.600 --> 00:02:14.900 align:middle line:84%
be able to export any
credentials of produced

00:02:14.900 --> 00:02:19.060 align:middle line:84%
users that are a member
of protected users.

00:02:19.060 --> 00:02:23.510 align:middle line:84%
With Windows 8.1
and server 2012 R2

00:02:23.510 --> 00:02:26.620 align:middle line:84%
double digest will also not
cache plain text credentials

00:02:26.620 --> 00:02:29.330 align:middle line:84%
when users are a
member of this group.

00:02:29.330 --> 00:02:32.870 align:middle line:84%
NTLM will not cache
its NTLM hash.

00:02:32.870 --> 00:02:35.480 align:middle line:84%
And that's just
absolutely fantastic

00:02:35.480 --> 00:02:38.510 align:middle line:84%
because we're not talking about
only not caching plain text

00:02:38.510 --> 00:02:44.750 align:middle line:84%
credentials but we're also not
caching NTLM password hashes.

00:02:44.750 --> 00:02:49.540 align:middle line:84%
Then Kerberos will no
longer use DES or RC4

00:02:49.540 --> 00:02:52.190 align:middle line:84%
for users that are a
member of this group.

00:02:52.190 --> 00:02:55.040 align:middle line:84%
And this is where we
start seeing problems

00:02:55.040 --> 00:02:58.340 align:middle line:84%
because many
applications rely on

00:02:58.340 --> 00:03:02.570 align:middle line:84%
or they require RC4 to
authenticate their users.

00:03:02.570 --> 00:03:04.430 align:middle line:84%
And it's a whole
different question

00:03:04.430 --> 00:03:08.120 align:middle line:84%
of why would you have an
administrative account needing

00:03:08.120 --> 00:03:12.320 align:middle line:84%
access to an application such
as something that requires RC4?

00:03:12.320 --> 00:03:15.020 align:middle line:84%
But the fact is that
in many enterprises

00:03:15.020 --> 00:03:19.400 align:middle line:84%
this is what people do and when
a user is a member of protected

00:03:19.400 --> 00:03:22.370 align:middle line:84%
users it might
cause applications

00:03:22.370 --> 00:03:26.260 align:middle line:84%
to not authenticate
or SSO will not work.

00:03:26.260 --> 00:03:30.170 align:middle line:84%
I've seen multiple organizations
where SSO broke immediately

00:03:30.170 --> 00:03:32.870 align:middle line:84%
for users that were a
member of protected users

00:03:32.870 --> 00:03:39.500 align:middle line:84%
because that SSO relied on RC4
to be allowed with Kerberos

00:03:39.500 --> 00:03:41.450 align:middle line:90%
authentication.

00:03:41.450 --> 00:03:43.490 align:middle line:84%
The next one that
is problematic is

00:03:43.490 --> 00:03:47.330 align:middle line:84%
that you can no longer
send to machine that is not

00:03:47.330 --> 00:03:49.160 align:middle line:84%
on the network,
you need actively

00:03:49.160 --> 00:03:51.307 align:middle line:90%
to contact a domain controller.

00:03:51.307 --> 00:03:54.350 align:middle line:90%


00:03:54.350 --> 00:03:57.200 align:middle line:84%
Think about before when you
give a workstation to someone,

00:03:57.200 --> 00:04:00.050 align:middle line:84%
you first ask them to sign-in
once so their profile will

00:04:00.050 --> 00:04:03.650 align:middle line:84%
be cached and then they can
sign-off afterwards as well.

00:04:03.650 --> 00:04:06.850 align:middle line:84%
If you're a member of protected
users you cannot sign offline,

00:04:06.850 --> 00:04:10.150 align:middle line:84%
you can only sign when
you're on the network.

00:04:10.150 --> 00:04:13.740 align:middle line:84%
And with that which also
comes as domain protection,

00:04:13.740 --> 00:04:15.240 align:middle line:84%
and we're going to
this in a second,

00:04:15.240 --> 00:04:17.700 align:middle line:84%
is that NTLM
authentication is not

00:04:17.700 --> 00:04:21.130 align:middle line:84%
going to be allowed if you're
a member of this group.

00:04:21.130 --> 00:04:23.410 align:middle line:90%
So does it sound crazy?

00:04:23.410 --> 00:04:26.620 align:middle line:84%
It probably does
because now we're really

00:04:26.620 --> 00:04:29.890 align:middle line:90%
thinking and talking problems.

00:04:29.890 --> 00:04:34.360 align:middle line:84%
Many tools and programs will
utilize NTLM to authenticate,

00:04:34.360 --> 00:04:36.610 align:middle line:84%
they just simply don't
support Kerberos.

00:04:36.610 --> 00:04:41.490 align:middle line:84%
Most common ones
are VPN providers.

00:04:41.490 --> 00:04:45.850 align:middle line:84%
So if you have a VPN likelihood
to be using NTLM is very high.

00:04:45.850 --> 00:04:50.560 align:middle line:84%
And you will not be able to
use that with a user that

00:04:50.560 --> 00:04:55.830 align:middle line:84%
is a member of protected users
anymore because to authenticate

00:04:55.830 --> 00:04:59.110 align:middle line:84%
with VPN you're obviously
not on the network

00:04:59.110 --> 00:05:00.570 align:middle line:84%
so you can't login
with Kerberos,

00:05:00.570 --> 00:05:02.310 align:middle line:84%
you can't get your
Kerberos ticket

00:05:02.310 --> 00:05:05.640 align:middle line:90%
that is a requirement now.

00:05:05.640 --> 00:05:08.220 align:middle line:84%
Again, domain-wide
we are also blocking

00:05:08.220 --> 00:05:12.910 align:middle line:84%
Kerberos pre-authentication
with RC4 and DES.

00:05:12.910 --> 00:05:16.270 align:middle line:84%
Something great that came
afterwards was also that

00:05:16.270 --> 00:05:20.420 align:middle line:84%
if you're a member protected
users, you cannot be delegated.

00:05:20.420 --> 00:05:23.470 align:middle line:84%
So all the delegation attacks
that we discussed with Kerberos

00:05:23.470 --> 00:05:25.990 align:middle line:84%
delegation in the
beginning of this course

00:05:25.990 --> 00:05:30.400 align:middle line:84%
will be mitigated if a user
is a member of this group.

00:05:30.400 --> 00:05:32.440 align:middle line:84%
But this protection
is only for that user

00:05:32.440 --> 00:05:36.560 align:middle line:84%
or the members of the
group, not for the domain.

00:05:36.560 --> 00:05:40.290 align:middle line:84%
And the last protection
is that the Kerberos TGTs

00:05:40.290 --> 00:05:45.210 align:middle line:84%
will need to be renewed after
the initial four-hour lifetime.

00:05:45.210 --> 00:05:48.780 align:middle line:84%
Now, I want to show
you how problematic it

00:05:48.780 --> 00:05:52.230 align:middle line:84%
could be to get into a machine
which is not on the domain

00:05:52.230 --> 00:05:55.230 align:middle line:84%
network if you want to
log in as a user that

00:05:55.230 --> 00:05:58.010 align:middle line:90%
is a member of protected users.

00:05:58.010 --> 00:06:00.300 align:middle line:84%
And this is not because
it's problematic,

00:06:00.300 --> 00:06:02.040 align:middle line:84%
it's more that it's
something you should

00:06:02.040 --> 00:06:06.240 align:middle line:84%
be aware of before
going forward and having

00:06:06.240 --> 00:06:08.160 align:middle line:90%
members of this group.

00:06:08.160 --> 00:06:11.580 align:middle line:84%
And while I highly recommend
you go forward and have

00:06:11.580 --> 00:06:15.270 align:middle line:84%
your produced accounts being
members of protected users,

00:06:15.270 --> 00:06:18.630 align:middle line:84%
at least tier-0
to begin with, you

00:06:18.630 --> 00:06:20.880 align:middle line:84%
should be careful
while adding them

00:06:20.880 --> 00:06:24.510 align:middle line:84%
and start by taking only a
few accounts at a the time

00:06:24.510 --> 00:06:26.190 align:middle line:84%
instead of just taking
all your accounts

00:06:26.190 --> 00:06:28.860 align:middle line:84%
and adding them to this group
because you might end up

00:06:28.860 --> 00:06:31.590 align:middle line:84%
in a position where you just
simply lock out yourself

00:06:31.590 --> 00:06:33.720 align:middle line:90%
of your active directory.

00:06:33.720 --> 00:06:35.640 align:middle line:84%
Let's look into
the demonstration.

00:06:35.640 --> 00:06:38.520 align:middle line:84%
Let's begin by looking at
the protected users group.

00:06:38.520 --> 00:06:42.910 align:middle line:84%
It is located by
default in the users OU.

00:06:42.910 --> 00:06:45.010 align:middle line:84%
If I double click
and look at members,

00:06:45.010 --> 00:06:48.010 align:middle line:84%
I already added the account
administrator of this domain

00:06:48.010 --> 00:06:50.920 align:middle line:90%
to showcase with this account.

00:06:50.920 --> 00:06:53.180 align:middle line:84%
Because this account is
a member of the group,

00:06:53.180 --> 00:06:56.380 align:middle line:84%
now it automatically inherits
all of the protections

00:06:56.380 --> 00:06:57.820 align:middle line:90%
that this group provides.

00:06:57.820 --> 00:06:59.350 align:middle line:84%
And what we're
going to see in here

00:06:59.350 --> 00:07:04.900 align:middle line:84%
is that domain functional
level since 2016

00:07:04.900 --> 00:07:06.910 align:middle line:84%
so we are inheriting
and benefiting

00:07:06.910 --> 00:07:11.160 align:middle line:84%
from all the protections
that this group provides.

00:07:11.160 --> 00:07:14.000 align:middle line:84%
Now, I'll move away from
the domain controller

00:07:14.000 --> 00:07:15.910 align:middle line:90%
and go to a server.

00:07:15.910 --> 00:07:19.660 align:middle line:84%
I will try to login with
the account administrator

00:07:19.660 --> 00:07:21.820 align:middle line:84%
and as you'll see
there's no issues,

00:07:21.820 --> 00:07:23.620 align:middle line:90%
everything works expected.

00:07:23.620 --> 00:07:27.130 align:middle line:84%
My server is on the
network, I can get on.

00:07:27.130 --> 00:07:30.070 align:middle line:84%
And this login is
now with Kerberos

00:07:30.070 --> 00:07:32.880 align:middle line:84%
because NTLM is
no longer allowed.

00:07:32.880 --> 00:07:38.630 align:middle line:84%
Now what I'm going to do
is I will sign-out and cut

00:07:38.630 --> 00:07:42.130 align:middle line:84%
the network connection
of this machine.

00:07:42.130 --> 00:07:46.670 align:middle line:84%
That would be into my
settings, I will just not

00:07:46.670 --> 00:07:48.470 align:middle line:90%
have it connected.

00:07:48.470 --> 00:07:51.440 align:middle line:84%
Now, you can see immediately
that the network changed.

00:07:51.440 --> 00:07:54.050 align:middle line:84%
And even though we just saw
that I had logged in with this

00:07:54.050 --> 00:07:56.150 align:middle line:84%
account in the
machine previously,

00:07:56.150 --> 00:08:00.680 align:middle line:84%
if I try to do that now
I'm getting an error,

00:08:00.680 --> 00:08:03.140 align:middle line:90%
the account cannot sign-in.

00:08:03.140 --> 00:08:05.900 align:middle line:84%
Now, this might not be very
problematic with servers, which

00:08:05.900 --> 00:08:08.000 align:middle line:84%
are constantly on
the network, it

00:08:08.000 --> 00:08:11.780 align:middle line:84%
could be problematic
with logging

00:08:11.780 --> 00:08:15.630 align:middle line:84%
into workstations with devices
which are not on your network.

00:08:15.630 --> 00:08:18.830 align:middle line:84%
So having
administrative accounts,

00:08:18.830 --> 00:08:21.080 align:middle line:84%
member of this
group for users that

00:08:21.080 --> 00:08:24.380 align:middle line:84%
require to log into
a device offline

00:08:24.380 --> 00:08:26.480 align:middle line:90%
is going to be very dangerous.

00:08:26.480 --> 00:08:30.800 align:middle line:84%
Out of fairness, if only tier-0
are the only accounts that

00:08:30.800 --> 00:08:32.809 align:middle line:84%
are members of protected
users or the ones

00:08:32.809 --> 00:08:36.350 align:middle line:84%
that you start with, you should
never use that tier-0 account

00:08:36.350 --> 00:08:37.940 align:middle line:90%
out of your network.

00:08:37.940 --> 00:08:41.570 align:middle line:84%
You might need to do
it during an emergency

00:08:41.570 --> 00:08:44.900 align:middle line:84%
if you're urgently needed
and you're at home.

00:08:44.900 --> 00:08:48.530 align:middle line:84%
So you have to log in through
a produced admin workstation

00:08:48.530 --> 00:08:50.300 align:middle line:90%
and access your environment.

00:08:50.300 --> 00:08:54.170 align:middle line:84%
And that's where we'll keep
our regular produced admin

00:08:54.170 --> 00:08:57.170 align:middle line:84%
workstation users, not
being a member of this group

00:08:57.170 --> 00:08:59.930 align:middle line:84%
to gain access to the network
but transferring the network,

00:08:59.930 --> 00:09:04.500 align:middle line:84%
we can utilize our protected
users going forward.

00:09:04.500 --> 00:09:05.000 align:middle line:90%