WEBVTT

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


00:00:03.388 --> 00:00:06.776 align:middle line:90%
[MUSIC PLAYING]

00:00:06.776 --> 00:00:10.170 align:middle line:90%


00:00:10.170 --> 00:00:12.180 align:middle line:90%
Clearing Windows Event Logs--

00:00:12.180 --> 00:00:14.010 align:middle line:84%
in this video, we
will be exploring

00:00:14.010 --> 00:00:17.430 align:middle line:84%
the process of clearing our
tracks on a Windows system

00:00:17.430 --> 00:00:21.300 align:middle line:84%
after exploitation, and
obviously, post exploitation.

00:00:21.300 --> 00:00:24.360 align:middle line:84%
So the process of clearing
your tracks when you're done

00:00:24.360 --> 00:00:26.050 align:middle line:90%
falls under post exploitation.

00:00:26.050 --> 00:00:28.560 align:middle line:90%
And it's extremely important.

00:00:28.560 --> 00:00:30.960 align:middle line:84%
And it's a step that
you really cannot miss,

00:00:30.960 --> 00:00:33.660 align:middle line:84%
or you cannot skip over,
and for good reason,

00:00:33.660 --> 00:00:35.950 align:middle line:84%
as we'll be exploring
within this video.

00:00:35.950 --> 00:00:39.540 align:middle line:84%
So because we're dealing
with the Windows system,

00:00:39.540 --> 00:00:42.540 align:middle line:84%
we need to get an idea of
what Windows Event logs are,

00:00:42.540 --> 00:00:48.000 align:middle line:84%
as this is pretty much the
most important logging system

00:00:48.000 --> 00:00:49.990 align:middle line:84%
within the Windows
operating system.

00:00:49.990 --> 00:00:53.400 align:middle line:84%
So the Windows operating
system stores and catalogs

00:00:53.400 --> 00:00:56.880 align:middle line:84%
all actions or events that have
been performed on the system

00:00:56.880 --> 00:00:59.580 align:middle line:84%
and stores them in
the Windows event log

00:00:59.580 --> 00:01:02.490 align:middle line:84%
or in various Windows
Event log files, right?

00:01:02.490 --> 00:01:04.860 align:middle line:84%
So event logs are
categorized based

00:01:04.860 --> 00:01:06.510 align:middle line:84%
on the type of events
that they store.

00:01:06.510 --> 00:01:09.750 align:middle line:84%
So you'll typically find that
you have application logs that

00:01:09.750 --> 00:01:12.330 align:middle line:84%
are responsible for storing
application or program

00:01:12.330 --> 00:01:16.200 align:middle line:84%
events like startups,
crashes, shutdowns, et cetera.

00:01:16.200 --> 00:01:19.530 align:middle line:84%
You then have your system
logs, which are very important.

00:01:19.530 --> 00:01:22.290 align:middle line:84%
And these store system events
like startups, reboots,

00:01:22.290 --> 00:01:26.040 align:middle line:84%
crashes, anything pertinent
to the functioning

00:01:26.040 --> 00:01:28.090 align:middle line:84%
or the functionality
of the system.

00:01:28.090 --> 00:01:30.790 align:middle line:84%
And then we have the
most important event log,

00:01:30.790 --> 00:01:32.220 align:middle line:90%
which is the security logs.

00:01:32.220 --> 00:01:35.430 align:middle line:84%
So the security logs
store security events

00:01:35.430 --> 00:01:37.980 align:middle line:84%
like password changes,
authentication failures,

00:01:37.980 --> 00:01:38.490 align:middle line:90%
et cetera.

00:01:38.490 --> 00:01:41.280 align:middle line:84%
So whenever you're
done with a penetration

00:01:41.280 --> 00:01:44.190 align:middle line:84%
test or an assessment,
it's very important

00:01:44.190 --> 00:01:46.350 align:middle line:84%
that you actually go
through the process

00:01:46.350 --> 00:01:49.230 align:middle line:84%
of clearing the event
logs on the target system

