WEBVTT

00:00.950 --> 00:08.660
Hi and welcome to this video drive imaging with DC 3D in the previous video we introduce to command

00:08.660 --> 00:17.210
line forensic acquisition tools DC F.L. DD and DC 3D and looked at the manual page of the DC 3 DD showing

00:17.210 --> 00:22.970
its various options in this video we're going to take a look at how to identify our target drive among

00:22.970 --> 00:25.580
the drives attached to the forensic workstation.

00:25.670 --> 00:30.760
Then we'll cover the procedure of acquiring the forensic image of the drive with DC 3D.

00:30.770 --> 00:35.630
Finally how do cryptographically signed the hash log file with GBG.

00:35.630 --> 00:40.550
As a practical example we're going to acquire the image of the 40 gigabyte hard drive shown in this

00:40.550 --> 00:47.030
picture which we imagine having removed from an old suspect computer we assume having attached our target

00:47.030 --> 00:52.140
drive to the forensic workstation using a right blocking mechanism as described in the first video the

00:52.180 --> 00:54.910
section introduction to forensic imaging.

00:54.920 --> 00:57.640
The first step is the correct identification of the drive.

00:57.680 --> 01:03.710
Among the other drivers on our system remember that Linux identifies drivers as block device files under

01:03.710 --> 01:05.510
the dash dev directory.

01:05.510 --> 01:12.890
Usually in the form of Dash dev dash STA X dash STA X where X is a letter that identifies the drive

01:13.070 --> 01:18.180
while N is the number that represents the partition number to list all the attached drives.

01:18.230 --> 01:21.830
We can use the F disk tool followed by the negative option

01:25.150 --> 01:30.550
the output of the command shows for each drive the capacity and the total number of sectors the disk

01:30.550 --> 01:35.140
label type and the disk ID below.

01:35.170 --> 01:40.020
They list the partitions in which the disk is divided for each partition of the drive.

01:40.030 --> 01:45.850
There are a lot of detailed information such as If the partition is bootable sectors where the partition

01:45.850 --> 01:50.940
starts and ends the number of sectors the size and the file system type.

01:50.980 --> 01:57.010
In our case since we know that the target drive is 40 gigabytes of size we must repots that it's represented

01:57.010 --> 02:02.700
by device dev STA because it has total capacity of 40 gigabytes.

02:02.740 --> 02:08.200
The first number being the total capacity available to the user and we could see that the drive contains

02:08.200 --> 02:14.020
only one partition that is marked with the NTFS file system.

02:14.180 --> 02:17.500
In case you still have some doubt about the identification of the drive.

02:17.540 --> 02:23.360
Recall that we can use the HD Park tool to obtain more detailed information about the drive so we run

02:23.360 --> 02:23.990
the command

02:30.760 --> 02:34.870
and the output of the command shows the model number and the serial number.

02:35.050 --> 02:40.120
We can compare these two values with those printed on the drive itself so we can be sure that our drive

02:40.150 --> 02:42.120
is correctly identified.

02:42.310 --> 02:46.940
Having identified the drive we can run DC 3 DD to acquire its image.

02:47.170 --> 02:51.570
First we had to decide a location where to store the output image file.

02:51.640 --> 02:55.420
This location obviously must have enough free space to store it.

02:55.600 --> 03:01.870
In our case we decided to store the image file on an external hard disk to see the device file attached

03:02.710 --> 03:05.210
to see the device file associated with the disk.

03:05.320 --> 03:07.990
We could run as usual the disk tool

03:11.570 --> 03:22.760
as we notice the external 500 gigabyte hard disk is associated with the death SD device file.

03:22.810 --> 03:28.300
We run the F dash h command to see the directory on which this device file is mounted.

03:28.300 --> 03:34.720
Now we could run the DC three-D tool.

03:34.950 --> 03:41.170
The first parameter to specify is I-F followed by the input device that in our case is dead.

03:41.190 --> 03:46.420
Sta.

03:46.510 --> 03:51.790
Then we should specify the H-2 a parameter that takes the path and the name of the image file where

