WEBVTT

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


00:00:03.976 --> 00:00:07.455 align:middle line:90%
[GLITCHY MUSICAL SOUND EFFECTS]

00:00:07.455 --> 00:00:10.440 align:middle line:90%


00:00:10.440 --> 00:00:12.450 align:middle line:90%
Port scanning and enumeration.

00:00:12.450 --> 00:00:15.540 align:middle line:84%
So welcome to the first
section of the first video

00:00:15.540 --> 00:00:18.630 align:middle line:84%
within the Windows Black
Box Penetration Test.

00:00:18.630 --> 00:00:20.570 align:middle line:84%
In this specific
video, we're going

00:00:20.570 --> 00:00:22.680 align:middle line:84%
to be taking a
look at performing

00:00:22.680 --> 00:00:26.520 align:middle line:84%
port scanning on the target
system, identifying open ports

00:00:26.520 --> 00:00:29.460 align:middle line:84%
as well as the
respective services that

00:00:29.460 --> 00:00:30.960 align:middle line:90%
are running on those ports.

00:00:30.960 --> 00:00:34.290 align:middle line:84%
And we'll take a look at how
to sort all of this data,

00:00:34.290 --> 00:00:37.920 align:middle line:84%
or all of the data that we're
getting from the port scans,

00:00:37.920 --> 00:00:40.140 align:middle line:84%
and how to import them into
the Metasploit framework

00:00:40.140 --> 00:00:42.570 align:middle line:90%
for ease of access.

00:00:42.570 --> 00:00:46.140 align:middle line:84%
And also, we'll take a look
at some basic enumeration.

00:00:46.140 --> 00:00:48.720 align:middle line:84%
The objective here is to
learn as much information

00:00:48.720 --> 00:00:52.560 align:middle line:84%
as possible from the services
that are running on the target

00:00:52.560 --> 00:00:56.130 align:middle line:84%
system, as well as more
information regarding

00:00:56.130 --> 00:01:00.000 align:middle line:84%
the exact version of Windows
Server 2008 that is running

00:01:00.000 --> 00:01:01.210 align:middle line:90%
on the target system.

00:01:01.210 --> 00:01:06.270 align:middle line:84%
So as I said, in this
entire section of Windows

00:01:06.270 --> 00:01:08.850 align:middle line:84%
exploitation, you'll
essentially be given access

00:01:08.850 --> 00:01:10.860 align:middle line:84%
to one lab
environment, or rather

00:01:10.860 --> 00:01:12.040 align:middle line:90%
the same lab environment.

00:01:12.040 --> 00:01:14.280 align:middle line:84%
So you don't have
to start and stop

00:01:14.280 --> 00:01:17.460 align:middle line:84%
the lab environment
after every video

00:01:17.460 --> 00:01:18.690 align:middle line:90%
that I'll be going through.

00:01:18.690 --> 00:01:21.180 align:middle line:84%
You can essentially just
start up one instance

00:01:21.180 --> 00:01:24.390 align:middle line:84%
and then follow along, or you
can go through and essentially

00:01:24.390 --> 00:01:26.910 align:middle line:84%
try and gain access
yourself with everything

00:01:26.910 --> 00:01:28.390 align:middle line:90%
that you have learned so far.

00:01:28.390 --> 00:01:30.150 align:middle line:84%
So these videos are
essentially just going

00:01:30.150 --> 00:01:32.220 align:middle line:90%
to be references for you to--

00:01:32.220 --> 00:01:34.920 align:middle line:84%
if you're finding
something difficult,

00:01:34.920 --> 00:01:36.810 align:middle line:84%
then this is where
I'll be coming in.

00:01:36.810 --> 00:01:39.070 align:middle line:90%
So let's get started.

00:01:39.070 --> 00:01:41.580 align:middle line:84%
So all you need to do is just
fire up the lab environment.

00:01:41.580 --> 00:01:42.780 align:middle line:90%
And I'll also do that.

00:01:42.780 --> 00:01:44.760 align:middle line:84%
And I'll switch over
to my lab environment,

00:01:44.760 --> 00:01:46.080 align:middle line:90%
and we can get started.

00:01:46.080 --> 00:01:49.290 align:middle line:90%


00:01:49.290 --> 00:01:49.790 align:middle line:90%
All right.

00:01:49.790 --> 00:01:51.740 align:middle line:84%
So I'm back within
the lab environment.

00:01:51.740 --> 00:01:53.660 align:middle line:84%
And as you can see,
you're not going

00:01:53.660 --> 00:01:56.660 align:middle line:84%
to be provided with
access to the target

00:01:56.660 --> 00:01:59.840 align:middle line:84%
system via the additional
tab at the top.

00:01:59.840 --> 00:02:03.140 align:middle line:84%
You're also not going to be
provided with the target IP

00:02:03.140 --> 00:02:03.780 align:middle line:90%
address.

00:02:03.780 --> 00:02:06.800 align:middle line:84%
So again, that is something
that we'll have to identify.

00:02:06.800 --> 00:02:09.169 align:middle line:84%
Now, given the fact that this
lab environment is running

00:02:09.169 --> 00:02:12.860 align:middle line:84%
in the cloud, the quickest way
of identifying the target IP

00:02:12.860 --> 00:02:16.550 align:middle line:84%
address is to check your
hosts file, because a URL

00:02:16.550 --> 00:02:18.620 align:middle line:84%
that corresponds to
the target IP address

00:02:18.620 --> 00:02:22.340 align:middle line:84%
has already been added as
an actual record there.

00:02:22.340 --> 00:02:27.950 align:middle line:84%
So you can just cat out the
contents of /etc and hosts.

00:02:27.950 --> 00:02:29.180 align:middle line:90%
There we are, /etc/hosts.

00:02:29.180 --> 00:02:32.270 align:middle line:84%
And at the bottom, you
should have an IP address

00:02:32.270 --> 00:02:34.910 align:middle line:90%
assigned to demo.ine.local.

00:02:34.910 --> 00:02:37.280 align:middle line:90%
And this URL might change.

00:02:37.280 --> 00:02:39.787 align:middle line:84%
But all you need to do
is just copy the IP here.

00:02:39.787 --> 00:02:42.120 align:middle line:84%
And of course, in your case,
it's going to be different.

00:02:42.120 --> 00:02:44.160 align:middle line:84%
So do take that
into consideration.

00:02:44.160 --> 00:02:45.830 align:middle line:84%
So I'm just going
to copy that there.

00:02:45.830 --> 00:02:48.170 align:middle line:84%
And I'll head over
into my desktop.

00:02:48.170 --> 00:02:50.630 align:middle line:84%
And we are going to
create a new folder here,

