WEBVTT

00:00:00.040 --> 00:00:00.340
Yes,

00:00:00.340 --> 00:00:03.530
so when we're building this virtual machine, we've got the ISO, the

00:00:03.530 --> 00:00:06.300
Windows ISO, what's a good place to get the Windows ISO from in the

00:00:06.310 --> 00:00:08.200
first place if that's the one we're talking about? Do you have any

00:00:08.200 --> 00:00:09.460
good recommendations for that?

00:00:09.470 --> 00:00:12.700
Sure, you can go out to, if you have an MSDN subscription,

00:00:12.710 --> 00:00:14.220
you can download it from there.

00:00:14.420 --> 00:00:19.650
If you don't, and you need to go out and get a limited version of Windows,

00:00:19.840 --> 00:00:24.420
you can go to Microsoft and download trial copies of

00:00:24.420 --> 00:00:27.930
Windows. They're limited for 30 to 90 days, and you can

00:00:27.930 --> 00:00:29.790
renew those, but at least they're free,

00:00:29.790 --> 00:00:33.930
and you can get the modern versions of Windows to test malware out on. And you

00:00:33.930 --> 00:00:36.540
just download them and install them into your VM. Excellent.

00:00:37.690 --> 00:00:39.830
So some malware,

00:00:39.840 --> 00:00:42.940
a lot of current malware is concerned about whether it's on a real machine or

00:00:42.940 --> 00:00:46.790
not. Right. And we need to make the machine look real, and even from, we talked

00:00:46.800 --> 00:00:51.440
before about it's more common that you're using horizon viewers in desktop or

00:00:51.440 --> 00:00:52.610
something like that in your enterprise.

00:00:52.610 --> 00:00:55.060
So it's not necessarily looking for just a virtual machine,

00:00:55.060 --> 00:00:57.500
but maybe an actual production machine. So your

00:00:57.500 --> 00:00:59.270
desktop could be a virtual machine.

00:00:59.440 --> 00:01:02.880
But if it only has 1 core and 1 GB of RAM, that's not really realistic.

00:01:02.890 --> 00:01:03.270
Yeah,

00:01:03.280 --> 00:01:06.580
exactly. A lot of malware, they have techniques in there where

00:01:06.580 --> 00:01:10.480
they look to see how many CPUs does the machine that it's on

00:01:10.480 --> 00:01:12.410
have? How much RAM does it have?

00:01:12.420 --> 00:01:14.340
How big is the disk drive?

00:01:14.440 --> 00:01:18.700
And if it's too small, if it's smaller than what it expects,

00:01:18.870 --> 00:01:22.810
then it knows that it's either on a system that is being analyzed because we

00:01:22.810 --> 00:01:26.750
may not give a virtual machine as many resources as a normal machine would

00:01:26.750 --> 00:01:29.440
have, or it's on a system that has so few resources,

00:01:29.440 --> 00:01:31.190
why would it want to compromise it anyway, so there's

00:01:31.190 --> 00:01:32.950
probably nothing on there that it wants.

00:01:33.210 --> 00:01:36.390
So as we go in before we even install our operating system,

00:01:36.420 --> 00:01:38.580
we're going to want to configure the hardware for the

00:01:38.580 --> 00:01:40.840
virtual machine to look as real as possible.

00:01:41.030 --> 00:01:44.830
And so the way that we do that is you want to give it at least 4 GB of RAM,

00:01:44.880 --> 00:01:49.180
probably 8 GB of RAM because that's kind of standard now. You want to make

00:01:49.180 --> 00:01:52.460
sure that the number of CPUs that you configure for your virtual machine to

00:01:52.460 --> 00:01:55.520
have at least two CPUs with two cores each.

00:01:55.530 --> 00:02:00.100
And just kind of go in and look at all the other settings. A lot

00:02:00.100 --> 00:02:04.710
of virtual machines start off by having a floppy disk connected

00:02:04.710 --> 00:02:06.480
to the system still. Take that off.

00:02:06.490 --> 00:02:10.560
I haven't seen a computer come with a floppy disk drive in at least a decade,

00:02:10.560 --> 00:02:11.540
if not longer.

00:02:11.540 --> 00:02:16.404
So that could be another check that malware does to see if these commonly

00:02:16.404 --> 00:02:20.310
seen things in virtual machines are on your system.

00:02:20.430 --> 00:02:21.610
Yeah, that's a really good note.

00:02:22.180 --> 00:02:23.605
Same thing like I know within VMWare and probably within VirtualBox

00:02:23.605 --> 00:02:27.170
also, there're different driver sets you can use for your NICs. Is

00:02:28.130 --> 00:02:29.540
that something else we're going to look at?

00:02:29.550 --> 00:02:32.220
Yeah, we'll look at how we can change some of the virtual machine

00:02:32.220 --> 00:02:34.430
settings to kind of hide from these techniques.

00:02:34.430 --> 00:02:37.900
And, we'll actually use a tool, a really great tool called Pafish,

00:02:37.910 --> 00:02:41.050
which is going to kind of go through some of these checks and

00:02:41.050 --> 00:02:42.810
show us whether or not it detects those,

00:02:42.810 --> 00:02:45.180
and so we can tell if we're hiding from the malware that's

00:02:45.180 --> 00:02:46.950
using these checks. So that's really neat.
