SQL2K:How to insure that data is NOT recoverable by forensic metho

From: BAG (BAG_at_discussions.microsoft.com)
Date: 07/26/05 

Date: Mon, 25 Jul 2005 15:20:01 -0700

My customer has a lot of govt customers and has a non-classified SharePoint
2003 implementation with SQL2K for the backend (all SPS 2003 content is
stored in SQL server). They're very concerned about what to do if/when a user
unintentionally uploads a classified document to the site. Deleting the
content in SPS2003 executes the DELETE/COMMIT actions on the appropriate rows
in the SQL2K DB.

My question is, how do I make sure that the document (assume it's a mix of
text/image data and data pages) is completely UNrecoverable? I want to
provide my customer with reasonable confidence that every artifact on storage
media is overwritten, without having to resort to hardware confiscation.

For example, were this document stored on a filesystem, the customer would
consider it reasonable to delete the file, defrag the drive, then overwrite
the free space on the disk 7 times with 0's to make sure there's almost no
chance of retrieving the data.

Many thanks - any information is most welcome.

Relevant Pages

  • Re: Webservices references
    ... the "live" address in a config file of some description and at runtime read ... > we have a small pocketpc application that uses a webservice to connect to ... > everything works fine until we try to build a customer version. ... > is there a way around this or do u just overwrite every instance of the IP ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Webservices references
    ... Store ... >> we have a small pocketpc application that uses a webservice to connect ... >> everything works fine until we try to build a customer version. ... >> is there a way around this or do u just overwrite every instance of the ...
    (microsoft.public.dotnet.framework.compactframework)
  • Webservice Referencing
    ... we have a small pocketpc application that uses a webservice to connect to ... everything works fine until we try to build a customer version. ... is there a way around this or do u just overwrite every instance of the IP ...
    (microsoft.public.dotnet.framework.webservices)
  • Webservices references
    ... we have a small pocketpc application that uses a webservice to connect to ... everything works fine until we try to build a customer version. ... is there a way around this or do u just overwrite every instance of the IP ...
    (microsoft.public.dotnet.framework.compactframework)
  • Webservices References
    ... we have a small pocketpc application that uses a webservice to connect to ... everything works fine until we try to build a customer version. ... is there a way around this or do u just overwrite every instance of the IP ...
    (microsoft.public.pocketpc.developer)