00:01:49.230 --> 00:01:50.760 align:middle line:90%
that you compromised.

00:01:50.760 --> 00:01:53.820 align:middle line:84%
The reason you want to do
this is because the event logs

00:01:53.820 --> 00:01:57.600 align:middle line:84%
are pretty much the first stop
for any forensic investigator

00:01:57.600 --> 00:01:59.670 align:middle line:84%
after a compromise
has been detected.

00:01:59.670 --> 00:02:04.080 align:middle line:84%
So it's therefore very important
that you know and understand

00:02:04.080 --> 00:02:06.030 align:middle line:84%
how to clear your
tracks after you're

00:02:06.030 --> 00:02:07.390 align:middle line:90%
done with your assessment.

00:02:07.390 --> 00:02:09.600 align:middle line:84%
So the clean-up
process will really

00:02:09.600 --> 00:02:12.540 align:middle line:84%
revolve around clearing
your event logs,

00:02:12.540 --> 00:02:15.167 align:middle line:84%
deleting any of the
files or exploit code

00:02:15.167 --> 00:02:17.250 align:middle line:84%
that you've transferred
over to the target, which,

00:02:17.250 --> 00:02:18.930 align:middle line:84%
in this case, was
fairly minimal.

00:02:18.930 --> 00:02:22.530 align:middle line:84%
And that's by design,
because you really only need

00:02:22.530 --> 00:02:24.990 align:middle line:84%
to understand how to
perform your activity

00:02:24.990 --> 00:02:29.550 align:middle line:84%
or your various phases of post
exploitation automatically,

00:02:29.550 --> 00:02:31.290 align:middle line:90%
preferably within memory.

00:02:31.290 --> 00:02:34.020 align:middle line:84%
So in our case, the
only thing we need to do

00:02:34.020 --> 00:02:36.060 align:middle line:84%
is explore the
process of clearing

00:02:36.060 --> 00:02:37.170 align:middle line:90%
the Windows event logs.

00:02:37.170 --> 00:02:40.380 align:middle line:84%
Now, on a Windows
system, you can

00:02:40.380 --> 00:02:44.250 align:middle line:84%
view the Windows event logs
by utilizing the event view

00:02:44.250 --> 00:02:47.410 align:middle line:84%
application, which we'll be
exploring in a few seconds,

00:02:47.410 --> 00:02:47.910 align:middle line:90%
right?

00:02:47.910 --> 00:02:50.160 align:middle line:84%
So now that we have an
understanding of what

00:02:50.160 --> 00:02:52.530 align:middle line:84%
Windows Event logs
are, why they are used,

00:02:52.530 --> 00:02:54.960 align:middle line:84%
and why they're important
in both the context

00:02:54.960 --> 00:02:57.900 align:middle line:84%
of a forensic investigator
as well as a penetration

00:02:57.900 --> 00:02:59.820 align:middle line:90%
tester or a hacker.

00:02:59.820 --> 00:03:02.520 align:middle line:84%
Let's take a look at how we can
go about clearing the Windows

00:03:02.520 --> 00:03:05.190 align:middle line:90%
event logs with my meterpreter.

00:03:05.190 --> 00:03:07.210 align:middle line:84%
So just fire up the
lab environment.

00:03:07.210 --> 00:03:09.570 align:middle line:84%
We'll be utilizing the
same lab environment we

00:03:09.570 --> 00:03:11.320 align:middle line:90%
utilized in the previous video.

00:03:11.320 --> 00:03:12.940 align:middle line:84%
So it's going to
be fairly simple.

00:03:12.940 --> 00:03:15.210 align:middle line:84%
So I'll see you within
the lab environment.

00:03:15.210 --> 00:03:18.260 align:middle line:90%


00:03:18.260 --> 00:03:20.450 align:middle line:84%
All right, so I'm back
within the lab environment.

00:03:20.450 --> 00:03:23.070 align:middle line:84%
And as we explored in
the previous video,

