WEBVTT

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


00:00:03.490 --> 00:00:07.790 align:middle line:84%
Hi Welcome to this video
lesson on Ping Castle.

00:00:07.790 --> 00:00:10.480 align:middle line:84%
Ping Castle is a tool,
which is going to scan

00:00:10.480 --> 00:00:12.290 align:middle line:90%
your entire environment.

00:00:12.290 --> 00:00:14.560 align:middle line:84%
And then create a report,
with all the findings

00:00:14.560 --> 00:00:18.250 align:middle line:84%
that it has on misconfigurations
or certain heartening

00:00:18.250 --> 00:00:21.190 align:middle line:84%
recommendations that
the tool can provide.

00:00:21.190 --> 00:00:23.680 align:middle line:84%
The report that the
tool generates is--

00:00:23.680 --> 00:00:25.700 align:middle line:84%
it consists of two
different parts.

00:00:25.700 --> 00:00:29.180 align:middle line:84%
The first part showcases
on a high level,

00:00:29.180 --> 00:00:31.180 align:middle line:84%
the risk level
towards the domain,

00:00:31.180 --> 00:00:33.550 align:middle line:84%
or your environment
and the second level

00:00:33.550 --> 00:00:37.810 align:middle line:84%
is the different technical
detection's and recommendations

00:00:37.810 --> 00:00:40.500 align:middle line:90%
that the tool comes up with.

00:00:40.500 --> 00:00:43.670 align:middle line:84%
So when, when Ping Castle
scans your environment,

00:00:43.670 --> 00:00:47.090 align:middle line:84%
It will extract information
about computers and users.

00:00:47.090 --> 00:00:50.040 align:middle line:84%
And then provide
information about--

00:00:50.040 --> 00:00:53.752 align:middle line:84%
for example one was
passwords or other one--

00:00:53.752 --> 00:00:56.210 align:middle line:84%
If there were any initiatives
that the password hasn't been

00:00:56.210 --> 00:00:59.330 align:middle line:84%
changed in the past three
years, or if there's

00:00:59.330 --> 00:01:01.290 align:middle line:84%
any Stale objects
like computer accounts

00:01:01.290 --> 00:01:03.360 align:middle line:84%
that haven't logged
in the past in years,

00:01:03.360 --> 00:01:04.954 align:middle line:84%
but they're still
active and enabled.

00:01:04.954 --> 00:01:07.790 align:middle line:84%
Like general things
for management active--

00:01:07.790 --> 00:01:09.560 align:middle line:90%
managing active directory.

00:01:09.560 --> 00:01:11.660 align:middle line:84%
It will also look into
some common issues,

00:01:11.660 --> 00:01:13.940 align:middle line:84%
such as the one that we
discussed previously,

00:01:13.940 --> 00:01:17.840 align:middle line:84%
specifically the group policy
preferences passwords, it

00:01:17.840 --> 00:01:21.140 align:middle line:84%
will check whether SMBv1
version or the Spooler service

00:01:21.140 --> 00:01:22.610 align:middle line:90%
is running domain controllers.

00:01:22.610 --> 00:01:25.775 align:middle line:84%
Is going to report on
all these small things.

00:01:25.775 --> 00:01:30.050 align:middle line:84%
It will also look into access
control list misconfigurations.

00:01:30.050 --> 00:01:33.440 align:middle line:84%
For example, if domain users
or authenticated users.

00:01:33.440 --> 00:01:36.830 align:middle line:84%
The everyone group if they
have been given any rights

00:01:36.830 --> 00:01:40.670 align:middle line:84%
for example, if they have any
rights towards changing a GPO

00:01:40.670 --> 00:01:44.690 align:middle line:84%
or changing a file that a GPO
is deploying to all workstations

00:01:44.690 --> 00:01:45.950 align:middle line:90%
and so on.

00:01:45.950 --> 00:01:49.070 align:middle line:84%
It will check for example,
if LAPS is installed

