WEBVTT

00:01.020 --> 00:06.660
Hey Guys welcome to memory analysis with volatility in the previous video we introduce the volatility

00:06.660 --> 00:09.130
framework this video.

00:09.160 --> 00:13.750
We're going to take a look at how to use the program and it's plug ins to analyze the sample memory

00:13.750 --> 00:17.330
image acquired in the last video which was memory acquisition.

00:17.380 --> 00:22.990
To begin we can verify our Windows memory image and have more info about it with the image info plugin

00:23.230 --> 00:29.350
we execute volatility specifying the f option with the name of the memory image and the name of the

00:29.370 --> 00:31.220
Plug-In image info.

00:31.360 --> 00:37.450
The image in Bill plugin displays info about the image including the OS type and version as you could

00:37.450 --> 00:44.250
see the output confirms that it's a Windows 7 64 bit image so we can use the relative profile when 7

00:44.260 --> 00:51.790
Sep 1 x 64 we don't obviously use all the available plugins for the sake of brevity but we'll only show

00:51.790 --> 00:53.900
most relevant ones.

00:53.920 --> 00:58.750
First thing we'd like to do is enumerate the active processes that were running on the target when we

00:58.750 --> 01:00.400
acquired the memory image.

01:00.520 --> 01:03.880
To accomplish this we can use the list plugin.

01:03.940 --> 01:09.430
Now we specify the profile to use with the image with the profile option that we paste the name of the

01:09.430 --> 01:10.220
profile.

01:10.270 --> 01:15.520
Then the f option with the name of the image and the list plug in the output shows info like the name

01:15.520 --> 01:20.150
of the process process id parent id and the start time.

01:20.200 --> 01:24.380
The output can also be redirected to a file used in the output file option.

01:26.550 --> 01:31.760
Also hidden or terminated processes can be enumerated with the scanned plugin.

01:32.010 --> 01:37.050
The DL list plugin displays all the DL L's referenced by all the processes.

01:37.140 --> 01:43.950
We can narrow the search specifying the ID option volatility dash dash profile equals Win 7 Sep 1 x

01:43.950 --> 01:55.350
64 dash f Win 7 mem DL elist dash dash P ID 24 28 we specified the ID of the win PM tool used to image

01:55.350 --> 01:56.370
the memory.

01:56.370 --> 02:02.960
This outputs all the DL relative to the specific processes to display the kernel modules and drivers.

02:02.970 --> 02:08.570
We use the modules plugin if we want to display also the hidden or residual modules.

02:08.620 --> 02:16.880
There's a mod scan plugin the pricky plugin allows us to see the value of cached registry keys.

02:17.100 --> 02:24.130
We have to also specify capital K option for the name of the registry key the output displays the subcase

02:24.220 --> 02:25.720
and its values.

02:25.840 --> 02:33.990
In this case it's only one the NetScan plugin enumerates the network connections on the target.

02:34.070 --> 02:40.100
For example in the output we can observe the TCAP connection initiated by the netcat process in order

02:40.100 --> 02:43.730
to transfer the memory image from the target to the forensic workstation.

02:44.030 --> 02:50.240
If the target is Windows XP or 2003 we must use connection's instead of NetScan.

02:50.480 --> 02:54.500
Here's also a plugin that displays the IP cache or history.

02:54.500 --> 03:01.520
Finally we scan the image for of rules that could reveal malware running on the target Jaar is a tool

03:01.520 --> 03:07.640
to identify and classify malware based is a tool to identify and classify malware based on rules that

03:07.640 --> 03:09.900
include sets of signatures.

03:09.920 --> 03:18.730
These rules can be downloaded from the Jaar repository at HTP colon slash slash get how dotcom slash

03:18.730 --> 03:20.640
Yerra slash rules.

03:20.780 --> 03:22.800
They're divided into various categories.

03:22.840 --> 03:25.680
The plug in to use volatility is your iscan.

03:25.960 --> 03:30.560
We must specify the path of the Jaar rules file to use the scan option.

03:30.760 --> 03:36.760
For example if you want to scan the image for signatures of eks Zeus malware we must specify the corresponding

03:36.760 --> 03:38.740
Jaar rule file.

03:38.740 --> 03:43.120
In this case no signatures of the malware are found on the memory image.

03:43.120 --> 03:49.660
We can also scan only a specific process with the ID option or the kernel memory with the kernel option.

03:49.780 --> 03:54.460
For more info on how to use plug ins to extract and examine several kinds of artifacts from a memory

03:54.460 --> 04:00.250
image a very useful reference is the volatility Chee-Chee which can be downloaded from the volatility

04:00.250 --> 04:01.250
wiki page.

04:01.260 --> 04:09.410
H s colon slash slash get hubcap slash volatility foundation slash volatility slash wiki.

04:09.580 --> 04:14.890
Great job in this section we covered some of the most relevant volatility plug ins to analyze a Windows

04:14.890 --> 04:20.320
7 memory image in the next section we're going to introduce network forensics and cover the capturing

04:20.350 --> 04:22.680
and analysis of network data traffic.
