Microsoft-Windows-Sysmon

Event ID 1: Process creation

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (ASD, others)
Task
Process Create (rule: ProcessCreate)
Opcode
Info

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.

Message #

Process Create:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
FileVersion: %6
Description: %7
Product: %8
Company: %9
OriginalFileName: %10
CommandLine: %11
CurrentDirectory: %12
User: %13
LogonGuid: %14
LogonId: %15
TerminalSessionId: %16
IntegrityLevel: %17
Hashes: %18
ParentProcessGuid: %19
ParentProcessId: %20
ParentImage: %21
ParentCommandLine: %22
ParentUser: %23

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that got spawned/created (child)
ProcessId UInt32Process ID used by the OS to identify the created process (child)
Image UnicodeStringFile path of the process being spawned/created. Considered also the child or source process3385 detection rules
FileVersion UnicodeStringVersion of the image associated with the main process (child)13 detection rules
Description UnicodeStringDescription of the image associated with the main process (child)112 detection rules
Product UnicodeStringProduct name the image associated with the main process (child) belongs to87 detection rules
Company UnicodeStringCompany name the image associated with the main process (child) belongs to49 detection rules
OriginalFileName UnicodeStringOriginal file name from the PE header, useful for detecting renamed executables1043 detection rules
CommandLine UnicodeStringArguments which were passed to the executable associated with the main process13182 detection rules
CurrentDirectory UnicodeStringThe path without the name of the image associated with the process27 detection rules
User UnicodeStringName of the account who created the process (child). It usually contains domain name and user name (parsed to show only username without the domain)63 detection rules
LogonGuid GUIDLogon GUID of the user who created the new process. Value that can help you correlate this event with others that contain the same Logon GUID (Sysmon Events)
LogonId HexInt64Logon ID of the user who created the new process. Value that can help you correlate this event with others that contain the same Logon ID4 detection rules
TerminalSessionId UInt32ID of the session the user belongs to
IntegrityLevel UnicodeStringIntegrity label assigned to a process
Known values
Untrusted
SID S-1-16-0; anonymous network logons and similar contexts.
Low
SID S-1-16-4096; AppContainer / Internet Explorer protected-mode and similar low-trust contexts.
Medium
SID S-1-16-8192; default for interactive desktop processes when UAC strips elevation.
Medium Plus
SID S-1-16-8448; elevated standard-user contexts (rare).
High
SID S-1-16-12288; elevated administrator processes.
System
SID S-1-16-16384; LocalSystem and other kernel-mode-equivalent contexts.
Protected Process
SID S-1-16-20480; protected-process-light and protected processes (anti-malware, system criticals; observed in ETW-TI but rarely surfaced via Sysmon).
109 detection rules
Hashes UnicodeStringHashes captured by Sysmon driver506 detection rules
ParentProcessGuid GUIDProcess GUID of the parent process that spawned/created this process
ParentProcessId UInt32Process ID of the process that spawned/created the main process (child)
ParentImage UnicodeStringFile path that spawned/created the main process896 detection rules
ParentCommandLine UnicodeStringArguments which were passed to the executable associated with the parent process316 detection rules
ParentUser UnicodeStringName of the account who created the process that spawned/created the main process (child)17 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 1,
    "version": 5,
    "level": 4,
    "task": 1,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.2562055+00:00",
    "event_record_id": 17612602,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:29.253",
    "ProcessGuid": "{8a99384c-6499-6a2d-a205-000000001000}",
    "ProcessId": "7704",
    "Image": "C:\\ludus\\background\\bginfo.exe",
    "FileVersion": "4.33",
    "Description": "BGInfo - Wallpaper text configurator",
    "Product": "BGInfo",
    "Company": "Sysinternals - www.sysinternals.com",
    "OriginalFileName": "BGInfo.exe",
    "CommandLine": "\"C:\\ludus\\background\\bginfo.exe\" /accepteula C:\\ludus\\background\\red.bgi /silent /timer:0",
    "CurrentDirectory": "C:\\Windows\\system32\\",
    "User": "cell-c\\domainadmin",
    "LogonGuid": "{8a99384c-e96f-6a2c-b6f3-0b0000000000}",
    "LogonId": "0xbf3b6",
    "TerminalSessionId": "1",
    "IntegrityLevel": "High",
    "Hashes": "SHA1=47C5CB3D6E01E139FEA41E94C43C29698FCD912B,MD5=34072C1DD7E0D04760108F565540F745,SHA256=599B391980A5C9CBADD6C70BA3D5A5258DB8B9D87C68B3FE587D9DC84EFFDF63,IMPHASH=B221E55CFCA1A7D0850D1B749ACE2D69",
    "ParentProcessGuid": "{8a99384c-e981-6a2c-c200-000000001000}",
    "ParentProcessId": "7180",
    "ParentImage": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
    "ParentCommandLine": "\"C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\" -ExecutionPolicy Bypass -NonInteractive -File \"C:\\ludus\\background\\set-bg.ps1\"",
    "ParentUser": "cell-c\\domainadmin"
  },
  "message": "Process Create:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:29.253\r\nProcessGuid: {8a99384c-6499-6a2d-a205-000000001000}\r\nProcessId: 7704\r\nImage: C:\\ludus\\background\\bginfo.exe\r\nFileVersion: 4.33\r\nDescription: BGInfo - Wallpaper text configurator\r\nProduct: BGInfo\r\nCompany: Sysinternals - www.sysinternals.com\r\nOriginalFileName: BGInfo.exe\r\nCommandLine: \"C:\\ludus\\background\\bginfo.exe\" /accepteula C:\\ludus\\background\\red.bgi /silent /timer:0\r\nCurrentDirectory: C:\\Windows\\system32\\\r\nUser: cell-c\\domainadmin\r\nLogonGuid: {8a99384c-e96f-6a2c-b6f3-0b0000000000}\r\nLogonId: 0xBF3B6\r\nTerminalSessionId: 1\r\nIntegrityLevel: High\r\nHashes: SHA1=47C5CB3D6E01E139FEA41E94C43C29698FCD912B,MD5=34072C1DD7E0D04760108F565540F745,SHA256=599B391980A5C9CBADD6C70BA3D5A5258DB8B9D87C68B3FE587D9DC84EFFDF63,IMPHASH=B221E55CFCA1A7D0850D1B749ACE2D69\r\nParentProcessGuid: {8a99384c-e981-6a2c-c200-000000001000}\r\nParentProcessId: 7180\r\nParentImage: C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\r\nParentCommandLine: \"C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\" -ExecutionPolicy Bypass -NonInteractive -File \"C:\\ludus\\background\\set-bg.ps1\"\r\nParentUser: cell-c\\domainadmin"
}

Detection Patterns #

81 rules

Sigma

yxinmiracle, Swachchhanda Shrawan Poudel (Nextron Systems)
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems)
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems)

Show 78 more (81 total) on the rules page

Show All Detection Patterns

Persistence: Create or Modify System Process

1 rule

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
event.typeeqstart239 ruleselastic
Imageends_with\powershell.exe162 rulessigma
Imageends_with\pwsh.exe150 rulessigma
Imageends_with\cmd.exe117 rulessigma
Imageends_with\rundll32.exe81 rulessigma
Imageends_with\cscript.exe60 rulessigma
Imageends_with\wscript.exe60 rulessigma
Imageends_with\wmic.exe58 rulessigma
OriginalFileNameeqpowershell.exe120 ruleselastic, sigma, splunk
OriginalFileNameeqpwsh.dll112 ruleselastic, sigma, splunk
OriginalFileNameeqcmd.exe64 ruleselastic, sigma, splunk
OriginalFileNameeqwmic.exe63 ruleselastic, sigma, splunk
OriginalFileNameeqrundll32.exe62 ruleselastic, sigma, splunk
process_nameeqpowershell.exe95 ruleselastic, splunk
process_nameeqcmd.exe73 ruleselastic, splunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • 7Zip Compressing Dump Files source medium: Detects execution of 7z in order to compress a file with a ".dmp"/".dump" extension, which could be a step in a process of dump file exfiltration.T1560, T1560.001
  • Compress Data and Lock With Password for Exfiltration With 7-ZIP source medium: An adversary may compress or encrypt data that is collected prior to exfiltration using 3rd party utilitiesT1560, T1560.001
  • Potential DLL Injection Via AccCheckConsole source medium: Detects the execution "AccCheckConsole" a command-line tool for verifying the accessibility implementation of an application's UI. One of the tests that this checker can run are called "verification routine", which tests for things like Consistency, Navigation, etc. The tool allows a user to provide a DLL that can contain a custom "verification routine". An attacker can build such DLLs and pass it via the CLI, which would then be loaded in the context of the "AccCheckConsole" utility.

Splunk # view in coverage

  • Detect Remote Access Software Usage FileInfo source: The following analytic detects the execution of processes with file or code signing attributes from known remote access software within the environment. It leverages Sysmon EventCode 1 data and cross-references a lookup table of remote…T1219
  • Excessive Usage Of SC Service Utility source: The following analytic detects excessive usage of the sc.exe service utility on a host machine. It leverages Sysmon EventCode 1 logs to identify instances where sc.exe is executed more frequently than normal within a 15-minute window.…T1569, T1569.002
  • Jscript Execution Using Cscript App source: The following analytic detects the execution of JScript using the cscript.exe process. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process and command-line telemetry. This behavior is significant…T1059, T1059.007

Kusto # view in coverage

YARA-L # view in coverage

References #

Event ID 2: A process changed a file creation time

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
File creation time changed (rule: FileCreateTime)
Opcode
Info

Description

The change **file creation time** event is registered when a file creation time is explicitly modified by a process. This event helps tracking the real creation time of a file. Attackers may change the file creation time of a backdoor to make it look like it was installed with the operating system. Note that many processes legitimately change the creation time of a file; it does not necessarily indicate malicious activity.

Message #

File creation time changed:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
TargetFilename: %6
CreationUtcTime: %7
PreviousCreationUtcTime: %8
User: %9

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that changed the file creation time
ProcessId UInt32Process ID used by the OS to identify the process changing the file creation time
Image UnicodeStringFile path of the process that changed the file creation time13 detection rules
TargetFilename UnicodeStringFull path name of the file7 detection rules
CreationUtcTime UnicodeStringNew creation time of the file1 detection rule
PreviousCreationUtcTime UnicodeStringPrevious creation time of the file1 detection rule
User UnicodeStringName of the account who changed the file creation time of a file

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 2,
    "version": 5,
    "level": 4,
    "task": 2,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:31:51.7752086+00:00",
    "event_record_id": 17461544,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 13:31:51.770",
    "ProcessGuid": "{8a99384c-5bb9-6a2d-3605-000000001000}",
    "ProcessId": "7796",
    "Image": "C:\\Windows\\system32\\wbem\\wmiprvse.exe",
    "TargetFilename": "C:\\Windows\\Temp\\B776E034-9102-4917-A2BF-152F782EA60A\\WimProvider.dll",
    "CreationUtcTime": "2026-06-13 13:31:38.052",
    "PreviousCreationUtcTime": "2026-06-13 13:31:38.052",
    "User": "NT AUTHORITY\\SYSTEM"
  },
  "message": "File creation time changed:\r\nRuleName: -\r\nUtcTime: 2026-06-13 13:31:51.770\r\nProcessGuid: {8a99384c-5bb9-6a2d-3605-000000001000}\r\nProcessId: 7796\r\nImage: C:\\Windows\\system32\\wbem\\wmiprvse.exe\r\nTargetFilename: C:\\Windows\\Temp\\B776E034-9102-4917-A2BF-152F782EA60A\\WimProvider.dll\r\nCreationUtcTime: 2026-06-13 13:31:38.052\r\nPreviousCreationUtcTime: 2026-06-13 13:31:38.052\r\nUser: NT AUTHORITY\\SYSTEM"
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Imageends_with\dns.exe1 rulesigma
Provider_NameeqMicrosoft-Windows-Sysmon1 ruleelastic
TargetFilenamewildcard?:\programdata\*1 ruleelastic
TargetFilenamewildcard?:\programdata\microsoft\windows\start menu\programs\startup\*1 ruleelastic
TargetFilenamewildcard?:\users\*\appdata\roaming\microsoft\windows\start menu\programs\startup\*1 ruleelastic
TargetFilenamewildcard?:\users\public\*1 ruleelastic
TargetFilenamewildcard?:\windows\system32\*1 ruleelastic
TargetFilenamewildcard?:\windows\syswow64\*1 ruleelastic
file.extensioneqdll1 ruleelastic
file.extensioneqexe1 ruleelastic
file.extensioneqlnk1 ruleelastic
file.extensioneqmsi1 ruleelastic
file.extensioneqpif1 ruleelastic
file.extensioneqscr1 ruleelastic
file.extensioneqsys1 ruleelastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • Unusual File Modification by dns.exe source high: Detects an unexpected file being modified by dns.exe which my indicate activity related to remote code execution or other forms of exploitation as seen in CVE-2020-1350 (SigRed)T1133
  • File Creation Date Changed to Another Year source low: Detects when the file creation time is changed to a year before 2020. Attackers may change the file creation time of a backdoor to make it look like it was installed with the operating system. Note that many processes legitimately change the creation time of a file; it does not necessarily indicate malicious activity. In order to use this rule in production, it is recommended first baseline normal behavior in your environment and then tune the rule accordingly. Hunting Recommendation: Focus on files with creation times set to years significantly before the current date, especially those in user-writable directories. Correlate with process execution logs to identify the source of the modification and investigate any unsigned or suspicious binaries involved.T1070, T1070.006

Elastic # view in coverage

  • Potential Timestomp in Executable Files source medium: Identifies the modification of a file creation time for executable files in sensitive system directories. Adversaries may modify file time attributes to blend malicious executables with legitimate system files. Timestomping is a technique that modifies the timestamps of a file often to mimic files that are in trusted directories.T1070, T1070.006

YARA-L # view in coverage

References #

Event ID 3: Network connection

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
Network connection detected (rule: NetworkConnect)
Opcode
Info

Description

