WEBVTT

00:00:00.000 --> 00:00:03.990
The first question I have is should I be using a Windows device

00:00:04.000 --> 00:00:07.920
and then virtualizing a Windows VM on top of that? Is that more

00:00:07.920 --> 00:00:13.040
or less dangerous than maybe using Mac or using like a Red Hat

00:00:13.040 --> 00:00:14.050
Linux or something like that?

00:00:15.070 --> 00:00:19.410
So I would say that if you have the ability to do it to have your host OS be

00:00:19.410 --> 00:00:23.210
different than your guest OS. So in other words, if you're running a Windows

00:00:23.210 --> 00:00:25.668
virtual machine and you're going to be running Windows malware within it, use

00:00:25.668 --> 00:00:29.870
Linux as your host OS or use Mac as your host OS, and the reason I say that is

00:00:29.870 --> 00:00:36.230
because it's less likely that malware is going to break into your host OS that

00:00:36.230 --> 00:00:39.620
way from across the virtual network that we'll be setting up or something like

00:00:39.620 --> 00:00:39.900
that.

00:00:39.900 --> 00:00:42.660
So think of it like this. Worst case scenario,

00:00:42.920 --> 00:00:46.740
if your malware that you're analyzing has some zero‑day exploit in it

00:00:46.750 --> 00:00:50.930
against Windows that you're running on a Windows OS virtual machine,

00:00:50.930 --> 00:00:55.030
and your host OS is also Windows, then there's always a chance that it

00:00:55.030 --> 00:00:58.760
could break into your host OS that way depending on how your network

00:00:58.760 --> 00:00:59.650
settings are set up.

00:01:00.200 --> 00:01:04.530
If you have a Mac host OS and a Windows Guest OS,

00:01:05.200 --> 00:01:10.520
it's less likely that malware is going to be cross OS compromising.

00:01:10.900 --> 00:01:13.850
There is malware that does that. They're pretty rare,

00:01:13.850 --> 00:01:16.190
but there's always that possibility.

00:01:16.450 --> 00:01:18.200
But if you have the ability to do it,

00:01:18.200 --> 00:01:20.950
if you have a Mac or you understand how to use Linux and

00:01:20.950 --> 00:01:24.550
you're comfortable with using Linux, I would recommend doing that when you can.

00:01:24.820 --> 00:01:25.670
Absolutely.

00:01:25.670 --> 00:01:29.170
And I was going to get into the various malware. So it's compiled,

00:01:29.170 --> 00:01:32.070
malware is compiled for a specific operating system,

00:01:32.080 --> 00:01:32.400
right?

00:01:32.410 --> 00:01:37.630
Yes. So if you're getting a Windows X86 executable, it's

00:01:37.630 --> 00:01:40.160
not likely going to be compatible to, In fact,

00:01:40.160 --> 00:01:42.460
over‑the‑network a Mac OS. Right. Now, remember,

00:01:43.560 --> 00:01:47.930
too, that when you get into things like .NET programs,

00:01:48.040 --> 00:01:51.180
those are compiled into byte code that could be run

00:01:51.180 --> 00:01:52.570
on multiple operating systems.

00:01:52.570 --> 00:01:56.060
It's the same thing with Java. A piece of Java malware could technically

00:01:56.070 --> 00:02:01.009
run on Windows, on Mac, on Linux as long as that Java interpreter is there.

00:02:01.009 --> 00:02:03.840
And the same thing even now with PowerShell. There're PowerShell

00:02:03.840 --> 00:02:06.120
interpreters for Windows and Mac and Linux.

00:02:06.270 --> 00:02:09.380
So, technically, there could be PowerShell malware that if you

00:02:09.380 --> 00:02:13.845
have the right stuff set up on your host OS that it could also,

00:02:13.845 --> 00:02:15.540
the malware could still run there.

00:02:15.660 --> 00:02:19.350
And that just kind of goes back to I think what we said that your host OS,

00:02:19.660 --> 00:02:20.950
you still have to lock it down,

00:02:20.950 --> 00:02:23.850
and you still have to assume that it could be compromised at some point.

00:02:23.850 --> 00:02:26.422
So don't use your corporate laptop for this. Don's use

00:02:26.422 --> 00:02:29.420
something that has important files on it,

00:02:29.420 --> 00:02:32.200
especially if you're using something, if you're analyzing something like

00:02:33.300 --> 00:02:35.945
ransomware. If somehow that gets out and starts encrypting your host OS, you've

00:02:36.880 --> 00:02:39.310
just lost all your files there. Right, and that's something that's made to

00:02:39.310 --> 00:02:42.600
spread too, so don't be connected to your corporate network. Absolutely not, no.

00:02:42.600 --> 00:02:47.320
Have a separate network segment that you're doing this on. One of the great

00:02:47.320 --> 00:02:51.310
things to do is have a separate wireless network that your virtual machine is

00:02:51.310 --> 00:02:55.425
connected to or your host OS is connected to. Have one of those little MiFi

00:02:55.425 --> 00:02:59.780
devices that you can jump on a cellular network or even just going through your

00:02:59.780 --> 00:03:02.730
cell phone and setting up to be a hot spot that you can turn on and off really

00:03:02.730 --> 00:03:06.990
fast will allow you to have internet access for your virtual machines that the

00:03:06.990 --> 00:03:11.050
malware can access if you want it to, but it would still keep it away from all

00:03:11.050 --> 00:03:12.990
of your other systems. That's a great note.

00:03:12.990 --> 00:03:17.310
So maybe even just as a kind of general rule, if you're looking at

00:03:17.310 --> 00:03:20.030
something that you think might have an interpreted language that's

00:03:20.030 --> 00:03:23.060
being compiled there, then that's where it's a little bit more

00:03:23.060 --> 00:03:25.280
dangerous for cross OS contamination,

00:03:25.290 --> 00:03:28.620
as opposed to something that's been compiled into a

00:03:28.620 --> 00:03:29.290
lower‑level language executable. Yes.
