WEBVTT

00:00:00.390 --> 00:00:20.235
Another tool that we're going to use is Process Monitor.

00:00:02.470 --> 00:00:04.570
This is another Microsoft Sysinternals tool.

00:00:04.570 --> 00:00:05.340
It's free.

00:00:05.430 --> 00:00:08.900
But what Process Monitor does is it kind of watches what's

00:00:08.900 --> 00:00:11.370
going on in real time on your system.

00:00:11.610 --> 00:00:15.560
The nice thing about Process Monitor is that it will go in and it will

00:00:15.560 --> 00:00:19.490
tell you which processes are writing files, which ones are modifying

00:00:19.500 --> 00:00:22.240
registry keys, and so on, and you can actually see what they're

00:00:22.240 --> 00:00:24.000
writing at least into the registry.

00:00:24.010 --> 00:00:26.530
With the files, you can see how much data is being written to it.

00:00:26.530 --> 00:00:29.270
You can't necessarily see what data is being written to it,

00:00:29.270 --> 00:00:34.610
but it gives us a way to tie back who is doing what on the operating system.

00:00:34.620 --> 00:00:34.970
Got it.

00:00:35.160 --> 00:00:37.730
And, again, what I'm going to do is I'm going to right‑click on this.

00:00:37.920 --> 00:00:39.950
I'm going to run it as an administrator.

00:00:40.370 --> 00:00:44.650
I'm seeing a pattern. And you'll see that it's immediately going to start.

00:00:45.820 --> 00:00:47.810
It has a great filtering interface.

00:00:47.820 --> 00:00:50.750
So some of these things I'm just going to turn off for the moment.

00:00:51.990 --> 00:00:54.130
Turn off these filters, click OK,

00:00:54.130 --> 00:00:56.950
and then it starts recording everything that's going on in the

00:00:57.000 --> 00:01:00.060
system. So this is historical, and this is actually going to be

00:01:00.070 --> 00:01:03.535
leveraging RAM as well, so you can't run this forever. You can't

00:01:04.209 --> 00:01:10.225
run it forever, but I've seen Process Monitor on a VM collect 8

00:01:10.225 --> 00:01:11.610
million, 9 million events.

00:01:11.610 --> 00:01:12.700
Okay, right.

00:01:12.710 --> 00:01:13.710
You run this.

00:01:13.720 --> 00:01:15.830
You have this recording, probably minimize it.

00:01:15.990 --> 00:01:18.370
Run the malware and then you'll go back in.

00:01:18.530 --> 00:01:20.260
You'll click this little magnifying glass up here,

00:01:20.260 --> 00:01:22.940
and that stops the capture, so then it's not capturing anything

00:01:22.940 --> 00:01:25.400
anymore. And then you go into the filter interface,

00:01:25.420 --> 00:01:28.860
and then you just start filtering down. The filtering

00:01:28.860 --> 00:01:30.790
interface in Process Monitor is amazing.

00:01:30.940 --> 00:01:32.835
And so what you would probably start doing is go to

00:01:32.835 --> 00:01:35.500
Process Name, choose the process,

00:01:35.550 --> 00:01:38.790
your malware process. That you found in Process Explorer. That

00:01:38.790 --> 00:01:42.090
you saw in Process Explorer, or at least the original file that

00:01:42.090 --> 00:01:43.910
you executed, and you choose that.

00:01:43.910 --> 00:01:47.060
So I'm just going to choose Process Explorer here. Then click

00:01:47.070 --> 00:01:50.190
Add. And you're going to see here in the lower left corner, right

00:01:50.330 --> 00:01:52.150
now it's showing about 15,000 events.

00:01:52.330 --> 00:01:54.200
If I filter down to just Process Monitor, it actually

00:01:54.200 --> 00:01:55.950
doesn't show us anything because apparently Process

00:01:55.950 --> 00:01:58.225
Monitor... It has an anti‑filter. Right. Oh,

00:01:59.440 --> 00:01:59.950
yeah, you're right.

00:02:00.400 --> 00:02:01.320
So let me remove that one.

00:02:01.320 --> 00:02:02.160
Let me choose a different one.

00:02:03.130 --> 00:02:07.515
Let's see here, svchost. There should definitely be some activity with

00:02:07.515 --> 00:02:12.620
svchost. Click Apply, and you can see that it still filtered it down to

00:02:12.620 --> 00:02:16.240
about 2700 events out of a possible 168,000.

00:02:16.250 --> 00:02:16.590
Okay.

00:02:16.600 --> 00:02:18.870
And we can filter it down even more down to the different

00:02:18.870 --> 00:02:21.680
operations, and we're going to use this tool to see what

00:02:21.690 --> 00:02:23.450
our malware is doing. Got it.
