Re: Tracking Confidential Files - solution?
From: Karl Levinson [x y] mvp (levinson_k_at_despammed.com)
Date: 08/14/04
- Next message: Roger Abell: "Re: Tracking Confidential Files - solution?"
- Previous message: Bill Sanderson: "Re: DSO EXPLOIT"
- In reply to: SBC: "Tracking Confidential Files - solution?"
- Next in thread: Roger Abell: "Re: Tracking Confidential Files - solution?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 14 Aug 2004 11:13:53 -0400
For this scenario, I would simply search all the hard drives for files of
that name. To do that, use a script that connects remotely via windows
networking and the NET USE command and search, or set up a script that runs
locally on each computer [less reliable] either in the user's logon script
or via a scheduled task / the AT command.
Of course, if a file were renamed, it wouldn't show up in your search. But
you don't seem too concerned about that in this scenario. To fix that,
you'd often try to compare file checksums, but those wouldn't match if the
file were changed in any way.
If you have Active Directory, SRP Software Restriction Policies can prevent
certain files from being executed by certain login IDs or computers without
permission.
"SBC" <SBC@discussions.microsoft.com> wrote in message
news:52EC6709-1813-453E-989F-31275FC60067@microsoft.com...
> We have recently been asked whether it was possible to track confidential
> files that may be temporarily copied to a workstation from a share and
> inadvertently left on the workstation.
>
> We have several shares that contain confidential files. Sometimes, an
> application specialist will need to copy these files down from a share to
a
> user's workstation to troubleshoot and/or resolve an issue. They should
> remove the file from the user's workstation once they are done; however,
> being the imperfect beings we all are, they may sometimes forget.
>
> In this case, we would like to be able to track the files somehow and then
> run a query daily or weekly to find these files and delete them.
>
> Using SMS, it would be relatively easy if we were dealing with files that
> were known and unknown files were never introduced, but that will not be
the
> case from what I have been told. That is, new files will probably be
created
> frequently. However, the shares in which these files are located will
remain
> constant.
>
> Is there a method or application that can be employed to track files
> originating in a share and then delete these files (preferably
automatically)?
>
> Thanks!
>
- Next message: Roger Abell: "Re: Tracking Confidential Files - solution?"
- Previous message: Bill Sanderson: "Re: DSO EXPLOIT"
- In reply to: SBC: "Tracking Confidential Files - solution?"
- Next in thread: Roger Abell: "Re: Tracking Confidential Files - solution?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|