The **network connection** event logs TCP/UDP connections on the machine. It is disabled by default. Each connection is linked to a process through the ProcessId and ProcessGUID fields. The event also contains the source and destination host names IP addresses, port numbers and IPv6 status.

Message #

Network connection detected:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
User: %6
Protocol: %7
Initiated: %8
SourceIsIpv6: %9
SourceIp: %10
SourceHostname: %11
SourcePort: %12
SourcePortName: %13
DestinationIsIpv6: %14
DestinationIp: %15
DestinationHostname: %16
DestinationPort: %17
DestinationPortName: %18

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that made the network connection
ProcessId UInt32Process ID used by the OS to identify the process that made the network connection
Image UnicodeStringFile path of the process that made the network connection394 detection rules
User UnicodeStringName of the account who made the network connection. It usually contains domain name and user name8 detection rules
Protocol UnicodeStringProtocol being used for the network connection. Sysmon emits the literal lowercase transport name rather than the IANA protocol number; tcp / udp are the only values produced by the kernel transport callback that drives this event.
Known values
tcp
TCP connection.
udp
UDP datagram.
8 detection rules
Initiated BooleanIndicates whether the process initiated the TCP connection49 detection rules
SourceIsIpv6 BooleanIs the source IP an IPv61 detection rule
SourceIp UnicodeStringSource IP address that made the network connection3 detection rules
SourceHostname UnicodeStringName of the host that made the network connection1 detection rule
SourcePort UInt16Source port number3 detection rules
SourcePortName UnicodeStringName of the source port being used (i.e. netbios-dgm)
DestinationIsIpv6 BooleanIs the destination IP an IPv61 detection rule
DestinationIp UnicodeStringDestination IP address72 detection rules
DestinationHostname UnicodeStringName of the host that received the network connection557 detection rules
DestinationPort UInt16Destination port number141 detection rules
DestinationPortName UnicodeStringName of the destination port4 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 3,
    "version": 5,
    "level": 4,
    "task": 3,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:46.6013699+00:00",
    "event_record_id": 17613679,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5404
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:43.178",
    "ProcessGuid": "{8a99384c-e92c-6a2c-0c00-000000001000}",
    "ProcessId": "896",
    "Image": "C:\\Windows\\System32\\lsass.exe",
    "User": "NT AUTHORITY\\SYSTEM",
    "Protocol": "tcp",
    "Initiated": "false",
    "SourceIsIpv6": "false",
    "SourceIp": "127.0.0.1",
    "SourceHostname": "telemetry-DC-c.cell-c.ludus.domain",
    "SourcePort": "57872",
    "SourcePortName": "-",
    "DestinationIsIpv6": "false",
    "DestinationIp": "127.0.0.1",
    "DestinationHostname": "telemetry-DC-c.cell-c.ludus.domain",
    "DestinationPort": "389",
    "DestinationPortName": "ldap"
  },
  "message": "Network connection detected:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:43.178\r\nProcessGuid: {8a99384c-e92c-6a2c-0c00-000000001000}\r\nProcessId: 896\r\nImage: C:\\Windows\\System32\\lsass.exe\r\nUser: NT AUTHORITY\\SYSTEM\r\nProtocol: tcp\r\nInitiated: false\r\nSourceIsIpv6: false\r\nSourceIp: 127.0.0.1\r\nSourceHostname: telemetry-DC-c.cell-c.ludus.domain\r\nSourcePort: 57872\r\nSourcePortName: -\r\nDestinationIsIpv6: false\r\nDestinationIp: 127.0.0.1\r\nDestinationHostname: telemetry-DC-c.cell-c.ludus.domain\r\nDestinationPort: 389\r\nDestinationPortName: ldap"
}

Detection Patterns #

Show All Detection Patterns

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Initiatedeqtrue48 rulessigma
Initiatedeqincoming10 ruleselastic
Initiatedeqingress10 ruleselastic
Initiatedeqegress5 ruleselastic
event.typeeqstart26 ruleselastic
src_ipis_not_null6 ruleselastic, kusto
src_ipne127.0.0.111 ruleselastic
src_ipne::110 ruleselastic
Protocoleqtcp8 ruleselastic, sigma
DestinationPorteq807 ruleselastic, kusto, sigma
DestinationPorteq4435 rulessigma
DestinationPortne07 rulessplunk
graph.metadata.entity_type (Chronicle)eqIP_ADDRESS7 ruleschronicle
graph.metadata.source_type (Chronicle)eqGLOBAL_CONTEXT6 ruleschronicle
process_nameeqrundll32.exe6 ruleselastic, splunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

  • Suspicious Instance Metadata Service (IMDS) API Request source medium: This rule identifies various tools/scripts performing network activities attempting to access the cloud service provider's instance metadata service (IMDS) API endpoint, which can be used to retrieve sensitive instance-specific information such as instance ID, public IP address, and even temporary security credentials if roles are assumed by that instance.T1016, T1082, T1552, T1552.005, T1580
  • Connection to Commonly Abused Web Services source low: Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in.T1071, T1071.001, T1090, T1090.002, T1102, T1102.001
  • Network Activity to a Suspicious Top Level Domain source high: Identifies DNS queries to commonly abused Top Level Domains by common LOLBINs or executables running from world writable directories or unsigned binaries. This behavior matches on common malware C2 abusing less formal domain names.T1071, T1071.004, T1127, T1127.001, T1218

Splunk # view in coverage

  • Detect Regasm with Network Connection source: The following analytic detects the execution of regasm.exe establishing a network connection to a public IP address, excluding private IP ranges. This detection leverages Sysmon EventID 3 logs to identify such behavior. This activity is…T1218, T1218.009
  • Detect Regsvcs with Network Connection source: The following analytic identifies instances of Regsvcs.exe establishing a network connection to a public IP address, excluding private IP ranges. This detection leverages Sysmon EventID 3 logs to monitor network connections initiated by…T1218, T1218.009
  • LOLBAS With Network Traffic source: The following analytic identifies the use of Living Off the Land Binaries and Scripts (LOLBAS) with network traffic. It leverages data from the Network Traffic data model to detect when native Windows binaries, often abused by adversaries,…T1105, T1218, T1567

Kusto # view in coverage

YARA-L # view in coverage

References #

Event ID 4: Sysmon service state changed

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
Sysmon service state changed
Opcode
Info

Description

The service state change event reports the state of the Sysmon service (started or stopped).

Message #

Sysmon service state changed:
UtcTime: %1
State: %2
Version: %3
SchemaVersion: %4

Fields #

NameDescriptionRules
UtcTime UnicodeStringTime in UTC when event was created
State UnicodeStringSysmon service state (i.e. stopped)
Known values
Started
Sysmon driver / service began collecting events.
Stopped
Sysmon driver / service stopped collecting events; a pairing 4 with State=Stopped immediately followed by State=Started indicates a config reload or driver restart.
2 detection rules
Version UnicodeStringSysmon version
SchemaVersion UnicodeStringSysmon config schema version

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 4,
    "version": 3,
    "level": 4,
    "task": 4,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:41:34.1645578+00:00",
    "event_record_id": 6120906,
    "correlation": {},
    "execution": {
      "process_id": 3872,
      "thread_id": 5252
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "UtcTime": "2026-06-13 13:41:34.151",
    "State": "Started",
    "Version": "15.20",
    "SchemaVersion": "4.91"
  },
  "message": "Sysmon service state changed:\r\nUtcTime: 2026-06-13 13:41:34.151\r\nState: Started\r\nVersion: 15.20\r\nSchemaVersion: 4.91"
}

Detection Patterns #

References #

Event ID 5: Process terminated

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Process terminated (rule: ProcessTerminate)
Opcode
Info

Description

The **process terminate** event reports when a process terminates. It provides the UtcTime, ProcessGuid and ProcessId of the process.

Message #

Process terminated:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
User: %6

Fields #

NameDescription
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that terminated
ProcessId UInt32Process ID used by the OS to identify the process that terminated
Image UnicodeStringFile path of the process that terminated
User UnicodeStringName of the account that terminated the process.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 5,
    "version": 3,
    "level": 4,
    "task": 5,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.7402157+00:00",
    "event_record_id": 17612823,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:29.726",
    "ProcessGuid": "{8a99384c-6499-6a2d-a205-000000001000}",
    "ProcessId": "7704",
    "Image": "C:\\ludus\\background\\bginfo.exe",
    "User": "cell-c\\domainadmin"
  },
  "message": "Process terminated:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:29.726\r\nProcessGuid: {8a99384c-6499-6a2d-a205-000000001000}\r\nProcessId: 7704\r\nImage: C:\\ludus\\background\\bginfo.exe\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
CommandLinecontains-r2 ruleskusto
CommandLinecontains-s2 ruleskusto
CommandLinecontains-exclusionpath1 rulekusto
CommandLinecontains-exec bypass -w 1 -enc1 rulekusto
CommandLinecontains-k gpsvcgroup1 rulekusto
CommandLinecontains-q1 rulekusto
CommandLinecontains-s gpsvc1 rulekusto
CommandLinecontains/set1 rulekusto
CommandLinecontainsaccepteula1 rulekusto
CommandLinecontainsadinfo1 rulekusto
CommandLinecontainsadvfirewall1 rulekusto
CommandLinecontainscomputers_pwdnotreqd1 rulekusto
CommandLinecontainsdclist1 rulekusto
CommandLinecontainsdcmodes1 rulekusto
Processcontainspowershell.exe2 ruleskusto

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Splunk # view in coverage

  • High Process Termination Frequency source: The following analytic identifies a high frequency of process termination events on a computer within a short period. It leverages Sysmon EventCode 5 logs to detect instances where 15 or more processes are terminated within a 3-second…T1486
  • Windows Processes Killed By Industroyer2 Malware source: The following analytic detects the termination of specific processes by the Industroyer2 malware. It leverages Sysmon EventCode 5 to identify when processes like "PServiceControl.exe" and "PService_PPD.exe" are killed. This activity is…T1489

References #

Event ID 6: Driver loaded

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
Driver loaded (rule: DriverLoad)
Opcode
Info

Description

The **driver loaded** events provides information about a driver being loaded on the system. The configured hashes are provided as well as signature information. The signature is created asynchronously for performance reasons and indicates if the file was removed after loading.

Message #

Driver loaded:
RuleName: %1
UtcTime: %2
ImageLoaded: %3
Hashes: %4
Signed: %5
Signature: %6
SignatureStatus: %7

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ImageLoaded UnicodeStringFull path of the driver loaded370 detection rules
Hashes UnicodeStringHashes captured by Sysmon driver5259 detection rules
Signed UnicodeStringWhether the loaded driver is signed
Signature UnicodeStringThe signer2 detection rules
SignatureStatus UnicodeStringStatus of the signature (i.e. valid)

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 6,
    "version": 4,
    "level": 4,
    "task": 6,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:42:26.1541821+00:00",
    "event_record_id": 6170407,
    "correlation": {},
    "execution": {
      "process_id": 3872,
      "thread_id": 5268
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 13:41:41.166",
    "ImageLoaded": "C:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\4.18.26050.15-0\\Drivers\\WdNisDrv.sys",
    "Hashes": "SHA1=F34854FEBF0D58F5F9C2F3081DA0C384E031CC48,MD5=D91B0982401E5C29F1E584228A774142,SHA256=8F98F2093E6373F1D275AAD30D9EF08ECFCE453F6ED02243FD284BDB6012377E,IMPHASH=FBF34F374D5BBC52DBDD4925A27836EF",
    "Signed": "true",
    "Signature": "Microsoft Windows",
    "SignatureStatus": "Valid"
  },
  "message": "Driver loaded:\r\nRuleName: -\r\nUtcTime: 2026-06-13 13:41:41.166\r\nImageLoaded: C:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\4.18.26050.15-0\\Drivers\\WdNisDrv.sys\r\nHashes: SHA1=F34854FEBF0D58F5F9C2F3081DA0C384E031CC48,MD5=D91B0982401E5C29F1E584228A774142,SHA256=8F98F2093E6373F1D275AAD30D9EF08ECFCE453F6ED02243FD284BDB6012377E,IMPHASH=FBF34F374D5BBC52DBDD4925A27836EF\r\nSigned: true\r\nSignature: Microsoft Windows\r\nSignatureStatus: Valid"
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Hashescontainsimphash=28dc68bb6d6bf4f6b2db8dd7588b25112 rulessigma
Hashescontainsimphash=45bfe170e0cd654bc1e2ae3fca3ac3f42 rulessigma
Hashescontainsimphash=821d74031d3f625bcbd0df08b70f1e772 rulessigma
Hashescontainsimphash=d41fa95d4642dc981f10de36f4dc8cd72 rulessigma
Hashescontainsimphash=f86759bb4de4320918615dc06e998a392 rulessigma
ImageLoadedcontains\temp\1 rulesigma
ImageLoadedends_with\kprocesshacker.sys2 rulessigma
ImageLoadedends_with\winring0.sys2 rulessigma
process_ideq42 ruleselastic
dll.code_signature.existseqfalse1 ruleelastic
dll.code_signature.statuseqerrorexpired1 ruleelastic
dll.code_signature.statuseqerrorrevoked1 ruleelastic
dll.code_signature.trustedeqfalse1 ruleelastic
is_drivereqtrue1 rulesplunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

Splunk # view in coverage

  • Windows Drivers Loaded by Signature source: The following analytic identifies all drivers being loaded on Windows systems using Sysmon EventCode 6 (Driver Load). It leverages fields such as driver path, signature status, and hash to detect potentially suspicious drivers. This…T1014, T1068
  • Windows Suspicious Driver Loaded Path source: The following analytic detects the loading of drivers from suspicious paths, which is a technique often used by malicious software such as coin miners (e.g., xmrig). It leverages Sysmon EventCode 6 to identify drivers loaded from…T1543, T1543.003
  • Windows Vulnerable Driver Loaded source: The following analytic detects the loading of known vulnerable Windows drivers, which may indicate potential persistence or privilege escalation attempts. It leverages Sysmon EventCode 6 to identify driver loading events and…T1543, T1543.003

