CyberKit

Event IDs

Security event 5145

A network share object was checked to see whether client can be granted desired access

Channel: Security. Category: Audit Detailed File Share.

What it records

Generated on every access to a file or folder within a network share, recording the specific relative target file/folder name, the detailed access rights requested (e.g., ReadData, WriteData, Delete, ReadAttributes), and the access-check result showing which ACE granted or denied each right. Per Microsoft's documentation, failure events are generated only when access is denied at the share level, not the NTFS level.

Why it matters

Where 5140 shows a share was touched, 5145 shows exactly which file inside it was requested and whether access was allowed or denied and by which permission entry: the level of detail needed to reconstruct what an intruder actually read, wrote, or was blocked from touching on a share during lateral movement or data-staging.

What triggers it

Legitimately: normal per-file access within a share, generated at high volume (this subcategory is verbose and typically enabled selectively on high-value shares only). Maliciously: an attacker traversing a share to locate and pull specific files (e.g., sensitive documents, credential stores) or attempting access to files they lack permission for.

Fields that carry the answer

Key fields
FieldWhat it tells you
Share Information > Relative Target NameThe specific file or folder requested within the share. This is the level of detail that shows exactly what an intruder tried to read or write, which 5140 alone doesn't capture.
Access Request Information > AccessesThe specific rights requested (e.g. WriteData, Delete, ReadAttributes). Prioritize failures on write/delete rights as the strongest signal of attempted tampering or exfiltration staging.
Network Information > Source AddressThe IP the access request originated from. Pivot point for tracing which host was traversing the share.
Share Information > Share NameThe share being accessed. Correlate with the parent 5140 event for the same session.

In practice

A 5145 for that same session might show Source Address 203.0.113.10, Share Name \\*\Documents, Relative Target Name payroll.xlsx, and Accesses ReadData, ReadAttributes: an Access Check Result of "Denied by" against WriteData, AppendData, or Delete on a sensitive filename is a stronger signal than a plain successful read, since Microsoft's own guidance singles out failed write/delete attempts as the access rights worth prioritizing over reads.

Sample record

A network share object was checked to see whether client can be granted desired access.

Subject:
	Security ID:		S-1-5-21-3457937927-2839227994-823803824-1104
	Account Name:		jsmith
	Account Domain:		CORP
	Logon ID:		0x3A2F1B7

Network Information:
	Object Type:		File
	Source Address:		203.0.113.10
	Source Port:		49212

Share Information:
	Share Name:		\\*\Documents
	Share Path:		\??\C:\Documents
	Relative Target Name:	payroll.xlsx

Access Request Information:
	Access Mask:		0x100081
	Accesses:		ReadData (or ListDirectory)
				ReadAttributes
				SYNCHRONIZE

Access Check Result:
	ReadData (or ListDirectory): Granted by D:(A;;FA;;;WD)
	ReadAttributes: Granted by D:(A;;FA;;;WD)
	SYNCHRONIZE: Granted by D:(A;;FA;;;WD)

ATT&CK techniques

Sources

Paste a record into Event XML or open a log in EVTX Reader.