This is a shot in the dark but I'm going to give it a shot. 

This is somewhat related to an earlier question I posed about  limitations of Audit Trail and possible ways to get around it. The governmental entity I am working with needs to have an audit log of field changes made to the system but they are also required to not store SS#'s and certain other information past a very short period of time (a time shorter than they are required to store the audit information). Simply having the log files locked down is not an acceptable solution according to their policies and procedures, so I can't just run a DB script to remove them from the SQL tables only.

Since there is no way to turn on/off auditing of fields on a per field basis we need some method to sanitize the data that is in audit trail while keeping the ability to see that user "John Doe" edited fields on the document. I thought that if I could write a script that would sanitize those fields (by putting in 999-99-9999 in the SS# field entries for example) I could set the rollover logs to kick off everyday, sanitize the file and put the sanitized file in another location that audit trail will read from. This would not allow them to see the changes until the next day but that would be acceptable to them. 

Is there any documentation out there that might help with this?