WEBVTT

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


00:00:03.374 --> 00:00:06.748 align:middle line:90%
[MUSIC PLAYING]

00:00:06.748 --> 00:00:10.140 align:middle line:90%


00:00:10.140 --> 00:00:12.120 align:middle line:84%
Welcome to the
Windows persistence

00:00:12.120 --> 00:00:14.100 align:middle line:90%
section of this course.

00:00:14.100 --> 00:00:17.220 align:middle line:84%
In this section, we're going to
be exploring what persistence

00:00:17.220 --> 00:00:21.750 align:middle line:84%
is and how we can establish
persistence access on a Windows

00:00:21.750 --> 00:00:24.150 align:middle line:84%
system that we have
compromised, all right?

00:00:24.150 --> 00:00:27.120 align:middle line:84%
So we'll be exploring
Windows persistence first,

00:00:27.120 --> 00:00:30.270 align:middle line:84%
and then we'll move on
to Linux persistence.

00:00:30.270 --> 00:00:31.830 align:middle line:84%
Now, before we
actually get started

00:00:31.830 --> 00:00:33.600 align:middle line:84%
with the practical
demonstration,

00:00:33.600 --> 00:00:36.000 align:middle line:84%
let's get an idea of
what persistence is.

00:00:36.000 --> 00:00:37.650 align:middle line:84%
And there are a
few things that I

00:00:37.650 --> 00:00:40.530 align:middle line:84%
want to highlight here because
it's very important, right?

00:00:40.530 --> 00:00:43.260 align:middle line:84%
So persistence
consists of techniques

00:00:43.260 --> 00:00:45.180 align:middle line:84%
that adversaries
use to keep access

00:00:45.180 --> 00:00:48.780 align:middle line:84%
to systems across restarts,
changed credentials,

00:00:48.780 --> 00:00:51.990 align:middle line:84%
and other interruptions that
could cut off their access.

00:00:51.990 --> 00:00:55.710 align:middle line:84%
Techniques used for persistence
include any access, action,

00:00:55.710 --> 00:00:57.990 align:middle line:84%
or configuration
changes that let

00:00:57.990 --> 00:01:00.270 align:middle line:84%
them maintain their
foothold on systems

00:01:00.270 --> 00:01:03.450 align:middle line:84%
such as replacing or
hijacking legitimate code

00:01:03.450 --> 00:01:05.069 align:middle line:90%
or adding startup code.

00:01:05.069 --> 00:01:08.340 align:middle line:84%
This definition was pulled
from the MITRE ATT&CK website.

00:01:08.340 --> 00:01:11.220 align:middle line:84%
And the reason I pulled it is
primarily because it really

00:01:11.220 --> 00:01:14.310 align:middle line:84%
encapsulates everything
about persistence

00:01:14.310 --> 00:01:19.080 align:middle line:84%
into one very well-formatted
paragraph, right?

00:01:19.080 --> 00:01:21.690 align:middle line:84%
So the crux of
what that is saying

00:01:21.690 --> 00:01:25.080 align:middle line:84%
is that once you gain
access to a target system,

00:01:25.080 --> 00:01:28.905 align:middle line:84%
the next logical step is to
perform local enumeration--

00:01:28.905 --> 00:01:30.840 align:middle line:84%
try and identify
as much information

00:01:30.840 --> 00:01:34.680 align:middle line:84%
as you can about the system
that you've just compromised.

00:01:34.680 --> 00:01:37.650 align:middle line:84%
You can then go ahead and
start transferring the files

00:01:37.650 --> 00:01:39.720 align:middle line:90%
that you need to transfer.

00:01:39.720 --> 00:01:42.720 align:middle line:84%
The next logical step would
be to elevate your privileges

00:01:42.720 --> 00:01:45.460 align:middle line:84%
if you obtained a
non-elevated session.

00:01:45.460 --> 00:01:47.400 align:middle line:84%
The reason you need to
elevate your privileges

00:01:47.400 --> 00:01:49.710 align:middle line:84%
before establishing
persistence is primarily

00:01:49.710 --> 00:01:52.440 align:middle line:84%
because persistence
techniques will typically

00:01:52.440 --> 00:01:55.230 align:middle line:84%
require administrative
access in order for them

00:01:55.230 --> 00:01:57.480 align:middle line:90%
to be performed correctly.

00:01:57.480 --> 00:02:01.020 align:middle line:84%
So why is persistence
important or why does it

00:02:01.020 --> 00:02:04.590 align:middle line:84%
feature within the
post-exploitation methodology?

00:02:04.590 --> 00:02:06.720 align:middle line:84%
Well, let's use
an example, right?

00:02:06.720 --> 00:02:08.669 align:middle line:84%
Let's say you're
performing a pen test

00:02:08.669 --> 00:02:11.220 align:middle line:84%
and you gain access
to a target system,

00:02:11.220 --> 00:02:13.230 align:middle line:84%
you're able to elevate
your privileges,

00:02:13.230 --> 00:02:15.420 align:middle line:84%
and you pack it up
for the day, right?

00:02:15.420 --> 00:02:17.580 align:middle line:84%
And the next day
when you actually

00:02:17.580 --> 00:02:19.860 align:middle line:84%
go ahead and try and gain
access to that system,

00:02:19.860 --> 00:02:21.690 align:middle line:90%
you find that that system--

00:02:21.690 --> 00:02:23.970 align:middle line:84%
the vulnerability that you're
exploited on that system

00:02:23.970 --> 00:02:25.848 align:middle line:90%
to gain access has been patched.

00:02:25.848 --> 00:02:28.140 align:middle line:84%
And you think to yourself,
well, how will I gain access

00:02:28.140 --> 00:02:29.580 align:middle line:90%
to this target system now?

00:02:29.580 --> 00:02:31.530 align:middle line:90%
I gained access yesterday.

00:02:31.530 --> 00:02:34.680 align:middle line:84%
Why didn't I set up
a system or mechanism

00:02:34.680 --> 00:02:38.370 align:middle line:84%
of ensuring that I have
persistent access on a target

00:02:38.370 --> 00:02:40.950 align:middle line:84%
system that I
compromised at one point?

00:02:40.950 --> 00:02:43.920 align:middle line:84%
So that's why persistence
is important is primarily

00:02:43.920 --> 00:02:46.470 align:middle line:84%
because once you've
compromised the system,

00:02:46.470 --> 00:02:48.540 align:middle line:84%
you want to make sure
that even if you're

00:02:48.540 --> 00:02:51.870 align:middle line:84%
done with it from the
perspective of a penetration

