WEBVTT

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


00:00:03.650 --> 00:00:05.690 align:middle line:90%
Let's talk about port scanning.

00:00:05.690 --> 00:00:09.570 align:middle line:84%
I'm Josh Mason, your
instructor for this lesson.

00:00:09.570 --> 00:00:12.200 align:middle line:84%
We'll go through the purpose,
the process, and the tools

00:00:12.200 --> 00:00:13.280 align:middle line:90%
for some port scanning.

00:00:13.280 --> 00:00:16.590 align:middle line:90%


00:00:16.590 --> 00:00:20.840 align:middle line:84%
Now, we did our host discovery
and found a whole bunch of IP

00:00:20.840 --> 00:00:22.580 align:middle line:90%
addresses and Mac addresses.

00:00:22.580 --> 00:00:26.190 align:middle line:84%
Now we need to turn those into
something a little more useful.

00:00:26.190 --> 00:00:29.060 align:middle line:84%
So we will identify
some operating systems

00:00:29.060 --> 00:00:31.970 align:middle line:84%
and then identify some services
running on those machines.

00:00:31.970 --> 00:00:34.040 align:middle line:84%
This will help us
understand whether we're

00:00:34.040 --> 00:00:37.880 align:middle line:84%
looking at firewalls
or servers or desktops.

00:00:37.880 --> 00:00:43.790 align:middle line:84%
And then we can later enumerate,
find some vulnerabilities

00:00:43.790 --> 00:00:46.760 align:middle line:84%
perhaps, and exploit
these machines

00:00:46.760 --> 00:00:47.960 align:middle line:90%
like an attacker would.

00:00:47.960 --> 00:00:50.990 align:middle line:90%


00:00:50.990 --> 00:00:53.180 align:middle line:84%
We identify the
operating systems

00:00:53.180 --> 00:00:57.170 align:middle line:84%
based on what's revealed
by their signatures

00:00:57.170 --> 00:01:00.930 align:middle line:90%
or by services.

00:01:00.930 --> 00:01:04.920 align:middle line:84%
We will send out
requests to the machines,

00:01:04.920 --> 00:01:09.710 align:middle line:84%
and then they will
send back a response.

00:01:09.710 --> 00:01:12.890 align:middle line:84%
The tools that
we'll use like Nmap

00:01:12.890 --> 00:01:16.460 align:middle line:84%
will examine those responses and
compare them to the signature

00:01:16.460 --> 00:01:21.080 align:middle line:84%
database and give us a best
guess at what that operating

00:01:21.080 --> 00:01:22.700 align:middle line:90%
system is.

00:01:22.700 --> 00:01:24.320 align:middle line:84%
And we can expect
to see something

00:01:24.320 --> 00:01:27.560 align:middle line:90%
like 80% solution, maybe 100%.

00:01:27.560 --> 00:01:29.960 align:middle line:84%
Some operating systems
are very obvious.

00:01:29.960 --> 00:01:31.010 align:middle line:90%
Others are not.

00:01:31.010 --> 00:01:35.450 align:middle line:84%
And we'll take whatever
we can get from the scan.

00:01:35.450 --> 00:01:38.420 align:middle line:84%
Also, sometimes
services or programs

00:01:38.420 --> 00:01:40.430 align:middle line:84%
that are running
on those machines

00:01:40.430 --> 00:01:42.680 align:middle line:84%
will tell us exactly
what the operating system

00:01:42.680 --> 00:01:45.170 align:middle line:84%
is because the version
of the software

00:01:45.170 --> 00:01:47.870 align:middle line:84%
includes the operating
system itself.

00:01:47.870 --> 00:01:51.265 align:middle line:90%


00:01:51.265 --> 00:01:52.140 align:middle line:90%
So how do we do this?

00:01:52.140 --> 00:01:54.020 align:middle line:90%
How do we scan for services?

00:01:54.020 --> 00:01:56.660 align:middle line:84%
Well, we'll try to connect
to the different ports,

