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

Branch was auto-updated.

Browse Source
This commit is contained in:
github-actions[bot]
2021-05-05 20:05:31 +00:00
committed by GitHub
parent 414763e282 503e6acd96
commit 1f6fd4d2aa
2 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
detections/endpoint/shedule_task_with_http_command_arguments.yml → detections/endpoint/schedule_task_with_http_command_arguments.yml
+11 -11
View File
@@ -1,4 +1,4 @@
name: Shedule Task with HTTP Command Arguments
name: Schedule Task with HTTP Command Arguments
id: 523c2684-a101-11eb-916b-acde48001122
version: 1
date: '2021-04-19'
@@ -10,20 +10,20 @@ description: The following query utilizes Windows Security EventCode 4698, `A sc
task was created`, to identify suspicious tasks registered on Windows either via
schtasks.exe OR TaskService with an arguments "HTTP" string that are unique entry
of malware or attack that uses lolbin to download other file or payload to the infected
machine.\ The search will return the first time and last time the task was registered,
machine. The search will return the first time and last time the task was registered,
as well as the `Command` to be executed, `Task Name`, `Author`, `Enabled`, and whether
it is `Hidden` or not.\ schtasks.exe is natively found in `C:\Windows\system32`
and `C:\Windows\syswow64`.\ The following DLL(s) are loaded when schtasks.exe or
TaskService is launched -`taskschd.dll`. If found loaded by another process, it
is possible a scheduled task is being registered within that process context in
memory.\ Upon triage, identify the task scheduled source. Was it schtasks.exe or
via TaskService? Review the job created and the Command to be executed. Capture
any artifacts on disk and review. Identify any parallel processes within the same
timeframe to identify source.'
it is `Hidden` or not. schtasks.exe is natively found in `C:\Windows\system32` and
`C:\Windows\syswow64`. The following DLL(s) are loaded when schtasks.exe or TaskService
is launched -`taskschd.dll`. If found loaded by another process, it is possible
a scheduled task is being registered within that process context in memory. Upon
triage, identify the task scheduled source. Was it schtasks.exe or via TaskService?
Review the job created and the Command to be executed. Capture any artifacts on
disk and review. Identify any parallel processes within the same timeframe to identify
source.'
search: '`wineventlog_security` EventCode=4698 | xmlkv Message| search Arguments IN
("*http*") | stats count min(_time) as firstTime max(_time) as lastTime by dest,
Task_Name, Command, Author, Enabled, Hidden, Arguments | `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` | `shedule_task_with_http_command_arguments_filter`'
| `security_content_ctime(lastTime)` | `schedule_task_with_http_command_arguments_filter`'
how_to_implement: To successfully implement this search, you need to be ingesting
logs with the task schedule (Exa. Security Log EventCode 4698) endpoints. Tune and
filter known instances of Task schedule used in your environment.
tests/endpoint/shedule_task_with_http_command_arguments.test.yml → tests/endpoint/schedule_task_with_http_command_arguments.test.yml
+3 -3
View File
@@ -1,7 +1,7 @@
name: Shedule Task with HTTP Command Arguments Unit Test
name: Schedule Task with HTTP Command Arguments Unit Test
tests:
- name: Shedule Task with HTTP Command Arguments
file: endpoint/shedule_task_with_http_command_arguments.yml
- name: Schedule Task with HTTP Command Arguments
file: endpoint/schedule_task_with_http_command_arguments.yml
pass_condition: '| stats count | where count > 0'
earliest_time: '-24h'
latest_time: 'now'