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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

in<strong>for</strong>mation <strong>of</strong> the total number <strong>of</strong> sectors that had been acquired by calculating the<br />

size and number <strong>of</strong> image files generated by the tool and converting it to the sector.<br />

The calculation is beyond the scope <strong>of</strong> this research. The tool is able to obtain the<br />

in<strong>for</strong>mation when acquiring the digital source but choosing whether to record the<br />

in<strong>for</strong>mation in the log file was the choice <strong>of</strong> the tool. The in<strong>for</strong>mation is important <strong>for</strong><br />

the <strong>for</strong>ensic investigators. With more relevant in<strong>for</strong>mation provided by the disk<br />

imaging tools, <strong>for</strong>ensic investigator will have more chance to locate and capture<br />

crucial in<strong>for</strong>mation from the digital evidence.<br />

Helix 3 Pro supports EnCase version 4, 5 and 6 as alternative disk image<br />

<strong>for</strong>mats besides raw image <strong>for</strong>mat. Helix 3 Pro successfully acquired the digital source<br />

to EnCase version 6 <strong>for</strong>mat during the testing. However, the log file that Helix 3 Pro<br />

generated did not clearly state that verification had been per<strong>for</strong>med like the log file<br />

generated in raw image <strong>for</strong>mat. The hash value was only calculated over the acquired<br />

data but not on the digital source. The user could not ascertain whether the acquired<br />

data was a bit-by-bit copy <strong>of</strong> the digital source. <strong>Forensic</strong> investigators may rely on the<br />

log file generated as part <strong>of</strong> the evidence or audit trails by the tool. Users may be<br />

required to take extra steps to verify the hash values <strong>of</strong> both acquired and source data.<br />

It is not a major flaw <strong>of</strong> the s<strong>of</strong>tware because when the tool acquiring the source to<br />

image files, both hash values could be calculated. The tool should clearly indicate that<br />

integrity has been verified on both acquired and digital source.<br />

Helix 3 Pro failed to acquire hidden sectors configured in cases where HPA or<br />

DCO setting was used. The fact that FTK Imager and AIR imaging tools also failed in<br />

the same test should be noted. In the test case where Helix 3 Pro acquired hidden<br />

areas, it was not able to obtain the partition table in<strong>for</strong>mation <strong>of</strong> the hard disk whereas<br />

the other two tools were able to per<strong>for</strong>m this task. Helix 3 Pro‟s per<strong>for</strong>mance was<br />

unsatisfactory in the test case TC-12 where partially and completely hidden partitions<br />

were involved. Helix 3 Pro was not able to complete the acquisition process within a<br />

reasonable timeframe. The tool acquired the digital source at an extremely slow speed<br />

when it encountered the hidden partition. The tool was attempting to access the hidden<br />

data in the same way as FTK Imager in the same case. Appropriate error message<br />

should have issued to notify the user <strong>of</strong> the situation when an excessive amount <strong>of</strong><br />

102

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

Saved successfully!

Ooh no, something went wrong!