WEBVTT

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


00:00:09.780 --> 00:00:12.330 align:middle line:84%
Linux black box
penetration test.

00:00:12.330 --> 00:00:15.060 align:middle line:84%
Welcome to the Linux
exploitation section

00:00:15.060 --> 00:00:18.810 align:middle line:84%
of this course, where we will
be taking a look at a black box

00:00:18.810 --> 00:00:21.910 align:middle line:84%
penetration test
on a Linux system.

00:00:21.910 --> 00:00:24.480 align:middle line:84%
So again, this is going to
follow the same flow that we

00:00:24.480 --> 00:00:26.700 align:middle line:84%
had during the
Windows exploitation,

00:00:26.700 --> 00:00:29.880 align:middle line:84%
where we took a look at a
black box penetration test

00:00:29.880 --> 00:00:31.830 align:middle line:84%
on a Windows system,
or rather how

00:00:31.830 --> 00:00:34.890 align:middle line:84%
to perform a black box
penetration test on a Windows

00:00:34.890 --> 00:00:35.390 align:middle line:90%
system.

00:00:35.390 --> 00:00:37.470 align:middle line:84%
So again, this
particular section

00:00:37.470 --> 00:00:39.850 align:middle line:84%
will follow the same flow
in terms of structure.

00:00:39.850 --> 00:00:42.600 align:middle line:84%
So we're going to be
utilizing one lab environment

00:00:42.600 --> 00:00:44.770 align:middle line:90%
for the entire section.

00:00:44.770 --> 00:00:48.810 align:middle line:84%
So, again, your job as a
junior penetration tester

00:00:48.810 --> 00:00:52.750 align:middle line:84%
is to try and find a way to gain
access to the target system.

00:00:52.750 --> 00:00:55.980 align:middle line:84%
And in this case, it is going
to be a Linux target that

00:00:55.980 --> 00:00:59.010 align:middle line:84%
has been configured to run
various services, most of which

00:00:59.010 --> 00:01:02.970 align:middle line:84%
are vulnerable, some of which
are actually set up to actually

00:01:02.970 --> 00:01:06.330 align:middle line:84%
deceive you as being vulnerable,
but they might not actually

00:01:06.330 --> 00:01:07.170 align:middle line:90%
be so.

00:01:07.170 --> 00:01:09.720 align:middle line:84%
It's an interesting
mix of services

00:01:09.720 --> 00:01:13.140 align:middle line:84%
that, again, will help you
understand how to structure

00:01:13.140 --> 00:01:16.320 align:middle line:84%
and perform a pain
test on a Linux

00:01:16.320 --> 00:01:19.200 align:middle line:84%
system and the various
services that you typically

00:01:19.200 --> 00:01:22.150 align:middle line:84%
expect to have running
on a Linux system.

00:01:22.150 --> 00:01:25.920 align:middle line:84%
So I've already explained what
a black box penetration test

00:01:25.920 --> 00:01:27.910 align:middle line:90%
is during the previous section.

00:01:27.910 --> 00:01:30.270 align:middle line:84%
So again, we're going to
be using the same black box

00:01:30.270 --> 00:01:36.690 align:middle line:84%
methodology, where we'll perform
a host discovery to discover

00:01:36.690 --> 00:01:38.310 align:middle line:90%
the target systems IP address.

00:01:38.310 --> 00:01:40.170 align:middle line:84%
Once we have obtained
that, we will then

00:01:40.170 --> 00:01:42.870 align:middle line:84%
move over to port
scanning and enumeration,

00:01:42.870 --> 00:01:45.420 align:middle line:84%
and we can then take a look
at vulnerability, detection,

00:01:45.420 --> 00:01:48.000 align:middle line:84%
scanning, exploitation,
et cetera.

00:01:48.000 --> 00:01:50.490 align:middle line:84%
We're not going to be taking
a look at post exploitation

00:01:50.490 --> 00:01:51.865 align:middle line:84%
as that is something
that we will

00:01:51.865 --> 00:01:53.800 align:middle line:90%
be covering in its own course.

00:01:53.800 --> 00:01:56.910 align:middle line:84%
So we are primarily
interested in gaining access

00:01:56.910 --> 00:01:59.440 align:middle line:90%
to the Linux target system.

00:01:59.440 --> 00:02:02.883 align:middle line:84%
So in terms of the scenario
and the scope, again,

00:02:02.883 --> 00:02:05.550 align:middle line:84%
we're just going to be using the
same scenario, whereby you have

00:02:05.550 --> 00:02:08.710 align:middle line:84%
just begun your job as a
junior penetration tester

00:02:08.710 --> 00:02:11.039 align:middle line:84%
and have been assigned to
assist in performing a pen

00:02:11.039 --> 00:02:13.180 align:middle line:90%
test on a client's network.

00:02:13.180 --> 00:02:15.570 align:middle line:84%
The pen test lead was very
pleased with your ability

00:02:15.570 --> 00:02:17.610 align:middle line:84%
to gain access to the
Windows Server target

00:02:17.610 --> 00:02:21.330 align:middle line:84%
during our previous engagement
in the previous section

00:02:21.330 --> 00:02:24.690 align:middle line:84%
and has assigned you to perform
a pen test on a Linux server

