admin/splunk-security_content
1
0
Fork 0
mirror of https://github.com/splunk/security_content synced 2026-06-08 17:32:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

space or tab, we'll never know

Browse Source
This commit is contained in:
Michael Haag
2022-09-12 08:18:30 -06:00
parent c3653c1404
commit 00a2a95961
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
detections/endpoint/windows_event_triggered_image_file_execution_options_injection.yml
+6 -6
View File
@@ -9,12 +9,12 @@ 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: '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)`
| `security_content_ctime(lastTime)`
| `windows_event_triggered_image_file_execution_options_injection_filter`'
search: '`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`'
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.
references: