ATTENTION: The new home of the Digital Forensics Wiki is at Yeah, it's a silly name, but it was cheap.
This wiki will be going offline permanently in the near future. An exact date will be announced soon. Thank you for being a part of this community.
If you wish to work on the new forensicswiki, please join the Google Group forensicswiki-reborn

Difference between revisions of "Imager NG Ideas"

From ForensicsWiki
Jump to: navigation, search
Line 47: Line 47:
** sparse ranges
** sparse ranges
** de-duplication
** de-duplication
=== de-duplication ===
* hash-based imaging
* sparse or repeated ranges
== Integrity checks ==
== Integrity checks ==

Revision as of 06:13, 6 September 2012

This page is for discussing ideas regarding next-generation (NG) imaging tools.

Note that some of the ideas mentioned can be already used by imaging tools, but the idea of this page is to determine how useful these features could be for next-generation of imaging tools. The scope is mainly a software-based imaging tools, but not limited to. Some features might not be doable, because of limitations of certain image file formats.

Please, do not delete text (ideas) here. Use something like this:

<s>bad idea</s>
good idea

This will look like:

bad idea

good idea



  • Compression
  • Integrity checks
  • Encryption
  • Error correction (parity)
  • Pre-processing during imaging
  • User suspend/resume, resume after failure
  • Remote imaging
  • Error resistance in reading storage media, e.d. disks
    • maybe have different techniques, e.g. to use for heavily damaged storage media
  • Support different types of storage media
    • disk
    • volume
    • optical discs
    • memory
    • files and directories
  • Store relevant data about the storage media and the imaging process
    • read errors
  • Support multiple image format
    • not all image formats have support for all the features


  • Reduces the amount of data that needs to be written; improved the overall imaging speed.
    • hash-based imaging
    • detection of easy (emtpy-block) and hard (encrypted block) to compress data
    • multi-threaded compression
    • sparse ranges
    • de-duplication


  • hash-based imaging
  • sparse or repeated ranges

Integrity checks

  • Integrity hash (MD5, SHA1, SHA256)
  • piecewise hashing

Image format

Implied features for an image format

  • High-speed imaging
  • Compact storage
  • Error-resistant storage (over a longer time)
  • Minimal overhead on read
  • Evidence bag
    • multiple images in one image format
    • support for additional information e.g. case data