/

How to Audit File Access on Shared Drives Without Expensive EDR Tools

by Grant Funtila, Technical Writer
How to Audit File Access on Shared Drives Without Expensive EDR Tools blog banner image
How to Audit File Access on Shared Drives Without Expensive EDR Tools blog banner image

Try our #1 rated endpoint management platform on G2

NinjaOne dashboard screenshot

Automate the Hardest Parts of IT

Key Points

  • Enable the Audit File System policy under Advanced Audit Policy Configuration to record file access on Windows file shares in the Security log without an EDR or XDR platform.
  • Add auditing entries (SACLs) to sensitive folders such as finance and HR data so Windows logs only the file access that matters.
  • Review Security log event IDs 4663, 4660, 4670, and 5145 to see who accessed, deleted, or changed permissions on files.
  • Forward Security log events to a central collector with Windows Event Forwarding or a SIEM so audit evidence survives log rollover and supports alerts.
  • Standardize audit settings across clients with Group Policy or a PowerShell script, then report findings in plain language.

To audit file access on a Windows file share without EDR, enable the Audit File System policy, add auditing entries to sensitive folders, and review the resulting events in the Security log. Forward those events to a central collector, then summarize them for clients in plain language.

This guide covers Windows file shares served over the Server Message Block (SMB) protocol. It does not cover Google Workspace shared drives or Microsoft 365 libraries, which use separate audit logs. Without auditing, MSPs and IT teams cannot see who opened, changed, or deleted files, which leaves unauthorized access and data loss undetected.

Endpoint Detection and Response (EDR) and Extended Detection and Response (XDR) can address these issues, but can be expensive for clients. Managed Service Providers (MSPs) can still deliver strong security value by using native auditing tools to track file access in shared drives and implementing structured processes for reviewing and responding to access activity.

Auditing file access on shared drives without EDR tools

To audit file access on shared drives without EDR tools, you must enable native file system auditing, review event logs, standardize auditing policies, and communicate findings to clients.

Prerequisites:

  • Administrative access to Windows Server or file shares.
  • Knowledge of file/folder permissions.
  • Access to client compliance requirements.
  • Optional: RMM or monitoring tool to centralize alerts.

Method 1: Enable Audit File System with Advanced Audit Policy

This step tells Windows to record file and folder access in the Security log, so you can see who opens, changes, or deletes data.

Use Case: A company handling confidential financial or HR records wants to monitor access to specific folders to ensure only authorized personnel interact with those files.

Audit File System creates events only for folders that also have an auditing entry, also called a system access control list (SACL). You turn on the policy here and add the entries in Method 3.

To enable the policy with Group Policy:

  1. Press Win + R, type gpmc.msc, and press Enter. Create or edit a GPO linked to your file servers. On a standalone server, open secpol.msc instead.
  2. Go to Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies > Object Access.
  3. Open Audit File System, select Configure the following audit events, and set it to Success and Failure.
  4. Go to Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options. Enable Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings. This stops legacy category settings from conflicting with the advanced policy.
  5. Run gpupdate /force on the file server.
  6. Open an elevated Command Prompt and verify the setting:

auditpol /get /subcategory:”File System”

Scripted equivalent for a single server:

auditpol /set /subcategory:”File System” /success:enable /failure:enable

auditpol /get /subcategory:”File System”

Note: Do not enable the legacy Audit Object Access category alongside the advanced policy. Microsoft advises against mixing basic and advanced audit settings because it can cause unexpected audit results.

Method 2: Review event logs for access activity

This step lets you monitor logs to provide insight into how sensitive data is used to ensure timely detection.

Use Case: A security administrator wants to detect when users attempt to mass-delete client files or modify confidential HR data. By collecting and analyzing Windows Security Event Logs, the organization can identify these incidents early and respond before significant data loss or compliance breaches occur.

Collect Windows security event logs

  1. Access event logs by pressing Win, typing Event Viewer, and then pressing Enter.
  2. Navigate to:
    • Event Viewer → Windows Logs → Security
  3. Focus on event IDs related to file system access and note down the written info:
    • 4663 – Access attempt on an object (e.g., file/folder read/write/delete).
    • 4660 – Object deleted.
    • 4656 – Handle requested for object access.
    • 4670 – Permissions changed on an object.

Forward logs to a central collection point

Windows Event Forwarding (WEF) sends Security log events from file servers to a Windows Event Collector and is built into Windows Server. If a client already has a SIEM, such as Microsoft Sentinel, forward the same events there for correlation and alerting. Microsoft Sentinel is moving from the Azure portal to the Microsoft Defender portal, and Microsoft has set March 31, 2027 as the end of Azure portal support.

