WEBVTT

00:00:00.340 --> 00:00:02.760
So the first thing we're concerned about is we're dealing with a live malware,

00:00:03.170 --> 00:00:05.770
right? We have something‑‑‑or something that we think is my live malware,

00:00:05.770 --> 00:00:08.370
and we want to detonate it inside a real environment. Yes.

00:00:08.510 --> 00:00:10.740
So how are we making sure that we're not infecting other

00:00:10.740 --> 00:00:13.670
systems, not infecting our system, or the main system we're using?

00:00:13.680 --> 00:00:14.660
How we quarantining?

00:00:15.380 --> 00:00:18.350
So the way that we're going to do that is we use virtual machine software.

00:00:18.630 --> 00:00:22.270
Now virtual machine software allows you to run a second operating system

00:00:22.480 --> 00:00:26.440
underneath what's called your host OS. And the great thing about virtual

00:00:26.440 --> 00:00:29.460
machines is you have a complete operating system,

00:00:29.460 --> 00:00:32.549
a complete computer within another computer that you can do

00:00:32.549 --> 00:00:35.330
whatever you want to. The best thing about virtual machine

00:00:35.330 --> 00:00:37.270
software is called snapshots.

00:00:37.560 --> 00:00:41.460
Snapshots allow you to take basically a picture of the operating

00:00:41.460 --> 00:00:45.600
system or that guest OS at a point in time.

00:00:45.770 --> 00:00:49.790
And what that does is it allows you to set up your system in a certain

00:00:49.790 --> 00:00:53.270
way and then save it so you can immediately jump back to that point in

00:00:53.270 --> 00:00:56.050
time and immediately begin your analysis.

00:00:56.140 --> 00:00:59.930
If you infect your virtual machine with a specific piece of malware, you

00:00:59.930 --> 00:01:03.450
can snapshot that at certain points in time, or even if you want to

00:01:03.450 --> 00:01:07.290
install specific pieces of software, let's say you want to do analysis on

00:01:07.530 --> 00:01:12.670
document malware, you might install Office 2010 in one snapshot and then

00:01:12.670 --> 00:01:18.491
Office 2016 in another and then the Office 365 version in a third one.

00:01:18.491 --> 00:01:21.200
Snapshotting each of these allows you to jump to all those different

00:01:21.200 --> 00:01:24.770
pieces of software without having to go through and reinstall it each

00:01:24.770 --> 00:01:25.050
time.

00:01:25.050 --> 00:01:27.110
It just makes analysis much, much faster.

00:01:27.140 --> 00:01:28.310
It's not just for quarantine.

00:01:28.310 --> 00:01:32.010
It's also for software versioning and discovering how that's going to work in

00:01:32.010 --> 00:01:35.580
different environments. Right, and you might find that malware works

00:01:35.590 --> 00:01:39.980
differently when different software is installed or when different patch levels

00:01:39.980 --> 00:01:42.380
are set up or different settings are available.

00:01:42.380 --> 00:01:45.090
And so you may want to have all those readily available to you

00:01:45.090 --> 00:01:48.030
so you can kind of jump in and see how things work. So it's the

00:01:48.030 --> 00:01:54.340
same base machine, same base OS, one license of (inaudible). Yeah, honestly,

00:01:54.340 --> 00:01:57.160
you don't even need to go out and buy a license of

00:01:57.160 --> 00:01:58.990
Windows or a new version of Windows.

00:01:59.200 --> 00:02:01.850
There are free versions that you can download from Microsoft,

00:02:01.860 --> 00:02:04.340
they're time limited, but you can download them,

00:02:04.340 --> 00:02:07.320
set them up, snapshot them, and always kind of revert back to them.

00:02:07.470 --> 00:02:10.889
Absolutely. With the snapshotting, is that vendor specific,

00:02:10.889 --> 00:02:14.450
or is there any benefit in certain snapshots with VMWare versus

00:02:15.110 --> 00:02:18.280
VirtualBox versus Hyper‑V or anything like that?

00:02:18.290 --> 00:02:22.270
So most of the major virtual machine software packages like

00:02:22.270 --> 00:02:25.430
VMWare and VirtualBox, they support snapshotting.

00:02:25.660 --> 00:02:27.840
You just want to make sure that whatever you choose,

00:02:28.000 --> 00:02:29.930
that it does support snapshotting.

00:02:30.020 --> 00:02:33.400
So VMWare, for example, has a number of different packages.

00:02:33.400 --> 00:02:35.470
There's VMWare Workstation.

00:02:35.470 --> 00:02:40.330
There's VMWare ESX. There's VMWare Player.

00:02:41.160 --> 00:02:44.850
All those except from VMWare Player support snapshotting.

00:02:44.850 --> 00:02:49.270
So you want to make sure that whatever you use works with that, has that

00:02:49.270 --> 00:02:52.410
ability for you to go in and do the snapshots because it is very important

00:02:52.410 --> 00:02:56.470
because, otherwise, you're going to be going in and reinstalling everything

00:02:56.470 --> 00:02:59.415
every single time, and it's just going to slow down your analysis process.

00:02:59.415 --> 00:03:03.940
When you do those snapshots, it's actually creating a change disk that adds on

00:03:03.940 --> 00:03:09.230
to the main file‑based hardware disk for that virtual machine, correct? Is

00:03:09.230 --> 00:03:13.260
there any analysis because those changes‑‑‑say you take a snapshot and then

00:03:13.260 --> 00:03:18.040
detonate the malware and then use that change disk as what has changed on the

00:03:18.460 --> 00:03:22.395
device. Is there any analysis that's available to use that change disk as an

00:03:22.395 --> 00:03:24.590
identifier for what's changed since you detonated malware?

00:03:24.920 --> 00:03:27.420
There are. There are a number of different tools that you can use

00:03:27.420 --> 00:03:31.230
to kind of look at the changes between the snapshots that you've

00:03:31.240 --> 00:03:35.900
made, and it does allow you to go in there and take multiple

00:03:35.900 --> 00:03:37.850
snapshots as you go through.

00:03:38.180 --> 00:03:40.340
But some of the tools that we're talking about will actually just make

00:03:40.340 --> 00:03:42.250
it a little bit easier for us to do it on the fly.

00:03:42.340 --> 00:03:42.930
Okay, great.

00:03:42.930 --> 00:03:45.310
So we're not just relying on the snapshots as a picture

00:03:45.490 --> 00:03:47.090
for what happened before or after.

00:03:47.180 --> 00:03:48.610
We're going to have other tools that we use for

00:03:49.120 --> 00:03:49.120
analysis as well, right? Exactly.
