Re: IBM i data deletion

I'd assume the IFS works just like any other OS file system.

But the given answer, re-write with blanks before deleting, would be
applicable for both IFS and DB2.

You could also look at porting a version of "shred" to PASE or QSH.

Charles


On Tue, Sep 13, 2016 at 1:20 PM, Mike Cunningham <mike.cunningham@xxxxxxx>
wrote:

I know that in a windows environment when you delete a file you really
just delete the directory entry that tells you the name of the file and
where it is on disk, and that the data in the file still exists at that
point and can be retrieved. Does the IFS on IBM i work the same way, and if
so, is there a way to actually overwrite the data space associated with a
file so it is unreadable? Same question for DB2. I know when a record is
deleted its not really deleted because there are utilities that can
undelete a record. And that a RGZPFM gets rid of deleted records but even
doing that does it make all the deleted records unreadable on disk?

This question is in relation to a PCI-DSS Requirement 3 that states
"Processes for secure deletion of data when no longer needed" and applies
to even data that is encrypted. Instead of just deleting records from any
database that has card holder data in it (encrypted) should the first step
being updating the card data in the record to blanks first so the blanks
are written to disk and then deleting the record? That way even if someone
was able to access a deleted record the card data would not be there
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.