00:02:50.630 --> 00:02:52.730 align:middle line:84%
and I'm just going
to call it Win2k8.

00:02:52.730 --> 00:02:54.890 align:middle line:90%
So that's Windows Server 2008.

00:02:54.890 --> 00:02:58.310 align:middle line:84%
And I also recommend doing
this because again, this

00:02:58.310 --> 00:03:00.050 align:middle line:84%
is very important,
and you need to keep

00:03:00.050 --> 00:03:02.450 align:middle line:90%
your data sorted and organized.

00:03:02.450 --> 00:03:05.630 align:middle line:84%
So within this folder is
where we're going to create

00:03:05.630 --> 00:03:07.070 align:middle line:84%
or where we're
going to store all

00:03:07.070 --> 00:03:11.990 align:middle line:84%
the relative or necessary
files for exploitation and port

00:03:11.990 --> 00:03:13.590 align:middle line:84%
scanning, et
cetera, all of that.

00:03:13.590 --> 00:03:16.050 align:middle line:84%
So we have identified
the target IP address.

00:03:16.050 --> 00:03:17.190 align:middle line:90%
So what can we do?

00:03:17.190 --> 00:03:19.280 align:middle line:84%
Well, firstly, can we
actually access it,

00:03:19.280 --> 00:03:21.600 align:middle line:90%
or can we actually reach it?

00:03:21.600 --> 00:03:24.140 align:middle line:84%
So I'll just perform
a quick ping,

00:03:24.140 --> 00:03:26.058 align:middle line:84%
and let's see whether
it actually responds.

00:03:26.058 --> 00:03:26.600 align:middle line:90%
There we are.

00:03:26.600 --> 00:03:27.767 align:middle line:90%
We can see that it responds.

00:03:27.767 --> 00:03:29.670 align:middle line:84%
So that means we can
communicate with it.

00:03:29.670 --> 00:03:33.560 align:middle line:84%
So the next obvious step is
to perform a simple nmap scan

00:03:33.560 --> 00:03:36.830 align:middle line:84%
on the default port range, which
is 1,000 of the most commonly

00:03:36.830 --> 00:03:37.670 align:middle line:90%
used ports.

00:03:37.670 --> 00:03:39.260 align:middle line:90%
And that can be done with nmap.

00:03:39.260 --> 00:03:42.140 align:middle line:84%
And we'll just perform a
service version detection scan.

00:03:42.140 --> 00:03:44.480 align:middle line:84%
And we'll paste in
the target IP there.

00:03:44.480 --> 00:03:46.910 align:middle line:84%
And let's see what's running
on the target, right?

00:03:46.910 --> 00:03:49.430 align:middle line:84%
So we're just getting a
basic idea of what's running.

00:03:49.430 --> 00:03:53.450 align:middle line:84%
We can then modify the scan
to identify more information

00:03:53.450 --> 00:03:56.270 align:middle line:84%
regarding any other open ports
that we might have missed.

00:03:56.270 --> 00:03:58.880 align:middle line:84%
Because remember,
this default scan

00:03:58.880 --> 00:04:02.450 align:middle line:84%
essentially scans 1,000 of
the most commonly used ports.

00:04:02.450 --> 00:04:05.300 align:middle line:84%
And in order to scan the
entire TCP range, which

00:04:05.300 --> 00:04:11.300 align:middle line:84%
is about 65,535 ports, we need
to specify that explicitly

00:04:11.300 --> 00:04:15.300 align:middle line:84%
with the nmap scan, or as part
of the nmap scan argument.

00:04:15.300 --> 00:04:17.510 align:middle line:84%
So I'll just wait
for this to complete.

00:04:17.510 --> 00:04:21.240 align:middle line:84%
Right, so the initial
nmap scan is done.

00:04:21.240 --> 00:04:23.150 align:middle line:84%
And as you can see
right over here,

00:04:23.150 --> 00:04:26.090 align:middle line:84%
we have been able to identify
various services running

00:04:26.090 --> 00:04:27.560 align:middle line:90%
on this target system.

00:04:27.560 --> 00:04:29.820 align:middle line:84%
And let's take a
closer look at them.

00:04:29.820 --> 00:04:32.330 align:middle line:84%
So we have ftp
running on port 21,

00:04:32.330 --> 00:04:37.190 align:middle line:84%
and the actual service
itself is Microsoft ftpd.

00:04:37.190 --> 00:04:40.280 align:middle line:84%
And it doesn't specify
the actual version.

00:04:40.280 --> 00:04:44.520 align:middle line:84%
We then have ssh, and more
specifically, OpenSSH 7.1.

00:04:44.520 --> 00:04:46.940 align:middle line:84%
Now, remember, OpenSSH
is running on Windows.

00:04:46.940 --> 00:04:49.080 align:middle line:90%
So just keep that in mind.

00:04:49.080 --> 00:04:51.140 align:middle line:84%
We also have a web server
running on port 80,

00:04:51.140 --> 00:04:53.750 align:middle line:84%
and that is the
Microsoft IIS httpd

00:04:53.750 --> 00:04:57.080 align:middle line:90%
7.5 version of Microsoft IIS.

00:04:57.080 --> 00:05:01.010 align:middle line:84%
We then have your standard
RPC port, netbios, and SMB.

00:05:01.010 --> 00:05:02.970 align:middle line:84%
And SMB tells us
that, of course,

00:05:02.970 --> 00:05:04.880 align:middle line:84%
it's running
Windows Server 2008.

00:05:04.880 --> 00:05:08.150 align:middle line:84%
And it could be running Windows
Server 2008 or Windows Server

00:05:08.150 --> 00:05:09.680 align:middle line:90%
2008 R2.

00:05:09.680 --> 00:05:12.650 align:middle line:84%
We also have a MySQL
database server

00:05:12.650 --> 00:05:15.710 align:middle line:84%
running on the default
port, which is 3306.

00:05:15.710 --> 00:05:21.230 align:middle line:84%
And we also have an RDP
port, which is on 3389.

00:05:21.230 --> 00:05:24.290 align:middle line:84%
It looks like we also have
another web application that's

00:05:24.290 --> 00:05:26.570 align:middle line:90%
running on port 4848.

00:05:26.570 --> 00:05:29.660 align:middle line:84%
And this requires an
SSL-- or actually has

00:05:29.660 --> 00:05:30.930 align:middle line:90%
an SSL certificate.

00:05:30.930 --> 00:05:35.420 align:middle line:84%
So that's running Oracle
GlassFish Application Server.

00:05:35.420 --> 00:05:39.980 align:middle line:84%
On port 7676 it looks like we
have the Java Message Service.

