WEBVTT

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


00:00:09.805 --> 00:00:11.430 align:middle line:84%
In this lab, I'm
going to introduce you

00:00:11.430 --> 00:00:14.100 align:middle line:90%
to a couple of tools.

00:00:14.100 --> 00:00:17.220 align:middle line:84%
They come from the United
States Department of Defense,

00:00:17.220 --> 00:00:23.100 align:middle line:84%
who originally had the CMMC
model for cyber maturity.

00:00:23.100 --> 00:00:27.870 align:middle line:84%
And it includes 17
capability domains and five

00:00:27.870 --> 00:00:30.900 align:middle line:90%
different maturity levels.

00:00:30.900 --> 00:00:33.540 align:middle line:84%
And the tool that was
most commonly used

00:00:33.540 --> 00:00:36.480 align:middle line:84%
is the Security Content
Application Protocol,

00:00:36.480 --> 00:00:40.530 align:middle line:84%
which is part of the Security
Technical Implementation

00:00:40.530 --> 00:00:42.730 align:middle line:90%
Guides.

00:00:42.730 --> 00:00:45.750 align:middle line:90%
So the guides are requirements.

00:00:45.750 --> 00:00:52.050 align:middle line:84%
And they actually map
back to NIST 800-53.

00:00:52.050 --> 00:00:54.450 align:middle line:84%
And then the SCAP
is the protocol.

00:00:54.450 --> 00:00:57.990 align:middle line:84%
It's the scanning
benchmarks that

00:00:57.990 --> 00:01:05.489 align:middle line:84%
then are used to check and see
if the requirements in 800-53

00:01:05.489 --> 00:01:07.330 align:middle line:90%
are completed or not.

00:01:07.330 --> 00:01:08.927 align:middle line:84%
So let's jump into
the environment

00:01:08.927 --> 00:01:09.885 align:middle line:90%
and see how that works.

00:01:09.885 --> 00:01:14.830 align:middle line:90%


00:01:14.830 --> 00:01:17.110 align:middle line:84%
We have this Windows
Server 2016--

00:01:17.110 --> 00:01:19.570 align:middle line:90%
or 2019, I should say.

00:01:19.570 --> 00:01:23.320 align:middle line:90%
We have the SCAP tool.

00:01:23.320 --> 00:01:25.097 align:middle line:90%
Run it as administrator.

00:01:25.097 --> 00:01:39.710 align:middle line:90%


00:01:39.710 --> 00:01:42.760 align:middle line:84%
And we can see here that
the benchmarks are already

00:01:42.760 --> 00:01:46.210 align:middle line:84%
in the Windows
Server 2019 state.

00:01:46.210 --> 00:01:48.130 align:middle line:84%
And we're just going
to start the scan.

00:01:48.130 --> 00:03:09.840 align:middle line:90%


00:03:09.840 --> 00:03:13.350 align:middle line:84%
And we can see that the
scan results are complete.

00:03:13.350 --> 00:03:16.920 align:middle line:90%
We then view results.

00:03:16.920 --> 00:03:20.230 align:middle line:84%
And a quick view over here
shows an average max and min

00:03:20.230 --> 00:03:21.990 align:middle line:90%
of 46.37%.

00:03:21.990 --> 00:03:25.140 align:middle line:90%
Well, let's dig in a little bit.

00:03:25.140 --> 00:03:27.105 align:middle line:84%
I right-clicked
Open Summary Viewer

00:03:27.105 --> 00:03:29.325 align:middle line:90%
in OS default web browser.

00:03:29.325 --> 00:03:35.390 align:middle line:90%


00:03:35.390 --> 00:03:37.040 align:middle line:84%
And initially it's
blocked content,

00:03:37.040 --> 00:03:38.195 align:middle line:90%
so allow blocked content.

00:03:38.195 --> 00:03:41.210 align:middle line:90%


00:03:41.210 --> 00:03:42.950 align:middle line:84%
We'll look at the
errors in HTML.

