WEBVTT

00:00.820 --> 00:03.370
Hi and welcome to our next section.

00:03.400 --> 00:09.460
Acquiring forensic images in this section we introduce some fundamental concepts about forensic imaging

00:09.730 --> 00:17.770
and then cover to command line tools DCF Beldi and DC 3D and a graphical user interface program.

00:17.860 --> 00:22.750
Guy maigre designed to acquire forensic images.

00:22.750 --> 00:28.170
Now we move onto the first video of the section that deals with a brief introduction to forensic imaging.

00:28.330 --> 00:32.590
In this video we explain hardware and software right blocking techniques.

00:32.770 --> 00:39.430
The various forensic image formats and hard disk physical structure and geometry together with special

00:39.940 --> 00:42.900
features that are relevant for digital forensics.

00:43.120 --> 00:49.150
Mainly the device configuration orderly and their host protected area forensic image acquisition can

00:49.150 --> 00:54.580
be defined as the process of acquiring a forensically sound copy or image of the device or media to

00:54.580 --> 01:00.910
analyze the image shall be forensically sound that is will be able to verify that it's really an exact

01:00.910 --> 01:05.560
copy of the original and that the procedure to acquire it is well documented.

01:05.590 --> 01:11.140
The forensic imaging phase is very important in the digital forensic process because the acquired image

01:11.140 --> 01:17.010
file is the basis from which examiners extract and analyze data to find the evidence.

01:17.020 --> 01:22.120
So if the image is not acquired correctly all the subsequent work is in vain.

01:22.480 --> 01:28.270
Typically speaking a forensic image is a bit by bit copy of the media to acquire it differs from a single

01:28.270 --> 01:34.240
clone of the file system as it's a copy of all the rural sectors of the disk or partition when acquiring

01:34.240 --> 01:34.780
an image.

01:34.810 --> 01:39.560
It must be ensured that no rights are made at all to the original media.

01:39.910 --> 01:45.460
Moreover we must use cryptographic caching to verify the integrity of the image and any input output

01:45.490 --> 01:51.820
errors must be logged as prescribed by the newest computer forensic tool testing program before collecting

01:51.820 --> 01:53.770
any drives or media to be analyzed.

01:53.770 --> 01:58.840
It's a good practice to take photos and notes about them as well as the scene and suspects computer

01:59.380 --> 02:03.760
in this and the following video we refer to imaging of a hard disk.

02:03.760 --> 02:09.460
We refer to the imaging of a hard disk as it still the most common case when dealing with desktop computers

02:09.550 --> 02:11.080
and laptops.

02:11.080 --> 02:14.710
There are basically two scenarios when it comes to acquiring a forensic image.

02:14.710 --> 02:20.500
The first is when the hard drive is not removed and second is when removed from the suspect's computer

02:20.950 --> 02:25.450
in the first case which has a beautiful example when a hard drive could not be physically removed or

02:25.450 --> 02:33.880
during incident response we must use a forensic Live-CD like Linux to acquire an image a live CD shall

02:33.880 --> 02:38.950
be booted to the so-called forensic mode that prevents the OS from automatically mounting any attached

02:38.950 --> 02:42.850
drives and does not make use of the swap partition when booting.

02:42.910 --> 02:47.530
If you want more information about the Kalli Linux forensic mode refer to the official documentation

02:47.590 --> 02:49.680
on the Kallie Linux web site.

02:49.750 --> 02:55.180
In the second case when their drive is being removed we must physically attach it to the forensic workstation

02:55.390 --> 03:00.940
using a right blocking mechanism right blocking mechanisms could be implemented both in hardware and

03:00.940 --> 03:06.570
software hardware right blockers are devices used to connect the drive to the forensic workstation that

03:06.820 --> 03:10.490
that block any right attempts from the operating system to the drive.

03:10.720 --> 03:15.580
We could have various types of connectors to deal with different types of drives hardware and blockers

03:15.580 --> 03:21.160
are usually quite expensive but their use is recommended because they're more reliable than software

03:21.160 --> 03:22.700
write block techniques.

03:22.750 --> 03:27.370
An example of the hardware right block is shown in this photo with a hard disk attached through the

