mirror of
https://github.com/trustedsec/SysmonCommunityGuide/
synced 2026-06-06 19:46:57 +00:00
de88fe585a
Added a paragraph about the ProcessGUID describing how it is created and accessed.
48 lines
1.7 KiB
Markdown
48 lines
1.7 KiB
Markdown
|
|
Process Events
|
|
==============
|
|
|
|
Sysmon can log process creation, process termination and process access
|
|
events. The prorocess actions are captured via ObjRegisterCallbacks at
|
|
the kernel level using its driver. These events are important since the
|
|
**ProcessGuid** field of these events are used by other so as to provide
|
|
more context on the process that relates to the actions and the
|
|
ProcessGuid maps to the **LogonGuid** that it is then used to track all
|
|
actions of a given logon session. The main reason for using this GUIDs
|
|
is that Process ID and Logon ID on a system get re-used as time passes.
|
|
In the case of processes ID it can happen multiple times in a days.
|
|
|
|

|
|
|
|
When a user logs onto on a modern version of Windows (Windows 2016/10)
|
|
they will have 2 Logon IDs assigned if:
|
|
|
|
* User is a member of local Administrator Group.
|
|
|
|
* UAC (User Access Control) is enabled.
|
|
|
|
These sessions will be linked by a Linked Login ID in Successful Logon
|
|
Event ID 4624, making the login of this event important.
|
|
|
|
The ProcessGUID depending on the event and where in the process tree it
|
|
is, it will also be known by other names by its relation to the action
|
|
monitored.
|
|
|
|
ProcessGUID is generated by Sysmon when Sysmon logs the event. ProcessGUID
|
|
specifically is not an attribute of the internal Windows process data structs
|
|
(EPROCESS). Sysmon keeps track of the GUID until the process exits.
|
|
|
|

|
|
|
|
The only Event Types that will not reference a ProcessGuid or one of its
|
|
derived names are
|
|
|
|
* WMI events
|
|
|
|
* Kernel Driver Load
|
|
|
|
The image of the process is also related in other processes and can be
|
|
used to track all actions related to a specific one.
|
|
|
|

|