U.S. Department of Justice 

Office of Justice Programs 

National Institute of Justice 

Special REPORT

Test Results for Hardware Write Block Device: 

Tableau T8 Forensic USB Bridge (FireWire Interface) 

AUG. 08 

Office of Justice Programs 

Innovation • Partnerships • Safer Neighborhoods 

www.ojp.usdoj.gov

www.ojp.usdoj.gov/nij 
U.S. Department of Justice 

Office of Justice Programs 

810 Seventh Street N.W. 

Washington, DC 20531 

Michael B. Mukasey 

Attorney General 

Jeffrey L. Sedgwick 

Acting Assistant Attorney General 

David W. Hagy 

Director, National Institute of Justice 

This and other publications and products of the National Institute 

of Justice can be found at: 

National Institute of Justice 

www.ojp.usdoj.gov/nij 

Office of Justice Programs 

Innovation • Partnerships • Safer Neighborhoods 

www.ojp.usdoj.gov 
AUG. 08 

Test Results for Hardware Write Block Device: 

Tableau T8 Forensic USB Bridge (FireWire 

Interface) 

NCJ 223431 
David W. Hagy 

Director, National Institute of Justice 

This report was prepared for the National Institute of Justice, U.S. Department of Justice, by the 

Office of Law Enforcement Standards of the National Institute of Standards and Technology 

under Interagency Agreement 2003–IJ–R–029. 

The National Institute of Justice is a component of the Office of Justice Programs, which also 

includes the Bureau of Justice Assistance, the Bureau of Justice Statistics, the Office of 

Juvenile Justice and Delinquency Prevention, and the Office for Victims of Crime. 
Test Results for Hardware Write Block Device: 

Tableau T8 Forensic USB Bridge (FireWire Interface) 

June 2008 
 

August 2008 Page ii Results for Tableau T8 FW June 2008 
 

Contents 

Introduction..................................................................................................................................... 1 
 

1 Results Summary by Requirements........................................................................................ 3 
 

2 Test Case Selection................................................................................................................. 4 
 

3 Testing Environment............................................................................................................... 4 
 

3.1 Test Computers ............................................................................................................... 4 
 

3.2 Protocol Analyzer ........................................................................................................... 4 
 

3.3 Hard Disk Drives ............................................................................................................ 4 
 

3.4 Support Software ............................................................................................................ 5 
 

4 Test Results............................................................................................................................. 5 
 

4.1 Test Results Report Key ................................................................................................. 5 
 

4.2 Test Details ..................................................................................................................... 7 
 

4.2.1 HWB-01.................................................................................................................. 7 
 

4.2.2 HWB-03-file ......................................................................................................... 11 
 

4.2.3 HWB-03-img ........................................................................................................ 12 
 

4.2.4 HWB-05................................................................................................................ 13 
 

4.2.5 HWB-06................................................................................................................ 14 
 

4.2.6 HWB-08................................................................................................................ 15 
 

4.2.7 HWB-09................................................................................................................ 16 
 

August 2008 Page iii Results for Tableau T8 FW June 2008 
 

Introduction 

The Computer Forensics Tool Testing (CFTT) program is a joint project of the National 

Institute of Justice (NIJ), the research and development organization of the U.S. 

Department of Justice, and the National Institute of Standards and Technology’s (NIST’s) 

Office of Law Enforcement Standards, and Information Technology Laboratory. CFTT is 

supported by other organizations, including the Federal Bureau of Investigation, the U.S. 

Department of Defense Cyber Crime Center, Internal Revenue Service Criminal 

Investigation’s Electronic Crimes Program, and the U.S. Department of Homeland 

Security’s Bureau of Immigration and Customs Enforcement, U.S. Customs and Border 

Protection, and U.S. Secret Service. The objective of the CFTT program is to provide 

measurable assurance to practitioners, researchers, and other applicable users that the 

tools used in computer forensics investigations provide accurate results. Accomplishing 

this requires the development of specifications and test methods for computer forensics 

