Re: Security Event Log (audit object access) logging too much?

From: Roc (
Date: 06/06/03

  • Next message: God Bless Texas: "Re: Islam hacks Vatican? Let's Not Be Sentimental!"
    Date: Fri, 6 Jun 2003 13:43:59 -0500

    "- AJS" <a smith att window products dit com> wrote in message
    > "Roc" <> wrote:
    > >I've set up audit logging on my Windows 2000 SP3 file server.
    > >
    > >I want the security event log to log every time a file changes in a
    > >subdirectory; meaning the data contained within the file is modified. I
    > >also want file deletions logged.
    > >
    > >I set up the Audit Logging on the directory to log successful access by
    > >"Everyone" and checked the boxes labeled "Create Files / Write Data",
    > >"Create Folders / Append Data", "Delete Subfolders and Files", and
    > >I did not get the results I anticipated in the event log. I scaled back
    > >auditing this morning to include only the check boxes "Create Files /
    > >Data" and "Delete", hoping this might fix my problem, but figured I'd
    > >it looking for ideas anyhow...
    > >
    > >Specifically, my problem is that when I look at Event Log, it reports
    > >something like the following: (results from dumpel.exe)
    > >
    > >"05/31/2003","07:51:24","Security","AUDITSUCCESS","Something",560,"Some
    > >7)/username/DOMAIN/(0x0,0x11EC7581)/%%1538 %%4417 %%4418
    > >%%4423 %%4424 /-/"
    > >
    > >Now, I know "username" did not *modify* the EXE, the person only ran the
    > >remotely from their workstation. This keeps happening over and over, and
    > >pollutes the data I am trying to collect - I don't know if the file is
    > >actually modified or just being "accessed". (The file server holds
    > >thousands of EXEs, none of which are changed).
    > >
    > >My suspicion is that a handle to the server object is being created to
    > >the workstation the actual file being accessed remotely. My audits are
    > >logging the memory-based "copies" of the objects the workstation
    > >and when the workstation closes the file, the object is deleted from
    > >memory - and that delete is also logged in the Security log. This seems
    > >fit with what I'm seeing in the log - 2 entries per file that is
    > >*accessed* - not just modified (well, the memory *is* modified, so
    > >appears correct - but I don't want to know about that stuff). Most of my
    > >files are not being modified or deleted - but how can I tell them apart?
    > >
    > >1. Is this a correct assesment?
    > >2. And more importantly, can I audit only changes & deletes to files like
    > >want?
    > Hi Mike,
    > A couple things come to mind.
    > 1) The Audit events should only be tripped by File Write, File Delete
    > processes, not removal from memory after Execution. I do Not know the
    cause of
    > the log entries, but they do not match my own quick testing of the same
    > 2) To 'Save Changes' in many documents requires Delete priv's in order to
    > remove the old copy. MS Word is one such app.
    > 3) Let's fix your issue, and then audit.
    > Consider using XCACLS.EXE from the resource kit, and work from the
    > assumption: You need to secure all files in %Path% with an .EXE extension.
    > First, run the following to APPLY Everyone=Read&Execute only on
    > XCACLS %PATH%\*.EXE /G Everyone:RXE /T /E /C /Y
    > Test that a bit. It does a lot more than the GUI Security Editor. Read the
    > and pay special attention to Directory Inherritance.
    > Now, audit for Failed: {Write, Delete, Change} events and you should be
    good to
    > go.
    > HTH,
    > - AJS

    This will not work in my situation. There are often times when the users
    will need to modify the data files that control how this software
    application runs (it's a DOS app and we're the vendor). I'm trying to
    produce a list of files every day that were intentionally modified, get that
    list in a database and eventually provide a report... As I said, there are
    potentially thousands of files changing every month, so finding a technical
    way to produce a report would be extremely beneficial for my users.

    The problem is, the audit log is reporting files are being modified when
    they clearly are not - people are simply running the application and event
    560s are being logged. My point about the EXE is that it is clear they are
    only running the application (they're not programmers, they cannot modify an
    EXE, but they could delete it. At first I thought the EXE was deleted, but
    I checked the directory and it was still there).

    MS told me (cross-posted it to another group): "You're really close. Event
    560 is generated when a handle to an object is granted with the audited
    access (not when the access is performed)." They said that this was changed
    in Win 2003 so that "real" modifies/deletes are recorded with an even 567,
    but this will not be backported to Win 2000.

    Any other ideas would be welcome, I didn't plan on upgrading that server for
    several months.


  • Next message: God Bless Texas: "Re: Islam hacks Vatican? Let's Not Be Sentimental!"

    Relevant Pages

    • Re: audit user activity
      ... have seen the Object Access event on Security event log? ... Audit group ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    • Re: Wireless Audit Reports
      ... Subject: Wireless Audit Reports ... that there are no rogue access points or peer networks hidden in our ... That would be an easy report to create after data ...
    • Re: auditing
      ... I need to audit the license usage of specific office components on our ... tool has many reports to pick from and many report output formats to ... Create a Batch or VBScript to run this command below on Logon. ...
    • Re: WebServices Testing
      ... I'm sure his client wants a report that says that their ... and often make it not appear in their final version of the report. ... If they don't the audit may go off without ... Cenzic Hailstorm finds vulnerabilities fast. ...
    • Re: % of Items Completed
      ... > Audit Name describes the document. ... > The second line is an audit of a second Blue Card that Kathy filled out on ... > The forth line is the second item on the second Blue Card audit. ... > I need to report the percentage of time that Kathy filled out the room ...