00:01:49.070 --> 00:01:51.530 align:middle line:84%
and the amount of checks
is really massive for us

00:01:51.530 --> 00:01:55.430 align:middle line:84%
to cover in this
presentation, the best way

00:01:55.430 --> 00:01:59.000 align:middle line:84%
to really understand the tool
is by executing it and then

00:01:59.000 --> 00:02:02.840 align:middle line:84%
looking into all the different
things that it detects.

00:02:02.840 --> 00:02:06.500 align:middle line:84%
And that is the best way because
it's constantly being improved,

00:02:06.500 --> 00:02:12.500 align:middle line:84%
the developers are releasing
new versions rather often.

00:02:12.500 --> 00:02:16.040 align:middle line:84%
So what we can cover in
here, or what we're not

00:02:16.040 --> 00:02:19.280 align:middle line:84%
going to showcase, Is most
likely not in the tool yet,

00:02:19.280 --> 00:02:21.090 align:middle line:90%
but it might come in the future.

00:02:21.090 --> 00:02:23.390 align:middle line:84%
But then again the current
list is really massive.

00:02:23.390 --> 00:02:25.740 align:middle line:90%
And let's take an example here.

00:02:25.740 --> 00:02:28.820 align:middle line:84%
If I remember in the high
overview report which

00:02:28.820 --> 00:02:31.910 align:middle line:84%
I was showing earlier
here the different,

00:02:31.910 --> 00:02:34.430 align:middle line:84%
the four different
categorizations

00:02:34.430 --> 00:02:38.450 align:middle line:84%
Stale objects, trust, first
accounts and anomalies.

00:02:38.450 --> 00:02:40.220 align:middle line:84%
So just to take some
of them, I wanted

00:02:40.220 --> 00:02:42.530 align:middle line:84%
to showcase the
different findings

00:02:42.530 --> 00:02:45.760 align:middle line:84%
that the two has for each of
the different categorizations.

00:02:45.760 --> 00:02:48.080 align:middle line:84%
For example for
the first accounts.

00:02:48.080 --> 00:02:50.870 align:middle line:84%
It detects that,
there are some 19

00:02:50.870 --> 00:02:53.060 align:middle line:84%
accounts at unconstrained
delegations configured

00:02:53.060 --> 00:02:54.170 align:middle line:90%
in our domain.

00:02:54.170 --> 00:02:57.680 align:middle line:84%
There's also a constraint
delegation configured

00:02:57.680 --> 00:02:59.400 align:middle line:90%
towards a domain controller.

00:02:59.400 --> 00:03:03.350 align:middle line:84%
And this risk I outlined
earlier in Keberos delegation.

00:03:03.350 --> 00:03:06.410 align:middle line:84%
Where an account with
delegation [INAUDIBLE]

00:03:06.410 --> 00:03:10.970 align:middle line:84%
can basically impersonate
anyone else the entire domain.

00:03:10.970 --> 00:03:12.180 align:middle line:90%
That could be really bad.

00:03:12.180 --> 00:03:13.970 align:middle line:84%
And then this too
will go undetected

00:03:13.970 --> 00:03:16.580 align:middle line:84%
if this exists in our
environment or not.

00:03:16.580 --> 00:03:20.120 align:middle line:90%
It will also check if the flag--

00:03:20.120 --> 00:03:22.520 align:middle line:84%
this account is sensitive
and cannot be delegated,

00:03:22.520 --> 00:03:25.910 align:middle line:90%
is set to our closed accounts.

00:03:25.910 --> 00:03:29.210 align:middle line:84%
It's also looking if service
accounts or an accounts that

00:03:29.210 --> 00:03:32.660 align:middle line:84%
have an SPN set are
also privileged.

00:03:32.660 --> 00:03:34.700 align:middle line:84%
And there is the
case in here, where

00:03:34.700 --> 00:03:37.940 align:middle line:84%
it says at least one member
of an administrative group

