|
midrange.com
You won't see complete records perhaps, but if you look at the data within
DST you will be able to see more than you will probably be comfortable
with. Enough to read names, SSNs, and ICD-9 or CPT codes was what I
remember seeing. (Your record layouts will determine if the chunks of data
are usable for anything...)
I was told that at one point (break the arrays and it won't be readable),
and was surprised to see how much was 'legible' within DST. The method
mentioned in the link that Shalom Carmel posted does a pretty good at
cleaning things up (delete disk unit data), where just breaking the arrays
doesn't. ESPECIALLY for the confidentiality concerns that a hospital
has... (that's where I worked when I checked the items from DST). I would
be comfortable with going to the effort of zeroing the data if you know
where the drives are 'going to'. Destroying the units is probably extreme
in most cases, but i'm sure it is a necessary step for some shops.
"John Candidi"
<jacandidi@rutger
sinsurance.com> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
09/20/2005 03:17 Subject
PM RE: complete "scrubbing" of our
data from the disk
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
If they are raided, just break the arrays by throwing some of them away
today out of some of the arrays and other another day. Can't read the data
if the arrays are broken. I believe
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Henza, Guy
Sent: Tuesday, September 20, 2005 1:19 PM
To: midrange-l@xxxxxxxxxxxx
Subject: complete "scrubbing" of our data from the disk
We are going to get rid of some disks. How do I do a complete
bit-overwrite before disposal?
Regards,
Guy Henza
Tri-State Hospital Supply Corporation
301 Catrel
Howell MI 48844
fon (517) 546-5400 x1312
fax (517) 540-1513
GHenza@xxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT0002C4FA
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