tools and subsequent testing of specific tools against those specifications. 

Test results provide the information necessary for developers to improve tools, users to 

make informed choices, and the legal community and others to understand the tools’ 

capabilities. This approach to testing computer forensic tools is based on well-recognized 

methodologies for conformance and quality testing. The specifications and test methods 

are posted on the CFTT Web site (http://www.cftt.nist.gov/) for review and comment by 

the computer forensics community. 

This document reports the results from testing the Tableau T8 Forensic Bridge 

(FireWire Interface) write blocker, against the Hardware Write Blocker (HWB) 

Assertions and Test Plan Version 1.0 and Hardware Write Blocker Device (HWB) 

Specification, Version 2.0, available at the CFTT Web site 

(http://www.cftt.nist.gov/hardware_write_block.htm). This specification identifies the 

following top-level tool requirements: 

•	 A hardware write block (HWB) device shall not transmit a command to a 
 

protected storage device that modifies the data on the storage device.
 


•	 An HWB device shall return the data requested by a read operation. 

•	 An HWB device shall return without modification any access-significant 
 

information requested from the drive.
 


•	 Any error condition reported by the storage device to the HWB device shall be 

reported to the host. 

August 2008 	 Page 1 of 16 Results for Tableau T8 FW June 2008 
 

Test results from other software packages can be found on NIJ’s computer forensics tool 

testing web page, http://www.ojp.usdoj.gov/nij/topics/technology/electroniccrime/cftt.htm. 

August 2008 Page 2 of 16 Results for Tableau T8 FW June 2008 
 

 

Test Results for Hardware Write Block Devices 

Device Tested: Tableau T8 Forensic USB Bridge1 

Model: T8 

Serial No: T005A016186,000ecc010008030a 

Firmware: Jul 26 2005 15:01:41 

Host to Blocker Interface: FireWire 

Blocker to Drive Interface: USB 

Supplier: Tableau, LLC 

Address: 	 N8 W22195 Johnson Drive, Suite 100 

Waukesha, WI 53186 

http://www.tableau.com/ 

1 Results Summary by Requirements 

•	 An HWB device shall not transmit a command to a protected storage device 

that modifies the data on the storage device. 

For all test cases run, the device always blocked any commands that would have 

changed user or operating system data stored on a protected drive. 

•	 An HWB device shall return the data requested by a read operation. 

For all test cases run, the device always allowed commands to read the protected 

drive. 

•	 An HWB device shall return without modification any access-significant 

information requested from the drive. 

For all test cases run, the device always returned access-significant information 

from the protected drive without modification. 

•	 Any error condition reported by the storage device to the HWB device shall 

be reported to the host. 

For all test cases run, the device always returned error codes from the protected 

drive without modification. 

1 Tableau produces this write block device for resale under various partner labels. See 

http://www.tableau.com for information on resellers. 

August 2008 	 Page 3 of 16 Results for Tableau T8 FW June 2008 
 

 

2 Test Case Selection 

Since a protocol analyzer was available for the interface between the blocker and the 

protected drive, the following test cases were appropriate: 

• HWB–01 

• HWB–03 

• HWB–05 

• HWB–06 

• HWB–08 

• HWB–09 

For test case HWB–03, two variations were selected: file (attempt to use operating 

system commands to create and delete files and directories from a protected drive) and 

image (use an imaging tool to attempt to write to a protected drive). 

3 Testing Environment 

The tests were run in the NIST CFTT lab. This section describes the hardware (test 

computers and hard drives) available for testing. 

3.1 Test Computers 

One test computer, JohnSteed, with the following configuration was used: 

Intel® Desktop Motherboard FIC IC-VL67 (865G; S478; 800MHz) 

BIOS Phoenix Award version v6.00PG 

Intel® PentiumTM 4 CPU 

Plextor DVDR PX–716A, ATAPI CD/DVD-ROM Drive 

Western Digital Corporation WD800JB-00JJC0, 80 GB ATA disk drive 

1.44 MB floppy drive 

Three IEEE 1394 ports 

Four USB ports 

3.2 Protocol Analyzer 

A Data Transit bus protocol analyzer (Bus Doctor Rx) was used to monitor and record 

commands sent from the host to the write blocker. Two identical protocol analyzers were 

available for monitoring commands. 

One of two Dell laptop computers (either Chip or Dale) was connected to each protocol 

analyzer to record commands observed by the protocol analyzer. 

3.3 Hard Disk Drives 

Two USB interface devices were used in testing: 

• 48–u12 is a Maxtor 3000LS with 80293248 sectors (40 GB). 

• D4–thumb is a USB flash memory drive. 

August 2008 Page 4 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

Drive label: 48-U12 

80293248 total number of sectors 

Non-IDE disk 

Model (F040L0)

N Start LBA Length Start C/H/S End C/H/S

1 X 000016065 080276805 0001/000/01 1023/254/63

2 S 000000063 000032067 0001/001/01 0002/254/63

3 x 000032130 000080325 0003/000/01 0007/254/63

4 S 000000063 000080262 0003/001/01 0007/254/63

5 x 000112455 002345490 0008/000/01 0153/254/63

6 S 000000063 002345427 0008/001/01 0153/254/63

7 S 000000000 000000000 0000/000/00 0000/000/00

8 P 000000000 000000000 0000/000/00 0000/000/00

9 P 000000000 000000000 0000/000/00 0000/000/00

10 P 000000000 000000000 0000/000/00 0000/000/00 

boot Partition type

0F extended 

01 Fat12 

05 extended 

0B Fat32 

05 extended 

07 NTFS 

00 empty entry

00 empty entry

00 empty entry

00 empty entry 

Drive label: d4-thumb 

505856 total number of sectors 

Model (usb2.0Flash Disk) 

3.4 Support Software 

The software in the following table was used to send commands to the protected drive. 

One widely used imaging tool, IXimager, was used to generate disk activity (reads and 

writes) consistent with a realistic scenario of an accidental modification of an unprotected 

hard drive during a forensic examination. This does not imply an endorsement of the 

imaging tool. 

Program Description 

sendSCSI A tool to send SCSI commands wrapped in the USB or IEEE 1394 

(FireWire) protocols to a drive. 

FS–TST Software from the FS–TST tools was used to generate errors from the hard 

drive by trying to read beyond the end of the drive. The FS–TST software 

was also used to setup the hard drives and print partition tables and drive 

size. 

IXimager An imaging tool (ILook IXimager version 1.0, August 25, 2004) for test 

case 04-img. 

4 Test Results 

The main item of interest for interpreting the test results is determining the conformance 

of the device with the test assertions. Conformance with each assertion tested by a given 

test case is evaluated by examining the Blocker Input and Blocker Output boxes of the 

test report summary. 

4.1 Test Results Report Key 

August 2008 Page 5 of 16 Results for Tableau T8 FW June 2008 
 

A summary of the actual test results is presented in this report. The following table 

presents a description of each section of the test report summary. 

Heading Description 

First Line Test case ID; name, model, and interface of device tested. 

Case Summary Test case summary from Hardware Write Blocker (HWB) 

Assertions and Test Plan Version 1.0. 

Assertions Tested The test assertions applicable to the test case, selected from 

Hardware Write Blocker (HWB) Assertions and Test Plan 

Version 1.0. 

Tester Name Name or initials of person executing test procedure. 

Test Date Time and date that test was started and completed. 

Test Configuration Identification of the following: 

1. Host computer for executing the test case. 

2. Laptop attached to each protocol analyzer. 

3. Protocol analyzers monitoring each interface. 

4. Interface between host and blocker. 

5. Interface between blocker and protected drive. 

6. Execution environment for tool sending commands 

from the host. 

Hard Drives Used Description of the protected hard drive. 

Blocker Input A list of commands sent from the host to the blocker. 

For test case HWB–01, a list of each command code 

observed on the bus between the blocker and the protected 

drive and a count of the number of times the command was 

observed is provided. 

For test cases HWB–03 and HWB–06, a list of each 

command sent and the number of times the command was 

sent. 

For test case HWB–05, a string of known data from a given 

location is provided for reference. 

Blocker Output A list of commands observed by the protocol analyzer on the 

bus from the blocker to the protected drive. 

For test case HWB–01, a list of each command code 

observed on the bus between the blocker and the protected 

drive and a count of the number of times the command was 

observed is provided. Also, a count of the number of unique 

commands sent (from the Blocker Input box) and a count of 

the number of unique commands observed on the bus 

between the blocker and the protected drive. 

August 2008 Page 6 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Heading Description 

For test cases HWB–03 and HW–-06, a list of each 

command sent and the number of times the command was 

sent. 

For test case HWB–05, a string read from a given location is 

provided for comparison to known data. 

For test case HWB–08, the number of sectors determined for 

the protected drive and the partition table are provided. 

For test case HWB–09, any error return obtained by trying to 

access a nonexistent sector of the drive is provided. 

Results Expected and actual results for each assertion tested. 

Analysis Whether or not the expected results were achieved. 

4.2 Test Details 

4.2.1 HWB-01 

Test Case HWB-01 Variation hwb-01 Tableau T8 FW 

Case Summary: HWB-01 Identify commands blocked by the HWB. 

Assertions Tested: HWB-AM-01 The HWB shall not transmit any modifying category operation to the protected storage device. 

HWB-AM-05 The action that a HWB device takes for any commands not assigned to the modifying, read or 

information categories is defined by the vendor. 

Tester Name: rpa 

Test Date: run start Thu Apr 12 11:04:08 2007 

run finish Thu Apr 12 11:16:05 2007 

Test Configuration: HOST: johnsteed 

HostToBlocker Monitor: dale 

HostToBlocker PA: aa00111 

HostToBlocker Interface: fw400 

BlockerToDrive Monitor: chip 

BlockerToDrive PA: aa00155 

BlockerToDrive Interface: usb 

Run Environment: linux 

Drives: Protected drive: 48-u12 

48-u12 is a Maxtor 3000LS with 80293248 sectors (40 GB) 

Blocker Input: Commands Sent to Blocker 

Count Commands 

1 AC MANAGE 

1 ASYNCHRONOUS CONNECTION 

1 BLANK

 1 CHANNEL USAGE 

1 CHG DEFINITN

 1 CLOS SESSION 

1 COMPARE 

1 CONNECT

 1 CONNECT AV 

1 CONNECTIONS 

1 COPY 

1 COPY/VERIFY

 1 CREATE DESCRIPTOR

 1 DIGITAL INPUT 

August 2008 Page 7 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Test Case HWB-01 Variation hwb-01 Tableau T8 FW 

1 DIGITAL OUTPUT

 1 DISCONNECT

 1 DISCONNECT AV 

1 ERASE

 1 ERASE(10)

 1 FORMAT UNIT

 1 GET CONFIG 

1 GET EVNT/STS 

1 GET PERFRMNC

 1 INPUT PLUG SIGNAL FORMAT 

1 INPUT SELECT 

1 INQUIRY 

1 LK/UNLK CACH 

1 LOAD/UNLOAD

 1 LOG SELECT

 1 LOG SENSE 

1 MECH STATUS

 1 MEDIUM SCAN

 2 MODE SELECT 

2 MODE SENSE(10)

 1 OBJECT NUMBER SELECT 

1 OPEN DESCRIPTOR 

1 OPEN INFO BLOCK 

1 OUTPUT PLUG SIGNAL FORMAT

 1 OUTPUT PRESET

 1 PAUSE/RESUME

 1 PERSISTENT RESERVE IN

 1 PERSISTENT RESERVE OUT 

1 PLAY AUD IDX 

1 PLAY AUD MSF 

2 PLAY AUDIO 

1 PLAY CD

 1 PLUG INFO

 1 PLY TRK RLTV

 1 PLY TRK RLTV(12)

 1 PRE-FETCH

 1 PREVENT/ALLOW MEDIUM REMOVAL 

1 RD BUF CPCTY 

1 RD GENERATN 

1 RD MSTR CUE 

1 RD STRUCTURE

 1 RD SUB-CHNL

 1 RD TOC/PMA

 1 RD UPDATED BLK 

1 READ BUFFER 

1 READ BULK LIMITS

 1 READ CAPACITY 

1 READ CD

 1 READ CD MSF 

2 READ DEFECT 

1 READ DESCRIPTOR 

1 READ ELEMENT STATUS 

1 READ FORMAT CAPACITY 

1 READ HEADER 

1 READ INFO BLOCK 

1 READ LONG

 1 READ REVERSE 

1 READ STATUS ATTACHED

 548 READ(10)

 1 READ(12)

 1 REASSIGN BLK 

1 RECEIVE DIAGNOSTIC RESULTS 

1 RECOVER BUFF DATA

 1 RELEASE(10)

 1 RELEASE(6) 

August 2008 Page 8 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Test Case HWB-01 Variation hwb-01 Tableau T8 FW 

1 REPAIR RZONE 

4 REPORT KEY 

1 REPORT LUNS 

1 REQ VOL ADDR 

1 RESERVE 

1 RESERVE(10)

 1 RESERVE(6) 

34 RESERVED 

1 REWIND/REZERO 

1 SCAN 

1 SEARCH DESCRIPTOR

 1 SECURITY 

1 SEEK(10)

 1 SEEK(6) 

1 SEND CUE SHT

 1 SEND DIAGNOSTIC 

1 SEND EVENT

 6 SEND KEY 

1 SET CD SPEED

 1 SET LIMITS 

1 SET RD AHEAD

 1 SET STREAMNG

 1 SIGNAL SOURCE

 1 SND OPC INFO 

1 SND STRUCTUR 

1 SPACE 

2 SRCH DATA EQ 

1 SRCH DATA HI 

2 SRCH DATA LO 

1 SRCH DATAHI

 1 START/STOP

 1 STOP PLY/SCN 

1 SUBUNIT INFO

 1 SYNCH CACHE 

1 TEST UNIT READY 

1 UNIT INFO 

1 UPDATE BLOCK

 1 VENDOR-DEPENDENT

 1 VERIFY(10)

 1 VERIFY(12)

 1 VERIFY(6) 

1 WRITE BUFFER 

1 WRITE DESCRIPTOR 

1 WRITE FILEMARK 

1 WRITE INFO BLOCK 

1 WRITE LONG

 1 WRITE SAME 

2 WRITE(10) 

1 WRITE(12) 

2 WRITE/VERIFY

 1 XDREAD(10) 

1 XDWRITE(10)

 1 XDWRITEREAD(10)

 1 XPWRITE(10) 

133 commands sent 

Blocker Output: Commands Allowed by Blocker 

Count Commands 

1 PREVENT/ALLOW

 548 READ(10) 

1 REQUEST_SENSE

 1 START/STOP

 1 SYNCH 

August 2008 Page 9 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

Test Case HWB-01 Variation hwb-01 Tableau T8 FW 

1 TEST

 1
 
 VERIFY 

133 commands sent, 7 commands allowed 

Results: Assertion & Expected Result Actual Result 

AM-01 Modifying commands blocked Modifying commands blocked 

AM-05 HWB behavior recorded HWB behavior recorded 

Analysis: Expected results achieved 

August 2008 Page 10 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

4.2.2 HWB-03-file 

Test Case HWB-03 Variation hwb-03-file Tableau T8 FW 

Case Summary: HWB-03 Identify commands blocked by the HWB while attempting to modify a protected drive with forensic 

tools. 

Assertions Tested: HWB-AM-01 The HWB shall not transmit any modifying category operation to the protected storage device. 

HWB-AM-05 The action that a HWB device takes for any commands not assigned to the modifying, read or 

information categories is defined by the vendor. 

Tester Name: rpa 

Test Date: run start Mon Apr 16 08:42:59 2007 

Test Configuration: HOST: johnsteed 

HostToBlocker Monitor: dale 

HostToBlocker PA: aa00111 

HostToBlocker Interface: fw400 

BlockerToDrive Monitor: chip 

BlockerToDrive PA: aa00155 

BlockerToDrive Interface: usb 

Run Environment: DOS 

Drives: Protected drive: 48-u12 

48-u12 is a Maxtor 3000LS with 80293248 sectors (40 GB) 

Blocker Input: Commands Sent to Blocker 

Count Commands 

5 MODE SENSE(6)

 10 READ CAPACITY 

426 READ(10)

 5 TEST UNIT READY 

Blocker Output: Commands Allowed by Blocker 

Count Commands 

426 READ(10) 

5 TEST 

Results: Assertion & Expected Result Actual Result 

AM-01 Modifying commands blocked Modifying commands blocked 

AM-05 HWB behavior recorded HWB behavior recorded 

Analysis: Expected results achieved 

August 2008 Page 11 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4.2.3 HWB-03-img 

Test Case HWB-03 Variation hwb-03-img Tableau T8 FW 

Case Summary: HWB-03 Identify commands blocked by the HWB while attempting to modify a protected drive with forensic 

tools. 

Assertions Tested: HWB-AM-01 The HWB shall not transmit any modifying category operation to the protected storage device. 

HWB-AM-05 The action that a HWB device takes for any commands not assigned to the modifying, read or 

information categories is defined by the vendor. 

Tester Name: rpa 

Test Date: run start Mon Apr 16 09:38:23 2007
 


run finish Mon Apr 16 10:54:22 2007
 


Test Configuration: HOST: johnsteed 
 

HostToBlocker Monitor: dale 
 

HostToBlocker PA: aa00111
 


HostToBlocker Interface: fw400 
 

BlockerToDrive Monitor: chip 
 

BlockerToDrive PA: aa00155
 


BlockerToDrive Interface: usb 
 

Run Environment: IX
 


Drives: Protected drive: D4-thumB 

Blocker Input: Commands Sent to Blocker 

Count Commands 

2 INQUIRY 

2 MODE SENSE(10)

 1 PREVENT/ALLOW MEDIUM REMOVAL 

2 READ CAPACITY 

5 READ DEFECT 

14 READ(10)

 17 TEST UNIT READY 

24 WRITE(10) 

Blocker Output: Commands Allowed by Blocker 

Count Commands 

1 PREVENT/ALLOW

 12 READ(10) 

1 REQUEST_SENSE

 17 TEST 

Results: Assertion & Expected Result 

AM-01 Modifying commands blocked 

AM-05 HWB behavior recorded 

 Actual Result 

Modifying commands blocked 

HWB behavior recorded 

Analysis: Expected results achieved 

August 2008 Page 12 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

4.2.4 HWB-05 
 

Test Case HWB-05 Variation hwb-05 Tableau T8 FW 

Case Summary: HWB-05 Identify read commands allowed by the HWB. 

Assertions Tested: HWB-AM-02 If the host sends a read category operation to the HWB and no error is returned from the 

protected storage device to the HWB, then the data addressed by the original read operation is returned to the 

host. 

Tester Name: rpa 

Test Date: run start Mon Apr 16 13:47:12 2007 

run finish Mon Apr 16 13:51:58 2007 

Test Configuration: HOST: johnsteed 

HostToBlocker Monitor: dale 

HostToBlocker PA: aa00111 

HostToBlocker Interface: fw400 

BlockerToDrive Monitor: none 

BlockerToDrive PA: none 

BlockerToDrive Interface: usb 

Run Environment: linux 

Drives: Protected drive: 48-u12 

48-u12 is a Maxtor 3000LS with 80293248 sectors (40 GB) 

Blocker Input: Commands Sent to Blocker 

Read sector 32767 for the string: 00002/010/08 000000032767 

Blocker Output: 00002/010/08 000000032767 

Results: Assertion & Expected Result Actual Result 

AM-02 Read commands allowed Read commands allowed 

Analysis: Expected results achieved 

August 2008 Page 13 of 16 Results for Tableau T8 FW June 2008 
 

 

 

 

 

 

 

 

 

 

 

 

4.2.5 HWB-06 
 

Test Case HWB-06 Variation hwb-06-img Tableau T8 FW 

Case Summary: 

Assertions Tested: 

HWB-06 Identify read and information commands used by forensic tools and allowed by the HWB. 

HWB-AM-02 If the host sends a read category operation to the HWB and no error is returned from the 

protected storage device to the HWB, then the data addressed by the original read operation is returned to the 

host. 

HWB-AM-03 If the host sends an information category operation to the HWB and if there is no error on the 

protected storage device, then any returned access-significant information is returned to the host without 

modification. 

HWB-AM-05 The action that a HWB device takes for any commands not assigned to the modifying, read or 

information categories is defined by the vendor. 

Tester Name: 

Test Date: 

Test Configuration: 

rpa 

run start Mon Apr 16 13:57:10 2007 

run finish Mon Apr 16 14:14:22 2007 

HOST: johnsteed 

HostToBlocker Monitor: dale 

HostToBlocker PA: aa00111 

HostToBlocker Interface: fw400 

BlockerToDrive Monitor: chip 

BlockerToDrive PA: aa00155 

BlockerToDrive Interface: usb 

Run Environment: IX 

Drives: Protected drive: D4-thumB 

Blocker Input: Commands Sent to Blocker 

Count Commands 

2 INQUIRY 

2 MODE SENSE(10)

 2 READ CAPACITY 

5 READ DEFECT 

15 READ(10)

 16 TEST UNIT READY 

23 WRITE(10) 

7 commands sent 

Blocker Output: Commands Allowed by Blocker 

Count Commands 

12 READ(10) 

16 TEST 

7 commands sent, 2 commands allowed 

Results: Assertion & Expected Result Actual Result 

AM-02 Read commands allowed Read commands allowed 

AM-03 Access Significant Information unaltered Access Significant Information unaltered 

AM-05 HWB behavior recorded HWB behavior recorded 

Analysis: Expected results achieved 

August 2008 Page 14 of 16 Results for Tableau T8 FW June 2008 
 

 

 

4.2.6 HWB-08 
 

Test Case HWB-08 Variation hwb-08 Tableau T8 FW 

Case Summary: HWB-08 Identify access significant information unmodified by the HWB. 

Assertions Tested: HWB-AM-03 If the host sends an information category operation to the HWB and if there is no error on the 

protected storage device, then any returned access-significant information is returned to the host without 

modification. 

Tester Name: rpa 

Test Date: run start Tue Apr 17 08:49:05 2007 

run finish Tue Apr 17 08:50:35 2007 

Test Configuration: HOST: johnsteed 

HostToBlocker Monitor: none 

HostToBlocker PA: none 

HostToBlocker Interface: fw400 

BlockerToDrive Monitor: none 

BlockerToDrive PA: none 

BlockerToDrive Interface: usb 

Run Environment: linux 

Drives: Protected drive: 48-u12 

48-u12 is a Maxtor 3000LS with 80293248 sectors (40 GB) 

Blocker Output: cmd: /mnt/floppy/partab hwb-08 johnsteed rpa /dev/sda -all 

80293248 total number of sectors 

Results: Assertion & Expected Result Actual Result 

AM-03 Access Significant Information unaltered Access Significant Information unaltered 

Analysis: Expected results achieved 

August 2008 Page 15 of 16 Results for Tableau T8 FW June 2008 
 

 

 

4.2.7 HWB-09 
 

Test Case HWB-09 Variation hwb-09 Tableau T8 FW 

Case Summary: HWB-09 Determine if an error on the protected drive is returned to the host. 

Assertions Tested: HWB-AM-04 If the host sends an operation to the HWB and if the operation results in an unresolved error on 

the protected storage device, then the HWB shall return an error status code to the host. 

Tester Name: rpa 

Test Date: run start Tue Apr 17 08:52:11 2007 

run finish Tue Apr 17 08:53:30 2007 

Test Configuration: HOST: johnsteed 
 

HostToBlocker Monitor: none
 


HostToBlocker PA: none 
 

HostToBlocker Interface: fw400 
 

BlockerToDrive Monitor: none 
 

BlockerToDrive PA: none 
 

BlockerToDrive Interface: usb 
 

Run Environment: linux
 


Drives: Protected drive: 48-u12 

48-u12 is a Maxtor 3000LS with 80293248 sectors (40 GB) 

Blocker Output: 04997/254/63 (max cyl/hd values) 

04998/255/63 (number of cyl/hd) 

80293248 total number of sectors 

cmd: /mnt/floppy/diskchg hwb-09 johnsteed rpa /dev/sda -read 90293248 0 2 

Disk addr lba 90293248 C/H/S 5620/126/11 offset 0 

Disk read error 0xFFFFFFFF at sector 5620/126/11 

Results: Assertion & Expected Result Actual Result 

AM-04 Error code returned Error code returned 

Analysis: Expected results achieved 

August 2008 Page 16 of 16 Results for Tableau T8 FW June 2008 
About the National Institute of Justice 

NIJ is the research, development, and evaluation agency of the U.S. Department of Justice. NIJ’s 

mission is to advance scientific research, development, and evaluation to enhance the administration of justice and public safety. NIJ’s principal authorities are derived from the Omnibus 

Crime Control and Safe Streets Act of 1968, as amended (see 42 U.S.C. §§ 3721–3723). 

The NIJ Director is appointed by the President and confirmed by the Senate. The Director establishes the Institute’s objectives, guided by the priorities of the Office of Justice Programs, the 

U.S. Department of Justice, and the needs of the field. The Institute actively solicits the views of 

criminal justice and other professionals and researchers to inform its search for the knowledge 

and tools to guide policy and practice. 

Strategic Goals 

NIJ has seven strategic goals grouped into three categories: 

Creating relevant knowledge and tools 

1. Partner with State and local practitioners and policymakers to identify social science research 

and technology needs. 

2. Create scientific, relevant, and reliable knowledge—with a particular emphasis on terrorism, 

violent crime, drugs and crime, cost-effectiveness, and community-based efforts—to enhance 

the administration of justice and public safety. 

3. Develop affordable and effective tools and technologies to enhance the administration of 

justice and public safety. 

Dissemination 

4. Disseminate relevant knowledge and information to practitioners and policymakers in an 

understandable, timely, and concise manner. 

5. Act as an honest broker to identify the information, tools, and technologies that respond to 

the needs of stakeholders. 

Agency management 

6. Practice fairness and openness in the research and development process. 

7. Ensure professionalism, excellence, accountability, cost-effectiveness, and integrity in the 

management and conduct of NIJ activities and programs. 

Program Areas 

In addressing these strategic challenges, the Institute is involved in the following program areas: 

crime control and prevention, including policing; drugs and crime; justice systems and offender 

behavior, including corrections; violence and victimization; communications and information 

technologies; critical incident response; investigative and forensic sciences, including DNA; lessthan-lethal technologies; officer protection; education and training technologies; testing and 

standards; technology assistance to law enforcement and corrections agencies; field testing of 

promising programs; and international crime control. 

In addition to sponsoring research and development and technology assistance, NIJ evaluates 

programs, policies, and technologies. NIJ communicates its research and evaluation findings 

through conferences and print and electronic media. 

To find out more about the National 

Institute of Justice, please visit: 

http://www.ojp.usdoj.gov/nij 

or contact: 

National Criminal Justice 

Reference Service 

P.O. Box 6000 

Rockville, MD 20849–6000 

800–851–3420 

http://www.ncjrs.gov