WEBVTT

00:01.010 --> 00:02.119
Hey, everyone, welcome back to the

00:02.120 --> 00:03.469
course. So in the last video, we

00:03.470 --> 00:04.819
just went ahead and ran our second

00:04.820 --> 00:06.259
and met command, so we combined

00:06.260 --> 00:08.024
three different IP addresses, one of

00:08.029 --> 00:09.920
the two one six eight zero

00:10.310 --> 00:11.780
one than we did 10, as well as

00:12.170 --> 00:13.170
that one hundred.

00:13.640 --> 00:15.180
So that was step 16 of our lab.

00:15.350 --> 00:17.020
So now the results are complete.

00:17.300 --> 00:18.799
So question number two here, are

00:18.800 --> 00:20.270
there any ports displaying for

00:20.750 --> 00:22.429
the particular IP addresses that we

00:22.430 --> 00:23.930
ran the scan on?

00:24.650 --> 00:25.819
So you can easily see in the

00:25.820 --> 00:27.349
background there for me at least,

00:27.350 --> 00:29.449
that, yes, I see all sorts of ports

00:29.450 --> 00:31.489
open, so I see them open

00:31.490 --> 00:32.779
on the dot.

00:32.780 --> 00:34.219
One address for us.

00:35.710 --> 00:37.509
All right, so the last step of our

00:37.510 --> 00:38.589
lab here, we're going to actually

00:38.590 --> 00:40.570
just run the ping three command,

00:40.580 --> 00:42.246
so I'm going to go ahead and clear

00:42.370 --> 00:43.899
my terminal window here to make it a

00:43.900 --> 00:44.960
little easier to read.

00:45.130 --> 00:46.419
You're welcome to do so as well.

00:46.420 --> 00:48.069
Or you can just levers as is.

00:48.550 --> 00:49.719
It doesn't actually affect the

00:49.720 --> 00:51.219
output of the command we're running.

00:51.670 --> 00:53.189
So to clear my screen, I'm just

00:53.350 --> 00:54.639
going to type in the word clear and

00:54.640 --> 00:56.259
then just press enter and you'll see

00:56.260 --> 00:57.849
all the commands I previously typed

00:57.850 --> 00:58.870
disappear for us.

01:00.090 --> 01:01.229
All right, so the command we're

01:01.230 --> 01:03.179
going to run here is going to be HPN

01:03.180 --> 01:05.219
three, Dash eight,

01:05.220 --> 01:06.419
which is basically just enabling the

01:06.420 --> 01:07.769
scan mode that we're going to give

01:07.770 --> 01:09.239
it a range of ports to scan.

01:09.840 --> 01:10.859
We're going to scan it with a

01:10.860 --> 01:13.079
CINCPAC sort of sending the sin flag

01:13.110 --> 01:14.629
or we're setting the same flag,

01:14.700 --> 01:16.049
excuse me, and then we're just going

01:16.050 --> 01:17.879
to do going to do it against just

01:17.880 --> 01:18.659
one IP address.

01:18.660 --> 01:19.920
So that main IP address that we've

01:19.950 --> 01:21.419
been using throughout this entire

01:21.420 --> 01:23.249
lab, our Cisco

01:23.250 --> 01:24.539
and type, that is we'll go step by

01:24.540 --> 01:25.540
step here.

01:25.590 --> 01:26.730
So HPN three,

01:28.110 --> 01:29.678
we'll put a space and then we're

01:29.970 --> 01:31.680
going to type in the Dash eight,

01:32.040 --> 01:33.359
and then we're going to put a space

01:33.360 --> 01:34.928
and then type in zero, dash five

01:35.460 --> 01:36.770
thousand. So let's go and do that.

01:36.780 --> 01:38.054
Now we're going to type in

01:38.610 --> 01:40.739
dash eight, space

01:40.740 --> 01:42.040
zero, dash five thousand.

01:42.060 --> 01:43.469
Again, we're specifying the range of

01:43.470 --> 01:44.700
ports that we want to scan.

01:45.390 --> 01:46.829
We're going to put another space

01:47.520 --> 01:48.719
and then we're just going to type in

01:48.750 --> 01:50.090
a dash capital S..

01:50.100 --> 01:51.100
Again, that the tell

01:52.260 --> 01:53.790
it that we want to do is scan

01:54.300 --> 01:55.829
and then our IP address again.

01:55.830 --> 01:56.999
Then we've been using this entire

01:57.000 --> 01:57.929
time.

01:57.930 --> 01:59.819
So Dash Capital s,

02:00.270 --> 02:01.799
we'll put another space and then our