00:02:51.870 --> 00:02:54.780 align:middle line:84%
tester, that you still have
access to it in the event

00:02:54.780 --> 00:02:56.520 align:middle line:84%
that you ever want
to do something else

00:02:56.520 --> 00:02:58.980 align:middle line:84%
or you want to
exfiltrate some data

00:02:58.980 --> 00:03:01.710 align:middle line:84%
or to perform some
additional tests, right?

00:03:01.710 --> 00:03:04.080 align:middle line:84%
So that's why
persistence is important.

00:03:04.080 --> 00:03:07.230 align:middle line:84%
Now, in the context
of Windows primarily,

00:03:07.230 --> 00:03:11.190 align:middle line:84%
the persistence technique that
you will use or end up using

00:03:11.190 --> 00:03:15.060 align:middle line:84%
will need to be in accordance
with the rules of engagement

00:03:15.060 --> 00:03:17.950 align:middle line:84%
laid out and agreed
upon with the client.

00:03:17.950 --> 00:03:21.150 align:middle line:84%
So if you go back to the
earlier sections of this course,

00:03:21.150 --> 00:03:25.290 align:middle line:84%
I mentioned very clearly that
whenever you're modifying data

00:03:25.290 --> 00:03:27.780 align:middle line:84%
on a target system that
does not belong to you--

00:03:27.780 --> 00:03:29.610 align:middle line:90%
it belongs to the client--

00:03:29.610 --> 00:03:32.100 align:middle line:84%
you need to make that
as clear as possible

00:03:32.100 --> 00:03:33.750 align:middle line:90%
before you begin the pen test.

00:03:33.750 --> 00:03:37.000 align:middle line:84%
You need to actually sit down
with the client and say, OK,

00:03:37.000 --> 00:03:40.710 align:middle line:84%
let's agree upon what we can and
cannot do after we have gained

00:03:40.710 --> 00:03:42.180 align:middle line:90%
access for example.

00:03:42.180 --> 00:03:45.270 align:middle line:84%
And the client will say, OK,
once you've gained access,

00:03:45.270 --> 00:03:48.000 align:middle line:84%
I don't want you
to modify any files

00:03:48.000 --> 00:03:50.910 align:middle line:84%
or I don't want you to
modify the Windows Registry.

00:03:50.910 --> 00:03:53.730 align:middle line:84%
I don't want you to leave any
artifacts on the operating

00:03:53.730 --> 00:03:57.160 align:middle line:84%
system that could be very
difficult to trace and remove,

00:03:57.160 --> 00:03:57.660 align:middle line:90%
right?

00:03:57.660 --> 00:03:58.800 align:middle line:90%
And that's a fair thing.

00:03:58.800 --> 00:04:01.450 align:middle line:84%
That's something that clients
actually request quite a bit.

00:04:01.450 --> 00:04:05.190 align:middle line:84%
So in that event,
you, again, will

00:04:05.190 --> 00:04:08.790 align:middle line:84%
need to decide or choose upon
the correct method or technique

00:04:08.790 --> 00:04:11.880 align:middle line:84%
of persistence that you're
going to use and one that

00:04:11.880 --> 00:04:15.480 align:middle line:84%
fits within or is in compliance
with the rules of engagement

00:04:15.480 --> 00:04:17.980 align:middle line:84%
that you agreed upon
with the client.

00:04:17.980 --> 00:04:22.200 align:middle line:84%
Now, the reason I'm saying
in this phase of this course

00:04:22.200 --> 00:04:23.700 align:middle line:84%
is primarily because
this is where

00:04:23.700 --> 00:04:27.990 align:middle line:84%
that particular statement
or where this really

00:04:27.990 --> 00:04:29.970 align:middle line:84%
comes into play or
why it's so important

00:04:29.970 --> 00:04:33.090 align:middle line:84%
here is primarily because
persistence techniques will

00:04:33.090 --> 00:04:37.680 align:middle line:84%
typically involve modifying
the system in various ways

00:04:37.680 --> 00:04:41.760 align:middle line:84%
from creating a new user or
backdoor user to changing user

00:04:41.760 --> 00:04:45.540 align:middle line:84%
passwords to creating services
to modifying the Windows

00:04:45.540 --> 00:04:46.320 align:middle line:90%
Registry.

00:04:46.320 --> 00:04:50.940 align:middle line:84%
Persistence, even if you
actually take a look at it

00:04:50.940 --> 00:04:54.090 align:middle line:84%
from the entire penetration
testing lifecycle,

00:04:54.090 --> 00:04:58.785 align:middle line:84%
persistence will typically leave
the most amount of artifacts

00:04:58.785 --> 00:05:00.870 align:middle line:84%
after you've performed
a persistence technique.

00:05:00.870 --> 00:05:05.400 align:middle line:84%
And furthermore or in addition
to that, if I, for example, try

00:05:05.400 --> 00:05:07.500 align:middle line:84%
and establish persistence
on a Windows system

00:05:07.500 --> 00:05:09.570 align:middle line:84%
through the Windows
Registry, that

00:05:09.570 --> 00:05:11.880 align:middle line:84%
can be very difficult
to actually trace

00:05:11.880 --> 00:05:15.060 align:middle line:84%
and then later on
removed from the system

00:05:15.060 --> 00:05:16.630 align:middle line:90%
that you've just compromised.

00:05:16.630 --> 00:05:18.810 align:middle line:84%
So do take that
into consideration.

00:05:18.810 --> 00:05:21.810 align:middle line:84%
If the rules of engagement that
you agree upon with a client

00:05:21.810 --> 00:05:25.050 align:middle line:84%
state that you cannot make any
changes to the system and you

00:05:25.050 --> 00:05:27.420 align:middle line:84%
cannot create any
users, then, again,

00:05:27.420 --> 00:05:29.740 align:middle line:84%
that's something that
you want to keep in mind.

00:05:29.740 --> 00:05:33.220 align:middle line:84%
Probably, the best option then
is to, essentially, perform

00:05:33.220 --> 00:05:36.970 align:middle line:84%
a hash dump and obtain the
hashes of the user accounts

00:05:36.970 --> 00:05:39.490 align:middle line:84%
on that system so that you
can always authenticate

00:05:39.490 --> 00:05:44.300 align:middle line:84%
legitimately back on that target
system that you've compromised.

00:05:44.300 --> 00:05:46.250 align:middle line:90%
So do keep that in mind.

00:05:46.250 --> 00:05:48.550 align:middle line:84%
Now, as I said, there is tons
of persistence techniques

