WEBVTT

00:00:00.440 --> 00:00:04.270
Okay, so we've got Autoruns and RedShot, what other tools are we using?

00:00:04.340 --> 00:00:07.490
I guess that's a lot of OS stuff that we're monitoring

00:00:07.880 --> 00:00:09.670
changes to, file changes, that kind of thing.

00:00:10.150 --> 00:00:11.450
What network tools do we have?

00:00:11.460 --> 00:00:13.850
‑We're going to look at one more tool, and this is FakeNet.

00:00:13.860 --> 00:00:15.210
We kind of mentioned this before.

00:00:15.210 --> 00:00:19.530
This is the tool that we run on our guest OS here, and it's

00:00:19.530 --> 00:00:22.680
going to basically act like the internet. It's going to

00:00:22.680 --> 00:00:26.550
intercept all of the traffic going out from the computer and

00:00:26.560 --> 00:00:28.340
respond to it so that the malware,

00:00:28.340 --> 00:00:31.930
when it tries to do a DNS request or connect to a web server, FakeNet

00:00:31.940 --> 00:00:36.100
will record that and respond to it so the malware thinks that it's

00:00:36.100 --> 00:00:38.470
online. ‑Excellent, so it's is going to respond to the DNS stuff, it's

00:00:38.570 --> 00:00:40.350
going to respond to HTTP traffic,

00:00:40.540 --> 00:00:43.750
hopefully any other type of C2, command and control, going out or

00:00:43.760 --> 00:00:46.210
maybe a stage or pulling down a stage. ‑Yeah,

00:00:46.220 --> 00:00:48.260
you have to remember, it's not, you know,

00:00:48.340 --> 00:00:49.900
it's not responding intelligently.

00:00:49.900 --> 00:00:53.450
It's not doing something like if the malware tries to go to google.com that

00:00:53.440 --> 00:00:56.600
FakeNet will actually go to Google and return that page, it's going to

00:00:56.600 --> 00:01:01.240
return like a generic page. And it doesn't know specific command and

00:01:01.240 --> 00:01:04.940
control servers for malware, so if malware tries to connect to something

00:01:05.160 --> 00:01:07.470
and it expects a specific response,

00:01:07.470 --> 00:01:09.940
it's not going to get that from FakeNet, but at least we'll see

00:01:09.940 --> 00:01:12.970
that connection and then we can kind of iteratively take our

00:01:12.970 --> 00:01:16.760
steps forward in order to get the malware what it needs to see

00:01:16.760 --> 00:01:18.320
how it behaves each time.

00:01:18.330 --> 00:01:20.890
‑So you can see what it's asking for. Next time we run it,

00:01:20.890 --> 00:01:23.670
we can try to get what it's asking for to give us more information.

00:01:23.780 --> 00:01:26.370
‑I'm going to run FakeNet from the command line.

00:01:26.380 --> 00:01:29.670
You don't need to, but I'm going to do it because I want to give it one option.

00:01:29.680 --> 00:01:33.140
I'm at an administrator command prompt, and so I'm going to run

00:01:33.140 --> 00:01:36.890
FakeNet, and I'm going to give it the ‑l option. I'm going to file

00:01:36.890 --> 00:01:38.900
name, and I'm just going to call it log.txt.

00:01:39.260 --> 00:01:44.380
And what this does is it will tell FakeNet to log all of its data that it's

00:01:44.380 --> 00:01:49.620
seeing to this file, log.txt. By default, it does log all the packets in a

00:01:49.620 --> 00:01:53.800
peek at format so we can go in and see that. But I also want it to log all the

00:01:53.800 --> 00:01:55.880
messages too, just so I have that as well.

00:01:55.880 --> 00:01:56.880
So I'm going to run that.

00:01:57.050 --> 00:01:57.050
‑Okay, great.

00:01:58.240 --> 00:01:59.860
‑And FakeNet is starting up.

00:01:59.870 --> 00:02:01.060
You're going to see some messages.

00:02:01.060 --> 00:02:03.200
You might see some error messages and so on,

00:02:03.370 --> 00:02:07.990
but right away you can see that it is actually working.

00:02:08.000 --> 00:02:11.820
Microsoft saw this new network came up and wanted to do this

00:02:11.820 --> 00:02:14.310
connection test, and FakeNet responded to it.

00:02:14.310 --> 00:02:16.950
And this is exactly what the FakeNet responses look like.

00:02:17.040 --> 00:02:19.550
And, yes, malware, if it's smart,

00:02:19.560 --> 00:02:23.560
it's going to look for these FakeNet responses. But at

00:02:23.560 --> 00:02:25.360
least we know that it's working.

00:02:25.370 --> 00:02:28.030
‑And if you want to go a step further you can customize responses. ‑You

00:02:28.030 --> 00:02:31.170
can, you can. FakeNet has a great configuration file.

00:02:31.180 --> 00:02:34.860
You can go in and customize responses, you can set up specific web servers.

00:02:35.040 --> 00:02:37.810
You can even do things like, FakeNet will even run on Linux.

00:02:38.360 --> 00:02:43.500
There's a Linux version. So you can go and you can modify it and set it up

00:02:43.500 --> 00:02:45.150
into that system setup that we talked about earlier.

00:02:46.710 --> 00:02:49.140
‑So FakeNet is going to simulate the network, we can change

00:02:49.590 --> 00:02:51.810
configs, we can also set up other web servers? ‑Yeah,

00:02:51.820 --> 00:02:56.090
other web servers, other FTP servers. FakeNet even has what it calls

00:02:56.090 --> 00:02:59.990
a dummy listener in it so that if something goes off onto some weird

00:03:00.360 --> 00:03:02.700
port it doesn't know, it'll just kind of throw that to it and it

00:03:02.700 --> 00:03:04.500
will long that connection.

00:03:04.690 --> 00:03:08.980
FakeNet's even smart enough that if the malware or whatever

00:03:08.980 --> 00:03:12.320
program tries to go directly to an IP address and not through

00:03:12.320 --> 00:03:14.200
a hostname, a DNS resolution,

00:03:14.340 --> 00:03:16.910
it will be able to grab that as well and make the malware think

00:03:16.910 --> 00:03:18.550
that it's actually going to the IP address.

00:03:18.640 --> 00:03:19.340
‑Yeah, that's awesome.

00:03:19.340 --> 00:03:23.910
And I see it now too, its logging the process IDs and the service names

00:03:23.910 --> 00:03:27.730
that are doing external connections and TCP connections,

00:03:27.730 --> 00:03:31.630
which is that OS kind of EDR perspective versus the network

00:03:31.630 --> 00:03:34.320
monitoring perspective and linking those two together that really

00:03:34.320 --> 00:03:36.600
helps us identify things in our network.

00:03:36.600 --> 00:03:41.080
And you can see, we talk about baselining, this is exactly what you want to do.

00:03:41.090 --> 00:03:43.990
Like we said, Windows is doing a lot of traffic in the

00:03:43.990 --> 00:03:46.400
background, and that's what we're seeing here.

00:03:46.400 --> 00:03:50.010
And so it's really good to run FakeNet for a little bit and

00:03:50.010 --> 00:03:53.900
look to see what Windows itself is doing so that we can,

00:03:54.090 --> 00:03:55.590
when we do analyze our malware,

00:03:55.600 --> 00:03:59.760
we know what's Windows versus what the malware is. ‑Right, so we're

00:03:59.760 --> 00:04:01.900
running our tools not just to get the EULAs done,

00:04:01.910 --> 00:04:05.550
but also to kind of get some logs down and establish a baseline.

00:04:05.550 --> 00:04:08.340
So in case we're not sure something was supposed to be there or not,

00:04:08.350 --> 00:04:12.960
we can go ahead and refer to our earlier logs or refer to our earlier

00:04:12.960 --> 00:04:14.310
state, because you can save the stuff from ProcMon, right?

00:04:14.660 --> 00:04:15.090
‑Absolutely.

00:04:15.100 --> 00:04:17.490
‑So you can save that down and refer to that as well? Was this

00:04:17.490 --> 00:04:20.760
there before malware? Well, if you don't say that,

00:04:20.760 --> 00:04:21.320
you can't tell.

00:04:21.320 --> 00:04:22.850
So at least like save everything down,

00:04:22.850 --> 00:04:25.350
run everything once, and you're good to go.

00:04:25.420 --> 00:04:26.080
‑Yeah, absolutely.