03:51.790 --> 03:53.500
to copy the input data.

03:53.710 --> 03:59.230
We must specify a location where to save the image that has more free space than the size of the input

03:59.230 --> 03:59.850
device

04:19.530 --> 04:24.530
the H.F. option also calculates the hash of the output to verify its integrity.

04:26.580 --> 04:32.090
This option must be used together with Dash hash specifying which algorithms to use.

04:32.130 --> 04:37.350
In our case SH A-one SH's 8 2 5 6 an essay.

04:37.520 --> 05:14.770
5:12 that we specify the dash log options to log any input output errors statistics and hashes.

05:14.860 --> 05:17.050
We can now execute the command.

05:17.050 --> 05:22.690
We must ensure before running the command that the input output file is not exchanged because otherwise

05:23.020 --> 05:25.070
we would overwrite the input media.

05:25.210 --> 05:31.630
And so we destroy the digital evidence the input file with then we don't specify any partition number

05:31.690 --> 05:38.620
because we want to acquire the full disk.

05:38.770 --> 05:43.900
We run the command and see that the output shows the progress of the acquisition the number of bytes

05:43.900 --> 05:47.620
copied the elapsed time and the transfer rate.

05:48.250 --> 05:54.160
Unfortunately we see that DC 3D determinates with an error saying that the output image file is too

05:54.160 --> 05:58.690
large and showing having copied only four gigabytes.

05:58.690 --> 06:05.790
That's because the external hard disk is formatted with the F-8 file system and it allows only a file

06:05.790 --> 06:08.340
maximum size of four gigabytes.

06:08.700 --> 06:15.090
Possible workaround could be as we've seen in the previous video to specify the HFS option to split

06:15.090 --> 06:17.970
the image file into different files.

06:18.120 --> 06:25.530
We add the S to the option and the format specifier to the filename and also the yoa as the option which

06:25.530 --> 06:27.340
set the max file size.

06:27.480 --> 06:36.300
That in our case should be less than the 4 gigabyte limit and so we set it for example to 3 gigabytes.

06:36.390 --> 06:37.840
Now he could run the command again

06:42.590 --> 06:43.380
after a while.

06:43.400 --> 06:49.850
The DC 3 DD terminates without any air and so the image acquisition is successfully completed.

06:49.910 --> 06:55.280
We could see that the destination directory contains all the image files and the log files.

06:55.280 --> 06:56.940
Very good.

06:56.990 --> 07:01.740
There's one more step to perform since we should be able to demonstrate that the hash is produced during

07:01.760 --> 07:06.290
the acquisition really refer to the original evidence and that they've not been tampered with.

07:06.290 --> 07:13.040
Afterwards it's a good practice to cryptographically sign the log file produced by DC 3 DD for this

07:13.040 --> 07:13.510
purpose.

07:13.520 --> 07:19.450
A useful tool is GBG the new version of PGE pretty good privacy.

07:19.520 --> 07:23.720
You should assume that we've already generated a couple of public or private keys.

07:23.900 --> 07:28.980
But if you don't know how to generate it please refer to the manual page of GPB to know how to generate

07:28.980 --> 07:31.000
it to sign the log file.

07:31.010 --> 07:32.750
We can execute the command.

07:32.750 --> 07:34.940
We verify the signature with the command

07:59.130 --> 08:03.840
great so now that we have the image file the hash and the signature of the log file.

08:03.840 --> 08:06.830
The acquisition page is complete in this video.

08:06.820 --> 08:12.710
We've seen how to image the target drive connect to the forensic workstation with the DC 3 D tool.

08:12.810 --> 08:18.990
First we've covered how to identify the drive and then how to execute DC 3 DD with the appropriate options

08:19.200 --> 08:21.380
to correctly acquire the image.

08:21.390 --> 08:28.080
Finally we've covered cryptographically signing the hash file with GBG in the next video Android device

08:28.110 --> 08:30.230
imaging with DC 3D.

08:30.300 --> 08:33.810
We're going to cover the forensic acquisition of an Android device.