00:03:23.070 --> 00:03:25.100 align:middle line:84%
this lab environment
provides you with access

00:03:25.100 --> 00:03:28.223 align:middle line:84%
to the attack machine as
well as the target machine.

00:03:28.223 --> 00:03:30.140 align:middle line:84%
This will be very
important, as we'll actually

00:03:30.140 --> 00:03:33.560 align:middle line:84%
be viewing the various event
logs before we actually

00:03:33.560 --> 00:03:36.530 align:middle line:84%
clear them and taking a look
at what type of data they store

00:03:36.530 --> 00:03:38.420 align:middle line:84%
and why it's so
important, right?

00:03:38.420 --> 00:03:40.250 align:middle line:84%
So first and
foremost, we actually

00:03:40.250 --> 00:03:42.150 align:middle line:84%
need to gain access
to the target system.

00:03:42.150 --> 00:03:44.670 align:middle line:84%
So we're just going to copy
the target IP right over here,

00:03:44.670 --> 00:03:46.370 align:middle line:90%
which is provided to us.

00:03:46.370 --> 00:03:49.280 align:middle line:84%
And we're just going to
maximize my terminal.

00:03:49.280 --> 00:03:51.950 align:middle line:84%
And I can start up the
PostgreSQL Database

00:03:51.950 --> 00:03:57.200 align:middle line:84%
Service as usual, and we'll
also start up msfconsole.

00:03:57.200 --> 00:03:59.560 align:middle line:84%
So we'll give that a couple
of seconds to start up.

00:03:59.560 --> 00:04:07.440 align:middle line:90%


00:04:07.440 --> 00:04:09.720 align:middle line:84%
All right, so the first
thing that we want to do

00:04:09.720 --> 00:04:10.800 align:middle line:90%
is create a workspace.

00:04:10.800 --> 00:04:18.750 align:middle line:84%
And we're just going to call
it Cleaev, so Clear Event logs.

00:04:18.750 --> 00:04:22.380 align:middle line:84%
And we can then set
up the global variable

00:04:22.380 --> 00:04:23.820 align:middle line:90%
for the RHOSTS option.

00:04:23.820 --> 00:04:26.010 align:middle line:84%
And we'll set that
to the target IP.

00:04:26.010 --> 00:04:27.720 align:middle line:84%
That'll again save
us from having

00:04:27.720 --> 00:04:30.510 align:middle line:84%
to type in the target IP address
whenever we load a module.

00:04:30.510 --> 00:04:33.390 align:middle line:84%
So you should be familiar
with how to exploit

00:04:33.390 --> 00:04:35.350 align:middle line:90%
the badblue application.

00:04:35.350 --> 00:04:38.230 align:middle line:84%
And in this case, we've
explored it quite a bit.

00:04:38.230 --> 00:04:41.370 align:middle line:84%
So we just need to search
for the module badblue.

00:04:41.370 --> 00:04:44.040 align:middle line:84%
And we're going to be
utilizing the badblue pass

00:04:44.040 --> 00:04:46.078 align:middle line:90%
through exploit module here.

00:04:46.078 --> 00:04:46.620 align:middle line:90%
There we are.

00:04:46.620 --> 00:04:49.680 align:middle line:90%
Copy and we'll say use.

00:04:49.680 --> 00:04:52.120 align:middle line:84%
And if we show the
options for this module,

00:04:52.120 --> 00:04:54.360 align:middle line:84%
you should have the target
IP specified as well as

00:04:54.360 --> 00:04:56.320 align:middle line:84%
the target port,
which, in this case,

00:04:56.320 --> 00:04:57.810 align:middle line:90%
we know it's running on port 80.

00:04:57.810 --> 00:05:02.700 align:middle line:84%
We only need to set the target
to badblue Enterprise Edition

00:05:02.700 --> 00:05:06.600 align:middle line:84%
2.7 Universal and
type in exploit.

