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 ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2.11. TC-03-DCO<br />
Helix3 Pro R3 (Release Date: 30 th , Dec 2009)<br />
Test Case TC-03-DCO (Helix3 Pro 2009 R3)<br />
Test &<br />
Case<br />
Summary:<br />
TC-03 Acquire a hard drive with hidden sectors to an image file<br />
Notes: DCO active<br />
Assertion: AFR-01 The tool accesses the digital source with a supported access interface<br />
AFR-02 The tool acquires a digital source<br />
AFR-03 The tool operates in an execution environment<br />
AFR-04 The tool creates an image file <strong>of</strong> the digital source<br />
AFR-05 The tool acquires all the visible data sectors from the digital source<br />
AFR-06 The tool acquires all the hidden data sectors from the digital source<br />
AFR-07 All data sectors acquired from the digital source are acquired accurately.<br />
AIC-01 The data represented by an image file is the same as the data acquired by the<br />
tool<br />
AIC-02 The tool creates an image file according to the file <strong>for</strong>mat the user specified.<br />
AIC-05 If multi-file image creation and the image file size is selected, the tool creates<br />
a multi-file image except that one file may be smaller<br />
AIC-06 If the image file integrity check is selected, the tool shall report to the user the<br />
image file has not been changed if the image file has not been changed.<br />
AIC-07 If the image file integrity check is selected, the tool shall report to the user the<br />
image file has been changed if the image file has been changed.<br />
AIC-08 If the image file integrity check is selected, the tool shall report to the user the<br />
image file has been changed and the involved location if the image file has<br />
been changed.<br />
ALOG- If the tool logs any in<strong>for</strong>mation regarding to the acquisition, the in<strong>for</strong>mation is<br />
Source<br />
Device:<br />
Drive<br />
Setup:<br />
Partition<br />
Table:<br />
01<br />
ALOG-<br />
02<br />
ALOG-<br />
03<br />
accurately logged in the log file.<br />
The tool display correct in<strong>for</strong>mation about the acquisition to the user. The<br />
in<strong>for</strong>mation about the acquisition at least including following: device, start<br />
sector, end sector, type and number <strong>of</strong> errors encountered, and start time and<br />
end time <strong>of</strong> acquisition.<br />
The tool display correct in<strong>for</strong>mation regarding to the acquisition to the user<br />
and the in<strong>for</strong>mation displayed is consistent with the log file if the log file<br />
function is supported<br />
AHS-01 The tool reports to the user if any hidden sectors are found<br />
AHS-02 The tool reports to the user that digital source may contain hidden sector but<br />
undetected if the tool is unable to determine whether hidden sectors are<br />
present due to incompatible execution environment<br />
AHS-03 The tool reports to the user that hidden sectors will not be acquired if the tool<br />
is unable to acquire hidden sectors due to incompatible execution<br />
environment<br />
Drive Model: ST380817AS (80GB)<br />
Serial Number: 5MR18V18<br />
Sector count: 156,301,488<br />
Write blocker: N/A<br />
Source hashes:<br />
MD5 checksum: 69fdef5d5de3a207bc2a04017c38c3fd<br />
SHA1 checksum: 9d768ab184ed9a172031f0f7b7f721f2bdf80b59<br />
/dev/sdb: current max LBA: 94,863,828<br />
/dev/sdb: native max LBA: 94,863,828<br />
/dev/sdb: physical max LBA: 156,301,488<br />
/dev/sdb: HPA not set<br />
/dev/sdb: DCO set from sector 94,863,828 to 156,301,487<br />
Device Start End #sectors File System<br />
/dev/sdb1 63 41945714 41945652 NTFS<br />
/dev/sdb2 41945715 94863824 52918110 Ext3<br />
228