00:03:42.950 --> 00:03:45.938 align:middle line:90%


00:03:45.938 --> 00:03:46.840 align:middle line:90%
All right.

00:03:46.840 --> 00:03:51.480 align:middle line:84%
So we see this score, 46.37%,
and for compliance, it

00:03:51.480 --> 00:03:53.770 align:middle line:90%
gives a status of red.

00:03:53.770 --> 00:03:55.440 align:middle line:84%
And you can see here
why it doesn't meet

00:03:55.440 --> 00:03:58.920 align:middle line:90%
the 80% threshold for yellow.

00:03:58.920 --> 00:03:59.890 align:middle line:90%
But what's in here?

00:03:59.890 --> 00:04:02.250 align:middle line:84%
Let's scroll down and
we can see the results.

00:04:02.250 --> 00:04:03.750 align:middle line:84%
There's a lot of
things in here that

00:04:03.750 --> 00:04:08.430 align:middle line:84%
failed, including Windows Server
2019 PowerShell script block

00:04:08.430 --> 00:04:12.292 align:middle line:90%
logging must be enabled.

00:04:12.292 --> 00:04:13.500 align:middle line:90%
Well, let's look at that one.

00:04:13.500 --> 00:04:15.690 align:middle line:90%
Where does that come from?

00:04:15.690 --> 00:04:18.450 align:middle line:84%
You can see the fix
for why it's here.

00:04:18.450 --> 00:04:23.460 align:middle line:84%
But right up here, it
talks about missed 853

00:04:23.460 --> 00:04:29.490 align:middle line:84%
and it gives references
to why it is what it is.

00:04:29.490 --> 00:04:34.260 align:middle line:84%
And you could even follow
more of these links

00:04:34.260 --> 00:04:38.280 align:middle line:90%
to gather more information.

00:04:38.280 --> 00:04:41.100 align:middle line:84%
But we'll close that
and close the results.

00:04:41.100 --> 00:04:43.200 align:middle line:90%
43% is not great.

00:04:43.200 --> 00:04:45.190 align:middle line:84%
Is there another
way we can view it?

00:04:45.190 --> 00:04:46.740 align:middle line:90%
Let's look at the STIG viewer.

00:04:46.740 --> 00:05:11.600 align:middle line:90%


00:05:11.600 --> 00:05:17.870 align:middle line:84%
And we can just open a checklist
that we've already created.

00:05:17.870 --> 00:05:20.870 align:middle line:90%


00:05:20.870 --> 00:05:26.090 align:middle line:84%
This checklist is based off
those STIGs, the Microsoft

00:05:26.090 --> 00:05:31.100 align:middle line:90%
Windows Server 2019 STIG.

00:05:31.100 --> 00:05:33.520 align:middle line:84%
Then we see there's
204 items in here.

00:05:33.520 --> 00:05:36.040 align:middle line:84%
It's broken up into
three categories.

00:05:36.040 --> 00:05:47.930 align:middle line:84%
Category one talks about
how failure to comply

00:05:47.930 --> 00:05:51.050 align:middle line:84%
can lead to
exploitation of which

00:05:51.050 --> 00:05:55.820 align:middle line:84%
will directly and immediately
result in loss of CIA.

00:05:55.820 --> 00:06:00.320 align:middle line:84%
Category two talks
about a potential

00:06:00.320 --> 00:06:01.880 align:middle line:90%
to result in loss of CIA.

00:06:01.880 --> 00:06:05.930 align:middle line:84%
And category three
degrades measures

00:06:05.930 --> 00:06:08.690 align:middle line:90%
to protect against loss of CIA.

00:06:08.690 --> 00:06:11.480 align:middle line:84%
And if we look at
what's included in here,

00:06:11.480 --> 00:06:16.460 align:middle line:84%
configuring the system to
disable IPv6 source routing

00:06:16.460 --> 00:06:19.517 align:middle line:90%
protects against spoofing.

00:06:19.517 --> 00:06:20.600 align:middle line:90%
Is that something we want?

