WEBVTT

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


00:00:03.700 --> 00:00:07.040 align:middle line:84%
In this exercise, we're going
to look at Zenmap on a Windows

00:00:07.040 --> 00:00:07.540 align:middle line:90%
machine.

00:00:07.540 --> 00:00:12.680 align:middle line:90%


00:00:12.680 --> 00:00:21.830 align:middle line:84%
So we have our vm, and
it has a maps Zenmap GUI.

00:00:21.830 --> 00:00:31.490 align:middle line:84%
While that loads, let's
see what our IP address is.

00:00:31.490 --> 00:00:37.150 align:middle line:90%


00:00:37.150 --> 00:00:43.520 align:middle line:90%
We are on a 10.4.25--

00:00:43.520 --> 00:00:47.945 align:middle line:90%
no, not 25-- this is cider 20.

00:00:47.945 --> 00:00:55.430 align:middle line:90%


00:00:55.430 --> 00:00:59.250 align:middle line:90%
So 10.4.16.0.

00:00:59.250 --> 00:01:01.070 align:middle line:84%
An easy way, look
at the gateway.

00:01:01.070 --> 00:01:14.800 align:middle line:90%


00:01:14.800 --> 00:01:15.970 align:middle line:90%
Here is Zenmap.

00:01:15.970 --> 00:01:19.090 align:middle line:90%


00:01:19.090 --> 00:01:29.410 align:middle line:84%
We'll put it in our IP
range 10.4.16.0 cider 20.

00:01:29.410 --> 00:01:32.710 align:middle line:84%
And you can pick
your scan profile.

00:01:32.710 --> 00:01:34.760 align:middle line:90%
Let's just do a ping scan.

00:01:34.760 --> 00:01:40.510 align:middle line:84%
And we see it's nmap -sn,
and our IP range, our subnet

00:01:40.510 --> 00:01:42.027 align:middle line:90%
that we gave it.

00:01:42.027 --> 00:01:42.985 align:middle line:90%
So we can run the scan.

00:01:42.985 --> 00:01:45.550 align:middle line:90%


00:01:45.550 --> 00:01:47.710 align:middle line:84%
And we got our results
as if the command line

00:01:47.710 --> 00:01:49.060 align:middle line:90%
was in verbose mode.

00:01:49.060 --> 00:01:54.230 align:middle line:90%


00:01:54.230 --> 00:02:01.657 align:middle line:84%
You can add verbosity
to the output

00:02:01.657 --> 00:02:05.650 align:middle line:84%
because this line right
here can be edited.

00:02:05.650 --> 00:02:08.152 align:middle line:90%
And we get a host [INAUDIBLE].

00:02:08.152 --> 00:02:13.650 align:middle line:90%


00:02:13.650 --> 00:02:22.530 align:middle line:84%
And what we could do is we could
pick out of these new targets,

00:02:22.530 --> 00:02:25.770 align:middle line:84%
or we could try a
more intense scan.

00:02:25.770 --> 00:02:27.770 align:middle line:84%
Let's just go with the
normal intense scan.

00:02:27.770 --> 00:02:33.210 align:middle line:84%
It's a tack T4 and
aggressive and a -v. So it'll

00:02:33.210 --> 00:02:36.450 align:middle line:84%
run operating
system enumeration,

00:02:36.450 --> 00:02:40.852 align:middle line:84%
service enumeration, default
scripts, and a traceroute.

00:02:40.852 --> 00:02:44.160 align:middle line:90%


00:02:44.160 --> 00:02:45.670 align:middle line:90%
I'll let that run.

00:02:45.670 --> 00:02:48.100 align:middle line:84%
Let's look at what
happens over here.

00:02:48.100 --> 00:02:49.440 align:middle line:90%
So we have these hosts.

00:02:49.440 --> 00:02:51.285 align:middle line:84%
We've got a nice
little list of hosts.

00:02:51.285 --> 00:02:54.150 align:middle line:90%


00:02:54.150 --> 00:02:57.750 align:middle line:84%
And we have this
topology that we've

00:02:57.750 --> 00:03:00.090 align:middle line:90%
looked at before in the lesson.

00:03:00.090 --> 00:03:03.470 align:middle line:90%