References #

Event ID 7: Image loaded

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
Image loaded (rule: ImageLoad)
Opcode
Info

Description

The **image loaded** event logs when a module is loaded in a specific process. This event is disabled by default and needs to be configured with the -l option. It indicates the process in which the module is loaded, hashes and signature information. The signature is created asynchronously for performance reasons and indicates if the file was removed after loading. This event should be configured carefully, as monitoring all image load events will generate a large number of events.

Message #

Image loaded:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
ImageLoaded: %6
FileVersion: %7
Description: %8
Product: %9
Company: %10
OriginalFileName: %11
Hashes: %12
Signed: %13
Signature: %14
SignatureStatus: %15
User: %16

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that loaded the image
ProcessId UInt32Process ID used by the OS to identify the process that loaded the image
Image UnicodeStringFile path of the process that loaded the image545 detection rules
ImageLoaded UnicodeStringFull path of the image loaded1018 detection rules
FileVersion UnicodeStringVersion of the image loaded1 detection rule
Description UnicodeStringDescription of the image loaded7 detection rules
Product UnicodeStringProduct name that the loaded image belongs to5 detection rules
Company UnicodeStringCompany name that the loaded image belongs to6 detection rules
OriginalFileName UnicodeStringOriginal file name from the PE header, useful for detecting renamed modules30 detection rules
Hashes UnicodeStringHash of the file contents using the algorithms specified in the HashType field18 detection rules
Signed UnicodeStringIs the image loaded signed26 detection rules
Signature UnicodeStringThe signer6 detection rules
SignatureStatus UnicodeStringStatus of the signature (i.e. valid)20 detection rules
User UnicodeStringName of the account that loaded the image.3 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 7,
    "version": 3,
    "level": 4,
    "task": 7,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.7375531+00:00",
    "event_record_id": 17612821,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:29.726",
    "ProcessGuid": "{8a99384c-6499-6a2d-a205-000000001000}",
    "ProcessId": "7704",
    "Image": "C:\\ludus\\background\\bginfo.exe",
    "ImageLoaded": "C:\\Windows\\SysWOW64\\CoreMessaging.dll",
    "FileVersion": "10.0.20348.1 (WinBuild.160101.0800)",
    "Description": "Microsoft CoreMessaging Dll",
    "Product": "Microsoft® Windows® Operating System",
    "Company": "Microsoft Corporation",
    "OriginalFileName": "CoreMessaging.dll",
    "Hashes": "SHA1=3461F4349EF97F0FDE633219894DA0F67F4A69BC,MD5=A8D1AC93678A40577CD19E7561D7A714,SHA256=7BF17030A0FFABA28D8322D466718DE8CF499CD1B72B7D7B50543E6D93914998,IMPHASH=345E67613280BA4F965702CB83E693FE",
    "Signed": "true",
    "Signature": "Microsoft Windows",
    "SignatureStatus": "Valid",
    "User": "cell-c\\domainadmin"
  },
  "message": "Image loaded:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:29.726\r\nProcessGuid: {8a99384c-6499-6a2d-a205-000000001000}\r\nProcessId: 7704\r\nImage: C:\\ludus\\background\\bginfo.exe\r\nImageLoaded: C:\\Windows\\SysWOW64\\CoreMessaging.dll\r\nFileVersion: 10.0.20348.1 (WinBuild.160101.0800)\r\nDescription: Microsoft CoreMessaging Dll\r\nProduct: Microsoft® Windows® Operating System\r\nCompany: Microsoft Corporation\r\nOriginalFileName: CoreMessaging.dll\r\nHashes: SHA1=3461F4349EF97F0FDE633219894DA0F67F4A69BC,MD5=A8D1AC93678A40577CD19E7561D7A714,SHA256=7BF17030A0FFABA28D8322D466718DE8CF499CD1B72B7D7B50543E6D93914998,IMPHASH=345E67613280BA4F965702CB83E693FE\r\nSigned: true\r\nSignature: Microsoft Windows\r\nSignatureStatus: Valid\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Execution: Exploitation for Client Execution

1 rule
Show All Detection Patterns

Persistence: Create or Modify System Process

1 rule

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Signedeqfalse9 rulessigma, splunk
Imagecontains:\users\public\4 rulessigma
Imageends_with\excel.exe8 rulessigma
Imageends_with\outlook.exe7 rulessigma
Imageends_with\winword.exe7 rulessigma
Imageends_with\powerpnt.exe6 rulessigma
Imageends_with\rundll32.exe6 rulessigma
Imageends_with\mspub.exe5 rulessigma
Imageends_with\onenote.exe5 rulessigma
Imageends_with\onenoteim.exe5 rulessigma
Imageends_with\svchost.exe4 ruleskusto, sigma
EventTypeeqload6 ruleselastic
ImageLoadedends_with.dll6 rulessigma, splunk
ImageLoadedends_with\dbgcore.dll6 rulessigma
ImageLoadedends_with\dbghelp.dll6 rulessigma

Community Notes #

Image loaded. Generated when a process loads a DLL into memory, ie, side-loading.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

Splunk # view in coverage

  • CMLUA Or CMSTPLUA UAC Bypass source: The following analytic detects the use of COM objects like CMLUA or CMSTPLUA to bypass User Account Control (UAC). It leverages Sysmon EventCode 7 to identify the loading of specific DLLs (CMLUA.dll, CMSTPLUA.dll, CMLUAUTIL.dll) by…T1218, T1218.003
  • Loading Of Dynwrapx Module source: The following analytic detects the loading of the dynwrapx.dll module, which is associated with the DynamicWrapperX ActiveX component. This detection leverages Sysmon EventCode 7 to identify processes that load or register dynwrapx.dll.…T1055, T1055.001
  • MS Scripting Process Loading Ldap Module source: The following analytic detects the execution of MS scripting processes (wscript.exe or cscript.exe) loading LDAP-related modules (Wldap32.dll, adsldp.dll, adsldpc.dll). It leverages Sysmon EventCode 7 to identify these specific DLL loads.…T1059, T1059.007

YARA-L # view in coverage

References #

Event ID 8: CreateRemoteThread

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
CreateRemoteThread detected (rule: CreateRemoteThread)
Opcode
Info

Description

The **CreateRemoteThread** event detects when a process creates a thread in another process. This technique is used by malware to inject code and hide in other processes. The event indicates the source and target process. It gives information on the code that will be run in the new thread: StartAddress, StartModule and StartFunction. Note that StartModule and StartFunction fields are inferred, they might be empty if the starting address is outside loaded modules or known exported functions.

Message #

CreateRemoteThread detected:
RuleName: %1
UtcTime: %2
SourceProcessGuid: %3
SourceProcessId: %4
SourceImage: %5
TargetProcessGuid: %6
TargetProcessId: %7
TargetImage: %8
NewThreadId: %9
StartAddress: %10
StartModule: %11
StartFunction: %12
SourceUser: %13
TargetUser: %14

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
SourceProcessGuid GUIDProcess GUID of the source process that created a thread in another process
SourceProcessId UInt32Process ID used by the OS to identify the source process that created a thread in another process
SourceImage UnicodeStringFile path of the source process that created a thread in another process112 detection rules
TargetProcessGuid GUIDProcess GUID of the target process
TargetProcessId UInt32Process ID used by the OS to identify the target process
TargetImage UnicodeStringFile path of the target process186 detection rules
NewThreadId UInt32ID of the new thread created in the target process
StartAddress UnicodeStringNew thread start address3 detection rules
StartModule UnicodeStringModule where the new thread starts execution, resolved from the thread start address1 detection rule
StartFunction UnicodeStringExported function where the new thread starts, if the start address matches a known export4 detection rules
SourceUser UnicodeStringName of the account of the source process that created a thread in another process.
TargetUser UnicodeStringName of the account of the target process

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 8,
    "version": 2,
    "level": 4,
    "task": 8,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:08:51.1140624+00:00",
    "event_record_id": 17610309,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:08:51.101",
    "SourceProcessGuid": "{8a99384c-e939-6a2c-5900-000000001000}",
    "SourceProcessId": "4028",
    "SourceImage": "C:\\Tools\\RPCFW_2.2.5\\rpcFwManager.exe",
    "TargetProcessGuid": "{8a99384c-6471-6a2d-a005-000000001000}",
    "TargetProcessId": "7864",
    "TargetImage": "C:\\Windows\\System32\\wsmprovhost.exe",
    "NewThreadId": "8000",
    "StartAddress": "0x00007FF9A37401F0",
    "StartModule": "C:\\Windows\\System32\\KERNEL32.DLL",
    "StartFunction": "LoadLibraryA",
    "SourceUser": "NT AUTHORITY\\SYSTEM",
    "TargetUser": "cell-c\\domainadmin"
  },
  "message": "CreateRemoteThread detected:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:08:51.101\r\nSourceProcessGuid: {8a99384c-e939-6a2c-5900-000000001000}\r\nSourceProcessId: 4028\r\nSourceImage: C:\\Tools\\RPCFW_2.2.5\\rpcFwManager.exe\r\nTargetProcessGuid: {8a99384c-6471-6a2d-a005-000000001000}\r\nTargetProcessId: 7864\r\nTargetImage: C:\\Windows\\System32\\wsmprovhost.exe\r\nNewThreadId: 8000\r\nStartAddress: 0x00007FF9A37401F0\r\nStartModule: C:\\Windows\\System32\\KERNEL32.DLL\r\nStartFunction: LoadLibraryA\r\nSourceUser: NT AUTHORITY\\SYSTEM\r\nTargetUser: cell-c\\domainadmin"
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
SourceImagecontains:\temp\1 rulesigma
SourceImagecontains:\users\public\1 rulesigma
SourceImageends_with\powershell.exe3 rulessigma
SourceImageends_with\pwsh.exe3 rulessigma
SourceImageends_with\excel.exe2 rulessigma
SourceImageends_with\winword.exe2 rulessigma
TargetImageends_with\lsass.exe2 rulessigma
TargetImageends_with\rundll32.exe2 rulessigma
TargetImageends_with\\lsass.exe1 rulesplunk
TargetImageends_with\calc.exe1 rulesigma
TargetImageends_with\calculator.exe1 rulesigma
TargetImagein*\\cmd.exe2 rulessplunk
TargetImagein*\\explorer.exe2 rulessplunk
TargetImagein*\\powershell.exe2 rulessplunk
Provider_NameeqMicrosoft-Windows-Sysmon1 ruleelastic

Community Notes #

CreateRemoteThread. Detects some process-injection methods.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

Splunk # view in coverage

  • Create Remote Thread In Shell Application source: The following analytic detects suspicious process injection in command shell applications, specifically targeting cmd.exe and powershell.exe. It leverages Sysmon EventCode 8 to identify the creation of remote threads within these shell…T1055
  • Create Remote Thread into LSASS source: The following analytic detects the creation of a remote thread in the Local Security Authority Subsystem Service (LSASS). This behavior is identified using Sysmon EventID 8 logs, focusing on processes that create remote threads in…T1003, T1003.001
  • Powershell Remote Thread To Known Windows Process source: The following analytic detects suspicious PowerShell processes attempting to inject code into critical Windows processes using CreateRemoteThread. It leverages Sysmon EventCode 8 to identify instances where PowerShell spawns threads in…T1055

References #

Event ID 9: RawAccessRead

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (JSCU-NL)
Task
RawAccessRead detected (rule: RawAccessRead)
Opcode
Info

Description

The **RawAccessRead** event detects when a process conducts reading operations from the drive using the .\ denotation. This technique is often used by malware for data exfiltration of files that are locked for reading, as well as to avoid file access auditing tools. The event indicates the source process and target device.

Message #

RawAccessRead detected:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
Device: %6
User: %7

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that conducted reading operations from the drive
ProcessId UInt32Process ID used by the OS to identify the process that conducted reading operations from the drive
Image UnicodeStringFile path of the process that conducted reading operations from the drive36 detection rules
Device UnicodeStringTarget device5 detection rules
User UnicodeStringName of the account of the process that conducted reading operations from the drive

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 9,
    "version": 2,
    "level": 4,
    "task": 9,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:23:56.8470704+00:00",
    "event_record_id": 16041099,
    "correlation": {},
    "execution": {
      "process_id": 4008,
      "thread_id": 5284
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-b.cell-b.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:23:56.843",
    "ProcessGuid": "{8a99384c-c2a8-6a19-9400-000000000f00}",
    "ProcessId": "6120",
    "Image": "C:\\Windows\\System32\\svchost.exe",
    "Device": "\\Device\\HarddiskVolume1",
    "User": "NT AUTHORITY\\SYSTEM"
  },
  "message": "RawAccessRead detected:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:23:56.843\r\nProcessGuid: {8a99384c-c2a8-6a19-9400-000000000f00}\r\nProcessId: 6120\r\nImage: C:\\Windows\\System32\\svchost.exe\r\nDevice: \\Device\\HarddiskVolume1\r\nUser: NT AUTHORITY\\SYSTEM"
}

Community Notes #

RawAccessRead, may indicate direct disk reads of ntds.dit, SAM, or page files for offline hash extraction.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Splunk # view in coverage

References #

Event ID 10: ProcessAccess

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (JSCU-NL)
Task
Process accessed (rule: ProcessAccess)
Opcode
Info

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.

Message #