00:03:37.940 --> 00:03:41.190 align:middle line:84%
could potentially be vulnerable
to the Kerberos attack.

00:03:41.190 --> 00:03:41.690 align:middle line:90%
And so on.

00:03:41.690 --> 00:03:44.930 align:middle line:84%
The list continues it's really
hundreds and hundreds of things

00:03:44.930 --> 00:03:47.240 align:middle line:90%
that the tool can detect.

00:03:47.240 --> 00:03:50.120 align:middle line:84%
For anomalies, it
would look into when

00:03:50.120 --> 00:03:53.120 align:middle line:84%
was the last time that the
Kerberos password or Kerberos

00:03:53.120 --> 00:03:55.250 align:middle line:90%
DGT password was changed.

00:03:55.250 --> 00:03:57.050 align:middle line:84%
This is a topic,
which I have not--

00:03:57.050 --> 00:03:59.550 align:middle line:84%
which we have not discussed
yet in the course,

00:03:59.550 --> 00:04:01.880 align:middle line:84%
but we'll come back
to it later on.

00:04:01.880 --> 00:04:07.430 align:middle line:84%
It also shows that it
discovered two passwords in GPOs

00:04:07.430 --> 00:04:11.480 align:middle line:84%
and this is exactly the
group policy preferences

00:04:11.480 --> 00:04:14.090 align:middle line:84%
passwords, that we had
discussed previously.

00:04:14.090 --> 00:04:16.920 align:middle line:84%
There were two passwords
that were stored in there,

00:04:16.920 --> 00:04:18.274 align:middle line:90%
which the tool discovered.

00:04:18.274 --> 00:04:20.890 align:middle line:90%


00:04:20.890 --> 00:04:24.080 align:middle line:84%
It will also see that the
Spooler Service is running

00:04:24.080 --> 00:04:27.280 align:middle line:84%
on a 404 domain controllers,
and that's a good, good thing

00:04:27.280 --> 00:04:32.020 align:middle line:84%
to outline because that's one
of the services which we really

00:04:32.020 --> 00:04:34.150 align:middle line:84%
want to disable the
main controllers.

00:04:34.150 --> 00:04:36.160 align:middle line:84%
And the reason for
that, is because it

00:04:36.160 --> 00:04:38.350 align:middle line:84%
can really, really
easily be abused

00:04:38.350 --> 00:04:40.480 align:middle line:84%
with unconstrained
delegation, which

00:04:40.480 --> 00:04:43.030 align:middle line:84%
is exactly what we did earlier
when we were discussing

00:04:43.030 --> 00:04:44.750 align:middle line:90%
Kerberos delegation.

00:04:44.750 --> 00:04:47.950 align:middle line:84%
And then I also wanted to look
at the Stale objects rules.

00:04:47.950 --> 00:04:50.290 align:middle line:84%
Here it's going to
detect whether we

00:04:50.290 --> 00:04:53.740 align:middle line:84%
have presence of systems
that are no longer supported

00:04:53.740 --> 00:04:54.910 align:middle line:90%
by their vendors.

00:04:54.910 --> 00:04:56.770 align:middle line:84%
And what we're
going to see here is

00:04:56.770 --> 00:05:01.090 align:middle line:84%
examples of Windows 2000,
Windows 2003 servers,

00:05:01.090 --> 00:05:02.395 align:middle line:90%
Windows XP.

00:05:02.395 --> 00:05:06.760 align:middle line:84%
It detects that there are users
in our active directory, whose

00:05:06.760 --> 00:05:08.740 align:middle line:84%
primary group is
not domain users.

00:05:08.740 --> 00:05:10.930 align:middle line:84%
That's also something
that's going to detect on.

00:05:10.930 --> 00:05:12.430 align:middle line:84%
This is something
that we also want

00:05:12.430 --> 00:05:16.720 align:middle line:84%
to know about, because if we
had certain GPOs that we want

