QuestionQ51

VerifiedWindows Automation, Auditing, and Forensics

You have reason to believe that someone using a domain user account has been accessing and modifying sensitive spreadsheets on one of your application servers.

You decide to enable file auditing to determine who is accessing and changing them. You enable the Audit Object Access policy for the files through Group Policy.

Two weeks later, you check the audit logs and find them empty. What is the most likely reason for this?

Explanation

Windows object-access auditing requires both an enabled audit policy and a matching system access control list (SACL) on the file system object. The policy alone does not configure which files or operations are audited, so no events are generated until auditing is set on the files or their containing folder.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!