00:06:20.600 --> 00:06:27.008 align:middle line:84%
[INAUDIBLE] It is not
going to end the world.

00:06:27.008 --> 00:06:32.960 align:middle line:84%
Cat two items, this first
one, Windows Server 2019

00:06:32.960 --> 00:06:36.200 align:middle line:84%
must be configured to audit
account management, security

00:06:36.200 --> 00:06:38.150 align:middle line:90%
group management successes.

00:06:38.150 --> 00:06:43.640 align:middle line:84%
And in here, it gives
references for what leads to it.

00:06:43.640 --> 00:06:44.895 align:middle line:90%
And there's fix items.

00:06:44.895 --> 00:06:46.520 align:middle line:84%
So you can just follow
the instructions

00:06:46.520 --> 00:06:49.340 align:middle line:90%
and fix all of them.

00:06:49.340 --> 00:07:01.930 align:middle line:84%
Well, let's import the results
of our scan on the desktop.

00:07:01.930 --> 00:07:07.030 align:middle line:84%
SCAP Scan Results, Sessions--
you should just have one.

00:07:07.030 --> 00:07:16.380 align:middle line:84%
Results, SCAP, XML, and
then the final data,

00:07:16.380 --> 00:07:17.700 align:middle line:90%
extraneous results found.

00:07:17.700 --> 00:07:18.540 align:middle line:90%
That's fine.

00:07:18.540 --> 00:07:21.810 align:middle line:90%


00:07:21.810 --> 00:07:25.440 align:middle line:84%
And in here we see
that looks like 43%.

00:07:25.440 --> 00:07:28.100 align:middle line:90%


00:07:28.100 --> 00:07:33.920 align:middle line:84%
These are not a finding, meaning
that they were not a problem.

00:07:33.920 --> 00:07:43.720 align:middle line:90%


00:07:43.720 --> 00:07:46.840 align:middle line:90%
There we go.

00:07:46.840 --> 00:07:51.790 align:middle line:84%
Fixed it, went to Overall Tools,
Imported-- or Overall Totals.

00:07:51.790 --> 00:07:54.440 align:middle line:90%
Now we can check [INAUDIBLE].

00:07:54.440 --> 00:07:57.820 align:middle line:90%
So what was still open?

00:07:57.820 --> 00:08:02.290 align:middle line:84%
I see that Windows Remote
Management client must not

00:08:02.290 --> 00:08:04.205 align:middle line:90%
use basic authentication.

00:08:04.205 --> 00:08:05.830 align:middle line:84%
Needs that "Allow
Basic Authentication"

00:08:05.830 --> 00:08:09.400 align:middle line:90%
to disable in that menu.

00:08:09.400 --> 00:08:13.870 align:middle line:84%
And that's how you
would fix these items.

00:08:13.870 --> 00:08:16.720 align:middle line:84%
Or we're going to
do something else.

00:08:16.720 --> 00:08:22.080 align:middle line:90%


00:08:22.080 --> 00:08:23.955 align:middle line:84%
Open a command line
as administrator.

00:08:23.955 --> 00:08:27.460 align:middle line:90%
See the Administrator command?

00:08:27.460 --> 00:08:34.199 align:middle line:84%
And we have this Group Policy,
here, with the LGPO tool.

00:08:34.199 --> 00:08:39.000 align:middle line:84%
I'm going to copy
the path, change

00:08:39.000 --> 00:08:42.370 align:middle line:90%
directories to that path.

00:08:42.370 --> 00:08:44.800 align:middle line:84%
Now we look there,
and we have our tool,

00:08:44.800 --> 00:08:47.760 align:middle line:84%
which is not installed,
which is why we need

00:08:47.760 --> 00:08:52.150 align:middle line:90%
to be in the same directory.

00:08:52.150 --> 00:08:53.640 align:middle line:90%
And we'll run LGPO.exe/g.

00:08:53.640 --> 00:08:57.030 align:middle line:90%