00:05:16.720 --> 00:05:20.530 align:middle line:84%
to apply startup scripts or
something on domain users,

00:05:20.530 --> 00:05:23.230 align:middle line:84%
unless these users were
manually added to domain users

00:05:23.230 --> 00:05:25.580 align:middle line:84%
afterwards, the GPO would
just not apply on them,

00:05:25.580 --> 00:05:28.820 align:middle line:84%
because the normal group
is not domain users.

00:05:28.820 --> 00:05:30.400 align:middle line:84%
So that's something
to be aware of

00:05:30.400 --> 00:05:33.787 align:middle line:84%
and again tool
check it up as well.

00:05:33.787 --> 00:05:35.620 align:middle line:84%
The last finding here
that I want to discuss

00:05:35.620 --> 00:05:38.140 align:middle line:84%
was the last one,
which is non admin

00:05:38.140 --> 00:05:40.410 align:middle line:90%
users that can add up to--

00:05:40.410 --> 00:05:43.210 align:middle line:84%
that can add up two
computers to domain.

00:05:43.210 --> 00:05:47.260 align:middle line:84%
The default in every domain,
is that every user can add up

00:05:47.260 --> 00:05:49.480 align:middle line:90%
to ten computers to a domain.

00:05:49.480 --> 00:05:51.580 align:middle line:84%
And that is really
against best practice

00:05:51.580 --> 00:05:55.210 align:middle line:84%
because you shouldn't let
users domain join machines,

00:05:55.210 --> 00:05:57.670 align:middle line:84%
rather it should only be
those specific accounts

00:05:57.670 --> 00:05:59.500 align:middle line:90%
that require this privilege.

00:05:59.500 --> 00:06:03.100 align:middle line:84%
So domain administrators
and one or two

00:06:03.100 --> 00:06:06.700 align:middle line:84%
accounts that are associated
with a system or other tools

00:06:06.700 --> 00:06:11.790 align:middle line:84%
that you might have for
domain joining new devices.

00:06:11.790 --> 00:06:14.150 align:middle line:84%
The finding here is that
every user could domain

00:06:14.150 --> 00:06:15.670 align:middle line:90%
join two computers.

00:06:15.670 --> 00:06:17.890 align:middle line:84%
And while it's not
the default ten,

00:06:17.890 --> 00:06:21.290 align:middle line:84%
it's still bad it
shouldn't be there.

00:06:21.290 --> 00:06:24.310 align:middle line:84%
Let's go into the environment,
and I want to just showcase

00:06:24.310 --> 00:06:26.320 align:middle line:90%
how to execute Ping Castle.

00:06:26.320 --> 00:06:29.410 align:middle line:84%
One thing to be aware of
is that Ping Castle is not

00:06:29.410 --> 00:06:30.580 align:middle line:90%
the free tool.

00:06:30.580 --> 00:06:33.520 align:middle line:84%
There is a free version
for experimenting

00:06:33.520 --> 00:06:35.870 align:middle line:90%
with getting used to the tool.

00:06:35.870 --> 00:06:39.430 align:middle line:84%
But if you want to use it in
an enterprise environment,

00:06:39.430 --> 00:06:41.470 align:middle line:84%
you have to pay the
license for that tool.

00:06:41.470 --> 00:06:44.800 align:middle line:84%
Let's move to the environment
and do a quick execution just

00:06:44.800 --> 00:06:49.670 align:middle line:84%
to see how easy it is
to get the data out.

00:06:49.670 --> 00:06:51.600 align:middle line:84%
I just connected
to the environment.

00:06:51.600 --> 00:06:55.640 align:middle line:84%
And I already downloaded the
what the Ping Castle tool.

00:06:55.640 --> 00:06:58.160 align:middle line:84%
I will go forward
and extract this zip

00:06:58.160 --> 00:07:04.200 align:middle line:84%
file, when extracted let's
navigate inside the folder.

00:07:04.200 --> 00:07:06.830 align:middle line:84%
In here, other than
the executable file,