Process accessed:
RuleName: %1
UtcTime: %2
SourceProcessGUID: %3
SourceProcessId: %4
SourceThreadId: %5
SourceImage: %6
TargetProcessGUID: %7
TargetProcessId: %8
TargetImage: %9
GrantedAccess: %10
CallTrace: %11
SourceUser: %12
TargetUser: %13

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
SourceProcessGUID GUID
SourceProcessId UInt32Process ID used by the os to identify the source process that opened another process. Derived partially from the EPROCESS kernel structure
SourceThreadId UInt32ID of the specific thread inside of the source process that opened another process
SourceImage UnicodeStringFile path of the source process that opened another process296 detection rules
TargetProcessGUID GUID
TargetProcessId UInt32Process ID used by the OS to identify the target process
TargetImage UnicodeStringFile path of the target process113 detection rules
GrantedAccess HexInt32The access flags (bitmask) associated with the process rights requested for the target process Process access rights reference199 detection rules
CallTrace UnicodeStringStack trace of where OpenProcess is called, including the DLL and relative virtual address of each function in the call stack52 detection rules
SourceUser UnicodeStringName of the account of the source process that opened another process.6 detection rules
TargetUser UnicodeStringName of the account of the target process

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 10,
    "version": 3,
    "level": 4,
    "task": 10,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:58.2417162+00:00",
    "event_record_id": 17614233,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:58.226",
    "SourceProcessGUID": "{8a99384c-e93e-6a2c-7000-000000001000}",
    "SourceProcessId": "5508",
    "SourceThreadId": "6764",
    "SourceImage": "C:\\Windows\\system32\\wbem\\wmiprvse.exe",
    "TargetProcessGUID": "{8a99384c-e976-6a2c-b900-000000001000}",
    "TargetProcessId": "6984",
    "TargetImage": "C:\\Windows\\System32\\RuntimeBroker.exe",
    "GrantedAccess": "0x1410",
    "CallTrace": "C:\\Windows\\SYSTEM32\\ntdll.dll+9f3b4|C:\\Windows\\System32\\KERNELBASE.dll+2aafe|C:\\Windows\\system32\\wbem\\cimwin32.dll+e3a5|C:\\Windows\\system32\\wbem\\cimwin32.dll+ea1c|C:\\Windows\\SYSTEM32\\framedynos.dll+4006|C:\\Windows\\SYSTEM32\\framedynos.dll+4e74|C:\\Windows\\system32\\wbem\\wmiprvse.exe+180e|C:\\Windows\\system32\\wbem\\wmiprvse.exe+1420|C:\\Windows\\System32\\RPCRT4.dll+749d3|C:\\Windows\\System32\\RPCRT4.dll+2f745|C:\\Windows\\System32\\combase.dll+c373b|C:\\Windows\\System32\\RPCRT4.dll+58a85|C:\\Windows\\System32\\combase.dll+9e2fd|C:\\Windows\\System32\\combase.dll+9e08e|C:\\Windows\\System32\\combase.dll+c9de6|C:\\Windows\\System32\\combase.dll+658bd|C:\\Windows\\System32\\combase.dll+ba051|C:\\Windows\\System32\\combase.dll+4b4ce|C:\\Windows\\System32\\combase.dll+49f0f|C:\\Windows\\System32\\combase.dll+48839|C:\\Windows\\System32\\RPCRT4.dll+57ff2|C:\\Windows\\System32\\RPCRT4.dll+4762f|C:\\Windows\\System32\\RPCRT4.dll+47258|C:\\Windows\\System32\\RPCRT4.dll+1d1a3",
    "SourceUser": "NT AUTHORITY\\NETWORK SERVICE",
    "TargetUser": "cell-c\\domainadmin"
  },
  "message": "Process accessed:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:58.226\r\nSourceProcessGUID: {8a99384c-e93e-6a2c-7000-000000001000}\r\nSourceProcessId: 5508\r\nSourceThreadId: 6764\r\nSourceImage: C:\\Windows\\system32\\wbem\\wmiprvse.exe\r\nTargetProcessGUID: {8a99384c-e976-6a2c-b900-000000001000}\r\nTargetProcessId: 6984\r\nTargetImage: C:\\Windows\\System32\\RuntimeBroker.exe\r\nGrantedAccess: 0x1410\r\nCallTrace: C:\\Windows\\SYSTEM32\\ntdll.dll+9f3b4|C:\\Windows\\System32\\KERNELBASE.dll+2aafe|C:\\Windows\\system32\\wbem\\cimwin32.dll+e3a5|C:\\Windows\\system32\\wbem\\cimwin32.dll+ea1c|C:\\Windows\\SYSTEM32\\framedynos.dll+4006|C:\\Windows\\SYSTEM32\\framedynos.dll+4e74|C:\\Windows\\system32\\wbem\\wmiprvse.exe+180e|C:\\Windows\\system32\\wbem\\wmiprvse.exe+1420|C:\\Windows\\System32\\RPCRT4.dll+749d3|C:\\Windows\\System32\\RPCRT4.dll+2f745|C:\\Windows\\System32\\combase.dll+c373b|C:\\Windows\\System32\\RPCRT4.dll+58a85|C:\\Windows\\System32\\combase.dll+9e2fd|C:\\Windows\\System32\\combase.dll+9e08e|C:\\Windows\\System32\\combase.dll+c9de6|C:\\Windows\\System32\\combase.dll+658bd|C:\\Windows\\System32\\combase.dll+ba051|C:\\Windows\\System32\\combase.dll+4b4ce|C:\\Windows\\System32\\combase.dll+49f0f|C:\\Windows\\System32\\combase.dll+48839|C:\\Windows\\System32\\RPCRT4.dll+57ff2|C:\\Windows\\System32\\RPCRT4.dll+4762f|C:\\Windows\\System32\\RPCRT4.dll+47258|C:\\Windows\\System32\\RPCRT4.dll+1d1a3\r\nSourceUser: NT AUTHORITY\\NETWORK SERVICE\r\nTargetUser: cell-c\\domainadmin"
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
TargetImageends_with\lsass.exe14 rulessigma
TargetImageends_withlsass.exe5 rulessplunk
GrantedAccessends_with0x14c24 rulessigma
GrantedAccessends_with104 rulessigma
GrantedAccessends_with184 rulessigma
GrantedAccessends_with1a4 rulessigma
GrantedAccessends_with304 rulessigma
GrantedAccessends_with384 rulessigma
GrantedAccessends_with3a4 rulessigma
GrantedAccessends_with504 rulessigma
GrantedAccessends_with584 rulessigma
GrantedAccesseq0x1fffff9 ruleskusto, sigma, splunk
CallTracecontainsunknown5 ruleselastic, sigma
CallTracecontainsdbgcore.dll4 ruleskusto, sigma, splunk
CallTracecontainsdbghelp.dll4 ruleskusto, sigma, splunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

Splunk # view in coverage

Kusto # view in coverage

  • Dumping LSASS Process Into a File source high: Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, the system generates and stores a variety of credential materials in LSASS process memory. These credential materials can be harvested by an administrative user or system and used to conduct lateral movement using alternate authentication materials. As well as in-memory techniques, the LSASS process memory can be dumped from the target host and analyzed on a local system. Ref: https://attack.mitre.org/techniques/T1003/001/T1003, T1003.001

YARA-L # view in coverage

References #

Event ID 11: FileCreate

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
File created (rule: FileCreate)
Opcode
Info

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.

Message #

File created:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
TargetFilename: %6
CreationUtcTime: %7
User: %8

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that created the file
ProcessId UInt32Process ID used by the OS to identify the process that created the file
Image UnicodeStringFile path of the process that created the file491 detection rules
TargetFilename UnicodeStringName of the file1797 detection rules
CreationUtcTime UnicodeStringFile creation time4 detection rules
User UnicodeStringName of the account who created the file2 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 11,
    "version": 2,
    "level": 4,
    "task": 11,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:34.7524084+00:00",
    "event_record_id": 17613105,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:34.741",
    "ProcessGuid": "{8a99384c-e971-6a2c-b200-000000001000}",
    "ProcessId": "6816",
    "Image": "C:\\Windows\\Explorer.EXE",
    "TargetFilename": "C:\\Users\\domainadmin\\AppData\\Roaming\\Microsoft\\Windows\\Themes\\CachedFiles\\CachedImage_1024_768_POS1.jpg",
    "CreationUtcTime": "2026-06-13 14:09:34.741",
    "User": "cell-c\\domainadmin"
  },
  "message": "File created:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:34.741\r\nProcessGuid: {8a99384c-e971-6a2c-b200-000000001000}\r\nProcessId: 6816\r\nImage: C:\\Windows\\Explorer.EXE\r\nTargetFilename: C:\\Users\\domainadmin\\AppData\\Roaming\\Microsoft\\Windows\\Themes\\CachedFiles\\CachedImage_1024_768_POS1.jpg\r\nCreationUtcTime: 2026-06-13 14:09:34.741\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Show All Detection Patterns

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
TargetFilenameends_with.dll23 rulessigma
TargetFilenameends_with.exe21 rulessigma, splunk
TargetFilenameends_with.vbs18 rulessigma
TargetFilenameends_with.bat17 rulessigma
TargetFilenameends_with.ps117 rulessigma
TargetFilenameends_with.vbe16 rulessigma
TargetFilenameends_with.hta14 rulessigma
TargetFilenameends_with.js10 rulessigma
TargetFilenamestarts_withc:\users\10 ruleselastic, sigma
event.typeeqcreation18 ruleselastic
Imageends_with\powershell.exe13 rulessigma
Imageends_with\pwsh.exe12 rulessigma
Imageends_with\mshta.exe11 rulessigma
Imageends_with\cmd.exe8 rulessigma
event_actioneqcreated9 rulessplunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • ADSI-Cache File Creation By Uncommon Tool source medium: Detects the creation of an "Active Directory Schema Cache File" (.sch) file by an uncommon tool.T1001, T1001.003
  • Advanced IP Scanner - File Event source medium: Detects the use of Advanced IP Scanner. Seems to be a popular tool for ransomware groups.T1046
  • Anydesk Temporary Artefact source medium: An adversary may use legitimate desktop support and remote access software, such as Team Viewer, Go2Assist, LogMein, AmmyyAdmin, etc, to establish an interactive command and control channel to target systems within networks. These services are commonly used as legitimate technical support software, and may be allowed by application control within a target environment. Remote access tools like VNC, Ammyy, and Teamviewer are used frequently when compared with other legitimate software commonly used by adversaries. (Citation: Symantec Living off the Land)T1219, T1219.002

Elastic # view in coverage

  • Remote File Copy via TeamViewer source medium: Identifies an executable or script file remotely downloaded via a TeamViewer transfer session.T1105, T1219
  • Kirbi File Creation source high: Identifies the creation of .kirbi files, a suspicious Kerberos ticket artifact often produced by ticket export or dumping tools such as Rubeus or Mimikatz. This can indicate preparation for Kerberos ticket theft or later abuse, including Pass-The-Ticket (PTT), and should be validated with writer process and follow-on activity.T1003, T1558
  • Windows Registry File Creation in SMB Share source medium: Identifies the creation or modification of a medium-size registry hive file on a Server Message Block (SMB) share, which may indicate an exfiltration attempt of a previously dumped Security Account Manager (SAM) registry hive for credential extraction on an attacker-controlled system.T1003, T1003.002, T1021, T1021.002, T1048

Splunk # view in coverage

  • Email files written outside of the Outlook directory source: The following analytic detects email files (.pst or .ost) being created outside the standard Outlook directories. It leverages the Endpoint.Filesystem data model to identify file creation events and filters for email files not located in…T1114, T1114.001
  • Batch File Write to System32 source: The following analytic detects the creation of a batch file (.bat) within the Windows system directory tree, specifically in the System32 or SysWOW64 folders. It leverages data from the Endpoint datamodel, focusing on process and…T1204, T1204.002
  • Common Ransomware Extensions source: The following analytic detects modifications to files with extensions commonly associated with ransomware. It leverages the Endpoint.Filesystem data model to identify changes in file extensions that match known ransomware patterns. This…T1485

Kusto # view in coverage

YARA-L # view in coverage

References #

Event ID 12: RegistryEvent (Object create and delete)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Registry object added or deleted (rule: RegistryEvent)
Opcode
Info

Description

**Registry key and value create and delete** operations map to this event type, which can be useful for monitoring for changes to Registry autostart locations, or specific malware registry modifications.

Message #

Registry object added or deleted:
RuleName: %1
EventType: %2
UtcTime: %3
ProcessGuid: %4
ProcessId: %5
Image: %6
TargetObject: %7
User: %8

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeStringRegistry event. Either Create or Delete
Known values
CreateKey
A new registry key was created.
DeleteKey
An existing registry key was deleted.
CreateValue
A new registry value was created under an existing key.
DeleteValue
An existing registry value was removed.
19 detection rules
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that created or deleted a registry key
ProcessId UInt32Process ID used by the OS to identify the process that created or deleted a registry key
Image UnicodeStringFile path of the process that created or deleted a registry key21 detection rules
TargetObject UnicodeStringComplete path of the registry key177 detection rules
User UnicodeStringThe name of the account that created or deleted a registry key or value2 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 12,
    "version": 2,
    "level": 4,
    "task": 12,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:44.0868063+00:00",
    "event_record_id": 17613579,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "EventType": "CreateKey",
    "UtcTime": "2026-06-13 14:09:44.085",
    "ProcessGuid": "{8a99384c-e939-6a2c-5500-000000001000}",
    "ProcessId": "3932",
    "Image": "C:\\Windows\\ADWS\\Microsoft.ActiveDirectory.WebServices.exe",
    "TargetObject": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters",
    "User": "NT AUTHORITY\\SYSTEM"
  },
  "message": "Registry object added or deleted:\r\nRuleName: -\r\nEventType: CreateKey\r\nUtcTime: 2026-06-13 14:09:44.085\r\nProcessGuid: {8a99384c-e939-6a2c-5500-000000001000}\r\nProcessId: 3932\r\nImage: C:\\Windows\\ADWS\\Microsoft.ActiveDirectory.WebServices.exe\r\nTargetObject: HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters\r\nUser: NT AUTHORITY\\SYSTEM"
}

Detection Patterns #

Show All Detection Patterns

Execution: PowerShell

8 rules

Sigma