00:05:39.980 --> 00:05:42.530 align:middle line:84%
On port 8080 we
also have GlassFish.

00:05:42.530 --> 00:05:46.490 align:middle line:84%
This is the Sun GlassFish
Open Source Edition 4.0.

00:05:46.490 --> 00:05:50.660 align:middle line:84%
And on port 8181, we also
have Oracle GlassFish.

00:05:50.660 --> 00:05:55.530 align:middle line:84%
And on port 9200, we aren't
able to identify that service.

00:05:55.530 --> 00:05:57.260 align:middle line:84%
So again, this is a
good start, but this

00:05:57.260 --> 00:06:01.408 align:middle line:84%
is by no means the entire
list or scope of services

00:06:01.408 --> 00:06:02.700 align:middle line:90%
that are running on the target.

00:06:02.700 --> 00:06:07.260 align:middle line:84%
So what we can do now is, if we
actually go to the bottom here,

00:06:07.260 --> 00:06:10.490 align:middle line:84%
we can perform another nmap scan
that's much more comprehensive.

00:06:10.490 --> 00:06:15.020 align:middle line:84%
So we can say nmap, and I'll
set the timing template to T4.

00:06:15.020 --> 00:06:17.730 align:middle line:84%
So that's a much faster
scan than the default one.

00:06:17.730 --> 00:06:20.120 align:middle line:84%
And we'll perform
ACK scan, so -PA.

00:06:20.120 --> 00:06:25.130 align:middle line:84%
And we'll also perform
the default script scan,

00:06:25.130 --> 00:06:27.830 align:middle line:84%
as well as service
version detection.

00:06:27.830 --> 00:06:32.630 align:middle line:84%
And we can set the port range
to 1 to 10,000, so 10,000 ports.

00:06:32.630 --> 00:06:35.450 align:middle line:84%
I'm not scanning the
entire TCP range yet.

00:06:35.450 --> 00:06:37.490 align:middle line:84%
And then we paste
in the target IP.

00:06:37.490 --> 00:06:39.390 align:middle line:84%
And this is something
that's very important.

00:06:39.390 --> 00:06:41.665 align:middle line:84%
We want to output the scan
results, because you always

00:06:41.665 --> 00:06:43.040 align:middle line:84%
want to make sure
that you output

00:06:43.040 --> 00:06:44.420 align:middle line:90%
all of your scan results.

00:06:44.420 --> 00:06:47.010 align:middle line:84%
I'm going to output
it into an XML format

00:06:47.010 --> 00:06:49.440 align:middle line:84%
so that we can import it into
the Metasploit framework.

00:06:49.440 --> 00:06:52.470 align:middle line:84%
So I'll say -oX, and then
I'll provide it with a name.

00:06:52.470 --> 00:06:55.400 align:middle line:84%
So I'll just call this
nmap 10,000, or 10k.

00:06:55.400 --> 00:06:56.090 align:middle line:90%
All right?

00:06:56.090 --> 00:06:59.780 align:middle line:84%
So that essentially tells
me that this particular scan

00:06:59.780 --> 00:07:02.960 align:middle line:90%
is for only 10,000 ports.

00:07:02.960 --> 00:07:06.450 align:middle line:90%
So that looks like it's good.

00:07:06.450 --> 00:07:07.550 align:middle line:90%
And I can just hit Enter.

00:07:07.550 --> 00:07:10.040 align:middle line:84%
And it's going to begin
performing the nmap scan.

00:07:10.040 --> 00:07:11.810 align:middle line:84%
Now, while it's
performing the nmap scan,

00:07:11.810 --> 00:07:14.600 align:middle line:84%
we can begin accessing
or trying to learn more

00:07:14.600 --> 00:07:18.800 align:middle line:84%
about some of the services
that can be accessed, maybe

00:07:18.800 --> 00:07:19.800 align:middle line:90%
through the web browser.

00:07:19.800 --> 00:07:21.710 align:middle line:84%
So let's try and
access the web server,

00:07:21.710 --> 00:07:24.380 align:middle line:84%
and let's see what
web application is

00:07:24.380 --> 00:07:25.740 align:middle line:90%
being hosted on there.

00:07:25.740 --> 00:07:27.950 align:middle line:84%
So if we click on it, it
looks like a very simple web

00:07:27.950 --> 00:07:28.640 align:middle line:90%
application.

00:07:28.640 --> 00:07:31.140 align:middle line:84%
And there is an image
being displayed here.

00:07:31.140 --> 00:07:33.380 align:middle line:84%
So we can open the
image in a new tab.

00:07:33.380 --> 00:07:36.710 align:middle line:84%
As I said, this has been set
up to actually tease you,

00:07:36.710 --> 00:07:37.700 align:middle line:90%
in many ways.

00:07:37.700 --> 00:07:41.870 align:middle line:84%
Because there are going
to be various access

00:07:41.870 --> 00:07:45.020 align:middle line:84%
vectors or vulnerabilities
within quite a few services

00:07:45.020 --> 00:07:46.700 align:middle line:90%
that you can actually exploit.

00:07:46.700 --> 00:07:49.250 align:middle line:84%
So it's just a simple
web application there.

00:07:49.250 --> 00:07:52.340 align:middle line:84%
We can also view the page
source to learn more about it.

00:07:52.340 --> 00:07:55.800 align:middle line:84%
And it just looks like we
have some basic HTML, CSS.

00:07:55.800 --> 00:07:59.367 align:middle line:84%
And it looks like we
have a value here.

00:07:59.367 --> 00:08:00.950 align:middle line:84%
I believe that's for
the actual image.

00:08:00.950 --> 00:08:03.650 align:middle line:90%
And this is encoded in base 64.

00:08:03.650 --> 00:08:04.910 align:middle line:90%
So yeah, there we are.

00:08:04.910 --> 00:08:06.380 align:middle line:84%
You can actually
go through that,

00:08:06.380 --> 00:08:09.730 align:middle line:84%
and that's still the
actual image code.

00:08:09.730 --> 00:08:11.390 align:middle line:90%
And there we go.

00:08:11.390 --> 00:08:11.890 align:middle line:90%
Right.

00:08:11.890 --> 00:08:15.160 align:middle line:84%
So again, that is all
pertinent to the image itself.

00:08:15.160 --> 00:08:17.240 align:middle line:84%
So we'll get to that
when we get there.

00:08:17.240 --> 00:08:19.480 align:middle line:84%
But I am primarily
interested in other services

00:08:19.480 --> 00:08:23.830 align:middle line:90%
like ftpd, OpenSSH.

00:08:23.830 --> 00:08:25.750 align:middle line:90%
We can also target SMB.

