Skip to content
SysmonfileRequires audit policy

Sysmon Event ID 11: FileCreate

Sysmon event 11 logs a file being created or overwritten and the process that wrote it. Key for dropped payloads, persistence folders and dump files.

Overview

Event ID
11
Log / channel
Microsoft-Windows-Sysmon/Operational
Provider
Microsoft-Windows-Sysmon
Category
file
Enabled by default
No
How to enable
Sysmon installed; filter with <FileCreate> rules in the configuration (include folders and extensions of interest).

What event 11 logs

Sysmon event 11 records file creation or overwrite, naming the file (TargetFilename) and the process that wrote it. It is the Sysmon answer to "where did this file come from?".

Useful targets are autostart locations (Startup folders, System32\Tasks), download and temp folders, script and executable extensions, and dump files such as lsass.dmp. CreationUtcTime is the file's creation timestamp; for an overwritten file it can be older than the event time.

File activity is heavy on any system, so configurations include specific folders and extensions rather than logging everything.

Fields

Every field recorded in event 11, with the values that matter for investigation.

ProcessGuid

Process that wrote the file; pivot to its event 1.

Image

Executable that wrote the file.

TargetFilename

Full path of the created file.

CreationUtcTime

Creation time of the file (can predate UtcTime when an existing file is overwritten).

User

Account of the process (newer Sysmon versions).

How to enable this event

Sysmon installed; filter with <FileCreate> rules in the configuration (include folders and extensions of interest).

Detection and investigation

Typically benign

  • Browsers writing downloads, installers writing to Program Files, updaters replacing binaries.
  • Office and Windows writing temp and cache files.

Worth investigating

  • Payloads dropped in %TEMP%, %APPDATA%, ProgramData or C:\Users\Public.
  • Persistence files in ...\Start Menu\Programs\Startup or new task XML in C:\Windows\System32\Tasks.
  • Memory dumps such as lsass.dmp written by ProcDump, Task Manager or rundll32.exe.
  • Tools copied to C:\Windows via admin shares by System during PsExec-style lateral movement.

Investigation notes

  • Pivot on ProcessGuid to event 1 to see which process and parent wrote the file.
  • Look for a later event 1 whose Image equals TargetFilename — the dropped file was executed.
  • Check event 15 for the Zone.Identifier stream on downloaded files to get the source URL.

MITRE ATT&CK techniques

Related event IDs

References