WEBVTT

00:00:00.420 --> 00:00:03.370
So another tool that we should talk about that we'll

00:00:03.370 --> 00:00:05.690
probably use moving forward is RegShot.

00:00:05.700 --> 00:00:07.250
RegShot is a really great tool,

00:00:07.340 --> 00:00:11.320
and it acts very similarly to Process Monitor in that it's going

00:00:11.320 --> 00:00:13.510
to tell us what changes happened on a system.

00:00:13.680 --> 00:00:17.190
But the way that RegShot works is it takes a snapshot of the system and

00:00:17.190 --> 00:00:19.770
kind of goes through your system, looks at the files,

00:00:19.780 --> 00:00:20.740
what files exist,

00:00:20.740 --> 00:00:23.810
what they look like, and does the same thing for the registry.

00:00:23.810 --> 00:00:25.970
And then it kind of saves that snapshot off.

00:00:25.980 --> 00:00:28.700
Then you would run your malware, and then you would take a second

00:00:28.700 --> 00:00:30.970
snapshot and do a comparison between the two,

00:00:30.970 --> 00:00:34.240
and it's going to tell you things like what files were modified,

00:00:34.250 --> 00:00:36.710
what registry entries were deleted, and so on.

00:00:36.800 --> 00:00:39.670
And you can use that to very quickly go in and see what

00:00:39.670 --> 00:00:42.200
changed on your computer and your guest OS.

00:00:43.160 --> 00:00:45.025
Got it. So that's like a point in time comparison as compared

00:00:45.025 --> 00:00:48.170
to procmon where it's kind of just streaming this registry

00:00:48.170 --> 00:00:49.570
change and that registry change, right?

00:00:49.570 --> 00:00:52.240
So you get a more holistic view of what happened. Right. That's

00:00:52.240 --> 00:00:55.360
exactly what it is. Procmon is more real time, kind of showing you

00:00:55.360 --> 00:00:58.710
everything. RegShot Is more kind of comparing two points in time.

00:00:58.830 --> 00:01:01.360
And the thing with RegShot too is you're only going to see the

00:01:01.360 --> 00:01:02.750
changes that were made.

00:01:02.910 --> 00:01:04.940
You're not going to see who made those changes.

00:01:04.950 --> 00:01:05.170
I see.

00:01:05.170 --> 00:01:08.570
So you kind of have to use both Process Monitor and RegShot together.

00:01:08.620 --> 00:01:10.520
And so RegShot will let you know who made the change as well? Okay,

00:01:11.450 --> 00:01:13.820
that's an awesome piece of information. That helps, right?

00:01:14.060 --> 00:01:16.060
So what else have we got? We have another great tool, Autoruns.

00:01:16.060 --> 00:01:20.755
Autoruns, again, we're seeing a pattern here, is another Microsoft Sysinternals

00:01:21.490 --> 00:01:24.200
tool, but the nice thing about Autoruns is when you run it,

00:01:24.960 --> 00:01:27.830
it will go through, and it will look at every place in your

00:01:27.830 --> 00:01:30.640
operating system where malware can maintain persistence.

00:01:30.650 --> 00:01:31.359
Right, okay.

00:01:31.420 --> 00:01:35.130
Is that essentially the main reason it was created was to look for

00:01:35.265 --> 00:01:38.910
malware persistence? Not necessarily malware persistence because I

00:01:38.910 --> 00:01:42.110
actually use this tool a lot on systems that aren't compromised, my own

00:01:42.110 --> 00:01:45.040
systems because when you install software,

00:01:45.140 --> 00:01:46.710
it's going to install all these little hooks in the OS to

00:01:46.710 --> 00:01:50.290
auto‑start, and you may not want that. So, for example,

00:01:50.290 --> 00:01:51.550
I just ran it on here.

00:01:51.700 --> 00:01:55.960
You can see that I've obviously installed Java on here and that the

00:01:55.960 --> 00:02:00.050
SunJava has an update scheduler that's set to auto‑start.

00:02:00.060 --> 00:02:04.760
If I don't want that, I can use Autoruns to detect that and turn that off.

00:02:04.770 --> 00:02:05.140
Got it.

00:02:05.140 --> 00:02:07.720
So a lot of these tools are essentially made for just

00:02:07.730 --> 00:02:09.350
understanding what's happening in the operating system,