Florian Roth (Nextron Systems), Markus Neis, Jonhnathan Ribeiro, Daniil Yugoslavskiy, oscd.community
Center for Threat Informed Defense (CTID) Summiting the Pyramid Team
Swachchhanda Shrawan Poudel (Nextron Systems)

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
event.typeeqchange44 ruleselastic
Detailsends_with.dll3 ruleselastic
Detailseq18 ruleselastic, kusto
Detailseq07 ruleselastic
Detailseq0x000000007 ruleselastic
Detailseq0x000000017 ruleselastic
Detailsis_not_null9 ruleselastic
Detailslength_compare04 ruleselastic
Detailslength_compare>4 ruleselastic
EventTypeeqsetvalue5 rulessigma
EventTypeeqdeleted4 rulessplunk
EventTypeeqcreatekey3 rulessigma
EventTypeinRegistryKeyCreated5 ruleskusto
EventTypeinRegistryValueSet5 ruleskusto
Imageis_not_null3 ruleselastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • Potential Persistence Via Disk Cleanup Handler - Registry source medium: Detects when an attacker modifies values of the Disk Cleanup Handler in the registry to achieve persistence. The disk cleanup manager is part of the operating system. It displays the dialog box […] The user has the option of enabling or disabling individual handlers by selecting or clearing their check box in the disk cleanup manager's UI. Although Windows comes with a number of disk cleanup handlers, they aren't designed to handle files produced by other applications. Instead, the disk cleanup manager is designed to be flexible and extensible by enabling any developer to implement and register their own disk cleanup handler. Any developer can extend the available disk cleanup services by implementing and registering a disk cleanup handler.
  • Potential Ursnif Malware Activity - Registry source high: Detects registry keys related to Ursnif malware.T1112
  • Potential NetWire RAT Activity - Registry source high: Detects registry keys related to NetWire RATT1112

Splunk # view in coverage

  • Windows CrowdStrike Agent Registry Key Removal source: Detects delete events on the CrowdStrike registry keys. These keys are removed as part of the agent uninstallation process. This activity should only occur during planned events and any instances outside that should be evaluated for…T1685
  • Windows Modify Registry Delete Firewall Rules source: The following analytic detects a potential deletion of firewall rules, indicating a possible security breach or unauthorized access attempt. It identifies actions where firewall rules are removed using commands like netsh advfirewall…T1112
  • Windows Registry Delete Task SD source: The following analytic detects a process attempting to delete a scheduled task's Security Descriptor (SD) from the registry path of that task. It leverages the Endpoint.Registry data model to identify registry actions performed by the…T1053, T1053.005, T1685

YARA-L # view in coverage

References #

Event ID 13: RegistryEvent (Value Set)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Registry value set (rule: RegistryEvent)
Opcode
Info

Description

This Registry event type identifies **Registry value modifications**. The event records the value written for Registry values of type DWORD and QWORD.

Message #

Registry value set:
RuleName: %1
EventType: %2
UtcTime: %3
ProcessGuid: %4
ProcessId: %5
Image: %6
TargetObject: %7
Details: %8
User: %9

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeStringRegistry value modification event27 detection rules
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that modified a registry value
ProcessId UInt32Process ID used by the OS to identify the process that modified a registry value
Image UnicodeStringFile path of the process that modified a registry value326 detection rules
TargetObject UnicodeStringComplete path of the registry key992 detection rules
Details UnicodeStringDetails added to the registry key1031 detection rules
User UnicodeStringThe name of the account that modified a registry value.4 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 13,
    "version": 2,
    "level": 4,
    "task": 13,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.7259683+00:00",
    "event_record_id": 17612810,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "EventType": "SetValue",
    "UtcTime": "2026-06-13 14:09:29.710",
    "ProcessGuid": "{8a99384c-6499-6a2d-a205-000000001000}",
    "ProcessId": "7704",
    "Image": "C:\\ludus\\background\\bginfo.exe",
    "TargetObject": "HKU\\S-1-5-21-1006758700-2167138679-1475694448-1105\\Software\\Winternals\\BGInfo\\WindowPosition",
    "Details": "Binary Data",
    "User": "cell-c\\domainadmin"
  },
  "message": "Registry value set:\r\nRuleName: -\r\nEventType: SetValue\r\nUtcTime: 2026-06-13 14:09:29.710\r\nProcessGuid: {8a99384c-6499-6a2d-a205-000000001000}\r\nProcessId: 7704\r\nImage: C:\\ludus\\background\\bginfo.exe\r\nTargetObject: HKU\\S-1-5-21-1006758700-2167138679-1475694448-1105\\Software\\Winternals\\BGInfo\\WindowPosition\r\nDetails: Binary Data\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Show All Detection Patterns

Execution: PowerShell

8 rules

Sigma

Florian Roth (Nextron Systems), Markus Neis, Jonhnathan Ribeiro, Daniil Yugoslavskiy, oscd.community
Center for Threat Informed Defense (CTID) Summiting the Pyramid Team
Swachchhanda Shrawan Poudel (Nextron Systems)

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Detailscontainspowershell10 ruleschronicle, sigma
Detailscontains\appdata\local\temp\7 rulessigma
Detailscontains%temp%5 ruleschronicle, sigma
Detailsends_with.dll8 ruleselastic, sigma, splunk
Detailseq0x0000000159 ruleselastic, splunk
Detailseq0x0000000040 ruleselastic, splunk
Detailseqdword (0x00000001)40 ruleschronicle, sigma
Detailseqdword (0x00000000)38 ruleschronicle, sigma
Detailseq110 ruleselastic, kusto, splunk
Detailseqdword (0x00000002)10 ruleschronicle, sigma
Detailseq08 ruleselastic, sigma
Detailsis_not_null54 ruleselastic, splunk
event.typeeqchange44 ruleselastic
EventTypeeqmodified7 rulessplunk
EventTypeeqsetvalue6 rulessigma

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Splunk # view in coverage

  • Active Setup Registry Autostart source: The following analytic detects suspicious modifications to the Active Setup registry for persistence and privilege escalation. It leverages data from the Endpoint.Registry data model, focusing on changes to the "StubPath" value within the…T1547, T1547.014
  • Allow Inbound Traffic By Firewall Rule Registry source: The following analytic detects suspicious modifications to firewall rule registry settings that allow inbound traffic on specific ports with a public profile. It leverages data from the Endpoint.Registry data model, focusing on registry…T1021, T1021.001
  • Allow Operation with Consent Admin source: The following analytic detects a registry modification that allows the 'Consent Admin' to perform operations requiring elevation without user consent or credentials. It leverages data from the Endpoint.Registry data model, specifically…T1548

Kusto # view in coverage

  • DSRM Account Abuse source high: This query detects an abuse of the DSRM account in order to maintain persistence and access to the organization's Active Directory. Ref: https://adsecurity.org/?p=1785T1098
  • Registry Persistence via AppCert DLL Modification source medium: Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppCert DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppCertDLLs Registry key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\ are loaded into every process that calls the ubiquitously used application programming interface (API) functions CreateProcess, CreateProcessAsUser, CreateProcessWithLoginW, CreateProcessWithTokenW, or WinExec. Ref: https://attack.mitre.org/techniques/T1546/009/T1546, T1546.009
  • Registry Persistence via AppInit DLLs Modification source medium: Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppInit DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppInit_DLLs value in the Registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows or HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows are loaded by user32.dll into every process that loads user32.dll. In practice this is nearly every program, since user32.dll is a very common library. Ref: https://attack.mitre.org/techniques/T1546/010/T1546, T1546.010

YARA-L # view in coverage

References #

Event ID 14: RegistryEvent (Key and Value Rename)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Registry object renamed (rule: RegistryEvent)
Opcode
Info

Description

**Registry key and value rename** operations map to this event type, recording the new name of the key or value that was renamed.

Message #

Registry object renamed:
RuleName: %1
EventType: %2
UtcTime: %3
ProcessGuid: %4
ProcessId: %5
Image: %6
TargetObject: %7
NewName: %8
User: %9

Fields #

NameDescriptionRules
EventType UnicodeString → stringRegistry event. Registry key and value renamed
Known values
RenameKey
An existing registry key was renamed (NewName carries the destination key path).
RenameValue
A registry value name was changed under an existing key.
4 detection rules
UtcTime UnicodeString → stringTime in UTC when event was created
ProcessGuid GUID → GUIDProcess GUID of the process that renamed a registry value and key
ProcessId UInt32 → PIDProcess ID used by the OS to identify the process that renamed a registry value and key
Image UnicodeString → stringFile path of the process that renamed a registry value and key35 detection rules
TargetObject UnicodeString → stringComplete path of the registry key27 detection rules
NewName UnicodeString → stringNew name of the registry key
RuleName UnicodeString → stringcustom tag mapped to event. i.e ATT&CK technique ID
User UnicodeString → string

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385f-c22a-43e0-bf4c-06f5698ffbd9}",
    "event_source_name": "",
    "event_id": 14,
    "version": 2,
    "level": 4,
    "task": 14,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-05-29T23:53:07.2285127+00:00",
    "event_record_id": 160620,
    "correlation": {},
    "execution": {
      "process_id": 11572,
      "thread_id": 11700
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "DESKTOP-FF3N5XK.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "EventType": "RenameKey",
    "UtcTime": "2026-05-29 23:53:07.227",
    "ProcessGuid": "{e124ce79-26e3-6a1a-dc11-000000000700}",
    "ProcessId": "11804",
    "Image": "C:\\caps\\dwrename.exe",
    "TargetObject": "HKU\\S-1-5-21-3798294047-1846905762-1150995898-1000\\Software\\dwtest_key",
    "NewName": "HKU\\S-1-5-21-3798294047-1846905762-1150995898-1000\\Software\\dwtest_key_renamed",
    "User": "DESKTOP-FF3N5XK\\localuser"
  },
  "message": "Registry object renamed:\r\nRuleName: -\r\nEventType: RenameKey\r\nUtcTime: 2026-05-29 23:53:07.227\r\nProcessGuid: {e124ce79-26e3-6a1a-dc11-000000000700}\r\nProcessId: 11804\r\nImage: C:\\caps\\dwrename.exe\r\nTargetObject: HKU\\S-1-5-21-3798294047-1846905762-1150995898-1000\\Software\\dwtest_key\r\nNewName: HKU\\S-1-5-21-3798294047-1846905762-1150995898-1000\\Software\\dwtest_key_renamed\r\nUser: DESKTOP-FF3N5XK\\localuser"
}

Detection Patterns #

Show All Detection Patterns

Execution: PowerShell

8 rules

Sigma

Florian Roth (Nextron Systems), Markus Neis, Jonhnathan Ribeiro, Daniil Yugoslavskiy, oscd.community
Center for Threat Informed Defense (CTID) Summiting the Pyramid Team
Swachchhanda Shrawan Poudel (Nextron Systems)

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
event.typeeqchange44 ruleselastic
Detailsends_with.dll3 ruleselastic
Detailseq18 ruleselastic, kusto
Detailseq07 ruleselastic
Detailseq0x000000007 ruleselastic
Detailseq0x000000017 ruleselastic
Detailsis_not_null9 ruleselastic
Detailslength_compare04 ruleselastic
Detailslength_compare>4 ruleselastic
EventTypeeqdeletevalue4 rulessigma
EventTypeeqsetvalue4 rulessigma
Imageis_not_null3 ruleselastic
TargetObjectcontains\software\microsoft\windows nt\currentversion\schedule\taskcache\tree\3 rulessigma
TargetObjectwildcardhkey_users\*\software\microsoft\windows\currentversion\policies\explorer\run\*3 ruleselastic
TargetObjectwildcardhklm\software\microsoft\windows\currentversion\policies\explorer\run\*3 ruleselastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • Delete Defender Scan ShellEx Context Menu Registry Key source medium: Detects deletion of registry key that adds 'Scan with Defender' option in context menu. Attackers may use this to make it harder for users to scan files that are suspicious.
  • Windows Credential Guard Related Registry Value Deleted - Registry source high: Detects attempts to disable Windows Credential Guard by deleting registry values. Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them. Adversaries may disable Credential Guard to gain access to sensitive credentials stored in the system, such as NTLM hashes and Kerberos tickets, which can be used for lateral movement and privilege escalation.T1685
  • Windows Recall Feature Enabled - DisableAIDataAnalysis Value Deleted source medium: Detects the enabling of the Windows Recall feature via registry manipulation. Windows Recall can be enabled by deleting the existing "DisableAIDataAnalysis" registry value. Adversaries may enable Windows Recall as part of post-exploitation discovery and collection activities. This rule assumes that Recall is already explicitly disabled on the host, and subsequently enabled by the adversary.T1113

References #

Event ID 15: FileCreateStreamHash

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
File stream created (rule: FileCreateStreamHash)
Opcode
Info

Description

This event logs when a **named file stream is created**, and it generates events that log the hash of the contents of the file to which the stream is assigned (the unnamed stream), as well as the contents of the named stream. There are malware variants that drop their executables or configuration settings via browser downloads, and this event is aimed at capturing that based on the browser attaching a Zone.Identifier "mark of the web" stream.

Message #

