30.06.2013 Views

Evaluating A Selection of Tools for Extraction of Forensic Data: Disk ...

Evaluating A Selection of Tools for Extraction of Forensic Data: Disk ...

Evaluating A Selection of Tools for Extraction of Forensic Data: Disk ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The method <strong>of</strong> data analysis is described in section 3.4.3. GA is selected as the method<br />

to analyse the data in this research project. According to Table 4.20, The GA matrix<br />

can be constructed based on Table 4.20 (see Appendix 6). The Gap <strong>of</strong> each evaluated<br />

tool can be identified as:<br />

Gap = Required Requirements – Actual per<strong>for</strong>mance <strong>of</strong> the Tool<br />

There are few major gaps between three tested tools. None <strong>of</strong> the three tested tools<br />

was able to acquire the disk image in test cases TC-03, TC-12 and TC-17 that involved<br />

HPA or DCO configuration. Furthermore, none <strong>of</strong> the tested tools were able to detect<br />

and report to the user the irregularities configured in test cases TC-13 to TC-15<br />

according to the test assertion TSP-AIC-11.<br />

According to the results presented in figure 4.1, FTK Imager achieved the<br />

expected test result in more than half <strong>of</strong> the test cases that were applied. FTK Imager<br />

presented problems in areas where hidden areas are existed and where the source drive<br />

had irregular configuration. Helix 3 Pro did not achieve the expected result in most <strong>of</strong><br />

the test cases.<br />

The testing requirements <strong>for</strong> this research specified that each tested tool was<br />

required to provide essential in<strong>for</strong>mation (such as start and end sectors) to the user in<br />

the log file. In the log file <strong>of</strong> Helix 3 Pro, start and end sectors were not provided as<br />

standard output in the log file. There<strong>for</strong>e, Helix 3 Pro was marked as failed on the test<br />

assertion ALOG-02 in each test case. Some popular file systems and partition table<br />

<strong>for</strong>mats, such as HFS, HFS+ and GUID partition table are not supported by Helix 3<br />

Pro. On the other hand, FTK Imager and AIR successfully identified and acquired the<br />

file system types and partition table that were not supported by Helix 3 Pro. AIR also<br />

presented few problems during the evaluation. Whenever there was a problem, AIR<br />

would stop the acquisition process immediately and no in<strong>for</strong>mation as to why the<br />

process had stopped would be provided to the user. For example, when the destination<br />

device did not have enough storage space to store the image files, AIR program would<br />

stop immediately and would not provide in<strong>for</strong>mation to the user why the process<br />

terminated.<br />

88

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!