00:08:25.750 --> 00:08:27.890 align:middle line:84%
And I'm guessing what
you're guessing--

00:08:27.890 --> 00:08:30.250 align:middle line:84%
we can also target
the MySQL database

00:08:30.250 --> 00:08:32.770 align:middle line:84%
server through a
brute-force attack,

00:08:32.770 --> 00:08:36.679 align:middle line:84%
or identify the exact version,
which is provided to us here.

00:08:36.679 --> 00:08:38.380 align:middle line:84%
And in addition to
this, we can also

00:08:38.380 --> 00:08:41.110 align:middle line:84%
perform some banner-grabbing
to learn more

00:08:41.110 --> 00:08:44.320 align:middle line:84%
about a specific service
whose version has not

00:08:44.320 --> 00:08:45.640 align:middle line:90%
been enumerated with nmap.

00:08:45.640 --> 00:08:49.990 align:middle line:84%
So for example, I'll just open
up a new terminal window here,

00:08:49.990 --> 00:08:52.060 align:middle line:84%
and let me just
minimize that there.

00:08:52.060 --> 00:08:54.760 align:middle line:90%
And we are targeting the--

00:08:54.760 --> 00:08:57.160 align:middle line:84%
let's try port 21,
because we weren't

00:08:57.160 --> 00:08:58.810 align:middle line:84%
able to get anything
conclusive there.

00:08:58.810 --> 00:09:00.760 align:middle line:90%
So netcat and -nv.

00:09:00.760 --> 00:09:03.190 align:middle line:90%
Paste in the target IP, port 21.

00:09:03.190 --> 00:09:04.210 align:middle line:90%
Hit Enter.

00:09:04.210 --> 00:09:07.220 align:middle line:84%
And again, it just tells
us Microsoft FTP Service.

00:09:07.220 --> 00:09:10.060 align:middle line:84%
So again, nothing
additional there.

00:09:10.060 --> 00:09:12.790 align:middle line:84%
As for the other services,
we've got the service versions.

00:09:12.790 --> 00:09:16.060 align:middle line:84%
We can try and access some of
the other web applications.

00:09:16.060 --> 00:09:20.313 align:middle line:84%
So we can try and access,
let's see, port 4848.

00:09:20.313 --> 00:09:21.730 align:middle line:84%
And let's see what
that brings up.

00:09:21.730 --> 00:09:23.897 align:middle line:84%
So again, we're just trying
to get an idea of what's

00:09:23.897 --> 00:09:25.040 align:middle line:90%
running on the target.

00:09:25.040 --> 00:09:28.720 align:middle line:90%
So we can say port 4848.

00:09:28.720 --> 00:09:30.790 align:middle line:84%
And this requires
an SSL certificate,

00:09:30.790 --> 00:09:32.360 align:middle line:90%
or has an SSL certificate.

00:09:32.360 --> 00:09:34.660 align:middle line:84%
So I'll just say Accept
the Risk and Continue.

00:09:34.660 --> 00:09:37.720 align:middle line:84%
And this is the GlassFish
Server Open Source Edition.

00:09:37.720 --> 00:09:40.150 align:middle line:90%
That's on port 4848.

00:09:40.150 --> 00:09:43.450 align:middle line:90%
And let's just close this here.

00:09:43.450 --> 00:09:45.280 align:middle line:84%
And let's go back to
the actual terminal

00:09:45.280 --> 00:09:48.180 align:middle line:84%
here, where the
nmap results are.

00:09:48.180 --> 00:09:51.660 align:middle line:84%
We also have a web
server on port 8080.

00:09:51.660 --> 00:09:53.160 align:middle line:84%
So let's see what's
running on that.

00:09:53.160 --> 00:09:54.780 align:middle line:84%
It's telling us that
we have GlassFish

00:09:54.780 --> 00:09:58.213 align:middle line:90%
running on there, so 8080.

00:09:58.213 --> 00:09:59.880 align:middle line:84%
And we'll give this
a couple of seconds.

00:09:59.880 --> 00:10:01.990 align:middle line:84%
This doesn't have
an SSL certificate,

00:10:01.990 --> 00:10:03.570 align:middle line:90%
so we can just say HTTP.

00:10:03.570 --> 00:10:04.188 align:middle line:90%
There we are.

00:10:04.188 --> 00:10:05.980 align:middle line:84%
So it tells us, your
server is now running.

00:10:05.980 --> 00:10:07.560 align:middle line:84%
So it looks like
this is a status

00:10:07.560 --> 00:10:10.350 align:middle line:84%
page that actually
tells you whether or not

00:10:10.350 --> 00:10:11.290 align:middle line:90%
GlassFish is running.

00:10:11.290 --> 00:10:14.550 align:middle line:84%
And you can see that this is
still the default configuration

00:10:14.550 --> 00:10:16.530 align:middle line:84%
because it tells us,
to replace this page,

00:10:16.530 --> 00:10:20.020 align:middle line:84%
overwrite the file index.html,
et cetera, et cetera.

00:10:20.020 --> 00:10:20.520 align:middle line:90%
OK.

00:10:20.520 --> 00:10:23.970 align:middle line:84%
So we know what's
running on port 8080.

00:10:23.970 --> 00:10:27.040 align:middle line:84%
And probably we can try
and access port 9200.

00:10:27.040 --> 00:10:28.290 align:middle line:90%
Let's just see what's on that.

00:10:28.290 --> 00:10:30.000 align:middle line:90%
That looks interesting.

00:10:30.000 --> 00:10:35.420 align:middle line:84%
So we can try 9200, and it looks
like this is an API endpoint.

00:10:35.420 --> 00:10:39.130 align:middle line:84%
So we really can't tell or
get any additional information

00:10:39.130 --> 00:10:43.120 align:middle line:84%
regarding this right now until
our advanced nmap scan is done.

00:10:43.120 --> 00:10:45.440 align:middle line:84%
And indeed, it looks
like it's done.

00:10:45.440 --> 00:10:50.950 align:middle line:84%
So you can see that this was the
scan options I specified here.

00:10:50.950 --> 00:10:57.190 align:middle line:84%
And the default script
scan results will also

00:10:57.190 --> 00:10:59.270 align:middle line:84%
be shown for each
applicable service.

00:10:59.270 --> 00:11:03.250 align:middle line:84%
So for example, for FTP, the
ftp system script was used,

00:11:03.250 --> 00:11:05.230 align:middle line:84%
and it tells us that
the target is indeed

00:11:05.230 --> 00:11:07.840 align:middle line:90%
running a Windows NT kernel.

00:11:07.840 --> 00:11:12.860 align:middle line:84%
For SSH, we just get the SSH
host keys for the web server.

