Skip to content

Commit

Permalink
Updated Windows Sysmon Events
Browse files Browse the repository at this point in the history
- Updated log_source to Microsoft-Windows-Sysmon. Aligned with OSSEM-DM
- Added User (UserName) if required.
- Added sample events (friendly view and xml). Sample events contain user data field.
  • Loading branch information
Cyb3rPandaH committed Sep 23, 2022
1 parent 2051434 commit 8fd44a4
Show file tree
Hide file tree
Showing 25 changed files with 1,261 additions and 279 deletions.
114 changes: 86 additions & 28 deletions windows/sysmon/events/event-1.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
name: 'Event ID 1: Process creation'
description: The **process creation** event provides extended information about a newly created process. The full command line provides context on the process execution. The ProcessGUID field is a unique value for this process across a domain to make event correlation easier. The hash is a full hash of the file with the algorithms in the HashType field.
platform: windows
log_source: sysmon
log_source: Microsoft-Windows-Sysmon
event_id: '1'
event_version: '4.32'
event_version: '5'
event_fields:
- standard_name: Tag
standard_type: TBD
Expand Down Expand Up @@ -52,7 +52,7 @@ event_fields:
name: Product
type: string
description: Product name the image associated with the main process (child) belongs to
sample_value: "Microsoft® Windows® Operating System"
sample_value: Microsoft® Windows® Operating System
- standard_name: FileCompany
standard_type: TBD
name: Company
Expand Down Expand Up @@ -150,30 +150,88 @@ references:
link: https://github.com/trustedsec/SysmonCommunityGuide/blob/master/process-creation.md
tags: []
event_sample:
- format: friendly view
sample: |-
Log Name: Microsoft-Windows-Sysmon/Operational
Source: Microsoft-Windows-Sysmon
Date: 9/22/2022 5:00:46 PM
Event ID: 1
Task Category: Process Create (rule: ProcessCreate)
Level: Information
Keywords:
User: SYSTEM
Computer: pedro-computer
Description:
The description for Event ID 1 from source Microsoft-Windows-Sysmon cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
-
2022-09-23 00:00:46.275
EV_RenderedValue_2.00
7860
C:\Windows\System32\svchost.exe
10.0.18362.1 (WinBuild.160101.0800)
Host Process for Windows Services
Microsoft® Windows® Operating System
Microsoft Corporation
svchost.exe
C:\Windows\system32\svchost.exe -k netsvcs -p -s wlidsvc
C:\Windows\system32\
NT AUTHORITY\SYSTEM
EV_RenderedValue_13.00
999
0
System
SHA1=75C5A97F521F760E32A4A9639A653EED862E9C61,MD5=9520A99E77D6196D0D09833146424113,SHA256=DD191A5B23DF92E12A8852291F9FB5ED594B76A28A5A464418442584AFD1E048,IMPHASH=247B9220E5D9B720A82B2C8B5069AD69
EV_RenderedValue_18.00
584
C:\Windows\System32\services.exe
C:\Windows\system32\services.exe
NT AUTHORITY\SYSTEM
The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded
- format: xml
sample: |-
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2021-11-03 04:38:27.500</Data>
<Data Name="ProcessGuid">{3710b5c6-1243-6182-8303-000000000a00}</Data>
<Data Name="ProcessId">4044</Data>
<Data Name="Image">C:\Windows\System32\notepad.exe</Data>
<Data Name="FileVersion">10.0.19041.1081 (WinBuild.160101.0800)</Data>
<Data Name="Description">Notepad</Data>
<Data Name="Product">Microsoft® Windows® Operating System</Data>
<Data Name="Company">Microsoft Corporation</Data>
<Data Name="OriginalFileName">NOTEPAD.EXE</Data>
<Data Name="CommandLine">"C:\Windows\system32\notepad.exe"</Data>
<Data Name="CurrentDirectory">C:\Users\pedro\</Data>
<Data Name="User">DESKTOP-4FPBTEN\pedro</Data>
<Data Name="LogonGuid">{3710b5c6-f53c-6181-cabe-120000000000}</Data>
<Data Name="LogonId">0x12beca</Data>
<Data Name="TerminalSessionId">1</Data>
<Data Name="IntegrityLevel">Medium</Data>
<Data Name="Hashes">SHA1=66B6158B28CC2B970E454B6A8CF1824DD99E4029,MD5=1C1760ED4D19CDBECB2398216922628B,SHA256=D66458A3EB1B68715B552B3AF32A9D2E889BBF8AC0C23C1AFA8D0982023D1CE2,IMPHASH=670212BD5FAE78855C331EDDEFFDD4EB</Data>
<Data Name="ParentProcessGuid">{3710b5c6-f548-6181-8c01-000000000a00}</Data>
<Data Name="ParentProcessId">4292</Data>
<Data Name="ParentImage">C:\Windows\explorer.exe</Data>
<Data Name="ParentCommandLine">C:\Windows\Explorer.EXE</Data>
<Data Name="ParentUser">DESKTOP-4FPBTEN\pedro</Data>
</EventData>
<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="2022-09-23T00:00:46.279844400Z" />
<EventRecordID>2472309</EventRecordID>
<Correlation />
<Execution ProcessID="6152" ThreadID="7900" />
<Channel>Microsoft-Windows-Sysmon/Operational</Channel>
<Computer>pedro-computer</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2022-09-23 00:00:46.275</Data>
<Data Name="ProcessGuid">{564ff025-f72e-632c-c407-000000000500}</Data>
<Data Name="ProcessId">7860</Data>
<Data Name="Image">C:\Windows\System32\svchost.exe</Data>
<Data Name="FileVersion">10.0.18362.1 (WinBuild.160101.0800)</Data>
<Data Name="Description">Host Process for Windows Services</Data>
<Data Name="Product">Microsoft® Windows® Operating System</Data>
<Data Name="Company">Microsoft Corporation</Data>
<Data Name="OriginalFileName">svchost.exe</Data>
<Data Name="CommandLine">C:\Windows\system32\svchost.exe -k netsvcs -p -s wlidsvc</Data>
<Data Name="CurrentDirectory">C:\Windows\system32\</Data>
<Data Name="User">NT AUTHORITY\SYSTEM</Data>
<Data Name="LogonGuid">{564ff025-d424-62f6-e703-000000000000}</Data>
<Data Name="LogonId">0x3e7</Data>
<Data Name="TerminalSessionId">0</Data>
<Data Name="IntegrityLevel">System</Data>
<Data Name="Hashes">SHA1=75C5A97F521F760E32A4A9639A653EED862E9C61,MD5=9520A99E77D6196D0D09833146424113,SHA256=DD191A5B23DF92E12A8852291F9FB5ED594B76A28A5A464418442584AFD1E048,IMPHASH=247B9220E5D9B720A82B2C8B5069AD69</Data>
<Data Name="ParentProcessGuid">{564ff025-d424-62f6-0b00-000000000500}</Data>
<Data Name="ParentProcessId">584</Data>
<Data Name="ParentImage">C:\Windows\System32\services.exe</Data>
<Data Name="ParentCommandLine">C:\Windows\system32\services.exe</Data>
<Data Name="ParentUser">NT AUTHORITY\SYSTEM</Data>
</EventData>
</Event>
83 changes: 66 additions & 17 deletions windows/sysmon/events/event-10.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
name: 'Event ID 10: ProcessAccess'
description: The **process accessed** event reports when a process opens another process, an operation that's often followed by information queries or reading and writing the address space of the target process. This enables detection of hacking tools that read the memory contents of processes like Local Security Authority (Lsass.exe) in order to steal credentials for use in Pass-the-Hash attacks. Enabling it can generate significant amounts of logging if there are diagnostic utilities active that repeatedly open processes to query their state, so it generally should only be done so with filters that remove expected accesses.
platform: windows
log_source: sysmon
log_source: Microsoft-Windows-Sysmon
event_id: '10'
event_version: '4.32'
event_version: '3'
event_fields:
- standard_name: Tag
standard_type: TBD
Expand Down Expand Up @@ -90,20 +90,69 @@ references:
link: https://github.com/trustedsec/SysmonCommunityGuide/blob/master/process-access.md
tags: []
event_sample:
- format: friendly view
sample: |-
Log Name: Microsoft-Windows-Sysmon/Operational
Source: Microsoft-Windows-Sysmon
Date: 9/22/2022 5:28:45 PM
Event ID: 10
Task Category: Process accessed (rule: ProcessAccess)
Level: Information
Keywords:
User: SYSTEM
Computer: pedro-computer
Description:
The description for Event ID 10 from source Microsoft-Windows-Sysmon cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
-
2022-09-23 00:28:45.094
EV_RenderedValue_2.00
884
1132
C:\Windows\system32\svchost.exe
EV_RenderedValue_6.00
1680
C:\Windows\System32\VBoxService.exe
4096
C:\Windows\SYSTEM32\ntdll.dll+9c524|C:\Windows\System32\KERNELBASE.dll+6a685|c:\windows\system32\lsm.dll+ef13|C:\Windows\System32\RPCRT4.dll+76963|C:\Windows\System32\RPCRT4.dll+da036|C:\Windows\System32\RPCRT4.dll+37a5c|C:\Windows\System32\RPCRT4.dll+548d8|C:\Windows\System32\RPCRT4.dll+2c931|C:\Windows\System32\RPCRT4.dll+2c1eb|C:\Windows\System32\RPCRT4.dll+1a86f|C:\Windows\System32\RPCRT4.dll+19d1a|C:\Windows\System32\RPCRT4.dll+19301|C:\Windows\System32\RPCRT4.dll+18d6e|C:\Windows\System32\RPCRT4.dll+169a5|C:\Windows\SYSTEM32\ntdll.dll+333fd|C:\Windows\SYSTEM32\ntdll.dll+34152|C:\Windows\System32\KERNEL32.DLL+17944|C:\Windows\SYSTEM32\ntdll.dll+6ce71
NT AUTHORITY\SYSTEM
NT AUTHORITY\SYSTEM
The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded
- format: xml
sample: |-
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2021-11-04 23:31:51.894</Data>
<Data Name="SourceProcessGUID">{3710b5c6-95f1-6184-1c00-000000000d00}</Data>
<Data Name="SourceProcessId">1136</Data>
<Data Name="SourceThreadId">1160</Data>
<Data Name="SourceImage">C:\Windows\System32\VBoxService.exe</Data>
<Data Name="TargetProcessGUID">{3710b5c6-6c6b-6184-9500-000000000d00}</Data>
<Data Name="TargetProcessId">1880</Data>
<Data Name="TargetImage">C:\Windows\System32\smartscreen.exe</Data>
<Data Name="GrantedAccess">0x1400</Data>
<Data Name="CallTrace">C:\Windows\SYSTEM32\ntdll.dll+9d234|C:\Windows\System32\KERNELBASE.dll+2c0fe|C:\Windows\System32\VBoxService.exe+13357|C:\Windows\System32\VBoxService.exe+145d4|C:\Windows\System32\VBoxService.exe+1487e|C:\Windows\System32\VBoxService.exe+102bb|C:\Windows\System32\VBoxService.exe+10dc0|C:\Windows\System32\VBoxService.exe+17ee|C:\Windows\System32\VBoxService.exe+3248f|C:\Windows\System32\VBoxService.exe+3604c|C:\Windows\System32\VBoxService.exe+103653|C:\Windows\System32\VBoxService.exe+1036e7|C:\Windows\System32\KERNEL32.DLL+17034|C:\Windows\SYSTEM32\ntdll.dll+52651</Data>
<Data Name="SourceUser">NT AUTHORITY\SYSTEM</Data>
<Data Name="TargetUser">DESKTOP-4FPBTEN\pedro</Data>
</EventData>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Sysmon" Guid="{5770385f-c22a-43e0-bf4c-06f5698ffbd9}" />
<EventID>10</EventID>
<Version>3</Version>
<Level>4</Level>
<Task>10</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2022-09-23T00:28:45.111072500Z" />
<EventRecordID>2511752</EventRecordID>
<Correlation />
<Execution ProcessID="6152" ThreadID="7900" />
<Channel>Microsoft-Windows-Sysmon/Operational</Channel>
<Computer>pedro-computer</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2022-09-23 00:28:45.094</Data>
<Data Name="SourceProcessGUID">{564ff025-d426-62f6-1200-000000000500}</Data>
<Data Name="SourceProcessId">884</Data>
<Data Name="SourceThreadId">1132</Data>
<Data Name="SourceImage">C:\Windows\system32\svchost.exe</Data>
<Data Name="TargetProcessGUID">{564ff025-d42c-62f6-2a00-000000000500}</Data>
<Data Name="TargetProcessId">1680</Data>
<Data Name="TargetImage">C:\Windows\System32\VBoxService.exe</Data>
<Data Name="GrantedAccess">0x1000</Data>
<Data Name="CallTrace">C:\Windows\SYSTEM32\ntdll.dll+9c524|C:\Windows\System32\KERNELBASE.dll+6a685|c:\windows\system32\lsm.dll+ef13|C:\Windows\System32\RPCRT4.dll+76963|C:\Windows\System32\RPCRT4.dll+da036|C:\Windows\System32\RPCRT4.dll+37a5c|C:\Windows\System32\RPCRT4.dll+548d8|C:\Windows\System32\RPCRT4.dll+2c931|C:\Windows\System32\RPCRT4.dll+2c1eb|C:\Windows\System32\RPCRT4.dll+1a86f|C:\Windows\System32\RPCRT4.dll+19d1a|C:\Windows\System32\RPCRT4.dll+19301|C:\Windows\System32\RPCRT4.dll+18d6e|C:\Windows\System32\RPCRT4.dll+169a5|C:\Windows\SYSTEM32\ntdll.dll+333fd|C:\Windows\SYSTEM32\ntdll.dll+34152|C:\Windows\System32\KERNEL32.DLL+17944|C:\Windows\SYSTEM32\ntdll.dll+6ce71</Data>
<Data Name="SourceUser">NT AUTHORITY\SYSTEM</Data>
<Data Name="TargetUser">NT AUTHORITY\SYSTEM</Data>
</EventData>
</Event>
67 changes: 55 additions & 12 deletions windows/sysmon/events/event-11.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
name: 'Event ID 11: FileCreate'
description: '**File create** operations are logged when a file is created or overwritten. This event is useful for monitoring autostart locations, like the Startup folder, as well as temporary and download directories, which are common places malware drops during initial infection.'
platform: windows
log_source: sysmon
log_source: Microsoft-Windows-Sysmon
event_id: '11'
event_version: '4.32'
event_version: '2'
event_fields:
- standard_name: Tag
standard_type: TBD
Expand Down Expand Up @@ -60,15 +60,58 @@ references:
link: https://github.com/trustedsec/SysmonCommunityGuide/blob/master/file-create.md
tags: []
event_sample:
- format: friendly view
sample: |-
Log Name: Microsoft-Windows-Sysmon/Operational
Source: Microsoft-Windows-Sysmon
Date: 9/22/2022 4:50:47 PM
Event ID: 11
Task Category: File created (rule: FileCreate)
Level: Information
Keywords:
User: SYSTEM
Computer: pedro-computer
Description:
The description for Event ID 11 from source Microsoft-Windows-Sysmon cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
-
2022-09-22 23:50:47.181
EV_RenderedValue_2.00
3976
C:\Windows\system32\mmc.exe
C:\Users\pedro-admin\AppData\Local\Temp\tmpE7EC.xml
2022-09-22 23:50:47.181
PEDRO-COMPUTER\pedro-admin
The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded
- format: xml
sample: |-
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2021-11-04 23:40:40.783</Data>
<Data Name="ProcessGuid">{3710b5c6-6c2f-6184-7f00-000000000d00}</Data>
<Data Name="ProcessId">4236</Data>
<Data Name="Image">C:\Windows\Explorer.EXE</Data>
<Data Name="TargetFilename">C:\Users\pedro\Desktop\New Text Document.txt</Data>
<Data Name="CreationUtcTime">2021-11-04 23:40:40.783</Data>
<Data Name="User">DESKTOP-4FPBTEN\pedro</Data>
</EventData>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Sysmon" Guid="{5770385f-c22a-43e0-bf4c-06f5698ffbd9}" />
<EventID>11</EventID>
<Version>2</Version>
<Level>4</Level>
<Task>11</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2022-09-22T23:50:47.184554800Z" />
<EventRecordID>2424474</EventRecordID>
<Correlation />
<Execution ProcessID="6152" ThreadID="7900" />
<Channel>Microsoft-Windows-Sysmon/Operational</Channel>
<Computer>pedro-computer</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="RuleName">-</Data>
<Data Name="UtcTime">2022-09-22 23:50:47.181</Data>
<Data Name="ProcessGuid">{564ff025-ee7b-632c-4507-000000000500}</Data>
<Data Name="ProcessId">3976</Data>
<Data Name="Image">C:\Windows\system32\mmc.exe</Data>
<Data Name="TargetFilename">C:\Users\pedro-admin\AppData\Local\Temp\tmpE7EC.xml</Data>
<Data Name="CreationUtcTime">2022-09-22 23:50:47.181</Data>
<Data Name="User">PEDRO-COMPUTER\pedro-admin</Data>
</EventData>
</Event>
Loading

0 comments on commit 8fd44a4

Please sign in to comment.