00:05:06.600 --> 00:05:08.280 align:middle line:84%
So we'll give that
a couple of seconds

00:05:08.280 --> 00:05:10.380 align:middle line:84%
to actually provide us
with a meterpreter session.

00:05:10.380 --> 00:05:13.330 align:middle line:90%


00:05:13.330 --> 00:05:14.330 align:middle line:90%
All right, there we are.

00:05:14.330 --> 00:05:16.220 align:middle line:90%
So we get a meterpreter session.

00:05:16.220 --> 00:05:20.630 align:middle line:84%
Some local system enumeration
will not hurt anyone.

00:05:20.630 --> 00:05:21.290 align:middle line:90%
There we are.

00:05:21.290 --> 00:05:24.300 align:middle line:84%
And getuid, we currently have
administrative privileges,

00:05:24.300 --> 00:05:25.460 align:middle line:90%
which is required, right?

00:05:25.460 --> 00:05:28.070 align:middle line:84%
So you do need elevated
privileges in order

00:05:28.070 --> 00:05:29.630 align:middle line:90%
to clear the Windows Event log.

00:05:29.630 --> 00:05:31.860 align:middle line:84%
That's something that you
want to keep in mind here.

00:05:31.860 --> 00:05:33.280 align:middle line:84%
Which, of course,
by this point, you

00:05:33.280 --> 00:05:35.447 align:middle line:84%
should already have, as we
have explored the process

00:05:35.447 --> 00:05:37.730 align:middle line:90%
of elevating our privileges.

00:05:37.730 --> 00:05:39.800 align:middle line:84%
So we head over to
the target machine.

00:05:39.800 --> 00:05:41.570 align:middle line:84%
And let's open up
the Event Viewer

00:05:41.570 --> 00:05:44.780 align:middle line:84%
to see what's been
logged exactly.

00:05:44.780 --> 00:05:47.880 align:middle line:84%
So I'm going to
say Event Viewer.

00:05:47.880 --> 00:05:50.220 align:middle line:84%
All right, so the Event
Viewer is started up.

00:05:50.220 --> 00:05:52.750 align:middle line:84%
And that's going to take a
while to actually load up.

00:05:52.750 --> 00:05:54.930 align:middle line:84%
So under Windows
Logs, you can see

00:05:54.930 --> 00:05:57.820 align:middle line:84%
it's sorted based on
Application, Security, Setup,

00:05:57.820 --> 00:05:58.320 align:middle line:90%
System.

00:05:58.320 --> 00:06:00.910 align:middle line:84%
But the three here that
we mentioned earlier,

00:06:00.910 --> 00:06:03.070 align:middle line:84%
we have Application,
Security, and System.

00:06:03.070 --> 00:06:04.620 align:middle line:90%
So we click on Application Logs.

00:06:04.620 --> 00:06:08.460 align:middle line:84%
Again, you can see it's going to
say a number of events at 255.

00:06:08.460 --> 00:06:10.720 align:middle line:84%
And this is going to take a
while to load all of them.

00:06:10.720 --> 00:06:13.660 align:middle line:84%
So if we click on
Security, there we are.

00:06:13.660 --> 00:06:15.610 align:middle line:90%
We have the security logs here.

00:06:15.610 --> 00:06:18.090 align:middle line:90%
So based on the time--

00:06:18.090 --> 00:06:21.510 align:middle line:84%
as you can see, the
current clock is 10:05 PM,

00:06:21.510 --> 00:06:26.310 align:middle line:84%
we can see that the last
security log was essentially

00:06:26.310 --> 00:06:28.950 align:middle line:90%
added here at 10:02.

00:06:28.950 --> 00:06:30.840 align:middle line:84%
So if we scroll
down, it's sorted

00:06:30.840 --> 00:06:32.760 align:middle line:90%
based on the date and time.

00:06:32.760 --> 00:06:36.287 align:middle line:84%
In this case, the events
that have just occurred

00:06:36.287 --> 00:06:37.620 align:middle line:90%
are going to be at the top here.