File stream created:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
TargetFilename: %6
CreationUtcTime: %7
Hash: %8
Contents: %9
User: %10

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that created the named file stream
ProcessId UInt32Process ID used by the OS to identify the process that created the named file stream
Image UnicodeStringFile path of the process that created the named file stream24 detection rules
TargetFilename UnicodeStringName of the file76 detection rules
CreationUtcTime UnicodeStringFile download time
Hash UnicodeStringHash of the file contents using the algorithms specified in the HashType field104 detection rules
Contents UnicodeStringContent of the named file stream (e.g., Zone.Identifier)86 detection rules
User UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 15,
    "version": 2,
    "level": 4,
    "task": 15,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:42:03.6658910+00:00",
    "event_record_id": 6137955,
    "correlation": {},
    "execution": {
      "process_id": 3872,
      "thread_id": 5252
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 13:42:03.651",
    "ProcessGuid": "{8a99384c-5e0b-6a2d-4c00-000000000a00}",
    "ProcessId": "3488",
    "Image": "C:\\Windows\\system32\\DFSRs.exe",
    "TargetFilename": "C:\\Windows\\SYSVOL\\staging\\domain\\ContentSet{F961A193-E171-4E37-B0B3-7E1394CCD8E0}-{02199C3B-68C2-47D3-88A0-F16A83088C75}:ReplicatedFolderList",
    "CreationUtcTime": "2026-05-28 00:46:59.105",
    "Hash": "SHA1=13D7A18758C123CD4479C81E4B2D70301C31F7C3,MD5=2CB80232D48F726137F136C129FB2D2D,SHA256=F0336167989447F25357C51FEF44D321E40A6310DD8DD2FEFF37B8E55E4543A0,IMPHASH=00000000000000000000000000000000",
    "Contents": "{",
    "User": "F"
  },
  "message": "File stream created:\r\nRuleName: -\r\nUtcTime: 2026-06-13 13:42:03.651\r\nProcessGuid: {8a99384c-5e0b-6a2d-4c00-000000000a00}\r\nProcessId: 3488\r\nImage: C:\\Windows\\system32\\DFSRs.exe\r\nTargetFilename: C:\\Windows\\SYSVOL\\staging\\domain\\ContentSet{F961A193-E171-4E37-B0B3-7E1394CCD8E0}-{02199C3B-68C2-47D3-88A0-F16A83088C75}:ReplicatedFolderList\r\nCreationUtcTime: 2026-05-28 00:46:59.105\r\nHash: SHA1=13D7A18758C123CD4479C81E4B2D70301C31F7C3,MD5=2CB80232D48F726137F136C129FB2D2D,SHA256=F0336167989447F25357C51FEF44D321E40A6310DD8DD2FEFF37B8E55E4543A0,IMPHASH=00000000000000000000000000000000\r\nContents: {\r\nUser: F"
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
TargetFilenamecontains.bat:zone3 rulessigma
TargetFilenamecontains.dll:zone3 rulessigma
TargetFilenamecontains.exe:zone3 rulessigma
TargetFilenamecontains.hta:zone3 rulessigma
TargetFilenamecontains.ps1:zone3 rulessigma
TargetFilenamecontains.vbe:zone3 rulessigma
TargetFilenamecontains.vbs:zone3 rulessigma
TargetFilenamecontains.xll:zone3 rulessigma
TargetFilenameends_with:zone.identifier3 rulessigma, splunk
Contentscontains.githubusercontent.com2 rulessigma
Contentscontains0x0.st2 rulessigma
Contentscontainsanonfiles.com2 rulessigma
Contentscontainsbashupload.com2 rulessigma
Contentscontainscdn.discordapp.com2 rulessigma
Contentscontainschunk.io2 rulessigma

Community Notes #

May contain Mark of the Web, referrer, and host URL data.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Splunk # view in coverage

  • Download Files Using Telegram source: The following analytic detects suspicious file downloads by the Telegram application on a Windows system. It leverages Sysmon EventCode 15 to identify instances where Telegram.exe creates files with a Zone.Identifier, indicating a…T1105
  • Windows Alternate DataStream - Base64 Content source: The following analytic detects the creation of Alternate Data Streams (ADS) with Base64 content on Windows systems. It leverages Sysmon EventID 15, which captures file creation events, including the content of named streams. ADS can…T1564, T1564.004
  • Windows Alternate DataStream - Executable Content source: The following analytic detects the writing of data with an IMPHASH value to an Alternate Data Stream (ADS) in the NTFS file system. It leverages Sysmon Event ID 15 and regex to identify files with a Portable Executable (PE) structure. This…T1564, T1564.004

References #

Event ID 16: ServiceConfigurationChange

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
Sysmon config state changed
Opcode
Info

Description

This event logs changes in the Sysmon configuration.

Message #

Sysmon config state changed:
UtcTime: %1
Configuration: %2
ConfigurationFileHash: %3

Fields #

NameDescription
UtcTime UnicodeString → stringTime in UTC when event was created
Configuration UnicodeString → stringName of the Sysmon config file being updated
ConfigurationFileHash UnicodeString → stringHash (SHA1) of the Sysmon config file being updated

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 16,
    "version": 3,
    "level": 4,
    "task": 16,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2023-11-06T00:47:11.932399+00:00",
    "event_record_id": 994662,
    "correlation": {},
    "execution": {
      "process_id": 8688,
      "thread_id": 13092
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "WinDev2310Eval",
    "security": {
      "user_id": "S-1-5-21-1992711665-1655669231-58201500-1000"
    }
  },
  "event_data": {
    "UtcTime": "2023-11-06 00:47:11.921",
    "Configuration": "C:\\Users\\User\\Downloads\\Sysmon\\sysmonconfig-trace.xml",
    "ConfigurationFileHash": "SHA256=43F367924B48AF65F121C0D369E7971C0757CC35D984C71887A5840987E154F9"
  },
  "message": ""
}

Detection Patterns #

Community Notes #

May indicate an attacker attempting to reduce visibility prior to staging a payload.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • Sysmon Configuration Change source medium: Detects a Sysmon configuration change, which could be the result of a legitimate reconfiguration or someone trying manipulate the configuration

References #

Event ID 17: PipeEvent (Pipe Created)

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Pipe Created (rule: PipeEvent)
Opcode
Info

Description

This event generates when a **named pipe is created**. Malware often uses named pipes for interprocess communication.

Message #

Pipe Created:
RuleName: %1
EventType: %2
UtcTime: %3
ProcessGuid: %4
ProcessId: %5
PipeName: %6
Image: %7
User: %8

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeStringThe type of pipe event (CreatePipe)8 detection rules
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that created the pipe
ProcessId UInt32Process ID used by the OS to identify the process that created the pipe
PipeName UnicodeStringName of the pipe created104 detection rules
Image UnicodeStringFile path of the process that created the pipe60 detection rules
User UnicodeStringThe name of the account that created the named pipe.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 17,
    "version": 1,
    "level": 4,
    "task": 17,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:08:49.4169649+00:00",
    "event_record_id": 17610185,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "EventType": "CreatePipe",
    "UtcTime": "2026-06-13 14:08:49.413",
    "ProcessGuid": "{8a99384c-6471-6a2d-a005-000000001000}",
    "ProcessId": "7864",
    "PipeName": "\\PSHost.134258333292497101.7864.DefaultAppDomain.wsmprovhost",
    "Image": "C:\\Windows\\system32\\wsmprovhost.exe",
    "User": "cell-c\\domainadmin"
  },
  "message": "Pipe Created:\r\nRuleName: -\r\nEventType: CreatePipe\r\nUtcTime: 2026-06-13 14:08:49.413\r\nProcessGuid: {8a99384c-6471-6a2d-a005-000000001000}\r\nProcessId: 7864\r\nPipeName: \\PSHost.134258333292497101.7864.DefaultAppDomain.wsmprovhost\r\nImage: C:\\Windows\\system32\\wsmprovhost.exe\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Named Pipe

30 rules

Sigma

Florian Roth (Nextron Systems)
Roberto Rodriguez @Cyb3rWard0g, Tim Shelton
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)

Show 16 more (19 total) on the rules page

Kusto

Microsoft Security Research

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
EventTypeinconnectpipe4 rulessplunk
EventTypeincreatepipe4 rulessplunk
toolis_not_null4 rulessplunk
PipeNameeq\psexesvc2 rulessigma
PipeNameeq\sdlrpc2 rulessigma
PipeNamestarts_with\PSHost2 rulessigma
AccessListcontains%%44181 rulekusto
Hashesis_not_null1 rulechronicle
Imagecontains:\users\public\1 rulesigma
Imagecontains:\windows\temp\1 rulesigma
Imagecontains\appdata\local\temp\1 rulesigma
Imagecontains\desktop\1 rulesigma
Imagecontains\downloads\1 rulesigma
Imageends_with\scrcons.exe1 rulesigma
Provider_NameeqMicrosoft-Windows-Sysmon1 ruleelastic

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

YARA-L # view in coverage

References #

Event ID 18: PipeEvent (Pipe Connected)

#
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Pipe Connected (rule: PipeEvent)
Opcode
Info

Description

This event logs when a named pipe connection is made between a client and a server.

Message #

Pipe Connected:
RuleName: %1
EventType: %2
UtcTime: %3
ProcessGuid: %4
ProcessId: %5
PipeName: %6
Image: %7
User: %8

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeStringThe type of pipe event (ConnectPipe)
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that connected the pipe
ProcessId UInt32Process ID used by the OS to identify the process that connected the pipe
PipeName UnicodeStringName of the pipe connected1 detection rule
Image UnicodeStringFile path of the process that connected the pipe
User UnicodeStringThe name of the account that made a named pipe connection.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 18,
    "version": 1,
    "level": 4,
    "task": 18,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.4179487+00:00",
    "event_record_id": 17612764,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "EventType": "ConnectPipe",
    "UtcTime": "2026-06-13 14:09:29.413",
    "ProcessGuid": "{8a99384c-6499-6a2d-a205-000000001000}",
    "ProcessId": "7704",
    "PipeName": "\\srvsvc",
    "Image": "C:\\ludus\\background\\bginfo.exe",
    "User": "cell-c\\domainadmin"
  },
  "message": "Pipe Connected:\r\nRuleName: -\r\nEventType: ConnectPipe\r\nUtcTime: 2026-06-13 14:09:29.413\r\nProcessGuid: {8a99384c-6499-6a2d-a205-000000001000}\r\nProcessId: 7704\r\nPipeName: \\srvsvc\r\nImage: C:\\ludus\\background\\bginfo.exe\r\nUser: cell-c\\domainadmin"
}

Detection Patterns #

Named Pipe

30 rules

Sigma

Florian Roth (Nextron Systems)
Roberto Rodriguez @Cyb3rWard0g, Tim Shelton
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)

Show 16 more (19 total) on the rules page

Kusto

Microsoft Security Research

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
EventTypeinconnectpipe4 rulessplunk
EventTypeincreatepipe4 rulessplunk
toolis_not_null4 rulessplunk
Computereqadfs_servers2 ruleskusto
PipeNameeq\psexesvc2 rulessigma
PipeNameeq\sdlrpc2 rulessigma
PipeNamestarts_with\PSHost2 rulessigma
AccessListcontains%%44181 rulekusto
DestinationPorteq801 rulekusto
Imagecontains:\users\public\1 rulesigma
Imagecontains:\windows\temp\1 rulesigma
Imagecontains\appdata\local\temp\1 rulesigma
Imagecontains\desktop\1 rulesigma
Imagecontains\downloads\1 rulesigma
Imageends_with\scrcons.exe1 rulesigma

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Kusto # view in coverage

  • ADFS Database Named Pipe Connection source medium: This detection uses Sysmon telemetry to detect suspicious local connections via a named pipe to the AD FS configuration database (Windows Internal Database). In order to use this query you need to be collecting Sysmon EventIdD 18 (Pipe Connected). If you do not have Sysmon data in your workspace this query will raise an error stating: Failed to resolve scalar expression named "[@Name]"T1005

YARA-L # view in coverage

References #

Event ID 19: WmiEvent (WmiEventFilter activity detected)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
WmiEventFilter activity detected (rule: WmiEvent)
Opcode
Info

Description

When a WMI event filter is registered, this event logs the WMI namespace, filter name and filter expression.

Message #

WmiEventFilter activity detected:
RuleName: %1
EventType: %2
UtcTime: %3
Operation: %4
User: %5
EventNamespace: %6
Name: %7
Query: %8

Fields #

NameDescription
RuleName UnicodeString → stringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeString → stringWMI event type
UtcTime UnicodeString → stringTime in UTC when event was created
Operation UnicodeString → stringWMI event filter operation
Known values
Created
A WMI persistence artifact was registered (filter, consumer, or binding established).
Deleted
An existing WMI persistence artifact was removed.
Modified
An existing WMI persistence artifact was updated in place (rare).
User UnicodeString → stringUser that created the WMI filter
EventNamespace UnicodeString → stringEvent namespace where the WMI class is registered
Name UnicodeString → stringWMI filter name being created
Query UnicodeString → stringWMI filter query

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 19,
    "version": 3,
    "level": 4,
    "task": 19,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2019-07-19T14:54:57.044623Z",
    "event_record_id": 4055,
    "correlation": {},
    "execution": {
      "process_id": 2796,
      "thread_id": 1776
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "MSEDGEWIN10",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "",
    "EventType": "WmiFilterEvent",
    "UtcTime": "2019-07-19 14:54:57.041",
    "Operation": "Created",
    "User": "MSEDGEWIN10\\IEUser",
    "EventNamespace": " \"root\\\\CimV2\"",
    "Name": " \"AtomicRedTeam-WMIPersistence-Example\"",
    "Query": " \"SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA 'Win32_PerfFormattedData_PerfOS_System' AND TargetInstance.SystemUpTime >= 240 AND TargetInstance.SystemUpTime < 325\""
  }
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
CommandLinecontainsrundll321 rulekusto
Computereqadfs_servers1 rulekusto

References #

Event ID 20: WmiEvent (WmiEventConsumer activity detected)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
WmiEventConsumer activity detected (rule: WmiEvent)
Opcode
Info

Description

This event logs the **registration of WMI consumers**, recording the consumer name, log, and destination.

Message #

WmiEventConsumer activity detected:
RuleName: %1
EventType: %2
UtcTime: %3
Operation: %4
User: %5
Name: %6
Type: %7
Destination: %8

Fields #

NameDescription
RuleName UnicodeString → stringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeString → stringWMI event type
UtcTime UnicodeString → stringTime in UTC when event was created
Operation UnicodeString → stringWMI consumer operation (e.g., Created, Deleted)
Known values
Created
A WMI persistence artifact was registered (filter, consumer, or binding established).
Deleted
An existing WMI persistence artifact was removed.
Modified
An existing WMI persistence artifact was updated in place (rare).
User UnicodeString → stringUser that created the WMI consumer
Name UnicodeString → stringName of the consumer created
Type UnicodeString → stringType of WMI consumer
Destination UnicodeString → stringDestination or command executed by the WMI consumer

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 20,
    "version": 3,
    "level": 4,
    "task": 20,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2019-07-19T14:54:58.819106Z",
    "event_record_id": 4056,
    "correlation": {},
    "execution": {
      "process_id": 2796,
      "thread_id": 1776
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "MSEDGEWIN10",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "",
    "EventType": "WmiConsumerEvent",
    "UtcTime": "2019-07-19 14:54:58.807",
    "Operation": "Created",
    "User": "MSEDGEWIN10\\IEUser",
    "Name": " \"AtomicRedTeam-WMIPersistence-Example\"",
    "Type": "Command Line",
    "Destination": " \"C:\\\\Windows\\\\System32\\\\notepad.exe\""
  }
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
CommandLinecontainsrundll321 rulekusto
Computereqadfs_servers1 rulekusto

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Splunk # view in coverage

  • Detect WMI Event Subscription Persistence source: The following analytic identifies the creation of WMI Event Subscriptions, which can be used to establish persistence or perform privilege escalation. It detects EventID 19 (EventFilter creation), EventID 20 (EventConsumer creation), and…T1546, T1546.003