00:01:56.660 --> 00:01:58.490 align:middle line:84%
and we'll check
back for responses.

00:01:58.490 --> 00:02:05.720 align:middle line:90%


00:02:05.720 --> 00:02:09.280 align:middle line:84%
So the normal TCP
three-way handshake,

00:02:09.280 --> 00:02:12.130 align:middle line:84%
if we connect we send a
SYN, we get a SYN ACC.

00:02:12.130 --> 00:02:13.720 align:middle line:90%
We send an ACC.

00:02:13.720 --> 00:02:16.450 align:middle line:84%
We know that the port
is open, and then we'll

00:02:16.450 --> 00:02:20.080 align:middle line:84%
send a RST ACC just to
close that connection.

00:02:20.080 --> 00:02:23.830 align:middle line:84%
And that's standard,
three-way handshake.

00:02:23.830 --> 00:02:26.530 align:middle line:84%
If we get that back, then
we know that port is there.

00:02:26.530 --> 00:02:30.300 align:middle line:84%
And then we'll
close the connection

00:02:30.300 --> 00:02:33.550 align:middle line:90%
and move on to the next port.

00:02:33.550 --> 00:02:36.190 align:middle line:84%
If the port is closed,
we'll try to connect to it.

00:02:36.190 --> 00:02:38.410 align:middle line:84%
And the machine will
send back our RST ACC.

00:02:38.410 --> 00:02:44.070 align:middle line:84%
And our scanner will know
that connection is not there.

00:02:44.070 --> 00:02:45.930 align:middle line:90%
It's not possible.

00:02:45.930 --> 00:02:47.910 align:middle line:90%
There's a stealthy scan.

00:02:47.910 --> 00:02:51.360 align:middle line:84%
The creators of
Nmap and some others

00:02:51.360 --> 00:02:54.280 align:middle line:84%
realized that their
scans were being caught.

00:02:54.280 --> 00:02:58.560 align:middle line:84%
Firewalls and IDSs
and IPSs were catching

00:02:58.560 --> 00:03:02.250 align:middle line:84%
on to all of these connections
and dropped connections.

00:03:02.250 --> 00:03:05.700 align:middle line:84%
So the stealthy scan
came about where

00:03:05.700 --> 00:03:08.820 align:middle line:84%
it sends a SYN, gets
a SYN ACC in response,

00:03:08.820 --> 00:03:14.330 align:middle line:84%
and rather than
finishing the connection,

00:03:14.330 --> 00:03:17.250 align:middle line:84%
it sends the RST just
to drop it there.

00:03:17.250 --> 00:03:20.750 align:middle line:84%
So if it gets a SYN ACC
back, it knows it's open,

00:03:20.750 --> 00:03:24.200 align:middle line:84%
and then it will
drop the connection.

00:03:24.200 --> 00:03:26.990 align:middle line:84%
This is also less stealthy
now because they caught on

00:03:26.990 --> 00:03:31.850 align:middle line:84%
very fast because that's
how this business works.

00:03:31.850 --> 00:03:33.930 align:middle line:84%
If you change something
and you tell people,

00:03:33.930 --> 00:03:38.510 align:middle line:84%
hey, it's changed so
that they'll then use it,

00:03:38.510 --> 00:03:41.360 align:middle line:84%
well, the people creating
the IDSs and the firewalls

00:03:41.360 --> 00:03:47.150 align:middle line:84%
and the IPSs will then take
that new signature and apply it.

00:03:47.150 --> 00:03:49.578 align:middle line:84%
Fortunately, sometimes we
can get away with things

00:03:49.578 --> 00:03:51.245 align:middle line:84%
because people haven't
made the updates.

00:03:51.245 --> 00:03:54.380 align:middle line:90%


00:03:54.380 --> 00:03:57.050 align:middle line:84%
So then how can we do
service enumeration?

00:03:57.050 --> 00:04:00.920 align:middle line:84%
Well, we'll do our three-way
handshake, a SYN, SYN ACC, ACC.

