Encase is an all-in-one computer forensics suite from Guidance Software Inc.
Perhaps the de facto standard for forensic analyses in law enforcement, Guidance Software's EnCase Forensic encase} uses a proprietary format for images, reportedly based on ASR Data's Expert Witness Compression Format. EnCase's Evidence File .E01) format contains a physical bitstream of an acquired disk, prefixed with a '"Case Info" header, interlaced with CRCs for every block of 64 sectors~(32 KB), and followed by a footer containing an MD5 hash for the entire bitstream. Contained in the header are the date and time of acquisition, an examiner's name, notes on the acquisition, and an optional password; the header concludes with its own CRC.
Version 3 of The Encase F introduced an "error2" sections that it uses to record the location and number of bad sector chunks. The way it handles the sections it can't read is that those areas are filled with zero. Then Encase displays to the user the areas that could not be read when the image was acquired. The granularity of unreadable chunks appears to be 32K.
File Systems Understood
File Search Facilities
Can it build timelines and search by creation date?
Can it search? Does it build an index? Can it focus on file types or particular kinds of metadata?
Can it create hashes of files and/or blocks? Can it compare these hash values to any databases? What sort of hash functions does it use?
Evidence Collection Features
Can it sign files? Does it keep an audit log?
Encase from at least in version 3, 4 and 5 can sign the data of the media it acquires. It does this by calculating a MD5 hash of the original media data and adds a hash section to the last of the segment files.
Originally written in (YEAR), it has now developed into a Forensic Edition and an Enterprise Edition.
Is it commercial or open source? Are there other licensing options?
EnCase Homepage - http://www.guidancesoftware.com/lawenforcement/ef_index.asp