skip navigation


Abstract Database

Register for Latest Research

Stay Informed
Register with NCJRS to receive NCJRS's biweekly e-newsletter JUSTINFO and additional periodic emails from NCJRS and the NCJRS federal sponsors that highlight the latest research published or sponsored by the Office of Justice Programs.

NCJRS Abstract

To download this abstract, check the box next to the NCJ number then click the "Back To Search Results" link. Then, click the "Download" button on the Search Results page. Also see the Obtain Documents page for direction on how to access resources online, via mail, through interlibrary loans, or in a local library.


NCJ Number: 209832 Add to Shopping cart Find in a Library
Title: Test Results for Software Write Block Tools: PDBLOCK Version 2.00
Corporate Author: Office of Law Enforcement Standards (OLES)
United States of America
Date Published: June 2005
Page Count: 88
Sponsoring Agency: National Institute of Justice (NIJ)
Washington, DC 20531
National Institute of Justice/NCJRS
Rockville, MD 20849
Office of Law Enforcement Standards (OLES)
Gaithersburg, MD 20899-8102
Grant Number: 2003-IJ-R-029
Sale Source: National Institute of Justice/NCJRS
Box 6000
Rockville, MD 20849
United States of America
Document: PDF
Type: Report (Technical); Test/Measurement
Format: Document
Language: English
Country: United States of America
Annotation: This report presents the results from testing PDBLOCK Version 2.00, copyrighted by Digital Intelligence, Inc., in 1999, against Software Write Block Tool Specification & Test Plan Version 3.0.
Abstract: This specification sets the following top-level tool requirements: it shall not allow a protected drive to be changed; it shall not prevent obtaining any information from or about any drive; and it shall not prevent any operations to a drive that is not protected. All 40 test cases listed in the specification were applied to PDBLOCK Version 2.00. For all test cases run, the tool always blocked all write commands sent to a protected drive; however, the tool did not block some commands from the configuration and miscellaneous categories that were either undefined (invalid) or outmoded and not routinely used by current software. These commands in current BIOS implementations do not write to a hard drive, but in the future they could be defined such that they would change the content or accessibility of a protected drive. In the test specification these commands are therefore included in categories that should be blocked. Five commands in the configuration category were not blocked: Initialize Drive parameters (0x09), PS/2 ESDI Diagnostic (0x0E), PC/XT Controller Ram Diagnostic (0x12), the controller drive diagnostic command (0x13), and Controller Internal Diagnostic (0x14). The tool only blocked three commands in the miscellaneous category (command codes 0x1A, 0x22, and 0xED). For all test cases run, the tool always allowed commands to obtain information from any protected drives; and the tool always allowed any command to access any unprotected drives for all test cases run. Extensive tabular data
Main Term(s): Computer software
Index Term(s): Computer abuse; Computer crime prevention measures; Computer privacy and security
Note: NIJ Special Report; downloaded November 8, 2005.
To cite this abstract, use the following link:

*A link to the full-text document is provided whenever possible. For documents not available online, a link to the publisher's website is provided. Tell us how you use the NCJRS Library and Abstracts Database - send us your feedback.