03:27.370 --> 03:34.330
Satta connector software right blogging is quite a controversial topic indeed simply mounting a drive

03:34.330 --> 03:39.670
on Linux as read only does not guarantee against possible writes that kernel drivers could make to the

03:39.670 --> 03:44.430
device that kernel drivers could make to the device to solve this issue.

03:44.440 --> 03:46.760
Various techniques have been developed.

03:47.080 --> 03:52.720
The most effective one seems the most effective one is a solution based on a kernel patch that blocks

03:52.720 --> 03:56.280
the write commands issued to the drive and the device driver level.

03:56.410 --> 04:02.350
So at the software lowest level as it's a kernel patch The drawback is that we have to recompile the

04:02.350 --> 04:03.660
kernel to apply it.

04:03.700 --> 04:07.520
For more information about this patch refer to the link on get hub.

04:07.750 --> 04:10.070
We've seen that in the image acquisition process.

04:10.120 --> 04:13.440
All the bytes of a disk are copied into an image file.

04:13.480 --> 04:19.500
There are different forensic image file formats most common in an open source forensics is the raw image.

04:19.600 --> 04:22.710
That is a mere duplicate of all sectors of a hard disk.

04:22.720 --> 04:28.570
Raw images contain no additional metadata apart from most of the file systems unlike the other forensic

04:28.570 --> 04:29.770
formats.

04:29.770 --> 04:32.650
We're going to use this format during the course.

04:32.650 --> 04:39.040
Raw images can be obtained with tools like Deedy data dump which copy stream of bytes from the input

04:39.040 --> 04:41.720
source drive to the output destination file.

04:41.770 --> 04:47.890
The limitation of DD is the limitation of DD is it lacks certain features that are required for forensics

04:48.090 --> 04:54.940
such as cryptographic caching and error handling cryptographic caching error handling and logging in

04:54.940 --> 05:01.410
the next video we're going to see some variants of DD specifically designed for forensics another open

05:01.410 --> 05:06.470
source forensic format is the advanced forensic format created by Garfinkel.

05:06.760 --> 05:12.930
This format supports compression and encryption of the images and a software package called a f f lib.

05:13.180 --> 05:16.680
It's been developed to convert and manage AFFO images.

05:16.710 --> 05:18.720
There are also proprietary formats.

05:18.730 --> 05:26.860
Most important are the expert witness format used by software and case and smart used by T.K. both support

05:26.860 --> 05:30.820
compression and encryption of images and about the expert witness format.

05:30.910 --> 05:37.850
An open source library and related tools have been created to cover and manage DWF images before proceeding

05:37.850 --> 05:39.080
into the hands on part.

05:39.100 --> 05:45.160
It's useful to recall the hard disk physical and logical addressing hard disk is formed by various platters

05:45.310 --> 05:50.490
each having two heads each having two heads that read and write data on its sides.

05:50.620 --> 05:56.470
Each side is subdivided into many constructs circular strips called tracks all the corresponding tracks

05:56.530 --> 05:59.260
aligned through the stack of platters form a cylinder.

05:59.260 --> 06:02.560
Each track is subdivided into units called sectors.

06:02.590 --> 06:09.250
A sector is the smallest addressable disk unit traditionally sector size is 512 bytes.

06:09.340 --> 06:16.600
But newer disks have moved to the advanced format for k n where the sector size is 4000 bytes though

06:16.640 --> 06:19.870
still providing 512 bytes sector emulation.

06:20.140 --> 06:25.850
Traditionally physical blocks or sectors are located using the cylinder head sector addressing scheme.

06:25.960 --> 06:31.300
Though it's now outdated and replaced by logical block addressing it still used to specify the hard

06:31.300 --> 06:37.390
disk geometry logical block addressing scheme is a linear addressing scheme where sectors are located

06:37.390 --> 06:38.420
by 48 bits.

06:38.440 --> 06:41.590
Integer indexes integer indexes.

06:41.590 --> 06:47.530
There's also a formula to convert the C-H s addresses to LBA addresses in this picture we could see

06:47.530 --> 06:53.410
an example of why a disk geometry specified in cylinder head sector together with the number of LBA

06:53.410 --> 06:55.430
sectors available.