00:04:00.920 --> 00:04:04.680 align:middle line:84%
And then with that ACC,
we'll grab a banner.

00:04:04.680 --> 00:04:09.020 align:middle line:84%
So initial connection to a
service, if it's there it'll

00:04:09.020 --> 00:04:10.650 align:middle line:90%
send us back some information.

00:04:10.650 --> 00:04:14.350 align:middle line:84%
So with the service
enumeration, we'll

00:04:14.350 --> 00:04:18.220 align:middle line:84%
actually expect that back,
listen for it, and gather it.

00:04:18.220 --> 00:04:19.209 align:middle line:90%
It's not quiet.

00:04:19.209 --> 00:04:20.959 align:middle line:90%
It is very loud.

00:04:20.959 --> 00:04:24.730 align:middle line:84%
But if we can do
it on our pen test,

00:04:24.730 --> 00:04:29.950 align:middle line:84%
that's OK so long as you don't
break anything that you're not

00:04:29.950 --> 00:04:31.235 align:middle line:90%
supposed to break.

00:04:31.235 --> 00:04:32.110 align:middle line:90%
We'll probably be OK.

00:04:32.110 --> 00:04:36.900 align:middle line:90%


00:04:36.900 --> 00:04:39.540 align:middle line:84%
There's connections
to UDP as well.

00:04:39.540 --> 00:04:40.800 align:middle line:90%
They're slower.

00:04:40.800 --> 00:04:43.080 align:middle line:84%
And usually what you
get back is either

00:04:43.080 --> 00:04:45.960 align:middle line:84%
it can be an
open-filtered, which

00:04:45.960 --> 00:04:48.300 align:middle line:90%
means that didn't drop it.

00:04:48.300 --> 00:04:53.970 align:middle line:84%
But it's filtered, so you
don't know the status.

00:04:53.970 --> 00:04:59.310 align:middle line:84%
UDP connections can be sped
up by applying certain flags

00:04:59.310 --> 00:05:00.225 align:middle line:90%
in your Nmap scan.

00:05:00.225 --> 00:05:04.760 align:middle line:90%


00:05:04.760 --> 00:05:06.740 align:middle line:90%
Speaking of Nmap, let's dive in.

00:05:06.740 --> 00:05:11.510 align:middle line:90%


00:05:11.510 --> 00:05:14.900 align:middle line:84%
Nmap is a very powerful
tool, and let's look

00:05:14.900 --> 00:05:20.360 align:middle line:84%
at the help page for Nmap
just to see how powerful.

00:05:20.360 --> 00:05:24.200 align:middle line:84%
There are a lot of flags that
you can throw in with Nmap,

00:05:24.200 --> 00:05:26.870 align:middle line:90%
a lot of switches.

00:05:26.870 --> 00:05:30.350 align:middle line:84%
Some things we want to look at,
we already did this ping scan

00:05:30.350 --> 00:05:32.480 align:middle line:90%
before in hopes of discovery.

00:05:32.480 --> 00:05:36.420 align:middle line:90%


00:05:36.420 --> 00:05:40.430 align:middle line:84%
And we talked about
doing a SYN scan.

00:05:40.430 --> 00:05:49.360 align:middle line:84%
There's also a full-connect
scan and a few other ways

00:05:49.360 --> 00:05:52.270 align:middle line:84%
of scanning if you want
to avoid detection.

00:05:52.270 --> 00:05:54.730 align:middle line:84%
If you want to pick specific
ports, that's doable.

00:05:54.730 --> 00:06:00.270 align:middle line:90%


00:06:00.270 --> 00:06:04.460 align:middle line:84%
We can look at
service detection,

00:06:04.460 --> 00:06:07.340 align:middle line:90%
-sV will do service detection.

00:06:07.340 --> 00:06:11.780 align:middle line:84%
There's some scripting
available in Nmap with Nmap

00:06:11.780 --> 00:06:13.340 align:middle line:90%
scripting engine.