00:07:06.830 --> 00:07:10.220 align:middle line:84%
we'll discover a few other
files which can tell us

00:07:10.220 --> 00:07:12.050 align:middle line:90%
how to use the tool itself.

00:07:12.050 --> 00:07:14.780 align:middle line:84%
We're going to omit them,
omit them at this point

00:07:14.780 --> 00:07:17.450 align:middle line:84%
and just focus on
the executable file.

00:07:17.450 --> 00:07:20.315 align:middle line:84%
We're going to run the
executable file from a Power

00:07:20.315 --> 00:07:24.860 align:middle line:84%
Shell prompt, so I'll
start Power Shell

00:07:24.860 --> 00:07:32.340 align:middle line:84%
and then type the executable
name, which is pingcastle.ac

00:07:32.340 --> 00:07:34.440 align:middle line:84%
Now when you run
the tool, it will

00:07:34.440 --> 00:07:38.370 align:middle line:84%
ask you to choose an
option which to proceed.

00:07:38.370 --> 00:07:41.740 align:middle line:84%
Option number one is
health checks score,

00:07:41.740 --> 00:07:45.210 align:middle line:84%
then you have different
checks that you can perform,

00:07:45.210 --> 00:07:47.580 align:middle line:84%
if you want to go
more [INAUDIBLE]..

00:07:47.580 --> 00:07:51.390 align:middle line:84%
For this specific test, we'll
just go with option one,

00:07:51.390 --> 00:07:55.610 align:middle line:84%
and simply press enter
to proceed forward with.

00:07:55.610 --> 00:08:00.830 align:middle line:84%
Now we get prompted to specify
the domain name that we want

00:08:00.830 --> 00:08:03.140 align:middle line:84%
investigate, and it
detects the current one

00:08:03.140 --> 00:08:05.340 align:middle line:84%
that the user is
going to look into.

00:08:05.340 --> 00:08:08.840 align:middle line:84%
In this case, there is ELS
bank, and this is a domain

00:08:08.840 --> 00:08:09.780 align:middle line:90%
that you want to scan.

00:08:09.780 --> 00:08:14.760 align:middle line:84%
So we're going to just go
forward and press enter again.

00:08:14.760 --> 00:08:17.760 align:middle line:84%
Now data gathering has
started, and depending

00:08:17.760 --> 00:08:20.600 align:middle line:84%
on how big the environment
is this tool might take

00:08:20.600 --> 00:08:23.150 align:middle line:84%
a couple of minutes to
execute as what you're

00:08:23.150 --> 00:08:26.300 align:middle line:84%
going to see in here in a
small environment like mine,

00:08:26.300 --> 00:08:28.910 align:middle line:84%
it will just take
a couple of seconds

00:08:28.910 --> 00:08:31.760 align:middle line:84%
and we'll have all the
data collected then

00:08:31.760 --> 00:08:35.120 align:middle line:84%
ready to be
displayed back to us.

00:08:35.120 --> 00:08:38.909 align:middle line:84%
It's gathering data about
many different arch, arch,

00:08:38.909 --> 00:08:42.500 align:middle line:84%
and arch directory and then
ensembles the final report,

00:08:42.500 --> 00:08:44.703 align:middle line:90%
with all of them being present.

00:08:44.703 --> 00:08:46.370 align:middle line:84%
And what we're seeing
on the screen now,

00:08:46.370 --> 00:08:49.770 align:middle line:84%
is that the actual final
report is already done.

00:08:49.770 --> 00:08:54.200 align:middle line:84%
And we can see it, in the
same folder as dedicatable.

00:08:54.200 --> 00:08:57.160 align:middle line:84%
And the new name is
an HTML document.

00:08:57.160 --> 00:09:04.530 align:middle line:84%
In this case, it is called a- g-
h- s- the domain name dot HTML.

00:09:04.530 --> 00:09:07.290 align:middle line:84%
So let's go forward
and open this file.

