WEBVTT

00:00:00.000 --> 00:00:02.990
So what are these tools we're going to be using to monitor? So

00:00:02.990 --> 00:00:05.820
there are a lot of different tools that you can use to monitor

00:00:05.820 --> 00:00:07.960
just various aspects of the system.

00:00:08.290 --> 00:00:10.680
We're going to talk about a couple of ones that are pretty

00:00:10.680 --> 00:00:13.990
common. When you install your tools onto your sandbox, we've

00:00:14.520 --> 00:00:17.050
talked about making sure you snapshot,

00:00:17.140 --> 00:00:20.060
but I would also say make sure you run your tools at least once before you

00:00:20.810 --> 00:00:23.710
snapshot because some of these tools have you EULAs that you have to click

00:00:23.710 --> 00:00:25.860
through, the end user license agreements.

00:00:26.040 --> 00:00:31.080
And so you don't want to have to click through that every single time you run

00:00:31.080 --> 00:00:35.960
the tool if you snapshot it in the wrong place. And I've done that, and it's

00:00:35.960 --> 00:00:40.250
more of an annoyance, but it's something, kind of lessons learned, make sure

00:00:40.250 --> 00:00:42.760
you at least run it once. Absolutely,

00:00:42.890 --> 00:00:45.040
especially if you're setting everything up to kind of run

00:00:45.040 --> 00:00:47.160
automatically or run from a scripted solution because it's

00:00:47.160 --> 00:00:48.650
multiple tools, and so if you're like,

00:00:48.660 --> 00:00:51.490
all right, do my monitoring, but you have EULAs waiting to be

00:00:51.490 --> 00:00:54.200
accepted, and they're not running. Right. Right. So do you want

00:00:54.200 --> 00:00:57.730
to get into some these tools? Like what's the first tool we use

00:00:57.730 --> 00:00:58.670
and what's its purpose?

00:00:58.730 --> 00:01:02.100
Yeah, so here we're back in my virtual machine,

00:01:02.110 --> 00:01:03.630
our sandbox that we've already set up.

00:01:03.640 --> 00:01:06.660
I've installed a number of tools. One of the first tools that I

00:01:06.660 --> 00:01:11.210
recommend running is Process Explorer. Process Explorer is

00:01:11.210 --> 00:01:13.450
basically Task Manager on steroids.

00:01:13.640 --> 00:01:15.160
It will do a lot of things,

00:01:15.720 --> 00:01:17.920
basically just showing you the processes that are running,

00:01:18.090 --> 00:01:20.550
but it shows you a lot more information than that.

00:01:21.360 --> 00:01:23.820
And what I'm going to do just to show how it runs,

00:01:24.210 --> 00:01:25.790
I'm going to just right‑click on it,

00:01:25.790 --> 00:01:28.310
and I'm going to recommend running it as an administrator.

00:01:28.490 --> 00:01:31.760
I recommend running all of these tools as administrators on your

00:01:31.760 --> 00:01:35.760
sandbox just because if you don't run as administrator,

00:01:35.760 --> 00:01:38.710
it could miss something, and some of these tools do require admin privileges.

00:01:38.890 --> 00:01:40.230
That's a Sysinternals tool.

00:01:40.290 --> 00:01:42.410
Yes, this is a Microsoft Sysinternals tool.

00:01:42.580 --> 00:01:42.880
Actually,

00:01:42.890 --> 00:01:45.300
all the tools we're talking about are free, so anybody can go

00:01:45.300 --> 00:01:46.630
download them. They're not commercial tools.

00:01:46.630 --> 00:01:48.110
You don't need to pay anything for them.

00:01:48.300 --> 00:01:50.650
You just download them and run them and you're good.

00:01:50.740 --> 00:01:51.270
Okay, great.

00:01:51.270 --> 00:01:54.600
And we'll make a list of those resources available in the demo content

00:01:54.610 --> 00:01:58.320
as well. Right. And what we'll use Process Explorer for is basically

00:01:58.320 --> 00:02:01.910
just kind of watching what is going on in our system once we execute

00:02:01.910 --> 00:02:05.350
our malware. So what I usually do is I just kind of push Process

00:02:05.350 --> 00:02:06.460
Explorer here to the side.

00:02:06.510 --> 00:02:09.229
I can see all the different processes that are running.

00:02:09.370 --> 00:02:11.170
I'm just going to kind of close this one a little bit because

00:02:11.170 --> 00:02:13.720
these are all system processes, and we could see all the

00:02:13.720 --> 00:02:14.960
different processes that are running.

00:02:14.970 --> 00:02:19.040
So what'll happen is when I execute the malware in my sandbox,

00:02:19.140 --> 00:02:21.910
I'm going to kind of watch Process Explorer to see what happens.

00:02:22.010 --> 00:02:25.920
Does the process immediately exit, which could mean that it's

00:02:25.920 --> 00:02:29.710
detecting that it's in a VM or that my tools are running. Is it

00:02:29.720 --> 00:02:34.330
launching another program? And we'll see that by the malware having a

00:02:34.330 --> 00:02:37.900
child process underneath it or something like that. Does it restart

00:02:38.210 --> 00:02:41.280
itself? This is kind of a visual indicator for us to see what's going

00:02:41.280 --> 00:02:42.020
on on the system.

00:02:42.090 --> 00:02:43.960
So you have watch it while it's happening.

00:02:43.970 --> 00:02:45.490
Yeah, absolutely, absolutely.
