WEBVTT

00:00.450 --> 00:06.840
Hey everyone welcome to our next section memory forensics in this section we're going to introduce the

00:06.840 --> 00:13.050
most important concepts of virtual memory and memory forensics will introduce memory acquisition techniques

00:13.050 --> 00:17.190
and tools and show a practical example of acquiring the target system RAM.

00:17.190 --> 00:22.170
Finally we'll look at the bold Tildy framework and cover the analysis of a memory image.

00:22.170 --> 00:25.400
Now we move on to the introduction to memory forensics.

00:25.410 --> 00:30.080
We're going to take a look at memory forensics and the fundamental theory behind virtual memory management

00:30.240 --> 00:32.160
and paging page files.

00:32.160 --> 00:37.530
Hibernation files and crash stubs in the second video of our first section brief introduction to digital

00:37.530 --> 00:38.370
forensics.

00:38.400 --> 00:43.900
We saw that forensic evidence can be divided into two types volatile and nonvolatile.

00:43.920 --> 00:50.280
So far we've covered the acquisition or imaging then the analysis of nonvolatile data and analyze volatile

00:50.280 --> 00:51.930
data in this specific case.

00:51.990 --> 00:57.510
RAM memory from live running systems memory forensics is still a field of development that has yet to

00:57.510 --> 00:58.740
reach full maturity.

00:58.740 --> 01:02.480
It's a fundamental part of the instant response investigation process.

01:02.490 --> 01:08.310
For example after the detection of an intrusion or a malware infection in these situations it's very

01:08.310 --> 01:13.230
important to acquire volatile data that otherwise could be lost when the system is shut down.

01:13.230 --> 01:19.560
For instance a list of running system services and user processes currently loaded drivers and modules

01:19.800 --> 01:23.430
even Network Connections routing and HRP tables.

01:23.490 --> 01:28.680
All of this data can be collected using live response tools designed for the target system but can also

01:28.680 --> 01:31.200
be recovered analyzing a memory image.

01:31.350 --> 01:36.900
Furthermore evidence such as user's password and decrypted data encryption keys and memory resident

01:36.900 --> 01:44.190
injected code fragments exist only in RAM for example advanced violence or memory only resident malware

01:44.250 --> 01:50.070
does not create files on the disk so they can only be detected from the analysis of memory before diving

01:50.070 --> 01:52.190
into memory acquisition and analysis.

01:52.200 --> 01:55.440
It's important to recall how the main system memory is structured.

01:55.440 --> 01:59.580
Modern operating systems use virtual memory to manage the main memory.

01:59.580 --> 02:04.560
Virtual Memory is an abstraction that allows to overcome the size limits of the physical memory and

02:04.560 --> 02:08.180
manages the mapping between logical to physical memory addresses.

02:08.220 --> 02:14.280
Each process has its own private virtual address space which is divided into chunks called pages which

02:14.280 --> 02:16.950
are mapped to page frames in physical memory.

02:16.950 --> 02:20.680
The mapping between pages and page frames can be found in the page table.

02:20.700 --> 02:26.240
The page table also keeps track whether pages are memory resident or not as we could see in this diagram.

02:26.280 --> 02:31.140
When the entire virtual memory space is larger than the available physical memory pages are swapped

02:31.140 --> 02:34.230
to the disk or a page file or a swap partition.

02:34.320 --> 02:39.090
According to page replace the algorithm for example least recently used algorithm.

02:39.150 --> 02:44.460
This way a larger number of processes could be resident in memory and run at a given time even at the

02:44.460 --> 02:45.950
physical RAM is full.

02:45.990 --> 02:51.360
When a process refers a virtual address belonging to a swopped page a page file is generated and the

02:51.360 --> 02:54.840
memory reads the page from the disk and loads it in memory.

02:54.840 --> 03:00.870
Updating the page table window swaps pages to the page file DOCSIS file located in the main system drive

03:01.020 --> 03:07.350
while Unix and Linux use the swap partition analysis of the page file or the swap partition can be complemented

03:07.350 --> 03:12.360
with that of the captured RAM to obtain a complete view of the entire virtual memory.

03:12.360 --> 03:18.510
Another source of evidence is the hibernation file where an OS saves the full contents of RAM before

03:18.510 --> 03:20.640
going into hibernation on Windows.

03:20.700 --> 03:25.050
This file is high profile DOCSIS and it's located in the main system drive.

03:25.050 --> 03:31.440
While Linux generally uses the Soie partitions but can also use a swap file sometimes crash dumps generated

03:31.440 --> 03:33.760
by the OS when an application crashes.

03:33.930 --> 03:36.330
Could be of interest to the forensic examiner.

03:36.360 --> 03:41.580
They could be either full kernel memory dumps or small dumps that contain more limited sets of data.

03:41.760 --> 03:47.700
Well done in this video we introduced the fundamental concepts of memory forensics and virtual memory.

03:47.760 --> 03:52.860
In the next video we're going to see how to acquire a memory image with various acquisition methods

03:52.860 --> 03:57.240
and tools and showed example of memory acquisition with wind penmen.