Set up alerts for suspicious activity

Define alert rules within your SIEM or monitoring system to flag:

  • Mass file deletions
  • Unauthorized access attempts
  • Permission escalation

For example, create an alert when one account generates a burst of delete events (4660) or write events (4663) on one share within a short window. Set the threshold from the baseline for that client, because normal activity differs by environment. A burst can point to bulk deletion, ransomware, or insider misuse, so treat it as a trigger for investigation.

Method 3: Standardize auditing policies across clients

This step standardizes auditing policies to ensure organizations can monitor critical data using the same rules.

Use Case: An MSP oversees dozens of client environments, each with varying configurations. To maintain consistent oversight and compliance, the MSP creates a baseline file access auditing policy that is applied across all clients.

Use PowerShell to define a standard audit setting for all client systems. To do so, follow the steps below:

  1. Press Win, type PowerShell, then click Run as administrator.
  2. Copy and paste the following script into the prompt, then press Enter:
# Enable Object Access Auditing

auditpol /set /subcategory:”File System” /success:enable /failure:enable

# Set the Security log to 1 GB (value is in bytes) and overwrite the oldest events when full

wevtutil sl Security /ms:1073741824 /rt:false

# Verify configuration

auditpol /get /category:*

Note: The /ms value is in bytes, and the minimum log size is 1,048,576 bytes. Choose a size based on the expected event volume for each server. Setting /rt:false lets Windows overwrite the oldest events when the log is full, so new events continue to be recorded. Forward events to a central collector for long-term retention. If a Group Policy Event Log setting controls the Security log size, it can override this local value, so check it under Computer Configuration > Policies > Windows Settings > Security Settings > Event Log.

  1. Note the following folders, as they are high-value data types you should constantly monitor:
    • Finance records
    • HR or employee data
    • Legal and compliance documentation
    • Client and project files
  2. Right-click the folder, then click Properties > Security > Advanced > Auditing > Add.
  3. Choose the Users or Groups to audit, then pick Action to Audit:
    • Read
    • Write
    • Delete
    • Change Permissions

Note: For large-scale environments, you can automate the folder definition by using the following PowerShell script:

# Example: Add auditing to a folder

# Run in an elevated PowerShell session on the file server

$folder = “D:\Shares\Finance”

$acl = Get-Acl -Path $folder -Audit

$rights = [System.Security.AccessControl.FileSystemRights]”Delete, DeleteSubdirectoriesAndFiles, ChangePermissions, TakeOwnership, Write”

$inherit = [System.Security.AccessControl.InheritanceFlags]”ContainerInherit, ObjectInherit”

$propagate = [System.Security.AccessControl.PropagationFlags]::None

$flags = [System.Security.AccessControl.AuditFlags]”Success, Failure”

$rule = New-Object System.Security.AccessControl.FileSystemAuditRule(“Everyone”, $rights, $inherit, $propagate, $flags)

rule)

Set-Acl -Path $folder -AclObject $acl

The three-argument constructor in the current script creates an entry for the folder only, so files inside it are not audited. FullControl for Everyone also logs every read and attribute check, which contradicts the post’s own advice to limit noise. The path should point to the folder behind the share.

Method 4: Communicate findings to clients

This step translates technical audit data into client-friendly summaries to help demonstrate the value of monitoring efforts.

Use Case: An MSP delivers monthly compliance reports to clients. Instead of sending dense event logs filled with Event IDs like 4663 and 4660, the MSP summarizes them into plain-language highlights.

  • Translate technical logs into client-friendly summaries.
  • Highlight successful detections and blocked attempts.
  • Demonstrate how auditing reduces compliance and insider risk.

Use FSRM and Access-Based Enumeration to control storage and visibility

This step uses built-in file server tools to limit what gets stored and what users can see. These tools reduce risk, but they do not record who accessed a file. For that record, rely on the Security log events from Methods 1 and 2.

Use case: An IT administrator manages shared folders for several departments on a central Windows file server. To prevent storage misuse and reduce exposure, the administrator sets quotas, blocks unwanted file types, and hides folders from users who do not need them.

Use File Server Resource Manager (FSRM)

File Server Resource Manager (FSRM) is a role service you can install through Server Manager. Use it to:

  • Quotas: limit the data stored in specific folders and send email notifications or run scripts when users approach the limit.
  • File screens: block selected file types in restricted folders.
  • Storage reports: list duplicate files, large files, files by owner, least and most recently accessed files, quota usage, and file screening events.