00:11:12.860 --> 00:11:16.480 align:middle line:84%
We can see that it gives
us the HTTP server as well

00:11:16.480 --> 00:11:18.770 align:middle line:84%
as the title and the
methods that are allowed.

00:11:18.770 --> 00:11:22.030 align:middle line:84%
So nothing risky there;
the only one is trace.

00:11:22.030 --> 00:11:25.720 align:middle line:84%
For port 1617, which
I don't believe

00:11:25.720 --> 00:11:28.280 align:middle line:84%
we discovered earlier on,
which is a good thing,

00:11:28.280 --> 00:11:30.580 align:middle line:90%
it looks like we have Java RMI.

00:11:30.580 --> 00:11:32.800 align:middle line:90%
That's an endpoint.

00:11:32.800 --> 00:11:38.230 align:middle line:84%
Port 3306, we get the
default script that's run

00:11:38.230 --> 00:11:39.770 align:middle line:90%
is mysql-info.

00:11:39.770 --> 00:11:43.900 align:middle line:84%
So this gives us the exact
version, the capabilities,

00:11:43.900 --> 00:11:47.710 align:middle line:84%
as well as the actual salt
and the authentication plugin,

00:11:47.710 --> 00:11:49.870 align:middle line:90%
which is mysql_native_password.

00:11:49.870 --> 00:11:52.610 align:middle line:84%
We then have RDP, which
we already know about.

00:11:52.610 --> 00:11:56.140 align:middle line:84%
And it looks like the
target name or the host name

00:11:56.140 --> 00:11:59.440 align:middle line:84%
is VAGRANT-2008R2, so
we've been able to identify

00:11:59.440 --> 00:12:04.360 align:middle line:84%
that the system is probably
running Windows Server 2008 R2.

00:12:04.360 --> 00:12:07.190 align:middle line:84%
We get the NetBIOS domain
name, the computer name,

00:12:07.190 --> 00:12:09.280 align:middle line:90%
which is pretty much the same.

00:12:09.280 --> 00:12:13.300 align:middle line:84%
On port 3700, which we weren't
able to identify previously,

00:12:13.300 --> 00:12:15.970 align:middle line:84%
we can see we have a
CORBA naming service.

00:12:15.970 --> 00:12:19.660 align:middle line:90%
4848-- that's Oracle GlassFish.

00:12:19.660 --> 00:12:22.460 align:middle line:90%
We also have 5985.

00:12:22.460 --> 00:12:22.960 align:middle line:90%
Hmm.

00:12:22.960 --> 00:12:25.000 align:middle line:84%
Did we actually
access that, or were

00:12:25.000 --> 00:12:26.680 align:middle line:84%
you able to identify
that previously?

00:12:26.680 --> 00:12:27.760 align:middle line:90%
I don't think so.

00:12:27.760 --> 00:12:30.340 align:middle line:84%
So 5985-- let's see
what's running on that,

00:12:30.340 --> 00:12:32.140 align:middle line:90%
because that is inconclusive.

00:12:32.140 --> 00:12:35.590 align:middle line:90%


00:12:35.590 --> 00:12:38.410 align:middle line:84%
5985-- it says the
resource is not found.

00:12:38.410 --> 00:12:39.306 align:middle line:90%
OK, interesting.

00:12:39.306 --> 00:12:40.750 align:middle line:90%
Interesting.

00:12:40.750 --> 00:12:43.180 align:middle line:90%
We also have port 7676.

00:12:43.180 --> 00:12:46.270 align:middle line:84%
It looks like it has the
Java Message Service.

00:12:46.270 --> 00:12:49.060 align:middle line:84%
8080-- we know that's
Oracle GlassFish.

00:12:49.060 --> 00:12:54.340 align:middle line:84%
We also have 8181,
as well as 8484,

00:12:54.340 --> 00:12:56.260 align:middle line:90%
which is running Jetty winstone.

00:12:56.260 --> 00:12:58.600 align:middle line:84%
And it looks like it
has Jenkins installed.

00:12:58.600 --> 00:13:01.510 align:middle line:84%
So 8484-- let's try
and access that.

00:13:01.510 --> 00:13:03.020 align:middle line:90%
That looks interesting.

00:13:03.020 --> 00:13:05.920 align:middle line:90%
So we can say 8484.

00:13:05.920 --> 00:13:10.030 align:middle line:84%
And yep, it has Jenkins running
on that particular port, which

00:13:10.030 --> 00:13:12.170 align:middle line:90%
is very, very interesting.

00:13:12.170 --> 00:13:15.050 align:middle line:84%
Let's go back to the
actual scan here.

00:13:15.050 --> 00:13:20.870 align:middle line:84%
We have another web
server running on 8585.

00:13:20.870 --> 00:13:24.080 align:middle line:84%
And then on 8686,
we have Java RMI.

00:13:24.080 --> 00:13:29.230 align:middle line:90%
So let's try 8585.

00:13:29.230 --> 00:13:33.460 align:middle line:84%
And OK, so we have a WampServer
that's running on port 8585.

00:13:33.460 --> 00:13:36.070 align:middle line:90%
And it looks like we have--

00:13:36.070 --> 00:13:37.630 align:middle line:84%
right over here
under our projects,

00:13:37.630 --> 00:13:41.260 align:middle line:84%
we have WordPress installed, as
well as an uploads directory.

00:13:41.260 --> 00:13:42.280 align:middle line:90%
So we click on that.

00:13:42.280 --> 00:13:44.920 align:middle line:90%
We have nothing within uploads.

00:13:44.920 --> 00:13:49.990 align:middle line:84%
Under WordPress, let's see what
this actually tells us here.

00:13:49.990 --> 00:13:53.190 align:middle line:84%
So it looks like we have a
WordPress installation that's

00:13:53.190 --> 00:13:56.340 align:middle line:84%
running on port 8585
on the WampServer

00:13:56.340 --> 00:13:58.922 align:middle line:90%
under the WordPress directory.

00:13:58.922 --> 00:14:00.630 align:middle line:84%
It looks like it's
still being developed.

00:14:00.630 --> 00:14:02.370 align:middle line:90%
We also have phpmyadmin.

00:14:02.370 --> 00:14:03.137 align:middle line:90%
That's awesome.

00:14:03.137 --> 00:14:05.470 align:middle line:84%
And it tells us we don't have
permission to access this.

00:14:05.470 --> 00:14:08.910 align:middle line:84%
So it looks like external
access is blocked,

00:14:08.910 --> 00:14:13.620 align:middle line:84%
or specific IPs only are
allowed to access phpmyadmin.