02:01.800 --> 02:03.609
one only two one six eight

02:04.500 --> 02:06.419
zero one and then just press

02:06.420 --> 02:07.420
and turn your keyboard.

02:07.980 --> 02:10.050
Now it might take a moment or so to

02:10.259 --> 02:11.159
pull back the results.

02:11.160 --> 02:12.359
You'll see it gives us some results

02:12.360 --> 02:13.169
right away there.

02:13.170 --> 02:14.429
So we can actually go ahead and

02:14.430 --> 02:16.370
answer our question on our lab as

02:16.380 --> 02:17.400
it's finishing running.

02:18.620 --> 02:19.879
So the question is, are there any

02:19.880 --> 02:20.900
ports not responding?

02:20.930 --> 02:22.149
So let's take a look at our output,

02:22.160 --> 02:23.449
you see just takes a few seconds to

02:23.450 --> 02:24.529
actually run that command.

02:26.040 --> 02:27.439
So we see all these different point

02:27.510 --> 02:28.510
numbers here.

02:28.560 --> 02:30.059
Well, let's scroll back up a little

02:30.060 --> 02:31.775
bit and see what does this actually

02:31.860 --> 02:33.029
mean? What are these poll numbers

02:33.030 --> 02:34.030
right here that we see?

02:34.140 --> 02:35.580
Are these open or closed?

02:36.590 --> 02:37.800
Where are they not responding?

02:37.820 --> 02:38.820
Let's see here.

02:38.930 --> 02:40.429
So my take a moment or so to come

02:40.430 --> 02:41.599
all the way back up and their

02:41.600 --> 02:42.600
results here.

02:43.760 --> 02:45.529
But basically what we're looking for

02:45.530 --> 02:47.509
is it's going to tell us that all

02:47.510 --> 02:48.979
these numbers we're seeing down here

02:48.980 --> 02:50.509
near the bottom section of the

02:50.510 --> 02:52.029
output, this is all going to be

02:52.280 --> 02:53.889
ports that are not responding.

02:53.930 --> 02:55.140
So let's go back up here.

02:55.160 --> 02:56.330
We should be almost there.

02:56.780 --> 02:57.769
And you'll see some of them are

02:57.770 --> 02:59.629
labeled like open VPN, et cetera.

03:00.050 --> 03:01.339
Many of them are not labeled.

03:01.340 --> 03:02.449
They're just random ports.

03:04.360 --> 03:05.799
All right, so you'll see here as we

03:05.800 --> 03:07.029
scroll back up, you'll see not

03:07.030 --> 03:07.899
responding.

03:07.900 --> 03:08.900
Right there.

03:09.830 --> 03:10.919
And that's what we're looking for.

03:10.940 --> 03:13.009
So here in question number three,

03:13.010 --> 03:14.349
are there any ports not responding?

03:14.360 --> 03:15.589
The answer, of course, would be yes,

03:15.590 --> 03:17.479
there. And if you wanted to put all

03:17.510 --> 03:18.469
these port numbers down, you

03:18.470 --> 03:19.470
certainly could do so.

03:19.730 --> 03:20.669
It's probably quite a bit.

03:20.670 --> 03:22.238
So it's it'll take you a moment,

03:22.340 --> 03:23.869
certainly. And then if we scroll

03:23.870 --> 03:25.279
back up a little further, we can see

03:25.280 --> 03:26.929
all the ports that are responding to

03:26.930 --> 03:28.639
us and the services running on those

03:28.640 --> 03:29.640
particular ports.

03:30.530 --> 03:31.729
All right. So this lab, again, we

03:31.730 --> 03:33.019
were just looking for some open

03:33.020 --> 03:34.609
ports again, just a little bit of

03:34.610 --> 03:36.259
hands on practice to

03:36.530 --> 03:37.629
take a look at those things.

03:37.640 --> 03:39.229
It's part of the scanning process

03:39.230 --> 03:40.580
that we would normally be doing.

03:40.790 --> 03:42.259
Again, the intent, of course, is to

03:42.260 --> 03:44.089
find vulnerable systems

03:44.330 --> 03:46.009
in a way into the network.

03:46.160 --> 03:47.779
And that way we can compromise and

03:47.780 --> 03:48.949
move forward with whatever our

03:49.100 --> 03:50.559
nefarious goal is from there.

03:51.680 --> 03:52.759
So in the next video, we're just

03:52.760 --> 03:54.080
going to go over some more scanning.

03:54.440 --> 03:55.639
So we'll take a look at that in the

03:55.640 --> 03:56.240
next module.