00:05:48.550 --> 00:05:50.230 align:middle line:90%
for both Windows and Linux.

00:05:50.230 --> 00:05:53.350 align:middle line:84%
And we're going to be exploring
two techniques in this section.

00:05:53.350 --> 00:05:55.420 align:middle line:84%
And before we
actually get started

00:05:55.420 --> 00:05:57.250 align:middle line:84%
with the practical
demonstration,

00:05:57.250 --> 00:05:59.710 align:middle line:84%
I want to highlight the
MITRE ATT&CK website

00:05:59.710 --> 00:06:01.990 align:middle line:84%
and just show you the
various types of techniques

00:06:01.990 --> 00:06:05.660 align:middle line:84%
that you can perform in terms
of establishing persistence.

00:06:05.660 --> 00:06:09.290 align:middle line:84%
So let me just switch over
to my browser really quickly.

00:06:09.290 --> 00:06:10.870 align:middle line:84%
All right, so I'm
back on my browser,

00:06:10.870 --> 00:06:13.570 align:middle line:84%
and I'm currently on the
MITRE ATT&CK website.

00:06:13.570 --> 00:06:16.690 align:middle line:84%
If you're not familiar with
the MITRE ATT&CK framework

00:06:16.690 --> 00:06:18.940 align:middle line:84%
as the description
states right over here,

00:06:18.940 --> 00:06:21.850 align:middle line:84%
MITRE ATT&CK is a
globally-accessible knowledge

00:06:21.850 --> 00:06:24.520 align:middle line:84%
base of adversary
tactics and techniques

00:06:24.520 --> 00:06:26.890 align:middle line:84%
based on real-world
observations.

00:06:26.890 --> 00:06:28.900 align:middle line:84%
The ATT&CK knowledge
base is used

00:06:28.900 --> 00:06:31.780 align:middle line:84%
as a foundation for the
development of specific threat

00:06:31.780 --> 00:06:34.570 align:middle line:84%
models and methodologies
in the private sector,

00:06:34.570 --> 00:06:37.480 align:middle line:84%
in government, and in
the cybersecurity product

00:06:37.480 --> 00:06:39.340 align:middle line:90%
and service community.

00:06:39.340 --> 00:06:42.130 align:middle line:84%
All right, so the
mission of MITRE ATT&CK

00:06:42.130 --> 00:06:45.040 align:middle line:84%
is essentially to solve
problems for a safer world

00:06:45.040 --> 00:06:47.200 align:middle line:84%
by bringing communities
together to develop

00:06:47.200 --> 00:06:49.300 align:middle line:90%
more effective cybersecurity.

00:06:49.300 --> 00:06:52.190 align:middle line:84%
Now, what this means is
that in the case of MITRE

00:06:52.190 --> 00:06:54.790 align:middle line:84%
ATT&CK for enterprise
is it actually

00:06:54.790 --> 00:07:00.160 align:middle line:84%
lists out the various phases
that adversaries or APT teams

00:07:00.160 --> 00:07:04.270 align:middle line:84%
will typically utilize when
they're trying to compromise

00:07:04.270 --> 00:07:06.610 align:middle line:90%
a company or a target network.

00:07:06.610 --> 00:07:09.400 align:middle line:84%
So they start off with
reconnaissance, resource

00:07:09.400 --> 00:07:12.520 align:middle line:84%
development, initial access--
which is exploitation.

00:07:12.520 --> 00:07:15.350 align:middle line:84%
You then have execution
and persistence.

00:07:15.350 --> 00:07:18.310 align:middle line:84%
So again, this can also be
used by penetration testers.

00:07:18.310 --> 00:07:20.980 align:middle line:84%
And the only reason I'm
using it is primarily

00:07:20.980 --> 00:07:24.010 align:middle line:84%
because it lists out pretty
much all of the techniques

00:07:24.010 --> 00:07:24.780 align:middle line:90%
that you can use.

00:07:24.780 --> 00:07:27.460 align:middle line:84%
So if I click on
Persistence here,

00:07:27.460 --> 00:07:29.920 align:middle line:84%
you can see that this is
the definition that I pulled

00:07:29.920 --> 00:07:31.760 align:middle line:90%
from the MITRE ATT&CK website.

00:07:31.760 --> 00:07:34.120 align:middle line:84%
And then it lists out the
various techniques, right?

00:07:34.120 --> 00:07:35.770 align:middle line:84%
So these are the
techniques that you

00:07:35.770 --> 00:07:38.920 align:middle line:84%
can use to essentially
establish persistence.

00:07:38.920 --> 00:07:43.066 align:middle line:84%
For example, we have
account manipulation.

00:07:43.066 --> 00:07:47.500 align:middle line:84%
What falls under account
manipulation is, of course,

00:07:47.500 --> 00:07:50.530 align:middle line:84%
you can modify user account
password, et cetera.

00:07:50.530 --> 00:07:53.830 align:middle line:84%
So it gives you an idea of
what that particular tactic

00:07:53.830 --> 00:07:55.540 align:middle line:90%
or technique is used for.

00:07:55.540 --> 00:07:58.360 align:middle line:84%
So adversaries may manipulate
accounts to maintain access

00:07:58.360 --> 00:07:59.620 align:middle line:90%
to victim systems.

00:07:59.620 --> 00:08:02.140 align:middle line:84%
Account manipulation may
consist of any action that

00:08:02.140 --> 00:08:04.690 align:middle line:84%
preserves adversary
access to a compromised

00:08:04.690 --> 00:08:07.180 align:middle line:84%
account, such as modifying
credentials or permission

00:08:07.180 --> 00:08:08.080 align:middle line:90%
groups.

00:08:08.080 --> 00:08:09.820 align:middle line:84%
We then have a few
other techniques

00:08:09.820 --> 00:08:14.330 align:middle line:84%
here that we can also
explore like, for example,

00:08:14.330 --> 00:08:16.110 align:middle line:84%
creating a logon
script on Windows.

00:08:16.110 --> 00:08:18.190 align:middle line:84%
So adversaries may use
Windows logon scripts

00:08:18.190 --> 00:08:22.090 align:middle line:84%
to automatically executed
at log on essentially

00:08:22.090 --> 00:08:23.620 align:middle line:90%
to establish persistence.

00:08:23.620 --> 00:08:24.610 align:middle line:90%
So that's another one.

00:08:24.610 --> 00:08:27.250 align:middle line:84%
One of the ones that we
are going to be utilizing