00:14:13.620 --> 00:14:17.370 align:middle line:84%
We also have
sqlbuddy, httpd-dav.

00:14:17.370 --> 00:14:20.290 align:middle line:84%
And it looks like we
have webgrind as well.

00:14:20.290 --> 00:14:23.070 align:middle line:84%
But we don't have permission
to access most of them,

00:14:23.070 --> 00:14:24.960 align:middle line:90%
except for WordPress.

00:14:24.960 --> 00:14:27.210 align:middle line:84%
So we have the
Java RMI endpoint.

00:14:27.210 --> 00:14:31.350 align:middle line:84%
And then it looks
like for port 9200

00:14:31.350 --> 00:14:32.940 align:middle line:90%
we have a few other services.

00:14:32.940 --> 00:14:35.010 align:middle line:90%
Port 9300, et cetera, right?

00:14:35.010 --> 00:14:37.230 align:middle line:84%
And the additional
script results

00:14:37.230 --> 00:14:39.000 align:middle line:90%
pertinent to the actual host--

00:14:39.000 --> 00:14:41.280 align:middle line:84%
for example, the
smb-security-mode.

00:14:41.280 --> 00:14:44.460 align:middle line:84%
We can see that message-signing
is disabled, so that's

00:14:44.460 --> 00:14:45.600 align:middle line:90%
quite important.

00:14:45.600 --> 00:14:49.630 align:middle line:84%
Does it tell us the exact
version of SMB that's running?

00:14:49.630 --> 00:14:50.520 align:middle line:90%
I believe it does.

00:14:50.520 --> 00:14:53.580 align:middle line:84%
So it's saying the SMB
security mode is 2.1;

00:14:53.580 --> 00:14:56.310 align:middle line:84%
message signing is
enabled, but not required.

00:14:56.310 --> 00:14:59.040 align:middle line:84%
For OS discovery, you
can see that it tells us

00:14:59.040 --> 00:15:03.510 align:middle line:84%
right over here, Windows Server
2008 R2 Standard Build 7601

00:15:03.510 --> 00:15:04.470 align:middle line:90%
Service Pack 1.

00:15:04.470 --> 00:15:06.780 align:middle line:84%
So that's very, very
important information.

00:15:06.780 --> 00:15:10.050 align:middle line:84%
The computer name, and of
course the NetBIOS computer name

00:15:10.050 --> 00:15:12.540 align:middle line:84%
and workgroup are
all enumerated there.

00:15:12.540 --> 00:15:14.530 align:middle line:84%
So this is very
important information.

00:15:14.530 --> 00:15:18.090 align:middle line:84%
So again, always make sure
to output your scan results

00:15:18.090 --> 00:15:18.750 align:middle line:90%
into a file.

00:15:18.750 --> 00:15:22.380 align:middle line:84%
In this case the output
file is in XML format.

00:15:22.380 --> 00:15:24.180 align:middle line:84%
And the reason I did
that is so that we

00:15:24.180 --> 00:15:28.090 align:middle line:84%
can import it into msfconsole,
or into the Metasploit

00:15:28.090 --> 00:15:28.590 align:middle line:90%
framework.

00:15:28.590 --> 00:15:30.048 align:middle line:84%
Now, before I start
it up, I'm just

00:15:30.048 --> 00:15:32.410 align:middle line:84%
going to start up the
PostgreSQL database service.

00:15:32.410 --> 00:15:34.860 align:middle line:84%
Because in order to
save or import results

00:15:34.860 --> 00:15:37.260 align:middle line:84%
into the Metasploit
framework and have them

00:15:37.260 --> 00:15:41.790 align:middle line:84%
saved or persisted throughout
various sessions or uses,

00:15:41.790 --> 00:15:44.860 align:middle line:84%
we need to start up the
PostgreSQL database service.

00:15:44.860 --> 00:15:47.770 align:middle line:90%
So service postgresql start.

00:15:47.770 --> 00:15:49.570 align:middle line:84%
And that's going to
start it, and then we

00:15:49.570 --> 00:15:50.980 align:middle line:90%
can start up msfconsole.

00:15:50.980 --> 00:15:54.898 align:middle line:90%


00:15:54.898 --> 00:15:57.440 align:middle line:84%
And we're going to give this a
couple of seconds to start up.

00:15:57.440 --> 00:15:59.060 align:middle line:90%
There we are.

00:15:59.060 --> 00:16:01.250 align:middle line:84%
And what we're going to
start off by doing now

00:16:01.250 --> 00:16:03.650 align:middle line:84%
is creating a workspace
for our current assessment.

00:16:03.650 --> 00:16:05.330 align:middle line:90%
So we are targeting one system.

00:16:05.330 --> 00:16:09.210 align:middle line:84%
So we'll create a new workspace
called Win2k8 as well,

00:16:09.210 --> 00:16:12.200 align:middle line:84%
so that we can switch between
engagements and systems

00:16:12.200 --> 00:16:14.805 align:middle line:84%
without actually messing up
the data in the back end.

00:16:14.805 --> 00:16:17.180 align:middle line:84%
Once that is done, you can
see that I'm currently working

00:16:17.180 --> 00:16:19.250 align:middle line:90%
within the Win2k8 workspace.

00:16:19.250 --> 00:16:23.600 align:middle line:84%
I can then use the db_import
command to import the scan

00:16:23.600 --> 00:16:27.605 align:middle line:84%
results, which are stored
under /root, under Desktop.

00:16:27.605 --> 00:16:30.230 align:middle line:84%
And of course, in your case, you
may have changed the directory

00:16:30.230 --> 00:16:31.272 align:middle line:90%
where you've stored them.

00:16:31.272 --> 00:16:34.880 align:middle line:84%
So in my case it's under
Desktop/Win2k8/nmap_10k.

00:16:34.880 --> 00:16:35.630 align:middle line:90%
Hit Enter.

00:16:35.630 --> 00:16:37.940 align:middle line:84%
That's going to import
the scan results.

00:16:37.940 --> 00:16:40.670 align:middle line:84%
And now if I type
in hosts, you can

00:16:40.670 --> 00:16:43.140 align:middle line:84%
see that we have the
host added there.

00:16:43.140 --> 00:16:44.730 align:middle line:90%
So we have the address.

00:16:44.730 --> 00:16:48.800 align:middle line:84%
We also have the name, which
is currently set incorrectly.

00:16:48.800 --> 00:16:52.400 align:middle line:84%
And we can also access
the services performed

00:16:52.400 --> 00:16:56.270 align:middle line:84%
with that default nmap scan
where we scanned, I think,

00:16:56.270 --> 00:16:57.590 align:middle line:90%
10,000 ports.

