Try in Splunk Security Cloud

Description

The following analytic identifies the creation or modification of Image File Execution Options (IFEO) registry keys, detected via EventCode 3000 in the Application channel. This detection leverages Windows Event Logs to monitor for process names added to IFEO under specific registry paths. This activity is significant as it can indicate attempts to set traps for process monitoring or debugging, often used by attackers for persistence or evasion. If confirmed malicious, this could allow an attacker to execute arbitrary code or manipulate process behavior, leading to potential system compromise.

  • Type: Hunting

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-31
  • Author: Michael Haag, Splunk
  • ID: f7abfab9-12ea-44e8-8745-475f9ca6e0a4

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1546.012 Image File Execution Options Injection Privilege Escalation, Persistence
Kill Chain Phase
  • Exploitation
  • Installation
NIST
  • DE.AE
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6



`wineventlog_application` EventCode=3000 
| rename param1 AS "Process" param2 AS "Exit_Code" 
| stats count min(_time) as firstTime max(_time) as lastTime by Process Exit_Code dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_event_triggered_image_file_execution_options_injection_filter`

Macros

The SPL above uses the following Macros:

:information_source: windows_event_triggered_image_file_execution_options_injection_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • Process
  • Exit_Code
  • dest
  • EventCode

How To Implement

This analytic requires capturing the Windows Event Log Application channel in XML.

Known False Positives

False positives may be present and tuning will be required before turning into a TTP or notable.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
25.0 50 50 Windows eventcode 3000 triggered on $dest$ potentially indicating persistence or a monitoring of a process has occurred.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2