|  | 
   The $ERAPAT erasure pattern buffer service was developed to allow sites
   to specify the pattern(s) used for the erasure buffer used by various
   OpenVMS system service routines, and to optionally allow the user to
   select US Department of Defense (US DoD) erasure patterns.
   Declassification also requires correctly handling issues of magnetic
   remanence and device-specific requirements such as bad-block handling,
   which cannot typically be handled by the erasure pattern tools alone,
   or cannot be handled by the erasure pattern tools.
   I am aware of relatively few tools rated for storage declassification,
   and these tools are specific to a specific class of disks and/or tapes.
   There are previous discussions of security erasure requirements around,
   and there are a few tools designed to comply with US DoD requirements
   for specific disk and tape devices.
   See ATPS::SEVMS note 285.*, SSAG::ASK_SSAG notes 93.*, 523.*, 680.*,
   720.*, 1487.*, 2074.*, 2453.*, 2518.*, 3637.*, 4797.*, 5092.*, 5610.*,
   and various others.  There are also likely some discussions on this
   topic over in your area, in KETJE::SECURITY_INFORMATION.
 | 
|  |   re .1:
    
>   I am aware of relatively few tools rated for storage declassification,
>   and these tools are specific to a specific class of disks and/or tapes.
    
    I've got some tools rated for storage declassification - a 5lb sledge
    hammer, tin of petrol and a box of matches ;-)
    
    						John Gillings, Sydney CSC
 | 
|  |     
:>   I am aware of relatively few tools rated for storage declassification,
:>   and these tools are specific to a specific class of disks and/or tapes.
:    
:    I've got some tools rated for storage declassification - a 5lb sledge
:    hammer, tin of petrol and a box of matches ;-)
   Sorry John, add a forge to the list and slag the disk, and I might buy
   off that the disks are actually declassified -- without that, what you
   are proposing :-) won't degauss the media reliably.  (Seriously.)
 |