00:06:13.340 --> 00:06:15.725 align:middle line:84%
If we run the -sC it'll
run the default scripts.

00:06:15.725 --> 00:06:18.370 align:middle line:90%


00:06:18.370 --> 00:06:21.280 align:middle line:84%
Our -O will do that
operating system detection

00:06:21.280 --> 00:06:24.140 align:middle line:90%
that we talked about.

00:06:24.140 --> 00:06:26.590 align:middle line:84%
And if you don't
mind being loud,

00:06:26.590 --> 00:06:30.880 align:middle line:84%
if you've got some
firewall evasion,

00:06:30.880 --> 00:06:36.370 align:middle line:84%
IDS evation if you want,
down here under miscellaneous

00:06:36.370 --> 00:06:40.420 align:middle line:84%
we've got -A. I think
of it as aggressive.

00:06:40.420 --> 00:06:43.930 align:middle line:84%
It does OS detection,
version detection,

00:06:43.930 --> 00:06:47.560 align:middle line:84%
does the script scanning
and a traceroute.

00:06:47.560 --> 00:06:50.190 align:middle line:90%
It can be very useful.

00:06:50.190 --> 00:06:53.170 align:middle line:84%
Let's look at what we
get as our outputs.

00:06:53.170 --> 00:06:58.810 align:middle line:84%
If we run just the
normal Nmap of--

00:06:58.810 --> 00:07:05.610 align:middle line:84%
I put all of our IPs into
this file here called IPs.

00:07:05.610 --> 00:07:07.360 align:middle line:84%
If we don't have to
scan the whole subnet,

00:07:07.360 --> 00:07:09.530 align:middle line:90%
it'll go a little faster.

00:07:09.530 --> 00:07:13.225 align:middle line:84%
We'll just run Nmap
-iL of our IPs.

00:07:13.225 --> 00:07:18.720 align:middle line:90%


00:07:18.720 --> 00:07:21.450 align:middle line:84%
Pressing V while it's scanning
will increase verbosity,

00:07:21.450 --> 00:07:22.920 align:middle line:90%
so you can see what's happening.

00:07:22.920 --> 00:07:25.450 align:middle line:90%


00:07:25.450 --> 00:07:28.920 align:middle line:84%
And you can see we
got a return back.

00:07:28.920 --> 00:07:31.683 align:middle line:84%
We have some services,
different ports

00:07:31.683 --> 00:07:32.850 align:middle line:90%
on these different machines.

00:07:32.850 --> 00:07:35.890 align:middle line:90%


00:07:35.890 --> 00:07:37.750 align:middle line:84%
Now it's taking a
guess at the service

00:07:37.750 --> 00:07:42.490 align:middle line:84%
is based off of known
ports because all it did

00:07:42.490 --> 00:07:49.600 align:middle line:84%
was that simple SYN scan or that
simple scan to connect and see

00:07:49.600 --> 00:07:51.460 align:middle line:90%
if the ports are open.

00:07:51.460 --> 00:07:54.550 align:middle line:84%
If we want to add
onto that, we can

00:07:54.550 --> 00:07:59.140 align:middle line:84%
run a service detection and also
the operating system detection.

00:07:59.140 --> 00:08:03.430 align:middle line:90%


00:08:03.430 --> 00:08:06.930 align:middle line:84%
And there's, of course,
sudo which is also

00:08:06.930 --> 00:08:08.820 align:middle line:90%
going to do a stealth scan.

00:08:08.820 --> 00:08:17.200 align:middle line:90%


00:08:17.200 --> 00:08:19.510 align:middle line:84%
Pressing spacebar in
the middle will give you

00:08:19.510 --> 00:08:23.500 align:middle line:90%
a heads up of what's happening.

00:08:23.500 --> 00:08:27.310 align:middle line:84%
If your scan is taking a long
while, press the spacebar

00:08:27.310 --> 00:08:33.700 align:middle line:84%
and you can see an update,
perhaps how much time is left.

