Difference between pages "Write Blockers" and "Books"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Commercial)
 
m
 
Line 1: Line 1:
'''Write blockers''' are devices that allow acquisition of information on a [[hard drive|drive]] without creating the possibility of accidentally damaging the drive contents. They do this by allowing read commands to pass but by blocking write commands, hence their name.
+
=General books about forensics=
  
There are two ways to build a write-blocker: the blocker can allow all commands to pass from the computer to the drive except for those that are on a particular list. Alternatively, the blocker can specifically block the write commands and let everything else through.
+
[http://www.amazon.com/gp/product/0849381274/ Principles and Practice of Criminalistics: The Profession of Forensic Science], by  Keith Inman and Norah Rudin.  (Highly recommended).
  
Write blockers may also include drive protection which will limit the speed of a drive attached to the blocker. Drives that run at higher speed work harder(the head moves back and forth more often due to read errors). This added protection could allow drives that can not be read at high speed (UDMA modes) to be read at the slower modes (PIO).
 
  
There are two types of write blockers, Native and Tailgate. A Native device uses the same interface on for both in and out, for example a IDE to IDE write block. A Tailgate device uses one interface for one side and a different one for the other, for example a Firewire to SATA write block.
+
=Books about computer forensics=
 
+
Steve Bress and Mark Menz invented hard drive write blocking (US Patent 6,813,682).
+
 
+
There are both hardware and software write blockers. Some software write blockers are designed for a specific operating system. One designed for Windows will not work on Linux. Most hardware write blockers are software independent.
+
 
+
= Hardware Write Blockers =
+
 
+
'''Hardware write blockers''' can be either [[IDE]]-to-IDE or [[Firewire]]/[[USB]]-to-IDE. Simson prefers the IDE-to-IDE because they deal better with errors on the drive and make it easier to access special information that is only accessible over the IDE interface. You may feel differently.
+
 
+
NIST test results are here: http://www.nist.gov/itl/ssd/cs/cftt/cftt-hardware-write-block.cfm
+
 
+
== Commercial ==
+
 
+
; [[ICS Drive Lock]]
+
: http://www.ics-iq.com/Super-DriveLock-Write-Blocker-Write-Protector-p/f.gr-0028-0000.htm
+
 
+
; MyKey Technology, Inc. NoWrite FPU and FlashBlock II
+
: 1.8"/2.5"/3.5"/ IDE to IDE, FireWire/USB to IDE & SATA, all media types - NIST Ver. 2 accepted 
+
: http://www.mykeytech.com/
+
 
+
; [[Tableau]] write blockers for IDE, SATA, SCSI, USB  NIST Ver. 1 accepted
+
: http://www.tableau.com/index.php?pageid=products
+
 
+
; WiebeTech write-blockers for almost any disk drive: 2.5"/3.5" IDE, SCSI, SATA, ...
+
: http://wiebetech.com/home.php?home=5  NIST Ver. 1 accepted
+
 
+
= Software Write Blockers =
+
 
+
'''Software write blockers''' can be either tailored to an individual operating system or can be an independent boot disk. Their main upsides are with ease of use, since they are on a CD and do not require you to open up the case, and speed since they do not become a bottle neck.
+
 
+
== Commercial ==
+
 
+
; [[SAFE Block XP]]
+
: SAFE Block XP is a software-based write blocker designed for the Windows XP Operating System. It comes in both 32 and 64 bit options. NIST Ver. 1.2 accepted
+
: http://www.forensicsoft.com/
+
 
+
; [[MacForensicsLab Write Controller]]
+
: MacForensicsLab Write Controller is a software-based write blocker designed for the Mac OS X operating system.  It runs on both 32 and 64 bit versions of Mac OS X 10.4 or later.
+
: http://www.macforensicslab.com/ProductsAndServices/index.php?main_page=product_info&cPath=1&products_id=339
+
 
+
[[Category:Disk Imaging]]
+

Revision as of 11:16, 29 November 2005

General books about forensics

Principles and Practice of Criminalistics: The Profession of Forensic Science, by Keith Inman and Norah Rudin. (Highly recommended).


Books about computer forensics