From c3653c14043a2a441ecc101ed2ede95f68229fef Mon Sep 17 00:00:00 2001
From: Michael Haag <5632822+MHaggis@users.noreply.github.com>
Date: Mon, 12 Sep 2022 07:57:53 -0600
Subject: [PATCH] test

---
 ...s_event_triggered_image_file_execution_options_injection.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/detections/endpoint/windows_event_triggered_image_file_execution_options_injection.yml b/detections/endpoint/windows_event_triggered_image_file_execution_options_injection.yml
index a1bbb9177e..38f54490fb 100644
--- a/detections/endpoint/windows_event_triggered_image_file_execution_options_injection.yml
+++ b/detections/endpoint/windows_event_triggered_image_file_execution_options_injection.yml
@@ -9,7 +9,7 @@ datamodel:
 description: The following hunting analytic identifies EventCode 3000 in Application channel indicating a process exit. This behavior is based on process names being added to the Image File Execution Options under HKLM \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ and \SOFTWARE\Microsoft\Windows NT\CurrentVersion\SilentProcessExit. Once these are set for a process, an eventcode 3000 will generate. 
   The example used is from Thinkst Canary where a CanaryToken is setup to monitor for a commonly abused living off the land binary (ex. Klist.exe) and generate an event when it occurs. This can be seen as settings traps to monitor for suspicious behavior.
   Monitor and tune this hunting analytic and setup traps across your organization and begin monitoring.
-search: '`wineventlog_application` EventCode=3000 
+search: 'source="XmlWinEventLog: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)`