Destruction at an approved metal destruction facility i. Application of an abrasive substance emery wheel or disk sander to a magnetic disk or drum recording surface. Make certain that the entire recording surface is completely removed before disposal. Also, ensure proper protection from inhaling the abraded dust. Acid solutions should be used in a well-ventilated area only by qualified personnel. Application of acid activator Dubias Race A and stripper Dubias Race B to a magnetic drum recording surface.
|Published (Last):||10 July 2004|
|PDF File Size:||6.69 Mb|
|ePub File Size:||17.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
Destruction at an approved metal destruction facility i. Application of an abrasive substance emery wheel or disk sander to a magnetic disk or drum recording surface.
Make certain that the entire recording surface is completely removed before disposal. Also, ensure proper protection from inhaling the abraded dust. Acid solutions should be used in a well-ventilated area only by qualified personnel. Application of acid activator Dubias Race A and stripper Dubias Race B to a magnetic drum recording surface. Technical acetone should then be applied to remove residue from the drum surface. The above should be done in a well-ventilated area, and personnel must wear eye protection.
Extreme caution must be observed when handling acid solutions. This procedure should be done only by qualified and approved personnel. Complete: Purge every system on the LAN and contaminated backups. Declassify the system s after observing the organization's respective validation and review procedures.
Then, reload software and data files from uncontaminated backup. Partial: Find where written, purge affected systems and contaminated backups. Then, reload from clean backup. Limited: Find where contaminating information is written.
Purge file, "wipe" unallocated disk space and swap temp file space on affected systems. If necessary, reload from clean backup. Unknown degree of Assurance Overwrites contaminating file, free space, temp space Possibly no data loss Unbalanced solution operations drives security Very little downtime Minimizes impact to majority of users May or may not require use of good backups.
The system is accredited to at least C2 or C2 functionality. The data is time sensitive i. The system frequently writes to the drive location s where the data was inadvertently written or suspected to be written. Note: generally, an e-mail server is overwritten more frequently than an application or file server. The amount of information needing to be purged is less than 0. The system DAA approves of using the limited purge in this particular instance.
AFSSI is a software-based data sanitization method used in various file shredder and data destruction programs to overwrite existing information on a hard drive or another storage device. Erasing a hard drive using the AFSSI data sanitization method will prevent all software based file recovery methods from lifting information from the drive and is also likely to prevent most hardware-based recovery methods from extracting information. Keep reading to learn how this data wipe method actually works and which sanitization methods are similar to it. All data sanitization methods are similar in some ways but slightly different in others. For example, the VSITR sanitization method writes several passes of ones and zeros before finishing with a random character. Write Zero only writes one pass of zeros, while Random Data uses random characters.
Guide to the AFSSI-5020 Data Sanitization Method
Can anyone explain what happens why I enable he overwrite function with BB, how does it ensure the data cannot be recovered if I overwrite a file on a hard disk or usb stick? I do think BB is a great solution for Linux, but how can I trust a functin that just says overwrite with no explanation of what is meant by this term, from a technical stance. Under BB's preferences options why not enable users to choose standard secure erasing patterns like:. Thank you to all contributors. User contributed content, such as forum posts and comments, is copyrighted by the contributors. Unless otherwise noted, the web page content is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3. The logo is copyrighted under the GPL.