
The investigation was undertaken in a scientific, step-by-step, repeatable approach. The experiment could be done again by somebody else and the same results would be achieved.
|
Step |
Explanation |
|
Created test machine |
Created the sandboxed Windows Server 2012 virtual machine. No network connections preventing any communications through a network. Operating System installed on a 30GB drive, allowing for storage, meaning attached drives at a later date would be only used for their respective tests. |
|
Created drives |
Each 5GB drive (one for NTFS, one for ReFS and one for FAT32) was created. If the drive needed to have previous action performed (a folder created) this would be done, then the drive would be copied. There was always an original drive to revert back to. |
|
Drives added to sandboxed machine |
Drives were loaded into the sandboxed Windows Server 2012 virtual machine. The NTFS drive was always drive "E:", ReFS was always "F:" and FAT32 was always "G:". |
|
Performed experiments |
Every experiment was undertaken in a methodological manner, which would be repeatable and had no external contributing factors. The experiments were performed in the order of NTFS, then ReFS, then FAT32. |
|
Drives loaded into Helix virtual machine and cloned |
The drives were loaded into a Helix VM before being cloned. No changes could happen to the drives as Helix was utilising a software write blocker. The command issued was DD. |
|
Data dump files manually analysed |
Using the Windows hex editor HxD, the data dump files were opened and manually analysed. |
|
Results noted |
An ongoing process of the analysis involved documenting knowledge gathered and information discovered throughout the investigation. |
|
Note taking throughout |
Thoughts, ideas and potential areas to investigate were noted as an ongoing process throughout the investigation. This directly adheres to ACPO principle 3. |
Throughout the report, different parts of hexadecimal will be highlighted in different colours to make it easier to interpret. See the table below for the colours and the corresponding data.
The table isn't exclusive; these colours are not just limited to the particular data. For example where data highlighting is necessary and no MACE times are in the data of interest, the colour green may be used to highlight some other information.
|
Data |
Colour Highlight |
|
MACE Times |
Green |
|
Used Partition Entries |
Orange |
|
Boot Signatures |
Red |
|
JMP Instructions |
Grey |
|
OEM IDs |
Blue |
|
Drive Labels |
Aqua |
This paper will use a similar category analysis method to Brian Carrier in the book File System Forensic Analysis (2005).
Carrier created this categorical method of analysing file systems so an abstracted view could be taken, allow the file system to be understood from a perspective that didn't need to take in the fine details. The categories he defined were File System, Content, Metadata, Filename and Application. The final one will not be used in this report and as ReFS uses 16KB metadata blocks, the File System category will be included within the Metadata category, so within this paper only three categories will be used.
When analysing a particular category, the heading of that section will correlate to the category it represents. For example, when analysing the MBR and VBR the headings of both of these sections will be yellow (as seen below). In the case of the absence of colour, in the top left hand corner of the page will be an icon representing that particular category (icon shown next to headings below).
Represented by yellow in this paper (and the icon above), this category can be thought of as a map. It provides the structure of the file system, disclosing essential information such as the size of the partition/s and layout information of said partitions, including sector sizes, offset addresses and pointing to where other necessary data can be found. The MBR and VBR are included in the File System category. These both provide essential information on the drives and the volumes they describe.
The Content category relates to the actual data the user saves and is represented in orange in this paper. For example a word document and the content inside of that would come under the scope of the Content category.
Metadata, often called descriptive data, is data that describes other data. The metadata category is represented in green in this paper. In this case it is data that describes the content. This includes the Modified and Created times of the files and file sizes. The Filename category, which includes the filename of the data that the metadata describes, is included within this category for this paper.