- clean the file's cluster tip / slack space (that's the most important one)
- scramble the file name, date, etc.
- perhaps also erase the alternate data stream if it exists (although I guess adding that could be too much hassle)
That's really secure file deleting. Of course there are tons of erasers that do that, but the point is that when a user gives the task of secure deleting of some files to CC, CC should do the task securely on its own.
