00:16:57.590 --> 00:16:59.780 align:middle line:84%
Now, if you want
the operating system

00:16:59.780 --> 00:17:02.210 align:middle line:84%
to be highlighted
here accordingly,

00:17:02.210 --> 00:17:05.450 align:middle line:84%
a quick little trick to
do that is to use a--

00:17:05.450 --> 00:17:07.250 align:middle line:84%
and this is in the
context of Windows--

00:17:07.250 --> 00:17:10.560 align:middle line:84%
is to use a module
called smb_version.

00:17:10.560 --> 00:17:11.810 align:middle line:90%
So I'll search for that there.

00:17:11.810 --> 00:17:13.435 align:middle line:84%
You can see that's
an auxiliary module.

00:17:13.435 --> 00:17:17.690 align:middle line:84%
So I'll say use, and I'll use
the auxiliary/scanner/smb/smb

00:17:17.690 --> 00:17:19.310 align:middle line:90%
version module.

00:17:19.310 --> 00:17:22.920 align:middle line:84%
And we can take a look
at the options here.

00:17:22.920 --> 00:17:25.040 align:middle line:84%
And we can set
the RHOSTS option.

00:17:25.040 --> 00:17:26.510 align:middle line:90%
That is the target IP.

00:17:26.510 --> 00:17:30.340 align:middle line:84%
And we'll paste in
the target IP there.

00:17:30.340 --> 00:17:31.460 align:middle line:90%
There we go.

00:17:31.460 --> 00:17:33.990 align:middle line:84%
And we can then
hit run, and this

00:17:33.990 --> 00:17:36.780 align:middle line:84%
will tell us the exact
operating system version.

00:17:36.780 --> 00:17:39.270 align:middle line:84%
So if we now type
in hosts, you can

00:17:39.270 --> 00:17:41.640 align:middle line:84%
see that that is
highlighted correctly there.

00:17:41.640 --> 00:17:45.600 align:middle line:84%
So the name of the
computer is VAGRANT-2008R2.

00:17:45.600 --> 00:17:48.840 align:middle line:84%
The OS name is Windows
Server 2008 R2.

00:17:48.840 --> 00:17:50.190 align:middle line:90%
OS flavor is standard.

00:17:50.190 --> 00:17:51.750 align:middle line:90%
Service pack, service pack 1.

00:17:51.750 --> 00:17:52.580 align:middle line:90%
Purpose, server.

00:17:52.580 --> 00:17:54.840 align:middle line:84%
So this is really where
the Metasploit framework

00:17:54.840 --> 00:17:55.620 align:middle line:90%
starts to shine.

00:17:55.620 --> 00:17:57.690 align:middle line:84%
And I personally
recommend that you

00:17:57.690 --> 00:18:00.660 align:middle line:84%
import all your scan results
into the Metasploit framework.

00:18:00.660 --> 00:18:03.960 align:middle line:84%
Because again, it provides
you with a very, very cool way

00:18:03.960 --> 00:18:06.780 align:middle line:84%
of viewing all the hosts
that you've scanned

00:18:06.780 --> 00:18:09.220 align:middle line:84%
and the services
pertinent to that host.

00:18:09.220 --> 00:18:12.510 align:middle line:84%
Now, as I said, this
only will work well

00:18:12.510 --> 00:18:15.390 align:middle line:84%
if you separate your
engagements or your hosts

00:18:15.390 --> 00:18:16.560 align:middle line:90%
based on the workspace.

00:18:16.560 --> 00:18:18.930 align:middle line:84%
So whenever you're
performing a new pen test,

00:18:18.930 --> 00:18:22.750 align:middle line:84%
just create another workspace
so that the data is separated.

00:18:22.750 --> 00:18:23.250 align:middle line:90%
OK.

00:18:23.250 --> 00:18:26.790 align:middle line:84%
So we have been able to
enumerate the services running

00:18:26.790 --> 00:18:29.190 align:middle line:84%
on the target system
via nmap, and we've

00:18:29.190 --> 00:18:31.920 align:middle line:84%
imported the scan results
into the Metasploit framework.

00:18:31.920 --> 00:18:35.400 align:middle line:84%
We've also identified the
exact operating system version.

00:18:35.400 --> 00:18:37.500 align:middle line:84%
So again, let me just
revisit that again.

00:18:37.500 --> 00:18:41.940 align:middle line:90%
So hosts, and services here.

00:18:41.940 --> 00:18:43.458 align:middle line:90%
There we go.

00:18:43.458 --> 00:18:44.750 align:middle line:90%
And these are all the services.

00:18:44.750 --> 00:18:47.090 align:middle line:84%
And I'll be targeting
quite a few of them.

00:18:47.090 --> 00:18:51.140 align:middle line:84%
And again, the
actual videos that

00:18:51.140 --> 00:18:52.820 align:middle line:84%
will be covering
the exploitation

00:18:52.820 --> 00:18:56.510 align:middle line:84%
phases of this particular
section of the course

00:18:56.510 --> 00:18:59.240 align:middle line:84%
will not involve me exploiting
each of these services.

00:18:59.240 --> 00:19:01.760 align:middle line:84%
As I said, I'll be exploiting
some of the most common ones,

00:19:01.760 --> 00:19:04.190 align:middle line:90%
or the low-hanging fruit.

00:19:04.190 --> 00:19:07.082 align:middle line:84%
So that will give you an idea
of what you should be targeting.

00:19:07.082 --> 00:19:09.290 align:middle line:84%
And then, of course, you
can go through this yourself

00:19:09.290 --> 00:19:13.250 align:middle line:84%
without my help and then use
the videos as references.

00:19:13.250 --> 00:19:16.170 align:middle line:84%
OK, so we've got a
lot of information.

00:19:16.170 --> 00:19:18.930 align:middle line:84%
Now, as I said, this is not
a comprehensive nmap scan.

00:19:18.930 --> 00:19:21.140 align:middle line:84%
So what you can
probably do as well

00:19:21.140 --> 00:19:23.540 align:middle line:84%
is, if I exit from the
Metasploit framework console,

00:19:23.540 --> 00:19:30.990 align:middle line:84%
I can also perform a scan on
the entire TCP port range.

00:19:30.990 --> 00:19:34.760 align:middle line:84%
So instead of just limiting
myself to 10,000 ports,

00:19:34.760 --> 00:19:38.420 align:middle line:84%
I can scan the
entire 65,535 ports.

00:19:38.420 --> 00:19:41.750 align:middle line:90%
So 65535.

00:19:41.750 --> 00:19:44.000 align:middle line:84%
And that will take
a while, trust me.