00:08:27.250 --> 00:08:29.470 align:middle line:84%
is the create account
technique, which

00:08:29.470 --> 00:08:32.169 align:middle line:84%
we will be exploring in the
second video in this section,

00:08:32.169 --> 00:08:34.909 align:middle line:84%
where we'll be creating an
account on the target Windows

00:08:34.909 --> 00:08:37.990 align:middle line:84%
system and then utilizing
it to essentially ensure

00:08:37.990 --> 00:08:42.260 align:middle line:84%
that we have persistent
access on that target system.

00:08:42.260 --> 00:08:44.440 align:middle line:84%
So I do recommend that
you go through this

00:08:44.440 --> 00:08:48.430 align:middle line:84%
if you want to learn more
about persistence techniques

00:08:48.430 --> 00:08:50.980 align:middle line:84%
as well as privilege
escalation, exploitation

00:08:50.980 --> 00:08:53.710 align:middle line:84%
techniques, credential
access, so on and so forth.

00:08:53.710 --> 00:08:56.740 align:middle line:90%
The website is attack.mitre.org

00:08:56.740 --> 00:08:59.980 align:middle line:84%
Now, that we have an idea
of the various techniques

00:08:59.980 --> 00:09:01.900 align:middle line:84%
that we can use to
establish persistence

00:09:01.900 --> 00:09:04.990 align:middle line:84%
and what persistence is and
the important considerations

00:09:04.990 --> 00:09:06.280 align:middle line:90%
to take in--

00:09:06.280 --> 00:09:08.750 align:middle line:84%
the important things that
you need to be aware of,

00:09:08.750 --> 00:09:11.200 align:middle line:84%
we can actually move on to
the practical demonstration

00:09:11.200 --> 00:09:13.900 align:middle line:90%
side of this video.

00:09:13.900 --> 00:09:17.440 align:middle line:84%
So this video has a lab
environment attached to it.

00:09:17.440 --> 00:09:19.200 align:middle line:84%
And of course, you
can start it up,

00:09:19.200 --> 00:09:21.250 align:middle line:84%
and you can follow along
with the techniques.

00:09:21.250 --> 00:09:23.470 align:middle line:84%
So the flow is going
to be as follows.

00:09:23.470 --> 00:09:26.208 align:middle line:84%
We're going to gain
access to the--

00:09:26.208 --> 00:09:28.500 align:middle line:84%
we're going to essentially
exploit a vulnerable service

00:09:28.500 --> 00:09:29.765 align:middle line:90%
on the target system.

00:09:29.765 --> 00:09:31.890 align:middle line:84%
Once we've have gained
access to the target system,

00:09:31.890 --> 00:09:33.810 align:middle line:84%
we can then establish
persistence.

00:09:33.810 --> 00:09:35.580 align:middle line:84%
If we need to elevate
our privileges,

00:09:35.580 --> 00:09:38.517 align:middle line:84%
we will do that before we
actually establish persistence.

00:09:38.517 --> 00:09:40.350 align:middle line:84%
And this is going to
be done through the use

00:09:40.350 --> 00:09:43.200 align:middle line:84%
of the Metasploit framework
as this is the easiest

00:09:43.200 --> 00:09:45.510 align:middle line:84%
way to essentially
showcase and demonstrate

00:09:45.510 --> 00:09:48.450 align:middle line:84%
how to set up persistence,
especially on Windows.

00:09:48.450 --> 00:09:50.850 align:middle line:84%
So I'll see you in
the lab environment.

00:09:50.850 --> 00:09:53.450 align:middle line:90%


00:09:53.450 --> 00:09:55.700 align:middle line:84%
All right, so I'm back
within the lab environment.

00:09:55.700 --> 00:09:58.500 align:middle line:84%
And you will be provided
with the target IP address.

00:09:58.500 --> 00:10:00.890 align:middle line:84%
Of course, in your case,
it's going to be different.

00:10:00.890 --> 00:10:03.030 align:middle line:84%
But all you need to
do is just copy it.

00:10:03.030 --> 00:10:05.313 align:middle line:84%
So the first step, of
course, is to identify

00:10:05.313 --> 00:10:07.730 align:middle line:84%
the vulnerable service that's
running on the target system

00:10:07.730 --> 00:10:08.900 align:middle line:90%
that we can exploit.

00:10:08.900 --> 00:10:10.850 align:middle line:84%
So I'll just open up
a terminal, and I'll

00:10:10.850 --> 00:10:12.860 align:middle line:84%
perform a quick service
version detection

00:10:12.860 --> 00:10:15.020 align:middle line:90%
scan on the target system.

00:10:15.020 --> 00:10:19.490 align:middle line:84%
And we can also, again,
specify additional options

00:10:19.490 --> 00:10:20.460 align:middle line:90%
regarding the ports.

00:10:20.460 --> 00:10:22.430 align:middle line:84%
But in this case,
I'll just hit Enter.

00:10:22.430 --> 00:10:24.080 align:middle line:84%
And I'll give this
a couple of seconds

00:10:24.080 --> 00:10:26.780 align:middle line:84%
to a couple of minutes given
the fact that this is a Windows

00:10:26.780 --> 00:10:29.180 align:middle line:90%
system.

00:10:29.180 --> 00:10:31.250 align:middle line:84%
All right, the Nmap
scan is complete.

00:10:31.250 --> 00:10:34.160 align:middle line:84%
And you can see on port 80
we have a web server running.

00:10:34.160 --> 00:10:38.090 align:middle line:84%
And the web server is the
all familiar HTTP file server

00:10:38.090 --> 00:10:40.610 align:middle line:84%
version 2.3
developed by Rejetto.

00:10:40.610 --> 00:10:42.980 align:middle line:84%
So by this point,
you should know

00:10:42.980 --> 00:10:45.530 align:middle line:84%
that there is a Metasploit
framework exploit module that

00:10:45.530 --> 00:10:47.960 align:middle line:84%
can exploit or that
can be used to exploit

00:10:47.960 --> 00:10:50.960 align:middle line:84%
this specific version
of the HTTP file server.

00:10:50.960 --> 00:10:54.130 align:middle line:84%
So I'll open up
MSF console here.

00:10:54.130 --> 00:10:55.960 align:middle line:84%
And we'll give that
a couple of seconds

00:10:55.960 --> 00:11:01.595 align:middle line:84%
to start up after which we can
search for the Rejetto module.

00:11:01.595 --> 00:11:04.490 align:middle line:90%


00:11:04.490 --> 00:11:08.290 align:middle line:84%
There we are so it's
say search and Rejetto.