00:09:07.290 --> 00:09:11.000 align:middle line:90%


00:09:11.000 --> 00:09:15.460 align:middle line:84%
Immediately we get presented
with the nice report

00:09:15.460 --> 00:09:19.360 align:middle line:84%
of all the different
indicators of risk

00:09:19.360 --> 00:09:22.420 align:middle line:84%
levels in our environment,
or the four different ones

00:09:22.420 --> 00:09:24.400 align:middle line:84%
that we discussed
already in the slides.

00:09:24.400 --> 00:09:28.600 align:middle line:84%
It tells us that, the
overall risk for our domain

00:09:28.600 --> 00:09:30.910 align:middle line:90%
is 80 out of 100.

00:09:30.910 --> 00:09:34.621 align:middle line:84%
And then it shows
us the different--

00:09:34.621 --> 00:09:38.550 align:middle line:84%
four categories which
assemble data for.

00:09:38.550 --> 00:09:42.970 align:middle line:84%
You will see that the overall
domain risk level, will always

00:09:42.970 --> 00:09:46.300 align:middle line:84%
be the same as the
highest one that it has

00:09:46.300 --> 00:09:48.100 align:middle line:90%
detected in these four areas.

00:09:48.100 --> 00:09:50.680 align:middle line:84%
And in this case it
is 80 out of 100,

00:09:50.680 --> 00:09:55.180 align:middle line:84%
because that is the score
under the previous account.

00:09:55.180 --> 00:09:59.690 align:middle line:84%
So if we go further down, we
can see the actual findings

00:09:59.690 --> 00:10:01.460 align:middle line:90%
that this tool has detected.

00:10:01.460 --> 00:10:03.800 align:middle line:84%
So under Stale objects
we'll see the we

00:10:03.800 --> 00:10:08.240 align:middle line:84%
have non admin users can add up
to ten computers to the domain.

00:10:08.240 --> 00:10:11.240 align:middle line:84%
Another interesting one is,
number of accounts which do not

00:10:11.240 --> 00:10:13.940 align:middle line:84%
required Keberos
specification is one.

00:10:13.940 --> 00:10:16.100 align:middle line:84%
We can actually
press on this, to get

00:10:16.100 --> 00:10:20.000 align:middle line:84%
a very detailed descriptive
information about defining

00:10:20.000 --> 00:10:22.640 align:middle line:84%
itself, some technical
explanation behind it

00:10:22.640 --> 00:10:27.170 align:middle line:84%
and a potential solution that
the developers of this tool

00:10:27.170 --> 00:10:28.460 align:middle line:90%
have advised.

00:10:28.460 --> 00:10:30.410 align:middle line:84%
But what is also
more important here

00:10:30.410 --> 00:10:34.200 align:middle line:84%
is that, it also show us
immediately the account,

00:10:34.200 --> 00:10:39.050 align:middle line:84%
which was found to be vulnerable
to this specific finding.

00:10:39.050 --> 00:10:42.700 align:middle line:84%
Now if we go further down
in Privileged accounts

00:10:42.700 --> 00:10:44.890 align:middle line:90%
we'll see that.

00:10:44.890 --> 00:10:47.620 align:middle line:84%
It gives us an
estimate that everyone

00:10:47.620 --> 00:10:50.200 align:middle line:84%
can take control of
a key domain object,

00:10:50.200 --> 00:10:52.270 align:middle line:90%
by abusing targeted permissions.

00:10:52.270 --> 00:10:55.300 align:middle line:84%
This finding if we
look further into it,

00:10:55.300 --> 00:10:58.960 align:middle line:84%
is essentially telling us
that every domain object user

00:10:58.960 --> 00:11:05.380 align:middle line:84%
computer, will has the ability
to hijack a path domain

00:11:05.380 --> 00:11:06.290 align:middle line:90%
identity.

00:11:06.290 --> 00:11:08.410 align:middle line:84%
It could be, for
example there's a path

