WEBVTT

00:00:00.760 --> 00:00:03.715
So detonating these things inside virtual machines, that

00:00:03.715 --> 00:00:05.520
gives us that quarantine capability.

00:00:06.280 --> 00:00:09.600
There're VM escapes and sandbox escapes that are published,

00:00:09.600 --> 00:00:11.950
and I understand that sometimes it's talking about the Window

00:00:11.950 --> 00:00:14.820
systems and sandbox browsers and that kind of thing that's

00:00:14.820 --> 00:00:16.950
kind of underlying kernel activity,

00:00:17.380 --> 00:00:20.150
but it can also apply to escaping virtual machines into a host. Right.

00:00:20.230 --> 00:00:22.300
So is that something that we need to be concerned about as well?

00:00:22.310 --> 00:00:23.680
You do need to keep that in mind.

00:00:23.980 --> 00:00:27.430
There are exploits available for virtual machine software,

00:00:27.430 --> 00:00:31.540
where the malware can try to escape from the guest into your host,

00:00:31.540 --> 00:00:33.810
and obviously you want to avoid that.

00:00:34.000 --> 00:00:35.870
So the things that I'll say about that is,

00:00:36.010 --> 00:00:41.000
first off, whatever system you're using to run your virtual machines on,

00:00:41.330 --> 00:00:44.700
don't make that a system that you care about. Don't make this your

00:00:44.700 --> 00:00:47.520
corporate laptop with all of your sensitive documents on it.

00:00:47.890 --> 00:00:52.510
Don't make it some system that if it gets completely compromised

00:00:52.510 --> 00:00:54.970
with malware that you can't just re‑image it.

00:00:55.170 --> 00:00:58.140
The second is really the virtual machine escapes that I've

00:00:58.140 --> 00:01:01.200
seen in malware tend to be pretty old,

00:01:01.210 --> 00:01:04.970
and they all tend to be based on exploits that are available in

00:01:04.970 --> 00:01:06.830
various pieces or versions of VM software,

00:01:08.400 --> 00:01:10.880
especially the virtual machine tools that typically

00:01:10.880 --> 00:01:12.300
get installed into the guest OS.

00:01:12.960 --> 00:01:15.420
So as long as you keep your systems up to date and your

00:01:15.420 --> 00:01:17.750
virtual machine software up to date, you should be okay.

00:01:18.120 --> 00:01:18.810
Absolutely.

00:01:18.810 --> 00:01:21.300
I've seen a ton of stuff published even for Workstation Pro.

00:01:21.470 --> 00:01:21.770
Actually,

00:01:21.770 --> 00:01:24.290
when I went to the 1903 Update on Windows, it wouldn't let

00:01:24.290 --> 00:01:26.300
me keep, and maybe that's a brand thing,

00:01:26.310 --> 00:01:26.540
too,

00:01:26.540 --> 00:01:30.040
but it wouldn't let me keep Workstation Pro 14 on my device as

00:01:30.040 --> 00:01:31.930
I upgraded. I actually had uninstall it,

00:01:31.940 --> 00:01:34.730
install a newer version of Workstation Pro because it said it had

00:01:34.730 --> 00:01:37.610
vulnerabilities in it. So that's kind of interesting, and I guess

00:01:37.610 --> 00:01:39.290
plus one for Microsoft for carrying about.

00:01:39.300 --> 00:01:40.040
Oh, yeah.

00:01:40.050 --> 00:01:43.510
Helping you, making sure that you're not going to accidentally

00:01:43.520 --> 00:01:45.640
compromise yourself because you have vulnerable software.

00:01:45.650 --> 00:01:46.250
Right.

00:01:46.280 --> 00:01:47.510
So that was pretty cool.

00:01:47.520 --> 00:01:50.390
So another thing, use a hypervisor, use one you're

00:01:50.390 --> 00:01:52.660
comfortable with, and use one that's updated.

00:01:52.670 --> 00:01:54.390
Yeah, make sure you keep it up the date.

00:01:54.400 --> 00:01:58.160
Obviously, don't go downloading pirated software because

00:01:58.160 --> 00:01:59.770
those could have back doors in it as well.

00:02:00.050 --> 00:02:02.590
And that's just going to mess up your system to begin with.

00:02:03.560 --> 00:02:07.190
But just make sure, the biggest thing is make sure that your tools

00:02:07.190 --> 00:02:10.630
and your virtual machine software is up to date.