00:11:08.290 --> 00:11:11.030 align:middle line:84%
And we are using this
exploit module here.

00:11:11.030 --> 00:11:12.730 align:middle line:90%
So we'll say use zero.

00:11:12.730 --> 00:11:15.940 align:middle line:84%
And this will provide us
with a Meterpreter session.

00:11:15.940 --> 00:11:18.850 align:middle line:84%
So you can see the default is
Windows Meterpreter reverse

00:11:18.850 --> 00:11:19.650 align:middle line:90%
TCP.

00:11:19.650 --> 00:11:22.120 align:middle line:84%
That's a 32-bit
Meterpreter payload.

00:11:22.120 --> 00:11:24.040 align:middle line:84%
You can modify this
if you want to.

00:11:24.040 --> 00:11:27.020 align:middle line:84%
However, do keep in
mind that at this point,

00:11:27.020 --> 00:11:29.500 align:middle line:84%
we still don't know what
the target operating system

00:11:29.500 --> 00:11:30.580 align:middle line:90%
architecture is.

00:11:30.580 --> 00:11:34.900 align:middle line:84%
So it's always safe to utilize
the 32-bit Meterpreter payload.

00:11:34.900 --> 00:11:37.390 align:middle line:84%
If we show the options
for the module,

00:11:37.390 --> 00:11:39.830 align:middle line:84%
you can see that we need to
set up the payload option.

00:11:39.830 --> 00:11:41.410 align:middle line:90%
So this is your Kali Linux IP.

00:11:41.410 --> 00:11:43.420 align:middle line:84%
You can set that by
saying set L host

00:11:43.420 --> 00:11:45.340 align:middle line:84%
and then specifying
your Kali IP.

00:11:45.340 --> 00:11:49.030 align:middle line:84%
The L port is set to the
default, which is 4444.

00:11:49.030 --> 00:11:50.920 align:middle line:84%
Make sure that this
is not in conflict

00:11:50.920 --> 00:11:54.520 align:middle line:84%
with any other reverse handlers
you have running or listeners.

00:11:54.520 --> 00:11:56.830 align:middle line:84%
And we need to set
up the target IP.

00:11:56.830 --> 00:11:59.590 align:middle line:84%
So I'm just going to
copy the target IP here.

00:11:59.590 --> 00:12:02.780 align:middle line:90%
And we'll say set Rhosts.

00:12:02.780 --> 00:12:04.010 align:middle line:90%
Paste that in there.

00:12:04.010 --> 00:12:07.090 align:middle line:90%
And I can type in exploit.

00:12:07.090 --> 00:12:10.750 align:middle line:84%
All right, this should provide
us with a Meterpreter session.

00:12:10.750 --> 00:12:11.560 align:middle line:90%
There we go.

00:12:11.560 --> 00:12:16.550 align:middle line:90%


00:12:16.550 --> 00:12:17.240 align:middle line:90%
Fantastic.

00:12:17.240 --> 00:12:20.090 align:middle line:84%
OK, so let's perform
some basic enumeration.

00:12:20.090 --> 00:12:22.100 align:middle line:90%
So I'll say sysinfo.

00:12:22.100 --> 00:12:26.240 align:middle line:84%
We can see the target system is
running Windows Server 2012 R2.

00:12:26.240 --> 00:12:28.670 align:middle line:84%
It is a 64-bit
version of Windows,

00:12:28.670 --> 00:12:32.180 align:middle line:84%
and we have a 32-bit
Meterpreter session.

00:12:32.180 --> 00:12:35.480 align:middle line:84%
We can also identify our
current user and the privileges

00:12:35.480 --> 00:12:38.930 align:middle line:84%
associated with that user
by typing and get user ID.

00:12:38.930 --> 00:12:40.940 align:middle line:84%
We are currently the
administrator user,

00:12:40.940 --> 00:12:42.180 align:middle line:90%
which is fantastic.

00:12:42.180 --> 00:12:44.970 align:middle line:84%
It means that we do not need
to elevate our privileges

00:12:44.970 --> 00:12:46.070 align:middle line:90%
and we can move--

00:12:46.070 --> 00:12:48.450 align:middle line:84%
we can essentially move
on to the next phase,

00:12:48.450 --> 00:12:51.620 align:middle line:84%
which is essentially
establishing persistence.

00:12:51.620 --> 00:12:54.390 align:middle line:84%
All right, now, as I
said, in this video,

00:12:54.390 --> 00:12:55.850 align:middle line:84%
we're going to be
focusing on how

00:12:55.850 --> 00:12:59.880 align:middle line:84%
to establish persistence to a
Windows persistence service,

00:12:59.880 --> 00:13:00.380 align:middle line:90%
right?

00:13:00.380 --> 00:13:01.940 align:middle line:84%
So we're going to
be exploring how

00:13:01.940 --> 00:13:06.590 align:middle line:84%
to set up a service that will
connect back to our Metasploit

00:13:06.590 --> 00:13:10.100 align:middle line:84%
framework multihandler
listener and provide us

00:13:10.100 --> 00:13:13.200 align:middle line:84%
with persistent access
whenever we want.

00:13:13.200 --> 00:13:17.070 align:middle line:84%
So in order to run
that particular module,

00:13:17.070 --> 00:13:19.670 align:middle line:84%
you do need to have
elevated privileges, right?

00:13:19.670 --> 00:13:21.860 align:middle line:84%
So let's put this
in the background,

00:13:21.860 --> 00:13:25.297 align:middle line:84%
and we're going to
search for the module.

00:13:25.297 --> 00:13:26.880 align:middle line:84%
All right, so I'm
going to say search.

00:13:26.880 --> 00:13:29.970 align:middle line:84%
And we're just going
to say persistence,

00:13:29.970 --> 00:13:31.320 align:middle line:90%
and we can say service.

00:13:31.320 --> 00:13:32.790 align:middle line:90%
And let's see if that comes up.

00:13:32.790 --> 00:13:33.810 align:middle line:90%
There's the one there.

00:13:33.810 --> 00:13:38.410 align:middle line:84%
This is a
postexploitation module.

00:13:38.410 --> 00:13:40.990 align:middle line:84%
However, it is categorized
as an exploit module,

00:13:40.990 --> 00:13:44.220 align:middle line:90%
so I'll say use zero, right?

00:13:44.220 --> 00:13:47.190 align:middle line:84%
And the default payload
is set to the Windows--

00:13:47.190 --> 00:13:49.450 align:middle line:84%
to the 32-bit
Meterpreter payload,

