Detection rules › Splunk

Windows EventLog Recon Activity Using Log Query Utilities

Status
production
Severity
low
Group by
IntegrityLevel, command_line, computer_name, event_action, original_file_name, parent_command_line, parent_process_guid, parent_process_id, parent_process_name, process_guid, process_hash, process_id, process_name, user, user_id, vendor_product
Author
Nasreddine Bencherchali, Splunk
Source
github.com/splunk/security_content

This analytic detects EventLog reconnaissance activity using utilities such as wevtutil.exe, wmic.exe, PowerShell cmdlets like Get-WinEvent, or WMI queries targeting Win32_NTLogEvent. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and command-line arguments. These tools are often used by adversaries to extract usernames, IP addresses, session data, and event information for credential access or situational awareness during lateral movement. While these utilities are legitimate, execution with specific arguments or targeting sensitive logs like Security, PowerShell, or specific EventIDs (e.g., 4624, 4778) can indicate malicious intent. If confirmed malicious, this behavior could allow an attacker to extract sensitive info and potentially have leveraged access or move laterally.

MITRE ATT&CK coverage

TacticTechniques
DiscoveryT1654 Log Enumeration

Event coverage

Rule body splunk

name: Windows EventLog Recon Activity Using Log Query Utilities
id: dc167f8b-3f9d-4460-9c98-8b6e703fd628
version: 7
creation_date: '2025-04-24'
modification_date: '2026-05-13'
author: Nasreddine Bencherchali, Splunk
status: production
type: Anomaly
description: |
    This analytic detects EventLog reconnaissance activity using utilities such as `wevtutil.exe`, `wmic.exe`, PowerShell cmdlets like `Get-WinEvent`, or WMI queries targeting `Win32_NTLogEvent`. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and command-line arguments. These tools are often used by adversaries to extract usernames, IP addresses, session data, and event information for credential access or situational awareness during lateral movement. While these utilities are legitimate, execution with specific arguments or targeting sensitive logs like `Security`, `PowerShell`, or specific EventIDs (e.g., 4624, 4778) can indicate malicious intent. If confirmed malicious, this behavior could allow an attacker to extract sensitive info and potentially have leveraged access or move laterally.
data_source:
    - Sysmon EventID 1
    - Windows Event Log Security 4688
    - CrowdStrike ProcessRollup2
search: |
    | tstats `security_content_summariesonly` values(Processes.process) as process
      min(_time) as firstTime max(_time) as lastTime
      from datamodel=Endpoint.Processes
      where (
        (
          (
            Processes.process_name IN ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
            OR
            Processes.original_file_name IN ("PowerShell.EXE", "pwsh.dll", "powershell_ise.EXE")
          )
          Processes.process IN ("*Get-WinEvent*", "*Get-EventLog*", "*EventLogQuery*", "*.ReadEvent(*")
        )
        OR
        (
          (
            Processes.process_name = wevtutil.exe
            OR
            Processes.original_file_name = wevtutil.exe
          )
          Processes.process IN ("* qe *", "* query-events *")
        )
        OR
        (
          (
            Processes.process_name = wmic.exe
            OR
            Processes.original_file_name = wmic.exe
          )
          Processes.process IN ("*ntevent*")
        )
        OR
        (
          Processes.process="*Win32_NTLogEvent*"
          Processes.process="*EventCode*"
        )
        OR
        (
          Processes.process IN ("*PsLogList*", "*Eventquery*")
        )
      )
      by
        Processes.action Processes.dest Processes.original_file_name Processes.parent_process Processes.parent_process_exec
        Processes.parent_process_guid Processes.parent_process_id Processes.parent_process_name
        Processes.parent_process_path Processes.process Processes.process_exec Processes.process_guid
        Processes.process_hash Processes.process_id Processes.process_integrity_level Processes.process_name
        Processes.process_path Processes.user Processes.user_id Processes.vendor_product
    
    | `drop_dm_object_name(Processes)`
    | `security_content_ctime(firstTime)`
    | `security_content_ctime(lastTime)`
    | `windows_eventlog_recon_activity_using_log_query_utilities_filter`
how_to_implement: |
    The detection is based on data that originates from Endpoint Detection
    and Response (EDR) agents. These agents are designed to provide security-related
    telemetry from the endpoints where the agent is installed. To implement this search,
    you must ingest logs that contain the process GUID, process name, and parent process.
    Additionally, you must ingest complete command-line executions. These logs must
    be processed using the appropriate Splunk Technology Add-ons that are specific to
    the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
    data model. Use the Splunk Common Information Model (CIM) to normalize the field
    names and speed up the data modeling process.
known_false_positives: |
    System administrators or monitoring tools may legitimately use these utilities to gather logs for troubleshooting or auditing. Filter known admin behavior or monitoring solutions as needed.