00:08:57.030 --> 00:09:00.700 align:middle line:84%
And then we have
these two policies.

00:09:00.700 --> 00:09:03.142 align:middle line:90%
So we'll go with that--

00:09:03.142 --> 00:09:06.446 align:middle line:90%


00:09:06.446 --> 00:09:07.760 align:middle line:90%
this one first.

00:09:07.760 --> 00:09:16.080 align:middle line:90%


00:09:16.080 --> 00:09:21.900 align:middle line:84%
And then LGPO.exe/g
and second one.

00:09:21.900 --> 00:09:25.930 align:middle line:90%


00:09:25.930 --> 00:09:29.710 align:middle line:84%
And you can see it did
all that work, changed

00:09:29.710 --> 00:09:34.090 align:middle line:84%
some registry items, and
you can go in and see

00:09:34.090 --> 00:09:36.760 align:middle line:90%
what all the changes were.

00:09:36.760 --> 00:09:39.535 align:middle line:90%
Or let's just open--

00:09:39.535 --> 00:09:45.250 align:middle line:90%


00:09:45.250 --> 00:09:47.215 align:middle line:84%
this guy again and
start a new scan.

00:09:47.215 --> 00:11:47.170 align:middle line:90%


00:11:47.170 --> 00:11:50.350 align:middle line:90%
And our results are back.

00:11:50.350 --> 00:11:52.750 align:middle line:90%
We can view these results.

00:11:52.750 --> 00:11:58.510 align:middle line:84%
And you can see it went
from a 46.37 to a 91.62.

00:11:58.510 --> 00:12:01.525 align:middle line:84%
You could view these
in the browser or--

00:12:01.525 --> 00:12:04.060 align:middle line:90%


00:12:04.060 --> 00:12:07.870 align:middle line:90%
we'll do this a simpler way.

00:12:07.870 --> 00:12:10.285 align:middle line:90%
Let's import the new results.

00:12:10.285 --> 00:12:13.264 align:middle line:90%


00:12:13.264 --> 00:12:15.920 align:middle line:84%
And then we'll go
back to Session

00:12:15.920 --> 00:12:21.570 align:middle line:84%
and pick the later
session, keep driving in

00:12:21.570 --> 00:12:23.850 align:middle line:90%
until we get to the results.

00:12:23.850 --> 00:12:31.625 align:middle line:84%
And, wow, that solved all
the cat ones except for one.

00:12:31.625 --> 00:12:34.350 align:middle line:90%


00:12:34.350 --> 00:12:38.750 align:middle line:84%
We can look at what this one is,
permissions on Active Directory

00:12:38.750 --> 00:12:43.220 align:middle line:84%
data files must only allow
system administrators access.

00:12:43.220 --> 00:12:45.980 align:middle line:84%
And the fix, mainly,
maintain the permissions

00:12:45.980 --> 00:12:51.350 align:middle line:84%
on NTDS database and
log files as follows.

00:12:51.350 --> 00:12:52.195 align:middle line:90%
All right.

00:12:52.195 --> 00:12:53.570 align:middle line:84%
So we can go in
and change those.

00:12:53.570 --> 00:12:58.780 align:middle line:90%


00:12:58.780 --> 00:13:00.580 align:middle line:84%
It also says that's
not applicable,

00:13:00.580 --> 00:13:03.750 align:middle line:90%
so we don't have that database.

00:13:03.750 --> 00:13:08.310 align:middle line:90%


00:13:08.310 --> 00:13:12.330 align:middle line:84%
A few things that were included
in cat two are certificates.

00:13:12.330 --> 00:13:15.150 align:middle line:90%


00:13:15.150 --> 00:13:19.220 align:middle line:84%
Those could go-- be
downloaded and installed.

00:13:19.220 --> 00:13:21.880 align:middle line:84%
If we were a part
of the DOD system,

00:13:21.880 --> 00:13:23.010 align:middle line:90%
we would want to do that.

00:13:23.010 --> 00:13:27.220 align:middle line:90%
Everyone else doesn't need to.

00:13:27.220 --> 00:13:29.340 align:middle line:84%
And one of the things
about this, this

00:13:29.340 --> 00:13:31.510 align:middle line:90%
is built for the DOD.

00:13:31.510 --> 00:13:34.440 align:middle line:90%


00:13:34.440 --> 00:13:37.860 align:middle line:84%
And you could implement in this
all yourself if you wanted.

00:13:37.860 --> 00:13:40.638 align:middle line:90%
But really it's just a--

00:13:40.638 --> 00:13:42.400 align:middle line:90%
it's an example.

00:13:42.400 --> 00:13:45.240 align:middle line:84%
It's an example of
how auditing works.

00:13:45.240 --> 00:13:47.520 align:middle line:90%
There are benchmarks.

00:13:47.520 --> 00:13:48.270 align:middle line:90%
There's standards.

00:13:48.270 --> 00:13:49.740 align:middle line:90%
There are best practices.

00:13:49.740 --> 00:13:53.490 align:middle line:84%
And they've made a
tool so that it can be

00:13:53.490 --> 00:13:55.080 align:middle line:90%
standardized across the board.

00:13:55.080 --> 00:13:58.320 align:middle line:84%
Everyone has these settings
and configurations.

00:13:58.320 --> 00:14:01.520 align:middle line:84%
And so every system
is in compliance.

00:14:01.520 --> 00:14:04.350 align:middle line:90%


00:14:04.350 --> 00:14:06.330 align:middle line:84%
But it all depends on
what the business needs,

00:14:06.330 --> 00:14:07.650 align:middle line:90%
what the organization requires.

00:14:07.650 --> 00:14:11.760 align:middle line:84%
A smaller organization will come
up with their own requirements.

00:14:11.760 --> 00:14:15.810 align:middle line:84%
They might have to follow
certain regulations.

00:14:15.810 --> 00:14:17.640 align:middle line:84%
And depending on
their cyber maturity,

00:14:17.640 --> 00:14:22.050 align:middle line:84%
they'll make choices based on
their risk-management appetite

00:14:22.050 --> 00:14:24.930 align:middle line:84%
and what works best
for the organization.

00:14:24.930 --> 00:14:28.737 align:middle line:84%
Going back to this
penetration tester student,

00:14:28.737 --> 00:14:30.570 align:middle line:84%
if you are going to be
a penetration tester,

00:14:30.570 --> 00:14:34.870 align:middle line:84%
you need to understand where
your customer is coming from,

00:14:34.870 --> 00:14:36.780 align:middle line:90%
where the organization is going.

00:14:36.780 --> 00:14:38.640 align:middle line:90%
What maturity level are they at?

00:14:38.640 --> 00:14:40.950 align:middle line:84%
What do they already
know about their system

00:14:40.950 --> 00:14:46.090 align:middle line:84%
through proper vulnerability
management, risk management?

00:14:46.090 --> 00:14:49.470 align:middle line:84%
And then what are you
actually adding value to?

00:14:49.470 --> 00:14:53.520 align:middle line:84%
You can utilize some
of the same tools

00:14:53.520 --> 00:14:55.890 align:middle line:84%
in penetration
testing that are used

00:14:55.890 --> 00:14:59.370 align:middle line:90%
in vulnerability management.

00:14:59.370 --> 00:15:02.940 align:middle line:84%
A lot of it all comes down
to the report and the scope.

00:15:02.940 --> 00:15:04.200 align:middle line:90%
What are you allowed to do?

00:15:04.200 --> 00:15:08.770 align:middle line:84%
What is most effective in
adding value to your customer?

00:15:08.770 --> 00:15:11.580 align:middle line:84%
And what would you put in
your report that actually

00:15:11.580 --> 00:15:17.615 align:middle line:84%
allows them to be more secure
and meet business requirements?

00:15:17.615 --> 00:15:20.030 align:middle line:90%
I'll leave you with that.

00:15:20.030 --> 00:15:21.000 align:middle line:90%