00:13:49.450 --> 00:13:51.600 align:middle line:84%
which is perfectly
fine as we can always

00:13:51.600 --> 00:13:55.020 align:middle line:84%
migrate our process
into a different process

00:13:55.020 --> 00:13:58.290 align:middle line:84%
that is actually
a 64-bit process.

00:13:58.290 --> 00:14:01.080 align:middle line:84%
So the way this module
works is that it

00:14:01.080 --> 00:14:04.620 align:middle line:84%
will generate and upload
an executable to the target

00:14:04.620 --> 00:14:05.280 align:middle line:90%
system.

00:14:05.280 --> 00:14:08.250 align:middle line:84%
It will then make it a
persistent service, right?

00:14:08.250 --> 00:14:10.020 align:middle line:84%
And you've already
learned about services.

00:14:10.020 --> 00:14:13.080 align:middle line:84%
They run in the
background as I already

00:14:13.080 --> 00:14:15.570 align:middle line:84%
went over that during the
Windows local enumeration

00:14:15.570 --> 00:14:16.230 align:middle line:90%
section.

00:14:16.230 --> 00:14:19.110 align:middle line:84%
This module will then
create a new service

00:14:19.110 --> 00:14:21.240 align:middle line:84%
which will start
the payload whenever

00:14:21.240 --> 00:14:22.650 align:middle line:90%
the service is running.

00:14:22.650 --> 00:14:26.040 align:middle line:84%
And you do require
administrative or system

00:14:26.040 --> 00:14:30.240 align:middle line:84%
privileges in order to utilize
this particular module here.

00:14:30.240 --> 00:14:33.140 align:middle line:84%
So if I show the
options, you can

00:14:33.140 --> 00:14:34.950 align:middle line:84%
see that there are
quite a few options.

00:14:34.950 --> 00:14:36.860 align:middle line:84%
And you might be a
little bit confused

00:14:36.860 --> 00:14:40.580 align:middle line:84%
here because if this is
so-called postexploitation

00:14:40.580 --> 00:14:43.200 align:middle line:84%
module, why do we have
the payload option here?

00:14:43.200 --> 00:14:46.400 align:middle line:84%
Well, remember, the way
this module works is it

00:14:46.400 --> 00:14:49.970 align:middle line:84%
generates a payload
with MSF Venom.

00:14:49.970 --> 00:14:53.000 align:middle line:84%
And in this case, it's going
to be the 32-bit Meterpreter

00:14:53.000 --> 00:14:56.450 align:middle line:84%
payload, so that means you
need to specify a different L

00:14:56.450 --> 00:14:59.150 align:middle line:84%
port here than the one
you're currently using.

00:14:59.150 --> 00:15:01.490 align:middle line:84%
Or you can keep the
same L port, however,

00:15:01.490 --> 00:15:04.370 align:middle line:84%
you then need to terminate
your previous session in order

00:15:04.370 --> 00:15:05.610 align:middle line:90%
to see if this works.

00:15:05.610 --> 00:15:11.290 align:middle line:84%
So in my case, I'll change
the L port to 4433, OK?

00:15:11.290 --> 00:15:14.155 align:middle line:84%
We then need to set the
session, which is required.

00:15:14.155 --> 00:15:15.280 align:middle line:90%
So let's do that right now.

00:15:15.280 --> 00:15:19.710 align:middle line:84%
So if I list out my
sessions, set session one.

00:15:19.710 --> 00:15:21.840 align:middle line:84%
OK, and if we show
the options again--

00:15:21.840 --> 00:15:23.320 align:middle line:84%
I'm going to explain
a few things.

00:15:23.320 --> 00:15:27.720 align:middle line:84%
So this module will generate
a payload with MSV Venom.

00:15:27.720 --> 00:15:31.020 align:middle line:84%
This payload will then
be essentially uploaded

00:15:31.020 --> 00:15:32.460 align:middle line:90%
to the target system.

00:15:32.460 --> 00:15:35.860 align:middle line:84%
This module will then make
it a persistent service.

00:15:35.860 --> 00:15:37.920 align:middle line:84%
So it'll create a new
service, which will then

00:15:37.920 --> 00:15:40.540 align:middle line:84%
start the payload
that was generated

00:15:40.540 --> 00:15:42.270 align:middle line:84%
and upload it to
the target system

00:15:42.270 --> 00:15:44.160 align:middle line:84%
whenever that
service is running.

00:15:44.160 --> 00:15:45.720 align:middle line:84%
And in order to
do this, in order

00:15:45.720 --> 00:15:47.580 align:middle line:84%
to create a new
service on Windows,

00:15:47.580 --> 00:15:52.170 align:middle line:84%
you require an elevated session
or elevated privileges, OK?

00:15:52.170 --> 00:15:54.970 align:middle line:84%
And there are a few other
options that you can customize.

00:15:54.970 --> 00:15:58.090 align:middle line:84%
So for example, the
remote victim name.

00:15:58.090 --> 00:16:01.650 align:middle line:84%
You can also change the
remote victim exe path to run.

00:16:01.650 --> 00:16:03.300 align:middle line:84%
So it's going to use
the temp directory

00:16:03.300 --> 00:16:04.980 align:middle line:90%
as a default, which is good.

00:16:04.980 --> 00:16:07.740 align:middle line:84%
The retry time that the
shell connect failed.

00:16:07.740 --> 00:16:10.770 align:middle line:90%
So again, the duration as to--

00:16:10.770 --> 00:16:14.370 align:middle line:84%
this is used to specify the
duration for essentially

00:16:14.370 --> 00:16:15.900 align:middle line:90%
retrying the connection.

00:16:15.900 --> 00:16:19.320 align:middle line:84%
So after every five seconds,
the persistent service

00:16:19.320 --> 00:16:21.990 align:middle line:84%
will execute the payload,
which will then try and connect

00:16:21.990 --> 00:16:24.910 align:middle line:84%
to the handler that
we will set up.

00:16:24.910 --> 00:16:26.410 align:middle line:84%
And then, of course,
you can specify

00:16:26.410 --> 00:16:28.250 align:middle line:90%
the unique name of the service.

00:16:28.250 --> 00:16:30.040 align:middle line:84%
This is a fantastic
feature as it

00:16:30.040 --> 00:16:33.820 align:middle line:84%
allows you to create a service
that is not easily identifiable

00:16:33.820 --> 00:16:37.940 align:middle line:84%
by an administrator
on the target system.