FSRM does not log who opened, changed, or deleted a file. Its “recently accessed” reports show which files were touched, not by whom.

Hide folders with Access-Based Enumeration

Access-Based Enumeration (ABE) hides files and folders from users who do not have permission to open them. Use ABE together with the Advanced Security Settings on shared folders to confirm that access rights match your organization’s policies and to reduce privilege creep.

ABE and folder permissions limit exposure, but neither one writes an audit event.

Review storage reports regularly

  • Open Storage Reports Management in the FSRM console and schedule reports for duplicate files, quota usage, and file screening events. Review them periodically to spot storage misuse and unusual file types, then check the Security log for the related access activity.

Verification

Once file access auditing is in place, it’s essential to verify that logs are collected, forwarded, and reviewed correctly.

Validate event collection and forwarding

Ensure file access events are recorded in the Windows Security Event Log and periodically test the forwarding configuration by generating sample access events and confirming they appear in the centralized dashboard. This process ensures no data loss between endpoints and the monitoring system.

Ensure audit trails meet compliance and SLA standards

Compare collected log details against client or regulatory requirements. Confirm that logs include:

  • User identity
  • Timestamp
  • Action type
  • Resource details

Regular compliance audits should cross-check this data to ensure records are secured.

Generate regular access reports

Schedule monthly or quarterly reports summarizing legitimate and suspicious activity. Deliver reports with summaries and visuals, while retaining logs for auditors or IT analysts.

Additional considerations

  • Noise management: Too much auditing can overwhelm logs, so it’s best to focus on sensitive data.
  • Storage impact: Log retention may need dedicated storage for compliance.
  • User awareness: Let employees know that activity is monitored to reduce insider risks.

Troubleshooting common file access on shared drives issues

Address common issues to ensure auditing remains accurate, efficient, and compliant.

No access events logged

Check these items in order:

  1. Confirm Audit File System is set to Success and Failure with:

auditpol /get /subcategory:”File System”

  1. Confirm Audit: Force audit policy subcategory settings is enabled, so legacy category settings do not override the advanced policy.
  2. Confirm the folder has an auditing entry. Right-click the folder, then select Properties > Security > Advanced > Auditing.
  3. Check for conflicting GPOs. If two GPOs set Audit File System differently, events can stop or appear intermittently.
  4. Make sure a Group Policy Event Log setting is not capping or overwriting the Security log.

Excessive false positives

Too many irrelevant logs can obscure risks. Refine the auditing configuration by focusing on sensitive folders.

How NinjaOne helps MSPs audit file access

NinjaOne does not replace Windows auditing. It helps you apply the audit process consistently across the Windows servers you manage.

  • Documentation: Store the audit procedure, client folder lists, and review checklists in the NinjaOne Documentation Knowledge Base, which exists at the system and organization level.
  • Automation: Run the audit configuration script from Method 3 on a schedule or on demand with NinjaOne scripting and scheduled tasks.
  • Monitoring: Send alerts by email or SMS when managed endpoints meet conditions you configure.
  • Reporting: Schedule reports for daily, weekly, or monthly delivery, and share them with specific technician roles.

Detect data losses by auditing file access on shared drives

Native Windows auditing gives MSPs and IT teams a record of who accessed, changed, or deleted files on a file share, without adding a new security platform. It does not replace EDR, which detects malicious behavior on endpoints, so treat the two as complementary.

Related topics:

FAQs

Usually not, because Windows records who deleted a file only if Audit File System and a folder auditing entry were already in place. You can still restore the file from a backup or a previous version, then turn on auditing so the next deletion is recorded.

It can, depending on how many events you generate. Scoped auditing entries on a few sensitive folders usually add little overhead, but broad entries or Audit Detailed File Share on a busy server can create very high event volume, so test on one server before a wider rollout.

Not directly, because Windows has no separate copy or download event. A copy appears as read access to the source file when you audit Read data, and the server cannot see what happens to the file after it reaches the user’s device.

Use the Everyone group when you want to capture every account, because an entry for a narrower group records only that group’s members. To control log volume, narrow the access types you audit, such as Delete, Write, and Change permissions, instead of narrowing who is audited.

Windows Security log auditing works only on Windows servers, so a NAS or Linux Samba share needs the audit feature built into that platform. Check the device’s file activity or audit logging settings, and on Samba, use the full_audit module.

Those platforms keep their own audit logs instead of the Windows Security log. In Google Workspace, review Drive log events in the Admin console, and in Microsoft 365, search the audit log in Microsoft Purview.

You might also like

Ready to simplify the hardest parts of IT?