00:06:37.620 --> 00:06:39.040 align:middle line:84%
And of course,
you can sort that.

00:06:39.040 --> 00:06:43.050 align:middle line:84%
So if we say show to
display the actual events

00:06:43.050 --> 00:06:46.780 align:middle line:84%
from the latest to the oldest,
we can do that as well.

00:06:46.780 --> 00:06:48.540 align:middle line:84%
So in our case, we're
just going to show

00:06:48.540 --> 00:06:50.880 align:middle line:90%
the latest, which was 10:02.

00:06:50.880 --> 00:06:51.880 align:middle line:90%
And you can click on it.

00:06:51.880 --> 00:06:53.880 align:middle line:84%
And in this case,
you can see it looks

00:06:53.880 --> 00:06:55.380 align:middle line:90%
like an account was logged off.

00:06:55.380 --> 00:06:59.140 align:middle line:84%
So that's a fairly
simple security event.

00:06:59.140 --> 00:07:00.960 align:middle line:84%
And if we click
on System, you can

00:07:00.960 --> 00:07:03.390 align:middle line:84%
see that the latest
one was 10:02, right?

00:07:03.390 --> 00:07:07.860 align:middle line:84%
So nothing really
has been logged here.

00:07:07.860 --> 00:07:10.710 align:middle line:84%
Nothing really has been
logged here after 10:02.

00:07:10.710 --> 00:07:13.530 align:middle line:84%
And of course, if we
click on Security now,

00:07:13.530 --> 00:07:15.750 align:middle line:84%
we'll just wait for
that to load up.

00:07:15.750 --> 00:07:19.260 align:middle line:84%
Hopefully we can actually view
the logs in a few seconds.

00:07:19.260 --> 00:07:22.170 align:middle line:84%
For some reason, it looks
like the security logs are not

00:07:22.170 --> 00:07:23.200 align:middle line:90%
being displayed here.

00:07:23.200 --> 00:07:24.160 align:middle line:90%
There we are.

00:07:24.160 --> 00:07:27.030 align:middle line:84%
And yeah, so if we
click on Security,

00:07:27.030 --> 00:07:28.560 align:middle line:84%
we can see there's
nothing really

00:07:28.560 --> 00:07:30.840 align:middle line:84%
that has been logged in
regards to anything that we've

00:07:30.840 --> 00:07:32.580 align:middle line:90%
done after we've gained access.

00:07:32.580 --> 00:07:34.350 align:middle line:84%
So let's try and do
something, right?

00:07:34.350 --> 00:07:37.740 align:middle line:84%
So let's say I want to open up
a shell session on the target

00:07:37.740 --> 00:07:39.090 align:middle line:90%
and get a command prompt.

00:07:39.090 --> 00:07:42.960 align:middle line:84%
And I want to change the actual
password for the administrator

00:07:42.960 --> 00:07:43.990 align:middle line:90%
user.

00:07:43.990 --> 00:07:46.060 align:middle line:84%
So I can say net
user administrator,

00:07:46.060 --> 00:07:48.570 align:middle line:84%
and I can change the
password to, maybe,

00:07:48.570 --> 00:07:52.770 align:middle line:90%
let's see, Password_123321.

00:07:52.770 --> 00:07:53.910 align:middle line:90%
Hit Enter.

00:07:53.910 --> 00:07:56.100 align:middle line:84%
As you can see, the command
completed successfully.

00:07:56.100 --> 00:07:58.350 align:middle line:84%
Well, let's see whether
that was actually logged.

00:07:58.350 --> 00:08:00.570 align:middle line:84%
So if we click on
Security, I'm just

00:08:00.570 --> 00:08:03.820 align:middle line:84%
going to load up
Security Events again.

00:08:03.820 --> 00:08:06.450 align:middle line:90%
And we can see this was 10:07.

00:08:06.450 --> 00:08:08.700 align:middle line:84%
Let's click on the first
one, User Account Management.