references:
    - http://blog.talosintelligence.com/2022/09/lazarus-three-rats.html
    - https://thedfirreport.com/2023/10/30/netsupport-intrusion-results-in-domain-compromise/
    - https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-144a
    - https://www.group-ib.com/blog/apt41-world-tour-2021/
    - https://labs.withsecure.com/content/dam/labs/docs/f-secureLABS-tlp-white-lazarus-threat-intel-report2.pdf
    - https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.diagnostics/get-winevent
    - https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-eventlog
    - https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/wevtutil
drilldown_searches:
    - name: View the detection results for - "$dest$" and "$user$"
      search: '%original_detection_search% | search  dest = "$dest$" user = "$user$"'
      earliest_offset: $info_min_time$
      latest_offset: $info_max_time$
    - name: View risk events for the last 7 days for - "$dest$" and "$user$"
      search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$dest$", "$user$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
      earliest_offset: 7d
      latest_offset: "0"
intermediate_findings:
    entities:
        - field: dest
          type: system
          score: 20
          message: Suspicious log query $process$ command was run on $dest$ by $user$
        - field: user
          type: user
          score: 20
          message: Suspicious log query $process$ command was run on $dest$ by $user$
analytic_story:
    - Windows Discovery Techniques
    - BlankGrabber Stealer
asset_type: Endpoint
mitre_attack_id:
    - T1654
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: endpoint
security_domain: endpoint
tests:
    - name: True Positive Test
      attack_data:
        - data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1654/eventlog_enumeration/eventlog_enumeration.log
          source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
          sourcetype: XmlWinEventLog
      test_type: unit

Stages and Predicates

Stage 1: tstats

| tstats `security_content_summariesonly` values(Processes.process) as process
  min(_time) as firstTime max(_time) as lastTime
  from datamodel=Endpoint.Processes
  where (
    (
      (
        Processes.process_name IN ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
        OR
        Processes.original_file_name IN ("PowerShell.EXE", "pwsh.dll", "powershell_ise.EXE")
      )
      Processes.process IN ("*Get-WinEvent*", "*Get-EventLog*", "*EventLogQuery*", "*.ReadEvent(*")
    )
    OR
    (
      (
        Processes.process_name = wevtutil.exe
        OR
        Processes.original_file_name = wevtutil.exe
      )
      Processes.process IN ("* qe *", "* query-events *")
    )
    OR
    (
      (
        Processes.process_name = wmic.exe
        OR
        Processes.original_file_name = wmic.exe
      )
      Processes.process IN ("*ntevent*")
    )
    OR
    (
      Processes.process="*Win32_NTLogEvent*"
      Processes.process="*EventCode*"
    )
    OR
    (
      Processes.process IN ("*PsLogList*", "*Eventquery*")
    )
  )
  by
    Processes.action Processes.dest Processes.original_file_name Processes.parent_process Processes.parent_process_exec
    Processes.parent_process_guid Processes.parent_process_id Processes.parent_process_name
    Processes.parent_process_path Processes.process Processes.process_exec Processes.process_guid
    Processes.process_hash Processes.process_id Processes.process_integrity_level Processes.process_name
    Processes.process_path Processes.user Processes.user_id Processes.vendor_product

Stage 2: search

| `drop_dm_object_name(Processes)`

Stage 3: search

| `security_content_ctime(firstTime)`

Stage 4: search

| `security_content_ctime(lastTime)`

Stage 5: search

| `windows_eventlog_recon_activity_using_log_query_utilities_filter`

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
Processes.original_file_nameeq
  • "wevtutil.exe" corpus 7 (sigma 5, elastic 1, splunk 1)
  • "wmic.exe" corpus 61 (sigma 36, splunk 18, elastic 7)
Processes.original_file_namein
  • "PowerShell.EXE" corpus 120 (sigma 84, splunk 30, elastic 6)
  • "powershell_ise.EXE" corpus 51 (splunk 30, sigma 18, elastic 3)
  • "pwsh.dll" corpus 112 (sigma 79, splunk 30, elastic 3)
Processes.processeq
  • "*EventCode*"
  • "*Win32_NTLogEvent*" corpus 3 (sigma 2, splunk 1)
Processes.processin
  • "* qe *" corpus 2 (sigma 2)
  • "* query-events *" corpus 2 (sigma 2)
  • "*.ReadEvent(*"
  • "*EventLogQuery*"
  • "*Eventquery*"
  • "*Get-EventLog*"
  • "*Get-WinEvent*"
  • "*PsLogList*"
  • "*ntevent*"
Processes.process_nameeq
  • "wevtutil.exe" corpus 8 (elastic 4, splunk 4)
  • "wmic.exe" corpus 47 (splunk 27, elastic 20)
Processes.process_namein
  • "powershell.exe" corpus 104 (elastic 60, splunk 44)
  • "powershell_ise.exe" corpus 50 (splunk 29, elastic 21)
  • "pwsh.exe" corpus 62 (elastic 33, splunk 29)