Sysmon 1 — Process creation

Source and collection

Microsoft-Windows-Sysmon/Operational; native XML export, not an EVTX binary file.

Install Sysmon and review the installed schema and filtering configuration. Use sysmon64 -s to inspect supported fields; preserve the deployed configuration version.

Native example and provenance

upstream test fixture. Published example; no independent capture provenance claimed.

Original publisher / pinned upstream fixture — events[51].event.original

Decoded event.original string; retained the complete Event XML element, excluding any appended rendered message; native XML values unchanged.

Pinned source commit: 9ae756f00f82786ac3496ce99c2dd288c5a5c031

Download the exact sample · Offline research kit

SHA-256: bffbcecc27871ee51eb79ecff5ad9eb7f263d5e104986e48ad456e85838ed585

<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Microsoft-Windows-Sysmon' Guid='{5770385f-c22a-43e0-bf4c-06f5698ffbd9}'/><EventID>1</EventID><Version>5</Version><Level>4</Level><Task>1</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime='2019-03-18T16:57:38.011477000Z'/><EventRecordID>3</EventRecordID><Correlation/><Execution ProcessID='4860' ThreadID='4516'/><Channel>Microsoft-Windows-Sysmon/Operational</Channel><Computer>vagrant-2012-r2</Computer><Security UserID='S-1-5-18'/></System><EventData><Data Name='RuleName'></Data><Data Name='UtcTime'>2019-03-18 16:57:37.949</Data><Data Name='ProcessGuid'>{42f11c3b-ce01-5c8f-0000-0010c73e2a00}</Data><Data Name='ProcessId'>4860</Data><Data Name='Image'>C:\Windows\Sysmon.exe</Data><Data Name='FileVersion'>9.01</Data><Data Name='Description'>System activity monitor</Data><Data Name='Product'>Sysinternals Sysmon</Data><Data Name='Company'>Sysinternals - www.sysinternals.com</Data><Data Name='CommandLine'>C:\Windows\Sysmon.exe</Data><Data Name='CurrentDirectory'>C:\Windows\system32\</Data><Data Name='User'>NT AUTHORITY\SYSTEM</Data><Data Name='LogonGuid'>{42f11c3b-6e1a-5c8c-0000-0020e7030000}</Data><Data Name='LogonId'>0x3e7</Data><Data Name='TerminalSessionId'>0</Data><Data Name='IntegrityLevel'>System</Data><Data Name='Hashes'>SHA1=AC93C3B38E57A2715572933DBCB2A1C2892DBC5E</Data><Data Name='ParentProcessGuid'>{42f11c3b-6e1a-5c8c-0000-0010f14d0000}</Data><Data Name='ParentProcessId'>488</Data><Data Name='ParentImage'>C:\Windows\System32\services.exe</Data><Data Name='ParentCommandLine'>C:\Windows\system32\services.exe</Data></EventData></Event>

Structure and field interpretation

EventID

1 in Microsoft-Windows-Sysmon.

UtcTime

Producer-supplied event time.

ProcessGuid

Process correlation identifier where present; case-sensitive field names vary by event.

Relevant fields

ProcessGuid, Image, CommandLine, ParentProcessGuid

Investigation uses

• Reconstruct process ancestry and suspicious command-line context.
• Correlate ProcessGuid across Sysmon events; keep the host identity and time interval with every join.

Validation boundaries

A process start does not prove successful payload behavior.

This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.

For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.

Related sources

• Windows Security 4688 — Process creation
• Sysmon 3 — Network connection
• Sysmon 7 — Image loaded
• Sysmon 8 — CreateRemoteThread
• Sysmon 13 — Registry value set
• Sysmon 22 — DNS query

Ecosystem connections

• Telemetry Library — ATT&CK data components
• Detection Rules — candidate detection content
• Threat hunting — from intelligence to validated defense
• Practical security learning paths
• AdversaryGraph — evidence-led investigation

• DC0032 — conceptual telemetry association, not coverage proof

References

• Sysmon - Sysinternals | Microsoft Learn
• Sysmon events | Microsoft Learn

Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.