00:16:37.940 --> 00:16:39.670 align:middle line:84%
So you can pretty
much give it a name

00:16:39.670 --> 00:16:42.280 align:middle line:84%
that is associated with
one of the Windows services

00:16:42.280 --> 00:16:44.020 align:middle line:90%
to make sure that it blends in.

00:16:44.020 --> 00:16:46.930 align:middle line:84%
If you don't specify
that, then a random string

00:16:46.930 --> 00:16:48.280 align:middle line:90%
is going to be used.

00:16:48.280 --> 00:16:50.320 align:middle line:84%
In this case, we'll
leave them as is,

00:16:50.320 --> 00:16:51.805 align:middle line:90%
and we can just type in exploit.

00:16:51.805 --> 00:16:54.530 align:middle line:90%


00:16:54.530 --> 00:16:58.020 align:middle line:84%
Once we exploit, you can see
a few things happening here,

00:16:58.020 --> 00:16:58.520 align:middle line:90%
all right?

00:16:58.520 --> 00:17:01.310 align:middle line:84%
So it'll stop the reverse
TCP handler, which is fine.

00:17:01.310 --> 00:17:02.730 align:middle line:90%
That's perfectly fine.

00:17:02.730 --> 00:17:05.119 align:middle line:84%
It's going to run the module
against the target system.

00:17:05.119 --> 00:17:08.480 align:middle line:84%
You can see that the Meterpreter
service executable was written

00:17:08.480 --> 00:17:11.720 align:middle line:84%
to the following
directory-- so C users admin

00:17:11.720 --> 00:17:15.450 align:middle line:84%
appdata local temp, and this
is the name of the executable.

00:17:15.450 --> 00:17:17.900 align:middle line:84%
So this particular
persistence technique

00:17:17.900 --> 00:17:21.349 align:middle line:84%
has created an artifact that
you need to actually note down

00:17:21.349 --> 00:17:23.329 align:middle line:84%
because after the
penetration test,

00:17:23.329 --> 00:17:28.220 align:middle line:84%
you actually need to be able
to delete this as, again, it

00:17:28.220 --> 00:17:29.990 align:middle line:84%
is going to be
stored on the system.

00:17:29.990 --> 00:17:32.180 align:middle line:90%
And as per the rules of--

00:17:32.180 --> 00:17:35.060 align:middle line:84%
the actual rules
of engagement, you

00:17:35.060 --> 00:17:37.100 align:middle line:84%
need to be aware of
all of this information

00:17:37.100 --> 00:17:39.590 align:middle line:84%
and you need to keep up with
all of the changes you're

00:17:39.590 --> 00:17:41.180 align:middle line:90%
making to the target system.

00:17:41.180 --> 00:17:44.070 align:middle line:84%
It'll also tell you the name
of the service that it created.

00:17:44.070 --> 00:17:45.740 align:middle line:84%
So again, this is
a random string.

00:17:45.740 --> 00:17:50.300 align:middle line:84%
And it will then receive
a connection, primarily

00:17:50.300 --> 00:17:52.640 align:middle line:84%
because the persistent
service is running.

00:17:52.640 --> 00:17:55.400 align:middle line:84%
And the service, after
every five seconds,

00:17:55.400 --> 00:17:58.820 align:middle line:84%
executes the payload which
consequently connects back

00:17:58.820 --> 00:18:00.440 align:middle line:90%
to the actual listener.

00:18:00.440 --> 00:18:03.050 align:middle line:84%
That is why we obtain
an Meterpreter session

00:18:03.050 --> 00:18:04.520 align:middle line:90%
almost immediately.

00:18:04.520 --> 00:18:08.750 align:middle line:84%
So we have essentially
established persistent access.

00:18:08.750 --> 00:18:12.170 align:middle line:84%
Now, they also provide you
with a clean up Meterpreter

00:18:12.170 --> 00:18:16.100 align:middle line:84%
RC that's stored under
the following path here.

00:18:16.100 --> 00:18:20.580 align:middle line:84%
This can be used to clean up all
the actual artifacts left over,

00:18:20.580 --> 00:18:22.730 align:middle line:84%
which is extremely
useful as you don't need

00:18:22.730 --> 00:18:24.200 align:middle line:90%
to go through this manually.

00:18:24.200 --> 00:18:26.360 align:middle line:84%
If you're not familiar
with Metasploit resource,

00:18:26.360 --> 00:18:28.970 align:middle line:84%
scripts then you can check out
the Metasploit framework course

00:18:28.970 --> 00:18:31.190 align:middle line:84%
that covers how to use
them and how they can

00:18:31.190 --> 00:18:33.350 align:middle line:90%
be executed almost immediately.

00:18:33.350 --> 00:18:36.380 align:middle line:84%
So with that in mind,
what we can do now

00:18:36.380 --> 00:18:38.550 align:middle line:84%
is let us exit
from this session.

00:18:38.550 --> 00:18:41.060 align:middle line:84%
Before we do that, we
can say get user ID.

00:18:41.060 --> 00:18:42.565 align:middle line:90%
You can see NT authority system.

00:18:42.565 --> 00:18:43.940 align:middle line:84%
So that's one of
the great things

00:18:43.940 --> 00:18:46.490 align:middle line:84%
with a persistent service
is it provides you

00:18:46.490 --> 00:18:48.080 align:middle line:84%
with the highest
level of privileges

00:18:48.080 --> 00:18:49.910 align:middle line:90%
available on a Windows system.

00:18:49.910 --> 00:18:52.950 align:middle line:84%
You are not tied down to
a particular user account.

00:18:52.950 --> 00:18:55.490 align:middle line:90%
So I'm going to exit.

00:18:55.490 --> 00:18:57.300 align:middle line:84%
And we also have the
other session here.

00:18:57.300 --> 00:19:01.790 align:middle line:84%
So I'll say sessions
kill one to terminate

00:19:01.790 --> 00:19:03.180 align:middle line:90%
that particular session.

00:19:03.180 --> 00:19:07.070 align:middle line:84%
So now, we don't have any
sessions on the target system,

00:19:07.070 --> 00:19:07.580 align:middle line:90%
all right?

00:19:07.580 --> 00:19:10.790 align:middle line:84%
And you might be a little bit
confused because I've just

00:19:10.790 --> 00:19:12.290 align:middle line:90%
terminated any access I had.

00:19:12.290 --> 00:19:14.030 align:middle line:84%
Well, remember the
persistent service is

00:19:14.030 --> 00:19:15.560 align:middle line:90%
running on the target system.