00:19:44.000 --> 00:19:46.520 align:middle line:84%
And then, of course, I can
output this into its own file

00:19:46.520 --> 00:19:49.970 align:middle line:84%
and say-- instead of
nmap_10k, I can say nmap_all.

00:19:49.970 --> 00:19:52.650 align:middle line:84%
And you can change the
naming to whatever you want.

00:19:52.650 --> 00:19:54.770 align:middle line:84%
However, I will
not be doing that,

00:19:54.770 --> 00:19:56.780 align:middle line:90%
because I really don't need to.

00:19:56.780 --> 00:19:59.360 align:middle line:90%
What I will do is--

00:19:59.360 --> 00:20:01.100 align:middle line:84%
or what I'll actually
show you how to do

00:20:01.100 --> 00:20:04.460 align:middle line:84%
is how to scan UDP ports,
which you should already

00:20:04.460 --> 00:20:05.270 align:middle line:90%
know how to do now.

00:20:05.270 --> 00:20:09.680 align:middle line:84%
So we can say nmap,
and -sU for UDP,

00:20:09.680 --> 00:20:13.010 align:middle line:84%
and then we can say -sV for
service version detection

00:20:13.010 --> 00:20:14.430 align:middle line:90%
and paste in the target IP.

00:20:14.430 --> 00:20:16.730 align:middle line:84%
Now, this system doesn't
have any UDP ports.

00:20:16.730 --> 00:20:19.250 align:middle line:84%
But this is something
that you should also do

00:20:19.250 --> 00:20:21.350 align:middle line:90%
during a standard engagement.

00:20:21.350 --> 00:20:24.450 align:middle line:84%
Be as comprehensive as
possible with your port scans.

00:20:24.450 --> 00:20:27.080 align:middle line:84%
I'm not really following through
with it because, again, I'm

00:20:27.080 --> 00:20:29.390 align:middle line:84%
the one who actually
set up this environment,

00:20:29.390 --> 00:20:32.930 align:middle line:84%
and I know what services
are running on what ports.

00:20:32.930 --> 00:20:35.570 align:middle line:84%
And I'll be focusing
on specific services

00:20:35.570 --> 00:20:37.820 align:middle line:84%
and showing you how a
penetration tester would

00:20:37.820 --> 00:20:39.330 align:middle line:90%
typically go about it.

00:20:39.330 --> 00:20:41.270 align:middle line:84%
With that being
said, that is going

00:20:41.270 --> 00:20:43.160 align:middle line:84%
to conclude the
practical demonstration

00:20:43.160 --> 00:20:44.000 align:middle line:90%
side of this video.

00:20:44.000 --> 00:20:45.680 align:middle line:84%
As I said, you're
free to use any

00:20:45.680 --> 00:20:48.200 align:middle line:84%
of the tools, any of
the port-scanning tools,

00:20:48.200 --> 00:20:50.960 align:middle line:84%
to essentially identify open
ports, the service versions,

00:20:50.960 --> 00:20:51.830 align:middle line:90%
et cetera.

00:20:51.830 --> 00:20:54.170 align:middle line:84%
And yeah, that's going
to conclude this session.

00:20:54.170 --> 00:20:56.960 align:middle line:84%
And we can move on
to the next session

00:20:56.960 --> 00:21:00.630 align:middle line:84%
within this particular
section of the course.

00:21:00.630 --> 00:21:01.130 align:middle line:90%
All right.

00:21:01.130 --> 00:21:05.750 align:middle line:84%
So we have just
completed the first video

00:21:05.750 --> 00:21:07.640 align:middle line:90%
within this particular section.

00:21:07.640 --> 00:21:09.800 align:middle line:84%
We have learned a lot
about the target system

00:21:09.800 --> 00:21:11.610 align:middle line:84%
and what services
are running on it.

00:21:11.610 --> 00:21:13.640 align:middle line:84%
And the reason it
has so many services

00:21:13.640 --> 00:21:16.010 align:middle line:84%
is primarily because
this is something

00:21:16.010 --> 00:21:20.760 align:middle line:84%
that you need to be very
competent at as a penetration

00:21:20.760 --> 00:21:21.260 align:middle line:90%
tester.

00:21:21.260 --> 00:21:23.600 align:middle line:84%
And what I'm referring
to is the ability

00:21:23.600 --> 00:21:26.450 align:middle line:84%
to identify services
that, again, can

00:21:26.450 --> 00:21:28.797 align:middle line:90%
be exploited relatively easily.

00:21:28.797 --> 00:21:30.380 align:middle line:84%
And again, that
doesn't mean that they

00:21:30.380 --> 00:21:31.610 align:middle line:90%
can be exploited easily.

00:21:31.610 --> 00:21:33.800 align:middle line:84%
It just means that you need
to pick your targets as

00:21:33.800 --> 00:21:37.970 align:middle line:84%
efficiently as possible and not
waste your time with dead ends

00:21:37.970 --> 00:21:38.835 align:middle line:90%
or rabbit holes.

00:21:38.835 --> 00:21:40.460 align:middle line:84%
So that's why it has
a lot of services,

00:21:40.460 --> 00:21:42.770 align:middle line:84%
because I want you
to be able to develop

00:21:42.770 --> 00:21:47.240 align:middle line:84%
the skill or the ability to
identify low-hanging fruit

00:21:47.240 --> 00:21:49.760 align:middle line:84%
and find the easiest
way into a system.

00:21:49.760 --> 00:21:52.970 align:middle line:84%
Because efficiency, as you'll
see within your career,

00:21:52.970 --> 00:21:55.760 align:middle line:84%
is very, very important in
the context of a pen test.

00:21:55.760 --> 00:21:59.270 align:middle line:84%
Because time is a factor,
and the actual deadline

00:21:59.270 --> 00:22:00.830 align:middle line:84%
to complete a pen
test is something

00:22:00.830 --> 00:22:04.050 align:middle line:84%
that will be on your mind as
you actually perform a pen test.

00:22:04.050 --> 00:22:07.220 align:middle line:84%
So in the next
video, we'll actually

00:22:07.220 --> 00:22:10.220 align:middle line:84%
begin targeting the first
service, which is FTP,

00:22:10.220 --> 00:22:12.710 align:middle line:84%
and I'll be walking you
through various techniques that

00:22:12.710 --> 00:22:16.130 align:middle line:84%
can be used to gain
access to the FTP server.

00:22:16.130 --> 00:22:18.890 align:middle line:84%
And we'll see what we can
do, and whether or not it

00:22:18.890 --> 00:22:22.500 align:middle line:84%
provides us with access
to the target system.

00:22:22.500 --> 00:22:23.000 align:middle line:90%