References #

Event ID 21: WmiEvent (WmiEventConsumerToFilter activity detected)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Olaf Hartong, others)
Task
WmiEventConsumerToFilter activity detected (rule: WmiEvent)
Opcode
Info

Description

When a consumer binds to a filter, this event logs the consumer name and filter path.

Message #

WmiEventConsumerToFilter activity detected:
RuleName: %1
EventType: %2
UtcTime: %3
Operation: %4
User: %5
Consumer: %6
Filter: %7

Fields #

NameDescription
RuleName UnicodeString → stringCustom tag mapped to event, i.e. ATT&CK technique ID
EventType UnicodeString → stringWMI event type
UtcTime UnicodeString → stringTime in UTC when event was created
Operation UnicodeString → stringWMI consumer-to-filter binding operation
Known values
Created
A WMI persistence artifact was registered (filter, consumer, or binding established).
Deleted
An existing WMI persistence artifact was removed.
Modified
An existing WMI persistence artifact was updated in place (rare).
User UnicodeString → stringUser that created the WMI consumer-to-filter binding
Consumer UnicodeString → stringConsumer created to bind
Filter UnicodeString → stringFilter created to bind

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 21,
    "version": 3,
    "level": 4,
    "task": 21,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2019-07-19T14:57:02.378480Z",
    "event_record_id": 4057,
    "correlation": {},
    "execution": {
      "process_id": 2796,
      "thread_id": 4356
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "MSEDGEWIN10",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "",
    "EventType": "WmiBindingEvent",
    "UtcTime": "2019-07-19 14:57:02.369",
    "Operation": "Created",
    "User": "MSEDGEWIN10\\IEUser",
    "Consumer": " \"\\\\\\\\.\\\\ROOT\\\\subscription:CommandLineEventConsumer.Name=\\\"AtomicRedTeam-WMIPersistence-Example\\\"\"",
    "Filter": " \"\\\\\\\\.\\\\ROOT\\\\subscription:__EventFilter.Name=\\\"AtomicRedTeam-WMIPersistence-Example\\\"\""
  }
}

Detection Patterns #

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
CommandLinecontainsrundll321 rulekusto
Computereqadfs_servers1 rulekusto
data_stream.dataseteqwindows.sysmon_operational1 ruleelastic

Community Notes #

May surface registration of WMI event-based auto-runs that survive reboots.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Elastic # view in coverage

Splunk # view in coverage

  • WMI Permanent Event Subscription - Sysmon source: The following analytic identifies the creation of WMI permanent event subscriptions, which can be used to establish persistence or perform privilege escalation. It leverages Sysmon data, specifically EventCodes 19, 20, and 21, to detect…T1546, T1546.003

References #

Event ID 22: DNSEvent (DNS query)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (JSCU-NL)
Task
Dns query (rule: DnsQuery)
Opcode
Info

Description

This event generates when a process executes a **DNS query**, whether the result is successful or fails, cached or not.

Message #

Dns query:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
QueryName: %5
QueryStatus: %6
QueryResults: %7
Image: %8
User: %9

Fields #

NameDescriptionRules
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that executed the DNS query
ProcessId UInt32Process ID of the process that executed the DNS query
QueryName UnicodeStringDNS query name342 detection rules
QueryStatus UnicodeStringDNS query status
Known values
0
Success (records returned or no error)
5
ERROR_ACCESS_DENIED
87
ERROR_INVALID_PARAMETER
1460
ERROR_TIMEOUT
9001
DNS_ERROR_RCODE_FORMAT_ERROR (FORMERR)
9002
DNS_ERROR_RCODE_SERVER_FAILURE (SERVFAIL)
9003
DNS_ERROR_RCODE_NAME_ERROR (NXDOMAIN)
9004
DNS_ERROR_RCODE_NOT_IMPLEMENTED (NOTIMP)
9005
DNS_ERROR_RCODE_REFUSED
9501
DNS_INFO_NO_RECORDS (no error, zero records)
9701
DNS_ERROR_RECORD_DOES_NOT_EXIST (specific record not found)
9702
DNS_ERROR_RECORD_FORMAT (record format error)
9714
DNS_ERROR_NAME_DOES_NOT_EXIST (name itself does not exist)
9852
DNS_ERROR_NO_DNS_SERVERS (no configured resolvers)
QueryResults UnicodeStringDNS query results
Image UnicodeStringThe full path related to the process that executed the DNS query226 detection rules
User UnicodeStringThe name of the account that executes a DNS Query.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 22,
    "version": 5,
    "level": 4,
    "task": 22,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:53.5641227+00:00",
    "event_record_id": 6320060,
    "correlation": {},
    "execution": {
      "process_id": 3872,
      "thread_id": 5372
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:52.247",
    "ProcessGuid": "{8a99384c-5e0c-6a2d-5d00-000000000a00}",
    "ProcessId": "3872",
    "QueryName": "172.210.232.199.in-addr.arpa.",
    "QueryStatus": "9003",
    "QueryResults": "-",
    "Image": "C:\\Windows\\Sysmon64.exe",
    "User": "NT AUTHORITY\\SYSTEM"
  },
  "message": "Dns query:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:52.247\r\nProcessGuid: {8a99384c-5e0c-6a2d-5d00-000000000a00}\r\nProcessId: 3872\r\nQueryName: 172.210.232.199.in-addr.arpa.\r\nQueryStatus: 9003\r\nQueryResults: -\r\nImage: C:\\Windows\\Sysmon64.exe\r\nUser: NT AUTHORITY\\SYSTEM"
}

Detection Patterns #

Execution: Exploitation for Client Execution

1 rule

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
graph.metadata.entity_type (Chronicle)eqDOMAIN_NAME5 ruleschronicle
QueryNameeq*3 rulessplunk
QueryNameis_not_null4 ruleselastic, kusto
scorege54 ruleskusto
EventTime_tcross_field_comparemin_t3 ruleskusto
ValidUntilis_null3 ruleskusto
CategoryeqAzureFirewallApplicationRule2 ruleskusto
DnsQueryTypeNameinA2 ruleskusto
DnsQueryTypeNameinAAAA2 ruleskusto
DnsResponseNameis_not_null2 ruleskusto
EventResultDetails_seqNXDOMAIN2 ruleskusto
EventTypeeqlookup_requested2 ruleselastic
EventTypeindnsevent (dns query)2 ruleselastic
EventTypeinlookup_requested2 ruleselastic
Imagein*\\appdata\\*2 rulessplunk

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

Elastic # view in coverage

  • First Time Seen DNS Query to RMM Domain source medium: Detects DNS queries to commonly abused remote monitoring and management (RMM) or remote access software domains from processes that are not browsers. Intended to surface RMM clients, scripts, or other non-browser activity contacting these services.T1219, T1219.002
  • Potential DNS Exfiltration via Excessive Chunked Queries source medium: Identifies potential DNS exfiltration on Windows hosts by detecting a high volume of DNS queries whose subdomain labels follow a chunked encoding pattern (index-payload.base_domain). Attackers split stolen data across many DNS queries to evade volume-based detection; this rule aggregates queries per process, base domain, and five-minute window and flags sessions with many distinct chunk indices and sufficiently long encoded payloads.T1048, T1048.003, T1572
  • External IP Lookup from Non-Browser Process source low: Identifies domains commonly used by adversaries for post-exploitation IP lookups. It is common for adversaries to test for Internet access and acquire their external IP address after they have gained access to a system. Among others, this has been observed in campaigns leveraging the information stealer, Trickbot.T1016, T1016.001, T1614

Splunk # view in coverage

  • Local LLM Framework DNS Query source: Detects DNS queries related to local LLM models on endpoints by monitoring Sysmon DNS query events (Event ID 22) for known LLM model domains and services. Local LLM frameworks like Ollama, LM Studio, and GPT4All make DNS calls to…T1590
  • Windows AI Platform DNS Query source: The following analytic detects DNS queries initiated by the Windows AI Platform to domains associated with Hugging Face, OpenAI, and other popular providers of machine learning models and services. Monitoring these DNS requests is…T1071, T1071.004
  • Windows BitLockerToGo with Network Activity source: The following analytic detects suspicious usage of BitLockerToGo.exe, which has been observed being abused by Lumma stealer malware. The malware leverages this legitimate Windows utility to manipulate registry keys, search for…T1218

Kusto # view in coverage

YARA-L # view in coverage

References #

Event ID 23: FileDelete (File Delete archived)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
File Delete archived (rule: FileDelete)
Opcode
Info

Description

A file was deleted. Additionally the deleted file is saved in the ArchiveDirectory.

Message #

File Delete archived:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
User: %5
Image: %6
TargetFilename: %7
Hashes: %8
IsExecutable: %9
Archived: %10

Fields #

NameDescriptionRules
RuleName UnicodeString → stringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeString → stringTime in UTC when event was created
ProcessGuid GUID → GUIDProcess GUID of the process that deleted the file
ProcessId UInt32 → PIDProcess ID used by the OS to identify the process that deleted the file
User UnicodeString → stringName of the account who deleted the file.2 detection rules
Image UnicodeString → stringFile path of the process that deleted the file22 detection rules
TargetFilename UnicodeString → stringFull path name of the deleted file79 detection rules
Hashes UnicodeString → stringHashes captured by the Sysmon driver of the deleted file
IsExecutable Boolean → booleanWhether the deleted file is a PE executable
Archived UnicodeString → stringStates if the file was archived when deleted

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 23,
    "version": 5,
    "level": 4,
    "task": 23,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2020-10-20T11:50:55.461859Z",
    "event_record_id": 769,
    "correlation": {},
    "execution": {
      "process_id": 7212,
      "thread_id": 9748
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "DESKTOP-NTSSLJD",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2020-10-20 11:50:55.457",
    "ProcessGuid": "23F38D93-CF1F-5F8E-CA08-000000000C00",
    "ProcessId": 8736,
    "User": "DESKTOP-NTSSLJD\\den",
    "Image": "C:\\Program Files\\Internet Explorer\\IEInstal.exe",
    "TargetFilename": "C:\\Users\\den\\AppData\\Local\\Temp\\dfcc1807-03a1-4ae1-ab29-5675b285edea\\consent.exe.dat",
    "Hashes": "SHA1=6BFB38629570909D3D9EEDFC783A948CE7849105,MD5=EE2A1C85C472F89B146CC8EE598CCCBC,SHA256=19FD0010DA92B654D1CA270247061A39EA13C0A58529FD8257A97E2EF7794911,IMPHASH=522D83761201075834F05037F5307949",
    "IsExecutable": true,
    "Archived": "true"
  }
}

Detection Patterns #

Show All Detection Patterns

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Hashes[0]eqsha2563 ruleskusto
TargetFilenameends_with:zone.identifier3 rulessigma, splunk
TargetFilenameends_with.log2 rulessigma
event.typeeqdeletion3 ruleselastic
ClientIPeqIPList2 ruleskusto
DestinationIPeqIPList2 ruleskusto
EventTypeeqFileCreated2 ruleskusto
Hashesis_not_null2 ruleskusto
Hashes[1]containssha256hashes2 ruleskusto
IPAddresseseqIPList2 ruleskusto
InitiatingProcessSHA256eqsha256hashes2 ruleskusto
Messagecontainsiplist2 ruleskusto
ObservableKeycontainsfile:hashes2 ruleskusto
ObservableValueis_not_null2 ruleskusto
SourceIPeqIPList2 ruleskusto

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

YARA-L # view in coverage

References #

Event ID 24: ClipboardChange (New content in the clipboard)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (JSCU-NL)
Task
Clipboard changed (rule: ClipboardChange)
Opcode
Info

Description

This event is generated when the system clipboard contents change.

Message #

Clipboard changed:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
Session: %6
ClientInfo: %7
Hashes: %8
Archived: %9
User: %10

Fields #

NameDescription
RuleName UnicodeString → string
UtcTime UnicodeString → string
ProcessGuid GUID → GUID
ProcessId UInt32 → PID
Image UnicodeString → string
Session UInt32 → unsignedInt
ClientInfo UnicodeString → string
Hashes UnicodeString → string
Archived UnicodeString → string
User UnicodeString → string

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 24,
    "version": 5,
    "level": 4,
    "task": 24,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2023-11-06T01:34:43.177918+00:00",
    "event_record_id": 1300545,
    "correlation": {},
    "execution": {
      "process_id": 7064,
      "thread_id": 18652
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "WinDev2310Eval",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2023-11-06 01:34:43.168",
    "ProcessGuid": "E56ADA26-3DE0-6548-E908-000000000D00",
    "ProcessId": 11112,
    "Image": "C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.18.2822.0_x64__8wekyb3d8bbwe\\WindowsTerminal.exe",
    "Session": 1,
    "ClientInfo": "user: WINDEV2310EVAL\\User",
    "Hashes": "SHA1=179A4D08834E913B14727CF6474BAC31E082D275,MD5=64D76D5B160C1EB41680025DD778622D,SHA256=35EC5A2FD3F20757A957DC280EF330892A9D76378252CD381BF34518E6A30427,IMPHASH=00000000000000000000000000000000",
    "Archived": "true",
    "User": "WINDEV2310EVAL\\User"
  },
  "message": ""
}

References #

Event ID 25: ProcessTampering (Process image change)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (Palantir, others)
Task
Process Tampering (rule: ProcessTampering)
Opcode
Info

Description