00:08:08.700 --> 00:08:11.010 align:middle line:84%
It's going to tell you a
user account was changed.

00:08:11.010 --> 00:08:13.780 align:middle line:84%
And you can go through
the details here.

00:08:13.780 --> 00:08:15.780 align:middle line:84%
So it'll tell you the
user administrator

00:08:15.780 --> 00:08:17.010 align:middle line:90%
account was changed.

00:08:17.010 --> 00:08:21.570 align:middle line:84%
And in terms of the value
or what was changed,

00:08:21.570 --> 00:08:23.760 align:middle line:84%
let's see if we
can see that here.

00:08:23.760 --> 00:08:27.587 align:middle line:84%
The changed attributes
are the SAM account name.

00:08:27.587 --> 00:08:28.170 align:middle line:90%
And let's see.

00:08:28.170 --> 00:08:28.712 align:middle line:90%
There we are.

00:08:28.712 --> 00:08:30.480 align:middle line:84%
The Password Last
Set, so it'll tell you

00:08:30.480 --> 00:08:31.780 align:middle line:90%
when the password was changed.

00:08:31.780 --> 00:08:35.370 align:middle line:84%
And as a forensic
investigator, this information

00:08:35.370 --> 00:08:37.505 align:middle line:90%
is very, very important.

00:08:37.505 --> 00:08:38.880 align:middle line:84%
So if we click on
the latest one,

00:08:38.880 --> 00:08:40.380 align:middle line:84%
you can see that
an attempt was made

00:08:40.380 --> 00:08:41.830 align:middle line:90%
to reset an account's password.

00:08:41.830 --> 00:08:43.200 align:middle line:90%
So that's the latest event log.

00:08:43.200 --> 00:08:45.360 align:middle line:84%
And of course,
this just confirms

00:08:45.360 --> 00:08:46.930 align:middle line:90%
that the password was changed.

00:08:46.930 --> 00:08:49.140 align:middle line:84%
So you can see that all
our actions are actually

00:08:49.140 --> 00:08:50.160 align:middle line:90%
being logged.

00:08:50.160 --> 00:08:51.730 align:middle line:90%
All right, and this is not good.

00:08:51.730 --> 00:08:55.260 align:middle line:84%
Because if there is an
indicator of compromise,

00:08:55.260 --> 00:08:58.080 align:middle line:84%
then the forensic
investigator will essentially

00:08:58.080 --> 00:09:00.210 align:middle line:84%
disconnect this system
from the internet

00:09:00.210 --> 00:09:03.510 align:middle line:84%
and then begin exploring the
actual event logs, right?

00:09:03.510 --> 00:09:07.270 align:middle line:84%
So let's take a look at how
we can clear all of this.

00:09:07.270 --> 00:09:10.285 align:middle line:84%
So it really is very, very
simple with meterpreter.

00:09:10.285 --> 00:09:12.660 align:middle line:84%
All you need to do is just
terminate the channel and head

00:09:12.660 --> 00:09:15.150 align:middle line:84%
back over into your
meterpreter session.

00:09:15.150 --> 00:09:17.970 align:middle line:90%
And we type in clearev.

00:09:17.970 --> 00:09:19.253 align:middle line:90%
Hit Enter.

00:09:19.253 --> 00:09:20.670 align:middle line:84%
As you can see,
it's going to wipe

00:09:20.670 --> 00:09:25.090 align:middle line:84%
255 records from Application,
System, and Security,

00:09:25.090 --> 00:09:26.560 align:middle line:90%
which is fantastic.

00:09:26.560 --> 00:09:28.710 align:middle line:84%
So let's actually
confirm and see

00:09:28.710 --> 00:09:31.870 align:middle line:90%
whether this was actually done.

00:09:31.870 --> 00:09:33.990 align:middle line:84%
So if we head over
to the Windows logs.

00:09:33.990 --> 00:09:36.120 align:middle line:90%
And let's click on Security now.