00:11:08.410 --> 00:11:11.590 align:middle line:84%
for escalation to the
domain admin centres.

00:11:11.590 --> 00:11:15.790 align:middle line:84%
The next one is telling us
that, there is a GPO item that

00:11:15.790 --> 00:11:18.340 align:middle line:90%
can be manipulated by any user.

00:11:18.340 --> 00:11:21.190 align:middle line:84%
If I expand this, we'll
see the information

00:11:21.190 --> 00:11:22.310 align:middle line:90%
for this specific GPO.

00:11:22.310 --> 00:11:26.640 align:middle line:84%
It will tell us that there's
a GPO which is lapse decoy,

00:11:26.640 --> 00:11:28.950 align:middle line:84%
and authenticated
users in the domain

00:11:28.950 --> 00:11:33.340 align:middle line:90%
have full control over this GPO.

00:11:33.340 --> 00:11:35.290 align:middle line:84%
And this is really
bad, this is one

00:11:35.290 --> 00:11:39.760 align:middle line:84%
of those findings which we
really have to rush and go fix

00:11:39.760 --> 00:11:44.440 align:middle line:84%
immediately because if this
is linked to a device where

00:11:44.440 --> 00:11:49.450 align:middle line:84%
the previous user is logging in
or accessing that could really

00:11:49.450 --> 00:11:53.110 align:middle line:84%
end up being full domain
compromise for us.

00:11:53.110 --> 00:11:56.610 align:middle line:84%
And of course something
that we want to avoid.

00:11:56.610 --> 00:11:59.760 align:middle line:84%
Scrolling further down
we'll see other information

00:11:59.760 --> 00:12:00.600 align:middle line:90%
about the domain.

00:12:00.600 --> 00:12:06.170 align:middle line:84%
Some of them are
really informative

00:12:06.170 --> 00:12:09.200 align:middle line:84%
like unconstrained delegations
are configured on one domain

00:12:09.200 --> 00:12:10.575 align:middle line:90%
account.

00:12:10.575 --> 00:12:12.710 align:middle line:84%
When unconstrained delegation
is one of those flaws

00:12:12.710 --> 00:12:15.560 align:middle line:84%
which we discussed and it's
really bad, but in many cases

00:12:15.560 --> 00:12:17.220 align:middle line:90%
it's required to be used.

00:12:17.220 --> 00:12:19.250 align:middle line:90%
So the tool just sluggish--

00:12:19.250 --> 00:12:21.500 align:middle line:84%
back, back to us that
there's an account, which

00:12:21.500 --> 00:12:22.700 align:middle line:90%
has disconfigured.

00:12:22.700 --> 00:12:25.170 align:middle line:84%
So it's up to us at
this point to decide,

00:12:25.170 --> 00:12:28.370 align:middle line:84%
does this account actually
need this permission or not.

00:12:28.370 --> 00:12:32.000 align:middle line:84%
Because if it doesn't we need to
do a clean up and simply remove

00:12:32.000 --> 00:12:33.830 align:middle line:90%
these permissions.

00:12:33.830 --> 00:12:36.350 align:middle line:84%
There's also some trust
which were identified

00:12:36.350 --> 00:12:39.308 align:middle line:90%
in the mine and some anomalies.

00:12:39.308 --> 00:12:41.850 align:middle line:84%
What we're going to see here
and probably interesting for you

00:12:41.850 --> 00:12:44.945 align:middle line:84%
we already discussed is that,
the Spooler service is running

00:12:44.945 --> 00:12:49.170 align:middle line:84%
on domain controllers, and
password policies for service

00:12:49.170 --> 00:12:50.730 align:middle line:90%
accounts have not been found.

00:12:50.730 --> 00:12:54.090 align:middle line:84%
And the tool recommends that
these password policies should

00:12:54.090 --> 00:12:56.730 align:middle line:84%
be at least 20 characters,
but our recommendation