00:03:03.470 --> 00:03:06.720 align:middle line:84%
These are all the different
IP addresses and how they're

00:03:06.720 --> 00:03:08.160 align:middle line:90%
connected to us by one hop.

00:03:08.160 --> 00:03:10.830 align:middle line:90%


00:03:10.830 --> 00:03:13.590 align:middle line:84%
You could look at
host information

00:03:13.590 --> 00:03:17.790 align:middle line:84%
once we have operating system
and services enumerated.

00:03:17.790 --> 00:03:22.910 align:middle line:84%
Not there yet, but
it's getting there.

00:03:22.910 --> 00:03:26.249 align:middle line:90%


00:03:26.249 --> 00:03:27.560 align:middle line:90%
Or we can look at the history.

00:03:27.560 --> 00:03:34.121 align:middle line:90%


00:03:34.121 --> 00:03:34.930 align:middle line:90%
All right.

00:03:34.930 --> 00:03:36.430 align:middle line:84%
Now it's starting
the service again.

00:03:36.430 --> 00:03:41.370 align:middle line:90%


00:03:41.370 --> 00:03:46.830 align:middle line:84%
Operating system scan,
and then an -sc, which

00:03:46.830 --> 00:03:48.240 align:middle line:90%
is the Nmap scripting engine.

00:03:48.240 --> 00:03:56.080 align:middle line:90%


00:03:56.080 --> 00:03:57.430 align:middle line:90%
All right.

00:03:57.430 --> 00:04:00.410 align:middle line:90%
Scan is complete.

00:04:00.410 --> 00:04:03.450 align:middle line:84%
Now, we can look at
some of our machines.

00:04:03.450 --> 00:04:05.320 align:middle line:90%
Let's look at topology.

00:04:05.320 --> 00:04:09.068 align:middle line:84%
We have a little
bit more breakdown.

00:04:09.068 --> 00:04:14.030 align:middle line:84%
We can always move this around
and pick out different hosts

00:04:14.030 --> 00:04:14.610 align:middle line:90%
to look at.

00:04:14.610 --> 00:04:18.160 align:middle line:90%


00:04:18.160 --> 00:04:27.530 align:middle line:84%
I'm more interested
in these host details

00:04:27.530 --> 00:04:28.970 align:middle line:90%
because we can really dive in.

00:04:28.970 --> 00:04:31.680 align:middle line:90%
Some, we have nothing.

00:04:31.680 --> 00:04:33.140 align:middle line:90%
It doesn't really tell us much.

00:04:33.140 --> 00:04:39.770 align:middle line:84%
We could look at ports,
but they don't have much.

00:04:39.770 --> 00:04:45.710 align:middle line:84%
These two, on the other hand,
a whole bunch of Windows

00:04:45.710 --> 00:04:46.610 align:middle line:90%
ports on them.

00:04:46.610 --> 00:04:51.470 align:middle line:84%
And the host operating
system information

00:04:51.470 --> 00:04:53.210 align:middle line:84%
says they're Windows.
[? That one ?] is

00:04:53.210 --> 00:04:58.430 align:middle line:90%
server 2012 and 89% accuracy.

00:04:58.430 --> 00:05:03.980 align:middle line:84%
And it does that based off of
the ports and operating system

00:05:03.980 --> 00:05:04.530 align:middle line:90%
class.

00:05:04.530 --> 00:05:05.420 align:middle line:90%
OK, useful.

00:05:05.420 --> 00:05:10.250 align:middle line:90%


00:05:10.250 --> 00:05:14.000 align:middle line:84%
And then this one is just
showing a Windows 10 vm,

00:05:14.000 --> 00:05:16.045 align:middle line:90%
Windows 10 machine.

00:05:16.045 --> 00:05:17.795 align:middle line:84%
And that's based off
the signature itself.

00:05:17.795 --> 00:05:22.090 align:middle line:90%


00:05:22.090 --> 00:05:25.380 align:middle line:84%
And that's what you
get out of the Zenmap.

00:05:25.380 --> 00:05:28.240 align:middle line:90%
You get a nice little GUI.

00:05:28.240 --> 00:05:30.560 align:middle line:90%
It can be useful.

00:05:30.560 --> 00:05:34.000 align:middle line:90%