CyberKit

Event IDs

Security event 5140

A network share object was accessed

Channel: Security. Category: Audit File Share.

What it records

Generated once per session, on the first access attempt, whenever a network share object is accessed. Records the requesting account, source IP address/port, the share name and its local (NTFS) path, and a coarse access mask (always 'ReadData (or ListDirectory)' for this event).

Why it matters

This is the baseline artifact for auditing SMB share access: it shows who connected to which share and from where, which is central to scoping lateral movement, insider data-staging, or unauthorized access to sensitive shares (e.g., admin shares like C$ on a domain controller) during an investigation.

What triggers it

Legitimately: any normal file-share access (mapped drives, `\\server\share` browsing, backup jobs, application file access). Maliciously: an attacker enumerating or connecting to administrative shares (C$, ADMIN$) or sensitive data shares as part of lateral movement or reconnaissance.

Fields that carry the answer

Key fields
FieldWhat it tells you
Subject > Account NameThe account that connected to the share: the identity to pivot on for lateral-movement or data-staging investigation.
Network Information > Source AddressThe IP the connection originated from. Pivot point for scoping which hosts touched a sensitive share.
Share Information > Share NameThe share that was accessed. Flag connections to administrative shares (C$, ADMIN$) on servers or domain controllers.
Share Information > Share PathThe underlying local NTFS path the share maps to, which ties the network-visible share name to the actual filesystem location for follow-up file-level review.

In practice

A 5140 might show Subject Account Name CORP\jsmith, Source Address 203.0.113.10, Share Name \\*\C$, and Share Path \??\C:\: a connection to the administrative C$ share from a workstation address with no legitimate reason to touch a server's admin share is a common SMB-based lateral-movement indicator (e.g. PsExec, Impacket), worth correlating with the matching 4624 Type 3 logon and any follow-on 5145 events for the same Logon ID.

Sample record

A network share object was accessed.

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:		\\*\C$
	Share Path:		\??\C:\

Access Request Information:
	Access Mask:		0x1
	Accesses:		ReadData (or ListDirectory)

ATT&CK techniques

Sources

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