00:19:15.560 --> 00:19:17.420 align:middle line:84%
And after every
five seconds, it's

00:19:17.420 --> 00:19:21.220 align:middle line:84%
going to execute the payload
that will then connect back

00:19:21.220 --> 00:19:21.967 align:middle line:90%
to the listener.

00:19:21.967 --> 00:19:23.300 align:middle line:90%
So we haven't set up a listener.

00:19:23.300 --> 00:19:24.920 align:middle line:84%
Now, to show you
that this works,

00:19:24.920 --> 00:19:27.020 align:middle line:84%
I'm going to exit from
the Metasploit framework,

00:19:27.020 --> 00:19:28.395 align:middle line:84%
and I'm then going
to start it up

00:19:28.395 --> 00:19:32.770 align:middle line:84%
again just to prove to you
that this indeed does work so.

00:19:32.770 --> 00:19:36.170 align:middle line:84%
We'll give this a
couple of seconds.

00:19:36.170 --> 00:19:39.207 align:middle line:84%
We can then set up the actual
handler or the listener

00:19:39.207 --> 00:19:40.290 align:middle line:90%
for lack of a better word.

00:19:40.290 --> 00:19:41.600 align:middle line:90%
So use multihandler.

00:19:41.600 --> 00:19:43.850 align:middle line:84%
We then set the
payload that we used

00:19:43.850 --> 00:19:47.030 align:middle line:84%
or that we specified when we
were using the persistence

00:19:47.030 --> 00:19:51.050 align:middle line:84%
module, which by default was
the 32-bit Meterpreter payload.

00:19:51.050 --> 00:19:57.250 align:middle line:84%
So we'll say set payload
Windows Meterpreter reverse TCP.

00:19:57.250 --> 00:19:59.860 align:middle line:84%
You then need to specify
the exact options

00:19:59.860 --> 00:20:02.390 align:middle line:84%
you used when you were using
the persistence module.

00:20:02.390 --> 00:20:05.360 align:middle line:84%
So if I say Show Options,
make sure that the Kali Linux

00:20:05.360 --> 00:20:06.050 align:middle line:90%
IP is set.

00:20:06.050 --> 00:20:09.280 align:middle line:84%
So we can say set L
host to ethernet one.

00:20:09.280 --> 00:20:11.560 align:middle line:84%
And then, the port that
we specified-- again,

00:20:11.560 --> 00:20:14.860 align:middle line:84%
remember that we actually
changed it to 4433.

00:20:14.860 --> 00:20:15.760 align:middle line:90%
There we are.

00:20:15.760 --> 00:20:17.780 align:middle line:84%
And you'll actually
see what will happen.

00:20:17.780 --> 00:20:21.270 align:middle line:84%
So I'll type in exploit,
and we immediately

00:20:21.270 --> 00:20:23.850 align:middle line:84%
get access to the target
system without even

00:20:23.850 --> 00:20:25.180 align:middle line:90%
targeting the system.

00:20:25.180 --> 00:20:29.430 align:middle line:84%
So just to prove it to
you-- sysinfo, get user ID.

00:20:29.430 --> 00:20:31.350 align:middle line:84%
We're on the system,
and we'll keep

00:20:31.350 --> 00:20:34.710 align:middle line:84%
getting access to the system so
long as the system is online.

00:20:34.710 --> 00:20:38.010 align:middle line:84%
When it comes back online, if
we have our listener running,

00:20:38.010 --> 00:20:40.030 align:middle line:84%
we'll get access
almost immediately.

00:20:40.030 --> 00:20:42.420 align:middle line:84%
And as I said, this runs
after every five seconds,

00:20:42.420 --> 00:20:43.510 align:middle line:90%
which you can customize.

00:20:43.510 --> 00:20:44.760 align:middle line:90%
So I'll prove it to you again.

00:20:44.760 --> 00:20:46.020 align:middle line:90%
I'll say exit.

00:20:46.020 --> 00:20:50.010 align:middle line:84%
And if I run the handler
once again or the listener,

00:20:50.010 --> 00:20:51.550 align:middle line:90%
there we are-- another session.

00:20:51.550 --> 00:20:54.570 align:middle line:84%
So what we've done here
is we've essentially

00:20:54.570 --> 00:20:58.770 align:middle line:84%
ensured that we have access to
this system irregardless of how

00:20:58.770 --> 00:21:01.210 align:middle line:84%
we gained access to the
system in the first place.

00:21:01.210 --> 00:21:04.680 align:middle line:84%
So we don't have to exploit
the Rejetto HTTP file server.

00:21:04.680 --> 00:21:06.150 align:middle line:90%
That service can be patched.

00:21:06.150 --> 00:21:08.590 align:middle line:84%
We will still have access
to the target system.

00:21:08.590 --> 00:21:13.260 align:middle line:84%
So I hope this was an
illuminating demonstration

00:21:13.260 --> 00:21:16.690 align:middle line:84%
as to how persistence works
and why it's so important.

00:21:16.690 --> 00:21:19.410 align:middle line:84%
So this is going to conclude
the practical demonstration

00:21:19.410 --> 00:21:22.090 align:middle line:90%
side of this video.

00:21:22.090 --> 00:21:24.420 align:middle line:84%
All right, so
hopefully, as I said,

00:21:24.420 --> 00:21:28.560 align:middle line:84%
that was a good example
how persistence works

00:21:28.560 --> 00:21:31.110 align:middle line:84%
and why it's important
and a technique that you

00:21:31.110 --> 00:21:33.540 align:middle line:90%
can utilize on Windows.

00:21:33.540 --> 00:21:35.325 align:middle line:84%
So that was one
of the techniques

00:21:35.325 --> 00:21:36.450 align:middle line:90%
that I wanted to highlight.

00:21:36.450 --> 00:21:38.367 align:middle line:84%
In the next video, we're
going to be exploring

00:21:38.367 --> 00:21:41.230 align:middle line:84%
another technique that will
involve creating another user

00:21:41.230 --> 00:21:44.310 align:middle line:84%
account, also known as
a backdoor user account,

00:21:44.310 --> 00:21:47.730 align:middle line:84%
that we will be privy to and
will essentially provide us

00:21:47.730 --> 00:21:50.760 align:middle line:84%
with a means of accessing
the target system whenever

00:21:50.760 --> 00:21:51.540 align:middle line:90%
we want to.

00:21:51.540 --> 00:21:55.160 align:middle line:84%
So I'll be seeing you
in the next video.

00:21:55.160 --> 00:21:56.000 align:middle line:90%