I thought that the DOD no longer recognized disk wiping as an acceptable means of sanitization, and that the only recognized methods now included physical destruction of said disk? Or maybe that was the Pentagon . . . btw, that document is over 2 years old . . .
James Winzenz Infrastructure Engineer - Security Pulte Homes Information Services -----Original Message----- From: Joe Heaton [mailto:[EMAIL PROTECTED] Posted At: Tuesday, April 29, 2008 10:34 AM Posted To: NTSysadmin Conversation: KillDisk and Symantec Ghost? Subject: RE: KillDisk and Symantec Ghost? Right, I meant sanitization when I said wipe. I've looked at those pages, and agree with the requirements, but there's really nothing specified in that document on how a hard drive should be erased, simply that "IS resources shall be sanitized before they are released from classified information controls or released for use at a lower classification level." I'm just not sure why you're using that as an end-all/be-all reference in your statement "Accept no substitutes." Wouldn't it be better to have some sort of reference that tells you to what degree you have to go in order to declare the media sanitized? I'm not trying to flame you, or anything, but it just kind of bothers me that people cite references that don't really say anything. Joe Heaton -----Original Message----- From: David W. McSpadden [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 9:55 AM To: NT System Admin Issues Subject: Re: KillDisk and Symantec Ghost? 53,54,58-61,66,69,84 all talk about media an in 58-61 it talks about cleaning and sanitation of the media but wiping is not mentioned.... ----- Original Message ----- From: "Joe Heaton" <[EMAIL PROTECTED]> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> Sent: Tuesday, April 29, 2008 12:25 PM Subject: RE: KillDisk and Symantec Ghost? Where exactly in that 106 page document does it tell you about hard drive erasure, other than the one liner that says that media should be wiped? Maybe I just missed it... Joe Heaton -----Original Message----- From: Christopher J. Bosak [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 7:49 AM To: NT System Admin Issues Subject: RE: KillDisk and Symantec Ghost? DoD Requirements for Hard Drive erasure. Accept no substitutes. http://www.dtic.mil/whs/directives/corres/pdf/522022mchaps.pdf Either that, or as Terry stated, destroy the drive and buy a new one. Christopher J. Bosak Vector Company c. 847.603.4673 [EMAIL PROTECTED] "You need to install an RTFM Interface, due to an LBNC issue." - B.O.F.H. (Merged 2 into 1) - Me -----Original Message----- From: Terry Dickson [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 09:45 hrs To: NT System Admin Issues Subject: RE: KillDisk and Symantec Ghost? I do not think you are defeating anything putting a ghost image back on. We also use Killdisk for our Sata Drives we have a hardware device for the IDE Drives. These programs and devices make it harder to recover old data. I have heard the data can be written over 7 or more times and still be recovered under the right circumstances. Complying with the Auditors usually makes you life easier. I would continue to do this unless you come up with something better, and by better I would say maybe more secure like a 7 or more times wipe. Or just remove and destroy the drive. At the current price of new drives it would be almost cheaper to replace the drive with a new one rather than taking the time to wipe 3+ times. -----Original Message----- From: David W. McSpadden [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 9:36 AM To: NT System Admin Issues Subject: KillDisk and Symantec Ghost? I have KillDisk and run it three times on a machine. (Free version) Then I ghost an image onto the machine. Am I defeating the KillDisk by using the ghosted image of an old machine or could I even reimage the machine after KillDisking and Ghosting the old image to create a new KillDisked/Ghosted machine? I am wanting to comply with auditors on wiping the drive at least three times and putting XP pro back on the machine using a ghosted image. Any recommendations? IT works, but keeping IT working is the hard part. Automation is great, until it breaks. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ______________________________________________________ This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by email and delete the message and any file attachments from your computer. Thank you. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
