/
sc_exe_manipulating_windows_services.yml
77 lines (77 loc) · 2.94 KB
/
sc_exe_manipulating_windows_services.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
name: Sc exe Manipulating Windows Services
id: f0c693d8-2a89-4ce7-80b4-98fea4c3ea6d
version: 4
date: '2020-07-21'
author: Rico Valdez, Splunk
status: production
type: TTP
description: This search looks for arguments to sc.exe indicating the creation or
modification of a Windows service.
data_source:
- Sysmon EventID 1
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 = sc.exe (Processes.process="* create *" OR Processes.process="*
config *") by Processes.process_name Processes.parent_process_name Processes.dest
Processes.user | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` | `sc_exe_manipulating_windows_services_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: Using sc.exe to manipulate Windows services is uncommon. However,
there may be legitimate instances of this behavior. It is important to validate
and investigate as appropriate.
references:
- https://www.secureworks.com/blog/drokbk-malware-uses-github-as-dead-drop-resolver
tags:
analytic_story:
- Windows Service Abuse
- DHS Report TA18-074A
- Orangeworm Attack Group
- Windows Persistence Techniques
- Disabling Security Tools
- NOBELIUM Group
- Azorult
- Windows Drivers
asset_type: Endpoint
confidence: 80
impact: 70
message: A sc process $process_name$ with commandline $process$ to create of configure
services in host $dest$
mitre_attack_id:
- T1543.003
- T1543
observable:
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.process_name
- Processes.process
- Processes.parent_process_name
- Processes.dest
- Processes.user
risk_score: 56
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1543.003/atomic_red_team/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog