WEBVTT

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


00:00:04.940 --> 00:00:07.410 align:middle line:90%
[MUSICAL INTRO]

00:00:07.410 --> 00:00:10.282 align:middle line:90%


00:00:10.282 --> 00:00:12.240 align:middle line:84%
In this lab, we're going
to cover some auditing

00:00:12.240 --> 00:00:15.810 align:middle line:90%
fundamentals utilizing Nmap.

00:00:15.810 --> 00:00:18.600 align:middle line:84%
We spoke before
about the CMMC model.

00:00:18.600 --> 00:00:20.910 align:middle line:90%
And there's many.

00:00:20.910 --> 00:00:24.390 align:middle line:84%
But I pull this one up
because asset management

00:00:24.390 --> 00:00:28.920 align:middle line:84%
is one of the 17 capabilities
of CMMC version 1.

00:00:28.920 --> 00:00:33.240 align:middle line:84%
Now, there's a lot that we
could do with asset management.

00:00:33.240 --> 00:00:37.930 align:middle line:84%
And I'm going to take you
over to our environment.

00:00:37.930 --> 00:00:42.330 align:middle line:84%
And we're going to utilize
Nmap for asset management.

00:00:42.330 --> 00:00:44.970 align:middle line:84%
Usually, you're going
to have a network

00:00:44.970 --> 00:00:52.290 align:middle line:84%
map in the organization, maybe
an Excel file or a database,

00:00:52.290 --> 00:00:57.370 align:middle line:84%
with all of the machines,
endpoints, routers, switches,

00:00:57.370 --> 00:01:00.900 align:middle line:84%
firewalls that are
connected to the network.

00:01:00.900 --> 00:01:03.360 align:middle line:84%
And that's a starting
point for the company

00:01:03.360 --> 00:01:06.390 align:middle line:84%
itself, the organization
itself, to understand

00:01:06.390 --> 00:01:09.510 align:middle line:90%
where all its devices are.

00:01:09.510 --> 00:01:12.630 align:middle line:84%
And then, it can look at what
services are hosted or present

00:01:12.630 --> 00:01:14.370 align:middle line:90%
on each of those devices.

00:01:14.370 --> 00:01:17.790 align:middle line:84%
It's the same thing that
you do during a pen test,

00:01:17.790 --> 00:01:20.940 align:middle line:84%
except you do it from a
black box point of view.

00:01:20.940 --> 00:01:24.420 align:middle line:84%
An audit or an
internal scan, they

00:01:24.420 --> 00:01:26.430 align:middle line:84%
should know what's
already out there.

00:01:26.430 --> 00:01:28.560 align:middle line:84%
They might be looking
for some shadow IT.

00:01:28.560 --> 00:01:31.620 align:middle line:84%
Maybe someone plugged
in their own device

00:01:31.620 --> 00:01:34.980 align:middle line:84%
in order to get work
done and work around

00:01:34.980 --> 00:01:39.315 align:middle line:84%
what was established by
the organization itself.

00:01:39.315 --> 00:01:43.210 align:middle line:90%


00:01:43.210 --> 00:01:45.375 align:middle line:90%
So let's look at our IP address.

00:01:45.375 --> 00:01:47.890 align:middle line:90%


00:01:47.890 --> 00:01:49.360 align:middle line:90%
And this is the network.

00:01:49.360 --> 00:01:51.790 align:middle line:90%
192.253.100.

00:01:51.790 --> 00:01:55.930 align:middle line:84%
And then, it's CIDR 24,
so the network is .0.

00:01:55.930 --> 00:01:59.330 align:middle line:90%
So let's run an Nmap scan.

00:01:59.330 --> 00:02:05.410 align:middle line:90%
And we'll place that with 0.24.

00:02:05.410 --> 00:02:14.860 align:middle line:84%
And it came back pretty
quickly, which is nice.

00:02:14.860 --> 00:02:15.820 align:middle line:90%
I didn't put any flags.

00:02:15.820 --> 00:02:24.106 align:middle line:90%
So .1 has 22, 80, and 443.3.

00:02:24.106 --> 00:02:27.830 align:middle line:90%
80, 443, and MySQL.

00:02:27.830 --> 00:02:31.120 align:middle line:84%
.4 doesn't seem to
have any endpoint,

00:02:31.120 --> 00:02:33.100 align:middle line:84%
or it doesn't seem to
have any ports open.

00:02:33.100 --> 00:02:35.170 align:middle line:90%
Same with .5.

00:02:35.170 --> 00:02:38.410 align:middle line:90%
And .6 has port 21 open.

00:02:38.410 --> 00:02:41.630 align:middle line:84%
So I would assume that we've got
some server in the FTP server,

00:02:41.630 --> 00:02:46.480 align:middle line:84%
a web server, and a SQL
database server that

00:02:46.480 --> 00:02:49.960 align:middle line:90%
might be attached to a website.

00:02:49.960 --> 00:02:51.460 align:middle line:90%
And then, we're on .2.

00:02:51.460 --> 00:03:00.580 align:middle line:84%
So we could dig in a little
more and Nmap all those,

00:03:00.580 --> 00:03:04.090 align:middle line:90%
the ones of note.

00:03:04.090 --> 00:03:11.520 align:middle line:90%
1, 3, and 6.

00:03:11.520 --> 00:03:13.390 align:middle line:84%
And we can run an
aggressive scan.

00:03:13.390 --> 00:03:14.790 align:middle line:90%
It's our network.

00:03:14.790 --> 00:03:16.920 align:middle line:84%
And the aggressive
scan is not going

00:03:16.920 --> 00:03:18.450 align:middle line:84%
to do anything that
should break it.

00:03:18.450 --> 00:03:22.140 align:middle line:84%
It's just going to show
up on all the scans.

00:03:22.140 --> 00:03:23.970 align:middle line:84%
Then again, the
Nmap scan's probably

00:03:23.970 --> 00:03:27.882 align:middle line:84%
going to show up in the
IDS and IPS anyways.

00:03:27.882 --> 00:03:29.590 align:middle line:84%
This scan might take
a little bit longer.

00:03:29.590 --> 00:03:39.840 align:middle line:90%


00:03:39.840 --> 00:03:41.670 align:middle line:90%
And we're back.

00:03:41.670 --> 00:03:43.200 align:middle line:90%
That wasn't too horrible.

00:03:43.200 --> 00:03:50.130 align:middle line:84%
The aggressive scan runs a
send scan, a service scan,

00:03:50.130 --> 00:03:58.320 align:middle line:84%
an operating system
identifier, and a traceroute.

00:03:58.320 --> 00:04:02.760 align:middle line:84%
And also, some of the default
scripts tack as C, if you will.

00:04:02.760 --> 00:04:07.290 align:middle line:90%


00:04:07.290 --> 00:04:10.010 align:middle line:90%
So-- OK, up here.

00:04:10.010 --> 00:04:10.940 align:middle line:90%
There we go.

00:04:10.940 --> 00:04:11.720 align:middle line:90%
Port 22.

00:04:11.720 --> 00:04:14.180 align:middle line:90%
We can see, it's got a open SSH.

00:04:14.180 --> 00:04:17.630 align:middle line:90%
We see that it's the Linux box.

00:04:17.630 --> 00:04:22.580 align:middle line:84%
And traceroute puts it one
hop away from us via .1.

00:04:22.580 --> 00:04:28.820 align:middle line:84%
That one's probably our router
or our switch in this case.

00:04:28.820 --> 00:04:32.100 align:middle line:90%


00:04:32.100 --> 00:04:34.190 align:middle line:84%
Can't come up with
anything too crazy.

00:04:34.190 --> 00:04:38.540 align:middle line:90%


00:04:38.540 --> 00:04:42.400 align:middle line:84%
Our .3, there's
another Ubuntu machine.

00:04:42.400 --> 00:04:46.960 align:middle line:84%
And we got some more
information out of this.

00:04:46.960 --> 00:04:50.140 align:middle line:84%
Looks like there's a gate
repository from the scans.

00:04:50.140 --> 00:04:55.760 align:middle line:90%


00:04:55.760 --> 00:04:59.540 align:middle line:84%
And then .6, We've
got this FTP server.

00:04:59.540 --> 00:05:03.300 align:middle line:84%
And those should be
pretty straightforward.

00:05:03.300 --> 00:05:05.630 align:middle line:84%
Those should be
exactly what we expect.

00:05:05.630 --> 00:05:10.700 align:middle line:84%
Now, after looking
at these findings,

00:05:10.700 --> 00:05:12.440 align:middle line:84%
looking at the network
map, an auditor

00:05:12.440 --> 00:05:14.700 align:middle line:90%
would say, OK, these all match.

00:05:14.700 --> 00:05:18.920 align:middle line:84%
Quality Assurance would say that
we have an accurate inventory.

00:05:18.920 --> 00:05:21.770 align:middle line:84%
If they don't, then it should
either be updated or mitigated

00:05:21.770 --> 00:05:23.640 align:middle line:90%
or looked at and worked with.

00:05:23.640 --> 00:05:27.260 align:middle line:84%
But that's fairly
straightforward,

00:05:27.260 --> 00:05:30.290 align:middle line:90%
simple look at asset management.

00:05:30.290 --> 00:05:31.940 align:middle line:90%
There are more tools.

00:05:31.940 --> 00:05:38.150 align:middle line:84%
There's many more ways of
managing a greater enterprise

00:05:38.150 --> 00:05:39.290 align:middle line:90%
system.

00:05:39.290 --> 00:05:47.330 align:middle line:84%
But the generic, the general
way of going about this

00:05:47.330 --> 00:05:50.510 align:middle line:84%
is kind of the same for auditing
that it is for pen testing.

00:05:50.510 --> 00:05:53.810 align:middle line:84%
And it's going to be the same
for a lot of your blue-teamers,

00:05:53.810 --> 00:05:57.980 align:middle line:84%
who also need to double check
and do, maybe, some asset

00:05:57.980 --> 00:06:01.030 align:middle line:90%
management on the fly.

00:06:01.030 --> 00:06:03.030 align:middle line:84%
A lot of cybersecurity
is the same for everyone.

00:06:03.030 --> 00:06:06.740 align:middle line:84%
It's just how you're looking
at the ball determines what

00:06:06.740 --> 00:06:08.830 align:middle line:90%
you're going to do with it.

00:06:08.830 --> 00:06:09.407 align:middle line:90%