American Department of Defense 5220.22-M standard wipe?
Moderators: dajhorn, Eraser DevTeam, Eraser Moderators
4 posts
• Page 1 of 1
American Department of Defense 5220.22-M standard wipe?
by ueivar » Tue Feb 10, 2004 1:53 pm
How is the DBAN implementation of DOD 5220.22-M actually done?
As I understand it after reading the US Department of Defense 5220.22-M Clearing and Sanitization Matrix, there are three methods listed for overwriting data on a harddisk.
DOD 5220.22-M c: Overwrite all addressable locations with a single character, 1 pass.
DOD 5220.22-M d: Overwrite all addressable locations with a character, its complement, then a random character and verify, 3 passes + verify on last pass.
DOD 5220.22-M e: Overwrite all addressable locations with a character, its complement, then a random character, 3 passes.
Since the DBAN implementation of DOD 5220.22-M uses 7 passes +verify on the last pass one could guess that this might be the combination of DOD 5220.22-M e + DOD 5220.22-M c + DOD 5220.22-M d.
Is this right?
If so, DBAN is clearly exceeding the demands of DOD 5220.22-M - and a wiping alternative that corresponds to DOD 5220.22-M d or e should be added for those who just need DOD 5220.22-M compliance (to save time).
Have got it wrong?
As I understand it after reading the US Department of Defense 5220.22-M Clearing and Sanitization Matrix, there are three methods listed for overwriting data on a harddisk.
DOD 5220.22-M c: Overwrite all addressable locations with a single character, 1 pass.
DOD 5220.22-M d: Overwrite all addressable locations with a character, its complement, then a random character and verify, 3 passes + verify on last pass.
DOD 5220.22-M e: Overwrite all addressable locations with a character, its complement, then a random character, 3 passes.
Since the DBAN implementation of DOD 5220.22-M uses 7 passes +verify on the last pass one could guess that this might be the combination of DOD 5220.22-M e + DOD 5220.22-M c + DOD 5220.22-M d.
Is this right?
If so, DBAN is clearly exceeding the demands of DOD 5220.22-M - and a wiping alternative that corresponds to DOD 5220.22-M d or e should be added for those who just need DOD 5220.22-M compliance (to save time).
Have got it wrong?
- ueivar
by dajhorn » Wed Feb 25, 2004 2:26 am
How is the DBAN implementation of DOD 5220.22-M actually done?
It is the same algorithm as is in the Heidi Eraser product.
Since the DBAN implementation of DOD 5220.22-M uses 7 passes +verify on the last pass one could guess that this might be the combination of DOD 5220.22-M e + DOD 5220.22-M c + DOD 5220.22-M d.
Is this right?
Yes, correct.
If so, DBAN is clearly exceeding the demands of DOD 5220.22-M - and a wiping alternative that corresponds to DOD 5220.22-M d or e should be added for those who just need DOD 5220.22-M compliance (to save time).
The latest beta has a short 3-pass variant of the DoD wipe.
DBAN uses the long method because I wanted DBAN to have parity with competing products.
Have got it wrong?
No.
- dajhorn
- Posts: 458
- Joined: Sun Jan 19, 2003 12:25 pm
- Location: Canada
by beiss » Thu Jul 21, 2005 9:42 am
Hello,
Which method does the short wipe use: DOD 5220.22-M d, as in the standard stated or DOD 5220.22-M e? If DOD 5220.22-M d is used how is the verify process realized?
Which method sequence does the long wipe use: DOD 5220.22-M c,d,e or an other?
Which method does the short wipe use: DOD 5220.22-M d, as in the standard stated or DOD 5220.22-M e? If DOD 5220.22-M d is used how is the verify process realized?
Which method sequence does the long wipe use: DOD 5220.22-M c,d,e or an other?
- beiss
- Posts: 1
- Joined: Tue Jul 19, 2005 1:29 pm
4 posts
• Page 1 of 1
Return to DBAN (Dariks Boot and Nuke) Support
Who is online
Users browsing this forum: No registered users and 3 guests