00:02:24.690 --> 00:02:26.140 align:middle line:90%
on the client's network.

00:02:26.140 --> 00:02:28.770 align:middle line:84%
So your primary
objectives are, you

00:02:28.770 --> 00:02:31.380 align:middle line:84%
need to identify the services
that are running on the target

00:02:31.380 --> 00:02:34.080 align:middle line:84%
system, you then need to
identify vulnerabilities

00:02:34.080 --> 00:02:37.770 align:middle line:84%
within the services, and exploit
these vulnerabilities to gain

00:02:37.770 --> 00:02:41.070 align:middle line:84%
or obtain an initial foothold
on the target system.

00:02:41.070 --> 00:02:42.990 align:middle line:84%
And as a side note,
you are permitted

00:02:42.990 --> 00:02:45.810 align:middle line:84%
to use the Metasploit
framework for exploitation,

00:02:45.810 --> 00:02:49.380 align:middle line:84%
although, again, you can
actually deviate between manual

00:02:49.380 --> 00:02:51.540 align:middle line:90%
and automated exploitation.

00:02:51.540 --> 00:02:54.060 align:middle line:84%
With that being said, as I
said, the lab environment

00:02:54.060 --> 00:02:56.993 align:middle line:84%
is exactly the same in
terms of its structure,

00:02:56.993 --> 00:02:58.410 align:middle line:84%
the target will
be different, it's

00:02:58.410 --> 00:02:59.535 align:middle line:90%
going to be a Linux target.

00:02:59.535 --> 00:03:02.520 align:middle line:84%
But remember that once you
terminate a lab session,

00:03:02.520 --> 00:03:05.190 align:middle line:84%
then, the data that's stored
within that lab session

00:03:05.190 --> 00:03:06.060 align:middle line:90%
will be wiped.

00:03:06.060 --> 00:03:09.180 align:middle line:84%
So if you want to go through
the actual penetration

00:03:09.180 --> 00:03:11.850 align:middle line:84%
test in one go, then
I would recommend

00:03:11.850 --> 00:03:14.580 align:middle line:84%
starting up the lab environment,
trying it out for yourself,

00:03:14.580 --> 00:03:17.370 align:middle line:84%
trying to gain access, and
you can use these videos

00:03:17.370 --> 00:03:20.910 align:middle line:84%
as a reference in regards
to identifying services

00:03:20.910 --> 00:03:22.470 align:middle line:84%
that you can exploit,
and, of course,

00:03:22.470 --> 00:03:23.980 align:middle line:90%
learning how to exploit them.

00:03:23.980 --> 00:03:26.790 align:middle line:84%
So again, if you want to
follow along with the videos,

00:03:26.790 --> 00:03:30.420 align:middle line:84%
please do so, and you can go
through this on a vulnerability

00:03:30.420 --> 00:03:32.040 align:middle line:90%
by vulnerability basis.

00:03:32.040 --> 00:03:33.510 align:middle line:84%
And, of course,
we'll be exploring

00:03:33.510 --> 00:03:35.310 align:middle line:90%
how to target various services.

00:03:35.310 --> 00:03:36.780 align:middle line:84%
Now, I'm not going
to be covering

00:03:36.780 --> 00:03:39.720 align:middle line:84%
the entire gamut of services
that you can exploit

00:03:39.720 --> 00:03:43.290 align:middle line:84%
on the Linux system, and as
we did during the Windows

00:03:43.290 --> 00:03:45.030 align:middle line:84%
exploitation section,
we're only going

00:03:45.030 --> 00:03:49.290 align:middle line:84%
to be focusing on the exploits
that are pretty much the most

00:03:49.290 --> 00:03:53.280 align:middle line:84%
straightforward to exploit, so
your actual low hanging fruit.

00:03:53.280 --> 00:03:55.290 align:middle line:84%
And again, this
will help you become

00:03:55.290 --> 00:03:58.110 align:middle line:84%
efficient in identifying
services that really

00:03:58.110 --> 00:04:01.812 align:middle line:84%
can be exploited as opposed
to prodding or banging

00:04:01.812 --> 00:04:04.020 align:middle line:84%
your head against the wall
with services that are not

00:04:04.020 --> 00:04:06.510 align:middle line:84%
giving you anything
feasible in regards

00:04:06.510 --> 00:04:09.510 align:middle line:90%
to potential exploitation.

00:04:09.510 --> 00:04:11.280 align:middle line:84%
With that being
said, we can actually

00:04:11.280 --> 00:04:12.930 align:middle line:84%
move on to the next
video, where we'll

00:04:12.930 --> 00:04:14.550 align:middle line:84%
be taking a look at
out of a form port

00:04:14.550 --> 00:04:18.329 align:middle line:84%
scanning and enumeration
on the Linux target system

00:04:18.329 --> 00:04:21.870 align:middle line:84%
in order to identify open ports,
as well as the services that

00:04:21.870 --> 00:04:24.240 align:middle line:90%
are running on those open ports.

00:04:24.240 --> 00:04:27.500 align:middle line:84%
So I'll see you
in the next video.

00:04:27.500 --> 00:04:28.000 align:middle line:90%