06:55.510 --> 07:00.580
There are two features that are unknown to the majority of the users but are very important for a digital

07:00.580 --> 07:01.700
investigation.

07:01.720 --> 07:07.930
The device configuration overlay and host protected area device configuration overlay was introduced

07:07.930 --> 07:14.230
in the basic standard to allow vendors to configure reported disk capacity and features host protected

07:14.230 --> 07:20.830
area was introduced in a for standard to hide certain portions of the disk to an operating system and

07:20.830 --> 07:27.850
reserve them to store for example recovery data and so on recovery data and so on while designed and

07:27.850 --> 07:29.430
used for legitimate purposes.

07:29.500 --> 07:36.220
These features have also been abused to store and hide malware and any kind of illicit data both device

07:36.220 --> 07:40.080
configuration overlay and home protected area could be detected and removed.

07:40.120 --> 07:42.490
Using a tool called HD parm.

07:42.490 --> 07:44.800
Now we're going to briefly show it's usage.

07:44.800 --> 07:50.860
Suppose that the target disk has been attached to the forensic workstation on Linux hard disks identified

07:50.860 --> 07:59.950
by block device files under the dev directory in the format for example slash dev slash SDH X SDD SDC

08:00.010 --> 08:01.030
etc..

08:01.030 --> 08:06.340
Suppose our disk is identified by STA 1 to have more information about the disk.

08:06.400 --> 08:08.410
We can run the command HD par

08:15.530 --> 08:15.980
in it.

08:16.030 --> 08:21.880
We could see information like the model number serial number firmware revision number of cylinders heads

08:21.940 --> 08:23.710
and sectors.

08:23.710 --> 08:29.980
Also the LBA user addressable sectors and scrolling down the device configuration overlay feature set

08:33.450 --> 08:36.110
to see more info on device configuration overlay.

08:36.150 --> 08:37.320
We can use the command

08:42.970 --> 08:46.960
it shows for example the whole protected area is set on the disk.

08:46.960 --> 08:52.000
There's another option of HD parm tool that allow us to see more information about the whole protected

08:52.000 --> 08:55.660
areas set about the host protected areas set on the disk.

08:55.810 --> 09:15.990
And it's the an option hashtag HD parm dash n slash dev slash sta.

09:16.060 --> 09:20.800
We could see that the most protected area is enabled on the disk and the first number is the maximum

09:20.800 --> 09:23.950
number of sectors that are visible to the operating system.

09:25.480 --> 09:29.780
While the second number is the total real number of sectors on the disk.

09:29.980 --> 09:34.540
So the difference between the two numbers are the number of sectors that are held between the operating

09:34.540 --> 09:35.190
system.

09:35.440 --> 09:44.360
And so to the user but are used to store our kind of data to remove the hosted protected area we can

09:44.360 --> 09:50.150
issue the command with the same option and followed by the total number of sectors of the disk and this

09:50.150 --> 09:55.730
command is the set the total number of sectors available to the operating system to be real total number

09:55.730 --> 10:01.640
of sectors and so disabling the whole protected area and allowing us to acquire the total real numbers

10:01.640 --> 10:02.570
of sectors.

10:03.690 --> 10:08.300
The total real number of sectors that is the full capacity of the disk.

10:08.520 --> 10:11.040
So we tied the total number of sectors here

10:15.980 --> 10:18.010
to make this change permanent to the reboot.

10:18.110 --> 10:28.460
We must prepend the number with letter P.

10:28.480 --> 10:33.340
Now we could see in the output that the number of sectors visible to the OS is equal to the number of

10:33.340 --> 10:41.040
real sectors available in the disk and the most protected area has been disabled in this video we've

10:41.040 --> 10:45.810
talked about the fundamentals of forensic imaging covered the topic such as hardware and software right

10:45.810 --> 10:53.280
blocking a forensic image formats disk geometry and its special features D.S.O. and HIPAA and how to

10:53.280 --> 10:54.990
practically remove them.

10:55.050 --> 10:55.950
Very good.

10:56.010 --> 11:01.140
In the next video we're going to introduce two command line tools specifically designed for forensic

11:01.140 --> 11:03.960
acquisition DCF Ltd..

11:04.120 --> 11:05.120
See 3D.