00:12:56.730 --> 00:12:58.357 align:middle line:90%
was 100 or more.

00:12:58.357 --> 00:12:59.940 align:middle line:84%
Scrolling further
down the report port

00:12:59.940 --> 00:13:02.670 align:middle line:84%
we'll get a very detailed
information about users,

00:13:02.670 --> 00:13:04.140 align:middle line:90%
about groups.

00:13:04.140 --> 00:13:06.360 align:middle line:84%
How many of them are
active, how many of them

00:13:06.360 --> 00:13:10.200 align:middle line:84%
are disabled,
logged and very rich

00:13:10.200 --> 00:13:14.490 align:middle line:84%
detailed information,
about our entire domain.

00:13:14.490 --> 00:13:16.340 align:middle line:84%
In here, for example,
we can see an overview

00:13:16.340 --> 00:13:19.700 align:middle line:84%
of how many users are members,
of the previous groups.

00:13:19.700 --> 00:13:21.980 align:middle line:84%
How many of them are enabled,
how many are disabled,

00:13:21.980 --> 00:13:24.290 align:middle line:90%
inactive and so on.

00:13:24.290 --> 00:13:27.050 align:middle line:84%
It could be really, really
valuable use information.

00:13:27.050 --> 00:13:29.540 align:middle line:84%
When we have all
delegations, it will

00:13:29.540 --> 00:13:31.950 align:middle line:84%
show us delegations on
organizational units.

00:13:31.950 --> 00:13:33.830 align:middle line:84%
So in here we can
see that the account

00:13:33.830 --> 00:13:38.300 align:middle line:84%
Rooney, has full control
over admin as the holder.

00:13:38.300 --> 00:13:41.480 align:middle line:84%
And this is again
one of those really

00:13:41.480 --> 00:13:46.430 align:middle line:84%
configurations because what this
means is that, Rooney will not

00:13:46.430 --> 00:13:50.360 align:middle line:84%
only have the ability
to modify the OU codes

00:13:50.360 --> 00:13:53.090 align:middle line:84%
admin as the holder,
but having the ability

00:13:53.090 --> 00:13:57.650 align:middle line:84%
over this specific object,
also gives you the same ability

00:13:57.650 --> 00:13:58.980 align:middle line:90%
over previous groups.

00:13:58.980 --> 00:14:02.200 align:middle line:84%
So because Rooney is set to
modify admin as the holder

00:14:02.200 --> 00:14:06.290 align:middle line:84%
he is going to inherit, that
he can also go and modify

00:14:06.290 --> 00:14:08.540 align:middle line:84%
the group for
example domain admins

00:14:08.540 --> 00:14:11.030 align:middle line:90%
and that's absolutely crazy.

00:14:11.030 --> 00:14:12.560 align:middle line:84%
Then scrolling
further down, we'll

00:14:12.560 --> 00:14:15.815 align:middle line:84%
just continuously get
the rich information

00:14:15.815 --> 00:14:19.120 align:middle line:84%
that this tool gives back to
us about the rest of domain.

00:14:19.120 --> 00:14:21.830 align:middle line:84%
I'll scroll all the
way down, and they'll

00:14:21.830 --> 00:14:24.350 align:middle line:84%
show you what they're
really like in here as well.

00:14:24.350 --> 00:14:27.800 align:middle line:84%
Is that it will give us an
overview of all the files

00:14:27.800 --> 00:14:29.390 align:middle line:90%
that GPOs are deploying.

00:14:29.390 --> 00:14:33.500 align:middle line:84%
In this case, there's only one
file, which a GPO is deploying.

00:14:33.500 --> 00:14:35.360 align:middle line:84%
And what is interesting
is that, it just

00:14:35.360 --> 00:14:37.310 align:middle line:84%
happens to be the
same GPO, that we

00:14:37.310 --> 00:14:42.020 align:middle line:84%
discovered every authenticated
users can go and modify.

00:14:42.020 --> 00:14:43.000 align:middle line:90%