00:09:36.120 --> 00:09:39.600 align:middle line:84%
As you can see, the
latest one was 10:08.

00:09:39.600 --> 00:09:41.760 align:middle line:84%
And if we click on that,
this will just tell you

00:09:41.760 --> 00:09:43.180 align:middle line:90%
that the audit log was cleared.

00:09:43.180 --> 00:09:46.483 align:middle line:84%
So that's really not helpful
for a forensic investigator

00:09:46.483 --> 00:09:48.900 align:middle line:84%
because the user that did it
was the administrator, right?

00:09:48.900 --> 00:09:53.370 align:middle line:84%
So again, you can see that it's
cleared the application logs,

00:09:53.370 --> 00:09:56.370 align:middle line:84%
the security logs, as well
as the system logs here.

00:09:56.370 --> 00:09:58.080 align:middle line:84%
And of course, this
one right over here

00:09:58.080 --> 00:10:00.120 align:middle line:84%
just tells you that the
remote registry service

00:10:00.120 --> 00:10:01.590 align:middle line:90%
entered the stopped state.

00:10:01.590 --> 00:10:05.130 align:middle line:84%
And Event Log, the system
log file was cleared, right?

00:10:05.130 --> 00:10:08.310 align:middle line:84%
So you can see how
helpful this is

00:10:08.310 --> 00:10:10.740 align:middle line:84%
for an attacker or
a penetration test

00:10:10.740 --> 00:10:12.870 align:middle line:84%
irregardless of whether
they're a white attacker

00:10:12.870 --> 00:10:14.190 align:middle line:90%
or a black attacker.

00:10:14.190 --> 00:10:16.020 align:middle line:84%
This is very, very
important to do.

00:10:16.020 --> 00:10:20.010 align:middle line:84%
So that is how to clear your
tracks on a Windows system.

00:10:20.010 --> 00:10:21.810 align:middle line:84%
Now, as I said,
clearing your event

00:10:21.810 --> 00:10:23.830 align:middle line:84%
logs is just one
part of the process.

00:10:23.830 --> 00:10:26.430 align:middle line:84%
The next thing you need
to do is delete or wipe

00:10:26.430 --> 00:10:28.650 align:middle line:84%
the actual exploit
files or executables

00:10:28.650 --> 00:10:30.970 align:middle line:84%
that you transferred over
to the target system,

00:10:30.970 --> 00:10:33.720 align:middle line:84%
which, in our case, we didn't
do much apart from Mimikatz.

00:10:33.720 --> 00:10:36.300 align:middle line:84%
And of course, it's fairly
simple to remove a file.

00:10:36.300 --> 00:10:39.360 align:middle line:84%
You just type in rm,
delete it, et cetera.

00:10:39.360 --> 00:10:42.570 align:middle line:84%
So that is going to conclude
the practical demonstration

00:10:42.570 --> 00:10:43.770 align:middle line:90%
site of this video.

00:10:43.770 --> 00:10:46.910 align:middle line:90%


00:10:46.910 --> 00:10:49.690 align:middle line:84%
In the next video, we will
be exploring the process

00:10:49.690 --> 00:10:51.310 align:middle line:90%
of performing pivoting.

00:10:51.310 --> 00:10:52.870 align:middle line:84%
So once we have
gained access, we'll

00:10:52.870 --> 00:10:55.060 align:middle line:84%
be exploring how
we can essentially

00:10:55.060 --> 00:10:59.020 align:middle line:84%
pivot to other systems that are
currently on the target system

00:10:59.020 --> 00:11:02.800 align:middle line:84%
network or the network that
the system is connected to

00:11:02.800 --> 00:11:06.250 align:middle line:84%
and how we can exploit other
devices or other computers that

00:11:06.250 --> 00:11:09.610 align:middle line:84%
are part of that network through
the exploited host, right?

00:11:09.610 --> 00:11:13.500 align:middle line:84%
So I'll see you
in the next video.

00:11:13.500 --> 00:11:14.000 align:middle line:90%