Forensic Handling of Data on a PC
How to avoid destroying the Chain of Custody when handling forensic evidence
Any alteration, or even an environment or situation that creates the possibility of alteration, could lead to rejection of the evidence in a court of law. This is why proof of the Chain of Custody is so important. This is the reason why all analysis and tests should be executed following the proper forensic handling of data process.
Chain of Custody
Being able to maintain the Chain of Custody is very important for forensic evidence. What this means is that you need to record, and be able to prove, that authorized personnel were in control of the evidence at all times, and that no unauthorized person or device or mechanism could have altered the evidence while in our custody.
Documentation and containment
To maintain the Chain of Custody, it is imperative to carefully document what happens to the evidence. This means:
- Clearly label the evidence. There must be no confusion about a piece of evidence. All evidence, whether hard drives, USB drives, DVDs, etc. should be clearly labeled with the following information:
- What the evidence relates to
- Who received the evidence
- Location of where the evidence was received
- Location of where the evidence was sourced from
- The date and time the evidence came into our possession
- Any other notes you think are relevant regarding this piece of evidence (the specifications of the computer a hard drive came from, etc.)
- If you have to send evidence via courier, or the postal service:
- Special containers should be used to seal the evidence in such a way that the container cannot be opened without it being apparent (e.g. seal with special tape that, if removed, cannot be replaced without showing that the container has been opened).
- Ideally make a copy (image) of the evidence before sending the original through the post or courier service, and generate a hash of the image.
Store the evidence in an anti-static bag, or similar appropriate container that will protect the device from static electricity or other destructive forces.
Every time the evidence changes hands, the next person responsible for the evidence should “sign for it”, which means documentation should be produced where the recipient of the evidence confirms they have received the evidence into their custody with their signature.
- Deny unauthorized personnel from accessing the data - Every reasonable effort must be taken so as to prevent unauthorized access to the stored evidence. This means:
- Storing the evidence in a locked safe
- Controlling access to areas where the evidence is stored and analyzed
- Not leaving unauthorized people alone with the evidence
Forensic Analysis of the Data
There are some procedures that must be followed to ensure the evidence is properly handled while the forensic analysis is taking place. These include:
- Keep a log of everything you do to analyze the data:
- What you connected it to, and how
- Each and every command you ran against the data image as you perform your investigation
- This log must identify who is performing the analysis
- Date and time stamps for each action performed
Only work on copies of the data, not the source data.
Ideally make multiple copies from the initial copy, as you may need to work on fresh copies if your analysis accidentally modifies the copy you are working on.
Immediately on receipt of the source data, make a cryptographic hash of that image, and store it in a safe place. This is your only guarantee that you have not tampered with the evidence you are working on!
After making a copy of the data, immediately create a cryptographic hash of that image, and check it against your master hash to ensure they match.
As you work on your investigation on a copy of the data, periodically check that data image with the cryptographic hash, to ensure you have not inadvertently modified the data by performing your investigation. If the hash does not match, then:
- Record the fact that the hash no longer matches in your activity log.
- Look in your log at all the steps you have taken between when you last checked the hash and now. One or more of the steps you have taken has modified the data of the copy, so you need to work out which step caused this, and work out how to perform a copy in the investigative step without modifying the data.
- Abandon the now modified copy of the data. This is tainted, so clearly mark it as such and return it to secure storage.
- Use a fresh copy of the data, again checking the hash to ensure it is clean before proceeding with the investigation.
- If necessary, make extra copies of the data from the original source image you created (making sure to never perform investigative steps on that source image).
How to Byte-Copy Data
By “target” we will refer to the hard drive or data image already acquired by the client and sent to the Helpline. When explaining the use of commands, the “target” will be also referred to as “source device”, while the place where the byte-copy data will be stored is referred to as “destination device”. The forensic image that will be acquired with this process will be used to execute tests without affecting the original evidence received.
Files and device block labels for the examples
For the command examples, these name conventions will be used:
[IMAGENAME].dd- The name of the image file to be created
[LOGFILENAME].txt- log file name
/dev/sdX- target drive or source (assuming we want to copy a hard drive or data image and sdX is the partition).
/dev/sdY- destination drive (assuming this is the media where the copy will be stored and sdY is the partition).
Prepare destination media to be used to save the forensic image
The forensic image that will be taken from the target should be saved in a proper labeled and formatted drive with available space greater that the size of the forensic image. Execute the actions described below before approaching the target.
- Select an equally sized or larger hard drive or storage device to store the image
- Properly label the destination media
- Prepare an additional USB stick to collect a file log
Capture the forensic image
There are two ways to capture the forensic image:
- using a bootable Linux forensic distribution on a CD or USB stick or
- by command line (terminal). If possible, use the forensic distribution, as this method does not mount devices by default.
Using a forensic distribution
In case you are using the forensic distribution, for example DEFT, boot the image by following these steps:
- While the PC/laptop is powered off, plug into it:
- the USB stick or CD with the Deft image,
- the USB stick to upload the log, and
- the enclosure with the wiped drive where the copy will be saved.
- Boot the DEFT Linux from the USB/CD/DVD: power the PC/laptop on, wait for the DEFT boot loader to start, select the language and then the system will display a text-based session with a bash shell with root permissions.
NOTE: in order to get the DEFT boot loader started, the BIOS of the system being analyzed should be set to boot from CD-ROM/DVD-ROM/BD-ROM or from external storage devices (depending on the media containing DEFT). In any other circumstances, configure the BIOS, save and restart the system either with the DVD already inserted in your CD/DVD drive or with the USB stick already connected. We recommend changing the boot order of the devices directly in the BIOS to prevent an accidental reboot of your PC (e.g. due to a power surge).
Using the command line
Otherwise, if it is not possible to use the forensic distribution, just open a command line terminal.
In the command prompt (bash shell in DEFT) enter the commands detailed in each step listed below.
Step 1: in order to keep the record of the procedure, a log file will be elaborated in a separate USB stick.
List all the partitions and storage devices connected to the system. Identify all the plugged devices (especially the internal hard disk, external drives, etc.) by entering the below command:
fdisk -l | less
Note: all mounted partitions and devices will be in the /dev directory, typically as /dev/sdX - where X is a letter starting with
Create a log directory in a separate USB stick by entering the following commands (assuming /dev/sdb1 is a partition on the USB stick):
Check if the USB stick partition you want to use for your log directory is mounted by launching this command:
mount | grep /dev
The output will be a list of mounted devices with several details, including the directory where they are mounted. Check if the USB partition you want to use features in this list, and in which directory it is mounted (for example,
/dev/sdb1 on /media/user/USBmeans that the USB stick partition
/dev/sdb1is mounted in the directory
If the USB stick partition you want to use is not mounted, you can mount it with the following commands:
Create a directory where you can mount the partition:
Mount the partition in the directory you just created:
mount /dev/sdb1 /mnt/[DirectoryNameUSB]
Create a directory labeled with your incident name in the mounted partition:
Take a copy of the fdisk output and write it to the USB stick using a command output redirection like this:
fdisk -l > /mnt/[DirectoryNameUSB]/[incidentname]/fdisk.txt
Create a directory in the destination media (assuming
/dev/sdc1is the partition to write the forensic image to):
If the destination media is not automatically mounted (see above on how to check), mount it with the following commands:
mount /dev/sdc1 /mnt/[DirectoryNameIMAGE]
Access the directory where you have mounted the destination media and create a directory with the incident name, then access the directory you have just created:
Step 2: Write-blockers to prevent alterations.
If you use the forensic distribution option, this step can be skipped. Otherwise, the following command should be entered to prevent any data from being written to the block device, allowing mounting of the block device with read-only access.
mount -o ro /dev/sdX /mnt/sdX/
Other block devices (the USB stick for the log or the destination block device) can be mounted without taking this precaution.
Step 3: Byte-copy the data to a data image for forensic analysis purposes.
When all the data from a disk is duplicated exactly from the source disk and stored in a file, the resulting bit-for-bit copy is called a raw image. Raw images can be created by several different utilities and frequently will use the following file extensions:
There are different tools available to obtain this raw image file. Which one we use will depend on which are available for our operating system, and which tool best suits our needs. These tools are listed below.
WARNING! Be extremely careful when typing the command line for this program. Reversing the
of flags, or confusing the label of the device block related to the source or destination device will cause the computer to destroy the evidence! Therefore it is imperative to check and re-check (and preferably have someone else check) the command before executing it.
Please keep in mind that the
if= flag refers to the input file, in this case, the source device or target and the
of= flag refers to the output file or destination device.
Tools for bit-by-bit copy
- dd - Functional utility that requires only minimal resources to run. This command takes as input the mass storage device and returns as output its clone within the file diskimage.img, to a file or to a mass storage device (and vice versa).
- Platform: Linux, Mac
- Difference from other tools: Lacks some of the useful features found in more capable imagers such as metadata gathering, error correction, piecewise hashing, and a user-friendly interface.
- dd.exe - Dd.exe is a Microsoft Windows implementation of the Unix dd utility. This utility, which does not come with the operating system, is one of the tools in the Forensic Acquisition Utilities suite written by George Garner, and should be downloaded from this page
- Platform: Windows
- Difference from other tools: Same features as dd, but this utility provides native encryption and compression capability. It functions very much like the Unix/Linux dd utility, with some notable exceptions. Dd.exe can send the output directly to a specified TCP or UDP port.
- dc3dd - This tool is a patched version of GNU dd with added features for computer forensics and a graphical interface developed for dc3dd called Automated Image and Restore (AIR).
- Platform: Linux
- Difference from other tools:
- On-the-fly hashing with multiple algorithms
- Able to write errors directly to a file
- Combined error log. Groups errors together
- Pattern wiping. Wipe output files with a single hex digit or a text pattern
- Verify mode
- Progress reports. See the progress of the operation while it’s running
- Split output. Able to split output files into fixed-size chunks
- dcfldd - dcfldd is a fork of GNU dd, so dcfldd has its own release schedule unrelated to dd updates.
- Platform: Linux
- Difference from other tools:
- On-the-fly hashing of the transmitted data
- Progress bar of how much data has already been sent
- Wiping of disks with known patterns
- Verification that the image is identical to the original drive, bit-for-bit
- Simultaneous output to more than one file/disk is possible
- The output can be split into multiple files
- Logs and data can be piped into external applications
- ddrescue - Data recovery tool. It copies data from one file or block device (hard disk, CD-ROM, etc.) to another, trying hard to rescue data in case of read errors.
- Platform: Windows, Linux
- Difference from other tools: ddrescue uses a sophisticated algorithm to copy data from failing drives, causing them as little additional damage as possible.
Command flags clarification
if=flag refers to the input file, the source device or target
of=flag refers to the output file or destination device or data image file name (.img)
hash=indicates the algorithm used to generate the hash
|dd||dd if=/dev/sdX of=/dev/sdY/[IMAGENAME].dd|
|dc3dd||dc3dd if=/dev/sdX of=[IMAGENAME].dd hash=md5 log=[LOGFILENAME].txt|
|ddrescue||ddrescue /dev/sdX /dev/sdY/[IMAGENAME].dd|
|dcfldd||dcfldd if=/dev/sdX of=/dev/sdY/[IMAGENAME].dd hash=sha1 (or hash=md5)|
Resources and further reading:
- DEFT 7 Manual - Digital Evidence and Forensics Toolkit [PDF]
- Justin C. Klein Keane, Capturing a Forensic Image [PDF]
- SANS Digital Forensics and Incident Response Blog: Forensics 101: Acquiring an Image with FTK Imager