00:08:33.700 --> 00:08:40.100 align:middle line:90%


00:08:40.100 --> 00:08:41.980 align:middle line:84%
We can see that operating
system detection

00:08:41.980 --> 00:08:43.659 align:middle line:90%
takes a little more effort.

00:08:43.659 --> 00:08:48.279 align:middle line:90%


00:08:48.279 --> 00:08:50.990 align:middle line:84%
And now our results have
a lot of information.

00:08:50.990 --> 00:08:55.520 align:middle line:90%


00:08:55.520 --> 00:09:02.080 align:middle line:84%
So our first machine,
111.1, we've got open SSH.

00:09:02.080 --> 00:09:07.570 align:middle line:90%
And it's the FreeBSD 20100308.

00:09:07.570 --> 00:09:10.840 align:middle line:84%
That's helpful because when we
look at our operating system

00:09:10.840 --> 00:09:18.410 align:middle line:84%
scan results, it says,
just guessing, OpenBSD 4.X.

00:09:18.410 --> 00:09:23.930 align:middle line:84%
And then the aggressive guess
is, again, the same, 4.3.

00:09:23.930 --> 00:09:26.320 align:middle line:84%
And we can back that
up with our service.

00:09:26.320 --> 00:09:28.010 align:middle line:84%
We see that it's
running open SSH

00:09:28.010 --> 00:09:31.080 align:middle line:90%
for FreeBSD, which makes sense.

00:09:31.080 --> 00:09:33.960 align:middle line:84%
There's also a DNS
mask and lighttpd.

00:09:33.960 --> 00:09:38.490 align:middle line:90%


00:09:38.490 --> 00:09:42.060 align:middle line:84%
What we'll do with those
we'll get to you later.

00:09:42.060 --> 00:09:44.580 align:middle line:84%
On our .6 we've got
open SSH, and it

00:09:44.580 --> 00:09:47.440 align:middle line:84%
says it's running
the Debian version.

00:09:47.440 --> 00:09:51.900 align:middle line:84%
So when we look down
at no exact OS matches,

00:09:51.900 --> 00:09:54.030 align:middle line:90%
it also gives us a fingerprint.

00:09:54.030 --> 00:09:57.050 align:middle line:84%
We could go and submit and
say that this fingerprint goes

00:09:57.050 --> 00:09:58.740 align:middle line:90%
with Debian.

00:09:58.740 --> 00:10:01.143 align:middle line:84%
You can make a good
guess based off

00:10:01.143 --> 00:10:03.060 align:middle line:84%
of the service that's
running on that machine.

00:10:03.060 --> 00:10:07.330 align:middle line:90%


00:10:07.330 --> 00:10:10.810 align:middle line:90%
On this .48, even more useful--

00:10:10.810 --> 00:10:16.090 align:middle line:84%
while our operating system scan
says there's no exact matches,

00:10:16.090 --> 00:10:20.530 align:middle line:84%
we see we're running Microsoft
Windows RPC, Microsoft Windows

00:10:20.530 --> 00:10:26.990 align:middle line:84%
NetBIOS, Microsoft
Windows XP Microsoft TS.

00:10:26.990 --> 00:10:28.970 align:middle line:84%
There's a good chance
this machine is

00:10:28.970 --> 00:10:34.420 align:middle line:90%
running Windows XP on port 445.

00:10:34.420 --> 00:10:36.990 align:middle line:90%
I feel like a net API attack.

00:10:36.990 --> 00:10:37.740 align:middle line:90%
We'll get to that.

00:10:37.740 --> 00:10:41.200 align:middle line:90%


00:10:41.200 --> 00:10:47.570 align:middle line:84%
It's just a known, good
exploit on Windows XP.

00:10:47.570 --> 00:10:51.410 align:middle line:84%
This next machine, again,
we have no exact OS matches.

00:10:51.410 --> 00:10:54.770 align:middle line:84%
But it's running
on port 80 Apache