00:02:09.350 --> 00:02:12.579
troubleshooting, system administration, that kind of thing.

00:02:12.580 --> 00:02:15.150
But we're dual‑purposing them for understanding what

00:02:15.160 --> 00:02:16.500
malware is accomplishing as well.

00:02:16.510 --> 00:02:17.020
Exactly.

00:02:17.020 --> 00:02:19.070
A lot of these aren't troubleshooting tools. We're just

00:02:19.070 --> 00:02:20.760
kind of using them for our purposes.

00:02:20.770 --> 00:02:21.830
Perfect. Autoruns, obviously,

00:02:22.170 --> 00:02:25.750
we would run this after the malware ran. And, really,

00:02:25.750 --> 00:02:27.550
we could see the same data in Process Monitor,

00:02:27.550 --> 00:02:28.950
but, again, like RegShot,

00:02:28.950 --> 00:02:33.580
we can use this to really see, get a quick idea for what is on the

00:02:33.580 --> 00:02:35.940
system and potentially how the malware is going to maintain

00:02:36.680 --> 00:02:39.480
persistence. Autoruns also is a great tool if you ever have to go

00:02:39.480 --> 00:02:42.589
to a system that you think is compromised. Run Autoruns on it and

00:02:43.110 --> 00:02:44.290
see if it finds anything.

00:02:44.390 --> 00:02:48.550
One of the best things about Autoruns is you can go into Scan Options,

00:02:48.900 --> 00:02:51.160
and if your system is connected to the internet,

00:02:51.170 --> 00:02:53.897
you could tell it to check VirusTotal so it will actually, it will

00:02:53.897 --> 00:02:57.230
upload the cryptographic hash of all the files that it sees to

00:02:57.230 --> 00:02:58.980
VirusTotal to see if there are any detections.

00:02:58.980 --> 00:02:59.380
Obviously,

00:02:59.380 --> 00:03:04.340
you need to be online to do that. It's the hash of the image file attached to

00:03:04.350 --> 00:03:07.470
whatever the registry key is and/or service entry or whatever.

00:03:07.470 --> 00:03:08.380
Yes, exactly.

00:03:08.540 --> 00:03:11.770
And you can also do what's called verify code signatures.

00:03:11.980 --> 00:03:15.570
I'm going to do that. And what it does is you can

00:03:15.570 --> 00:03:17.170
see here under the Publisher tab,

00:03:17.350 --> 00:03:20.200
it will go through and look at all the different files.

00:03:20.410 --> 00:03:21.780
And if it's code signed,

00:03:21.780 --> 00:03:24.760
it would tell you if that code signature matches. Now

00:03:24.760 --> 00:03:27.390
understand just because something has a code signature that

00:03:27.390 --> 00:03:29.300
doesn't match doesn't mean it's malicious.

00:03:29.300 --> 00:03:31.150
That's not the purpose of the code signatures.

00:03:31.200 --> 00:03:34.200
But this is a really quick way to go in and kind of

00:03:34.210 --> 00:03:36.160
exclude things that are already verified,

00:03:36.260 --> 00:03:38.690
which are less likely to be malware.

00:03:38.730 --> 00:03:43.000
Another good thing to go baseline your system. So run these before

00:03:43.000 --> 00:03:45.610
you run the malware, understand what's there first.

00:03:45.620 --> 00:03:47.790
And then you can understand the changes because stuff showing up in

00:03:47.790 --> 00:03:52.080
red right now inside Autoruns doesn't mean it's bad.

00:03:52.080 --> 00:03:53.190
It's just a flag.

00:03:53.920 --> 00:03:56.990
Right, and I would even recommend baselining your tools so you

00:03:56.990 --> 00:04:00.440
understand what your tools are doing to the system. Tools may have

00:04:00.440 --> 00:04:03.240
like an auto‑update feature in there that you need to turn off that

00:04:03.240 --> 00:04:04.590
you may not realize is in there.

00:04:04.640 --> 00:04:08.230
And so if you baseline your tool and you see it all of a sudden connecting

00:04:08.230 --> 00:04:10.790
out to some IP address or on the internet somewhere,

00:04:10.840 --> 00:04:13.230
you know that that's your tool doing it and not the

00:04:13.230 --> 00:04:14.320
malware that you're analyzing.

00:04:14.460 --> 00:04:15.290
Yeah, absolutely.