This event is generated when process hiding techniques are being detected.

Message #

Process Tampering:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
Image: %5
Type: %6
User: %7

Fields #

NameDescriptionRules
RuleName UnicodeString
UtcTime UnicodeString
ProcessGuid GUID
ProcessId UInt32
Image UnicodeString7 detection rules
Type UnicodeString
Known values
Image is replaced
The on-disk image backing the process was modified after the process started (process hollowing variant detected via PsSetCreateProcessNotifyRoutineEx hash comparison against the loaded image).
Image is unmapped
The PE image was unmapped from the process address space after creation; the loader's expected image is no longer present.
Image is locked for access
Sysmon could not open the on-disk PE for read because another handle holds it with an exclusive sharing mode. May indicate process herpaderping using the optional exclusive-lock variant (jxy-s/herpaderping `-e` flag; the herpaderping primitive itself is content modification after image mapping, not the lock — see https://github.com/jxy-s/herpaderping). Benign locking by AV/EDR scan engines and installers can produce the same Sysmon signal; the catalog sample observed Avira wsc_agent.exe triggering this Type.
1 detection rule
User UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 25,
    "version": 5,
    "level": 4,
    "task": 25,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:41:34.2634917+00:00",
    "event_record_id": 6122317,
    "correlation": {},
    "execution": {
      "process_id": 3872,
      "thread_id": 5252
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 13:41:19.666",
    "ProcessGuid": "{00000000-0000-0000-0000-000000000000}",
    "ProcessId": "604",
    "Image": "<unknown process>",
    "Type": "Image is replaced",
    "User": "NT AUTHORITY\\SYSTEM"
  },
  "message": "Process Tampering:\r\nRuleName: -\r\nUtcTime: 2026-06-13 13:41:19.666\r\nProcessGuid: {00000000-0000-0000-0000-000000000000}\r\nProcessId: 604\r\nImage: <unknown process>\r\nType: Image is replaced\r\nUser: NT AUTHORITY\\SYSTEM"
}

Community Notes #

Process tampering, detects process herpaderping.

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

References #

Event ID 26: FileDeleteDetected (File Delete logged)

#
Channel
Operational
Level
Informational
Collection Priority
Recommended (JSCU-NL)
Task
File Delete logged (rule: FileDeleteDetected)
Opcode
Info

Description

A file was deleted.

Message #

File Delete logged:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
User: %5
Image: %6
TargetFilename: %7
Hashes: %8
IsExecutable: %9

Fields #

NameDescription
RuleName UnicodeStringCustom tag mapped to event, i.e. ATT&CK technique ID
UtcTime UnicodeStringTime in UTC when event was created
ProcessGuid GUIDProcess GUID of the process that deleted the file
ProcessId UInt32Process ID used by the OS to identify the process that deleted the file
User UnicodeStringName of the account who deleted the file.
Image UnicodeStringFile path of the process that deleted the file
TargetFilename UnicodeStringFull path name of the deleted file
Hashes UnicodeStringHashes captured by the Sysmon driver of the deleted file
IsExecutable BooleanWhether the deleted file is a PE executable

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 26,
    "version": 5,
    "level": 4,
    "task": 26,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T14:09:29.6982228+00:00",
    "event_record_id": 17612805,
    "correlation": {},
    "execution": {
      "process_id": 4080,
      "thread_id": 5392
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-13 14:09:29.694",
    "ProcessGuid": "{8a99384c-e971-6a2c-b200-000000001000}",
    "ProcessId": "6816",
    "User": "cell-c\\domainadmin",
    "Image": "C:\\Windows\\Explorer.EXE",
    "TargetFilename": "C:\\Users\\domainadmin\\AppData\\Roaming\\Microsoft\\Windows\\Themes\\CachedFiles\\CachedImage_1024_768_POS1.jpg",
    "Hashes": "SHA1=45418D43C67E2CEE415B678094EABC2A7D9FF2E4,MD5=210CC081ECEF04E020E21D53341EE954,SHA256=4F3BA3A9948CDDF013F02C82832BE6CE9203B2E874D9675BAEF3F9026C3B266F,IMPHASH=00000000000000000000000000000000",
    "IsExecutable": "false"
  },
  "message": "File Delete logged:\r\nRuleName: -\r\nUtcTime: 2026-06-13 14:09:29.694\r\nProcessGuid: {8a99384c-e971-6a2c-b200-000000001000}\r\nProcessId: 6816\r\nUser: cell-c\\domainadmin\r\nImage: C:\\Windows\\Explorer.EXE\r\nTargetFilename: C:\\Users\\domainadmin\\AppData\\Roaming\\Microsoft\\Windows\\Themes\\CachedFiles\\CachedImage_1024_768_POS1.jpg\r\nHashes: SHA1=45418D43C67E2CEE415B678094EABC2A7D9FF2E4,MD5=210CC081ECEF04E020E21D53341EE954,SHA256=4F3BA3A9948CDDF013F02C82832BE6CE9203B2E874D9675BAEF3F9026C3B266F,IMPHASH=00000000000000000000000000000000\r\nIsExecutable: false"
}

Detection Patterns #

Show All Detection Patterns

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Hashes[0]eqsha2563 ruleskusto
TargetFilenameends_with:zone.identifier3 rulessigma, splunk
TargetFilenameends_with.log2 rulessigma
event.typeeqdeletion3 ruleselastic
EventTypeeqFileCreated2 ruleskusto
Hashesis_not_null2 ruleskusto
ObservableKeycontainsfile:hashes2 ruleskusto
ObservableValueis_not_null2 ruleskusto
countge1002 rulessplunk
ActionTypeeqFileCreated1 rulekusto
Anomaliesgt01 rulekusto
FilePathcontainsaccount details1 rulekusto
FilePathcontainsbank account1 rulekusto
FilePathcontainsbank details1 rulekusto
FilePathcontainsbank statement1 rulekusto

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

References #

Event ID 27: FileBlockExecutable

#
Channel
Operational
Level
Informational
Task
File Block Executable (rule: FileBlockExecutable)
Opcode
Info

Description

This event is generated when Sysmon detects and blocks the creation of executable files.

Message #

File Block Executable:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
User: %5
Image: %6
TargetFilename: %7
Hashes: %8

Fields #

NameDescription
RuleName UnicodeString → string
UtcTime UnicodeString → string
ProcessGuid GUID → GUID
ProcessId UInt32 → PID
User UnicodeString → string
Image UnicodeString → string
TargetFilename UnicodeString → string
Hashes UnicodeString → string

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 27,
    "version": 5,
    "level": 4,
    "task": 27,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2022-08-29T04:43:48.128507Z",
    "event_record_id": 1341,
    "correlation": {},
    "execution": {
      "process_id": 2060,
      "thread_id": 7132
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "DESKTOP-VQBONAV",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "ImageBlock",
    "UtcTime": "2022-08-29 04:43:48.117",
    "ProcessGuid": "3E153517-4404-630C-0003-000000000400",
    "ProcessId": 8636,
    "User": "DESKTOP-VQBONAV\\user",
    "Image": "C:\\Windows\\system32\\certutil.exe",
    "TargetFilename": "C:\\Users\\user\\AppData\\LocalLow\\Microsoft\\CryptnetUrlCache\\Content\\02E7958E9A9619FDA0A027756E601291",
    "Hashes": "MD5=E112A827FAB9F8378C76040187A6F336,SHA256=ED369187681A62247E38D930320F1CD771756D0B7B67072D8EC655EF99E14AEB,IMPHASH=8EEAA9499666119D13B3F44ECD77A729"
  }
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

References #

Event ID 28: FileBlockShredding

#
Channel
Operational
Level
Informational
Task
File Block Shredding (rule: FileBlockShredding)
Opcode
Info

Description

This event is generated when Sysmon detects and blocks file shredding.

Message #

File Block Shredding:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
User: %5
Image: %6
TargetFilename: %7
Hashes: %8
IsExecutable: %9

Fields #

NameDescription
RuleName UnicodeString → string
UtcTime UnicodeString → string
ProcessGuid GUID → GUID
ProcessId UInt32 → PID
User UnicodeString → string
Image UnicodeString → string
TargetFilename UnicodeString → string
Hashes UnicodeString → string
IsExecutable Boolean → boolean

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 28,
    "version": 5,
    "level": 4,
    "task": 28,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-03-12T03:06:00.105995+00:00",
    "event_record_id": 36714962,
    "correlation": {},
    "execution": {
      "process_id": 3860,
      "thread_id": 5148
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "LAB-WIN11",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-03-12 03:06:00.101",
    "ProcessGuid": "3792AB3B-0B4D-69B1-4300-000000000F00",
    "ProcessId": 3544,
    "User": "NT AUTHORITY\\LOCAL SERVICE",
    "Image": "C:\\Windows\\System32\\svchost.exe",
    "TargetFilename": "C:\\Windows\\System32\\sru\\SRU.log",
    "Hashes": "SHA1=1ADC95BEBE9EEA8C112D40CD04AB7A8D75C4F961,MD5=FCD6BCB56C1689FCEF28B57C22475BAD,SHA256=DE2F256064A0AF797747C2B97505DC0B9F3DF0DE4F489EAC731C23AE9CA9CC31,IMPHASH=00000000000000000000000000000000",
    "IsExecutable": false
  },
  "message": ""
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

References #

Event ID 29: FileExecutableDetected

#
Channel
Operational
Level
Informational
Task
File Executable Detected (rule: FileExecutableDetected)
Opcode
Info

Description

This event is generated when Sysmon detects the creation of a new executable file.

Message #

File Executable Detected:
RuleName: %1
UtcTime: %2
ProcessGuid: %3
ProcessId: %4
User: %5
Image: %6
TargetFilename: %7
Hashes: %8

Fields #

NameDescriptionRules
RuleName UnicodeString → string
UtcTime UnicodeString → string
ProcessGuid GUID → GUID
ProcessId UInt32 → PID
User UnicodeString → string
Image UnicodeString → string
TargetFilename UnicodeString → string1 detection rule
Hashes UnicodeString → string

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "5770385F-C22A-43E0-BF4C-06F5698FFBD9",
    "event_source_name": "",
    "event_id": 29,
    "version": 5,
    "level": 4,
    "task": 29,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-03-13T19:59:50.724328+00:00",
    "event_record_id": 25592993,
    "correlation": {},
    "execution": {
      "process_id": 3516,
      "thread_id": 4964
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "LAB-WIN11.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-03-13 19:59:50.723",
    "ProcessGuid": "3792AB3B-6CAF-69B4-C304-000000000800",
    "ProcessId": 6332,
    "User": "NT AUTHORITY\\SYSTEM",
    "Image": "C:\\Windows\\winsxs\\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.378_none_6b5c1260907d1384\\TiWorker.exe",
    "TargetFilename": "C:\\Windows\\WinSxS\\Temp\\InFlight\\4d85a1f323b3dc0131020000bc18500b\\amd64_hyperv-compute-containerdiagnosticstool_31bf3856ad364e35_10.0.22621.1_none_e8f6dc1e2b2810c4\\hcsdiag.exe",
    "Hashes": "SHA1=4151B8801065408E851608F5F586E83F841DDF73,MD5=5CDE58E943D06BF77B4595CF917E4BD6,SHA256=148B44E4D5251D533F66EB2352AE396DB612AE926703682C8CD271ADC8A8B03A,IMPHASH=BC0760AED3654197B70538C4350C093A"
  },
  "message": ""
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
TargetFilenameends_with.sed1 rulesigma

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

  • Potentially Suspicious Self Extraction Directive File Created source medium: Detects the creation of a binary file with the ".sed" extension. The ".sed" extension stand for Self Extraction Directive files. These files are used by the "iexpress.exe" utility in order to create self extracting packages. Attackers were seen abusing this utility and creating PE files with embedded ".sed" entries. Usually ".sed" files are simple ini files and not PE binaries.T1218
  • Sysmon File Executable Creation Detected source medium: Triggers on any Sysmon "FileExecutableDetected" event, which triggers every time a PE that is monitored by the config is created.

Splunk # view in coverage

References #

Event ID 255: Error report: UtcTime: UtcTime ID: ID Description: Description.

#
Channel
Operational
Level
Error
Collection Priority
Recommended (JSCU-NL)
Task
Error report
Opcode
Info

Description

This event is generated when an **error occurred within Sysmon**. They can happen if the system is under heavy load and certain tasks could not be performed or a bug exists in the Sysmon service.

Message #

Error report:
UtcTime: %1
ID: %2
Description: %3

Fields #

NameDescriptionRules
UtcTime UnicodeString
ID UnicodeString
Description UnicodeString8 detection rules

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Sysmon",
    "guid": "{5770385F-C22A-43E0-BF4C-06F5698FFBD9}",
    "event_source_name": "",
    "event_id": 255,
    "version": 3,
    "level": 2,
    "task": 255,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-06-13T13:41:07.6428879+00:00",
    "event_record_id": 6120904,
    "correlation": {},
    "execution": {
      "process_id": 3720,
      "thread_id": 5400
    },
    "channel": "Microsoft-Windows-Sysmon/Operational",
    "computer": "telemetry-DC-d.cell-d.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "UtcTime": "2026-06-13 13:41:07.630",
    "ID": "GetConfigurationOptions",
    "Description": "Failed to open service configuration with error 92 - Last error: The media is write protected.\n"
  },
  "message": "Error report:\r\nUtcTime: 2026-06-13 13:41:07.630\r\nID: GetConfigurationOptions\r\nDescription: Failed to open service configuration with error 92 - Last error: The media is write protected.\r\n"
}

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma # view in coverage

References #

Provenance

ETW provider GUID {5770385F-C22A-43E0-BF4C-06F5698FFBD9}

Defined in Sysmon64.exe, which carries the event manifest.

  • WS2022-20348.4893, sample captured from a live trace, binary version 15.15, captured 2026-06-02 — Manifest XML pack, 1.9 MB
  • WS2022-20348.4893, schema read from the registered manifest, binary version 15.15, captured 2026-06-02 — Manifest XML pack, 1.9 MB