00:10:54.770 --> 00:10:58.280 align:middle line:90%
HTTPD and the Debian version.

00:10:58.280 --> 00:11:02.970 align:middle line:84%
So we can make a good guess
that this is a Debian Linux web

00:11:02.970 --> 00:11:03.470 align:middle line:90%
server.

00:11:03.470 --> 00:11:10.080 align:middle line:90%


00:11:10.080 --> 00:11:13.920 align:middle line:84%
On our .100, it said it
scanned all the ports.

00:11:13.920 --> 00:11:15.810 align:middle line:84%
And there were too many
fingerprint matches

00:11:15.810 --> 00:11:18.240 align:middle line:90%
to have specific OS details.

00:11:18.240 --> 00:11:20.080 align:middle line:90%
So one's a little interesting.

00:11:20.080 --> 00:11:22.040 align:middle line:90%
It's a little different.

00:11:22.040 --> 00:11:23.040 align:middle line:90%
Perhaps it's a firewall.

00:11:23.040 --> 00:11:28.830 align:middle line:90%


00:11:28.830 --> 00:11:34.760 align:middle line:84%
And then our .99, we again have
open SSH and it says FreeBSD.

00:11:34.760 --> 00:11:37.400 align:middle line:90%
And similar results again--

00:11:37.400 --> 00:11:46.160 align:middle line:90%
OpenBSD and OpenBSD 4.3.

00:11:46.160 --> 00:11:51.830 align:middle line:84%
213-- another Debian web
server, even though it says

00:11:51.830 --> 00:11:53.045 align:middle line:90%
no exact OS matches.

00:11:53.045 --> 00:11:57.060 align:middle line:90%


00:11:57.060 --> 00:12:01.580 align:middle line:84%
And that's the basics that
you can get away with.

00:12:01.580 --> 00:12:07.370 align:middle line:84%
If we wanted to, we could
add in some scripts.

00:12:07.370 --> 00:12:11.585 align:middle line:84%
And some of the default scripts
will be discovery scripts.

00:12:11.585 --> 00:12:15.990 align:middle line:90%


00:12:15.990 --> 00:12:18.690 align:middle line:84%
Some are some
vulnerability scripts.

00:12:18.690 --> 00:12:20.430 align:middle line:84%
Now what's a little
different here

00:12:20.430 --> 00:12:29.963 align:middle line:84%
is after that operating
system detection,

00:12:29.963 --> 00:12:31.630 align:middle line:84%
then we've got a
little more work for it

00:12:31.630 --> 00:12:34.760 align:middle line:84%
to do because it'll run
the scripts based off

00:12:34.760 --> 00:12:36.010 align:middle line:90%
of the services that it finds.

00:12:36.010 --> 00:12:39.680 align:middle line:90%


00:12:39.680 --> 00:12:41.195 align:middle line:90%
And this scan takes much longer.

00:12:41.195 --> 00:12:44.320 align:middle line:90%


00:12:44.320 --> 00:12:47.140 align:middle line:84%
You can see it's initiating
the NSE, that Nmap scripting

00:12:47.140 --> 00:12:47.640 align:middle line:90%
engine.

00:12:47.640 --> 00:12:59.340 align:middle line:90%


00:12:59.340 --> 00:13:00.340 align:middle line:90%
Now we have our results.

00:13:00.340 --> 00:13:10.980 align:middle line:90%


00:13:10.980 --> 00:13:13.280 align:middle line:84%
Some of those
scripts, not only do

00:13:13.280 --> 00:13:16.880 align:middle line:84%
we have the version
of SSH, open SSH,

00:13:16.880 --> 00:13:18.800 align:middle line:84%
but now we've got
the SSH host key.

00:13:18.800 --> 00:13:21.590 align:middle line:90%


00:13:21.590 --> 00:13:29.550 align:middle line:84%
We have some PHP session ID
information, our HTTP server

00:13:29.550 --> 00:13:33.560 align:middle line:90%
headers, which adds even more.

