As several sites have rightfully pointed out....Accessdata has made a huge jump ahead with their recent release of FTK Imager v3.0. (not to mention FTK 3.2 and their most recent "Volatile tab.") Just finished testing it today by mounting physical images and using VFC to virtually boot XP and Win7 systems. Flawless! While wandering around their site (actually looking for updated RSR files to add to their most recent Registry Viewer version), I stumbled across two additional documents that I believe are very worthy of a good read - or at least printing out as a permanent reference.
Registry Quick Find Chart - a very recently updated 34-page reference documenting Registry locations for the standard 5 Registry files. The document has a few new columns in the document - one which lists what versions of Windows the reference pertains to (ie: XP, Vista or Win7) and a second column that states when the Registry reference is updated (immediately, when document opened, at logon...) This document would also be great starting reference to initiate further research on Registry locations and extractable artifacts. D/L it....know it....print it and keep it handy!
Mac System Artifacts - another reference document which provides 7 pages of Mac Artifact locations. With FTK's amazing ability to parse out the Mac OS (including Plists), this document is another one to print off. Updated in 2010.
Jad has also updated three of his applications:
Internet Evidence Finder (IEF) - updated to v3.6 to handle recent updates to Facebook Live chat. Commercial - Cdn $49.00; Free for Law Enforcement.
FChat - updated to v1.20. Commercial - Cdn $29.99
FJF - Facebook JPG finder - updated to v1.2.1. Currently free for use.
Showing posts with label FTKImager. Show all posts
Showing posts with label FTKImager. Show all posts
Friday, October 22, 2010
Sunday, October 3, 2010
Kindle 3G Wireless Reading Device - forensically speaking
Having just acquired the new model of Kindle, I got to wondering what kind of information was stored on the device and if necessary, how would I go about accessing this information in the most forensically-sound manner possible. Here's what I found.
1. Using a Digital Intelligence Tableau Ultrablock USB write-blocker, I connected my forensic computer to the device through the micro-USB cable that was provided with the Kindle.
2. Realizing that it was necessary to power on the device, I did so. I noted the date/time to compare this with the date/time stamps that were likely to change upon boot.
3. When powered on, I immediately checked to ensure the 3G/Wireless was turned off. Select "Menu", toggle the five-way controller up to "Turn Wireless Off" and select the five-way controller (center button). Alternatively, I could conduct the acquisition within our Faraday tent.
4. Using FTKImager v2.9.0.5, identified the physical drive attributed to the Kindle.
5. As noted, the drive recognized as "Kindle Internal Storage" with a size of 3240MB. I noted that this differs from the stated size of the device (4GB). Specifically, Amazon states the device has "Storage 4GB internal (approximately 3GB available for user content)." I then acquired the physical drive as a RAW (DD) format to allow a more robust selection of analysis tools.
Here's what the partition looks like:
And contents of the "documents" directory:
6. Made note of the filesystem, and VBR header - as noted in the following screenshot.
The filesystem is FAT32, formatted with mkdosfs - DOS formatting within a Linux environment. From looking at the USER partition which was available, I'm asking whether the SYSTEM partition is ARM Linux Kernel (?).
While admittedly, my Kindle had not been populated with a lot of user interaction, the Kindle definitely does not appear to readily give up information. It was obvious what books and documents were on my Kindle, and what the last document I accessed was, but as far as other artifacts, my brief analysis was not overly productive. I have surfed the Internet, opened several websites and likely populated the device with considerable Internet History. I could not readily locate any of this history.
Just for heck of it, I through Jad's Internet Evidence Finder at it - nothing. I'm thinking that a GREP search for Internet History might have more success. I'm also interesting in running a search for my Wireless Access Point SSID and see what other artifacts might show up.
Other things I found:
- IMEI (3G) information on the device.
- lots of deleted information.
- a significant number of dictionary terms (including in the unallocated space).
Eric Huber has a posting on the Kindle at A Fistful of Dongles - more great information.
More to come....perhaps I'll see how a boot CD such as Caine interacts with the device. I'm going to continue to see what the imaged USER image is willing to give up in terms of forensic artifacts. ps..EnCase will also be involved.
Any thoughts or ideas are welcome.
1. Using a Digital Intelligence Tableau Ultrablock USB write-blocker, I connected my forensic computer to the device through the micro-USB cable that was provided with the Kindle.
2. Realizing that it was necessary to power on the device, I did so. I noted the date/time to compare this with the date/time stamps that were likely to change upon boot.
3. When powered on, I immediately checked to ensure the 3G/Wireless was turned off. Select "Menu", toggle the five-way controller up to "Turn Wireless Off" and select the five-way controller (center button). Alternatively, I could conduct the acquisition within our Faraday tent.
4. Using FTKImager v2.9.0.5, identified the physical drive attributed to the Kindle.
Here's what the partition looks like:
6. Made note of the filesystem, and VBR header - as noted in the following screenshot.
The filesystem is FAT32, formatted with mkdosfs - DOS formatting within a Linux environment. From looking at the USER partition which was available, I'm asking whether the SYSTEM partition is ARM Linux Kernel (?).
While admittedly, my Kindle had not been populated with a lot of user interaction, the Kindle definitely does not appear to readily give up information. It was obvious what books and documents were on my Kindle, and what the last document I accessed was, but as far as other artifacts, my brief analysis was not overly productive. I have surfed the Internet, opened several websites and likely populated the device with considerable Internet History. I could not readily locate any of this history.
Just for heck of it, I through Jad's Internet Evidence Finder at it - nothing. I'm thinking that a GREP search for Internet History might have more success. I'm also interesting in running a search for my Wireless Access Point SSID and see what other artifacts might show up.
Other things I found:
- IMEI (3G) information on the device.
- lots of deleted information.
- a significant number of dictionary terms (including in the unallocated space).
Eric Huber has a posting on the Kindle at A Fistful of Dongles - more great information.
More to come....perhaps I'll see how a boot CD such as Caine interacts with the device. I'm going to continue to see what the imaged USER image is willing to give up in terms of forensic artifacts. ps..EnCase will also be involved.
Any thoughts or ideas are welcome.
Subscribe to:
Posts (Atom)