00:13:33.560 --> 00:13:36.515 align:middle line:84%
I mean, that's how we found
out what version it was here.

00:13:36.515 --> 00:13:40.200 align:middle line:90%


00:13:40.200 --> 00:13:42.190 align:middle line:84%
And as we continue
looking down, we

00:13:42.190 --> 00:13:44.900 align:middle line:84%
can see what
services are running

00:13:44.900 --> 00:13:46.820 align:middle line:84%
and make good guesses
on what operating

00:13:46.820 --> 00:13:48.590 align:middle line:90%
systems we're looking at.

00:13:48.590 --> 00:13:55.880 align:middle line:90%


00:13:55.880 --> 00:13:57.980 align:middle line:84%
Then we'll look at the
ports that are open,

00:13:57.980 --> 00:14:02.330 align:middle line:84%
the versions of the services
that are on those machines,

00:14:02.330 --> 00:14:05.270 align:middle line:84%
and try to find some
operating system information.

00:14:05.270 --> 00:14:07.872 align:middle line:90%


00:14:07.872 --> 00:14:10.330 align:middle line:84%
There are a handful of tools
that we can also use for this.

00:14:10.330 --> 00:14:13.000 align:middle line:84%
Zenmap is the GUI
version of Nmap.

00:14:13.000 --> 00:14:15.640 align:middle line:84%
And it will take all of
this console information

00:14:15.640 --> 00:14:18.130 align:middle line:84%
and put it into
that nice interface

00:14:18.130 --> 00:14:20.030 align:middle line:90%
that we saw in the last lesson.

00:14:20.030 --> 00:14:25.000 align:middle line:84%
There's also Nmap Automator,
which based off of the subnet

00:14:25.000 --> 00:14:27.190 align:middle line:84%
that you give it, based
off of what it finds,

00:14:27.190 --> 00:14:28.570 align:middle line:90%
it will run new scans.

00:14:28.570 --> 00:14:31.390 align:middle line:84%
And it will continue
enumeration all throughout what

00:14:31.390 --> 00:14:33.400 align:middle line:90%
we'll get to later.

00:14:33.400 --> 00:14:36.670 align:middle line:84%
Masscan is a very
fast port scanner.

00:14:36.670 --> 00:14:43.150 align:middle line:84%
It works by multithreading,
and it's very powerful.

00:14:43.150 --> 00:14:49.960 align:middle line:84%
Rustscan runs off of Rust, which
operates at a lower level, as

00:14:49.960 --> 00:14:55.120 align:middle line:84%
a lower-level language, and is
then able to work a lot faster.

00:14:55.120 --> 00:14:58.780 align:middle line:84%
And Autorecon, similar
to Nmap Automator,

00:14:58.780 --> 00:15:02.740 align:middle line:84%
based off of what it initially
finds it'll run a quick scan.

00:15:02.740 --> 00:15:05.775 align:middle line:90%
It'll run a more deep scan.

00:15:05.775 --> 00:15:07.150 align:middle line:84%
And really, what
it's doing is it

00:15:07.150 --> 00:15:11.080 align:middle line:84%
is continuing to scan either
a single host or subnet

00:15:11.080 --> 00:15:15.420 align:middle line:84%
or based off of a
list, same as Nmap,

00:15:15.420 --> 00:15:17.790 align:middle line:84%
and continue to
scan and enumerate

00:15:17.790 --> 00:15:20.340 align:middle line:84%
until everything
that could possibly

00:15:20.340 --> 00:15:23.220 align:middle line:84%
be known about it from
scanning is complete.

00:15:23.220 --> 00:15:26.110 align:middle line:84%
And it'll get into
some other tools

00:15:26.110 --> 00:15:30.210 align:middle line:84%
that we will get into
in later lessons--

00:15:30.210 --> 00:15:33.170 align:middle line:90%
very powerful tools there.

00:15:33.170 --> 00:15:34.000 align:middle line:90%