Files
splunk-security_content/detections/endpoint/windows_remote_create_service.yml
Bhavin Patel 7fda817c23 Release 4.19.0
2024-01-10 17:21:34 +00:00

89 lines
3.4 KiB
YAML

name: Windows Remote Create Service
id: 0dc44d03-8c00-482d-ba7c-796ba7ab18c9
version: 1
date: '2023-03-20'
author: Michael Haag, Splunk
status: production
type: Anomaly
data_source:
- Sysmon Event ID 1
description: This analytic identifies an endpoint that remotely connects to another
endpoint to create a new service using sc.exe. On the remote endpoint, the new service
will be created and this action will trigger the creation of EventCode 7045 along
with all the resulting service information.
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.process_name=sc.exe
Processes.process IN ("*create*") Processes.process="*\\\\*" by Processes.dest
Processes.user Processes.parent_process_name Processes.process_name Processes.original_file_name
Processes.process Processes.process_id Processes.parent_process_id | `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_remote_create_service_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: Note that false positives may occur, and filtering may be necessary,
especially when it comes to remote service creation by administrators or software
management utilities.
references:
- https://attack.mitre.org/techniques/T1543/003/
tags:
analytic_story:
- Active Directory Lateral Movement
- CISA AA23-347A
asset_type: Endpoint
confidence: 50
impact: 50
message: An instance of $parent_process_name$ spawning $process_name$ was identified
on endpoint $dest$ by user $user$ attempting to create a remote service.
mitre_attack_id:
- T1543
- T1543.003
observable:
- name: user
type: User
role:
- Victim
- name: dest
type: Hostname
role:
- Victim
- name: parent_process_name
type: Process
role:
- Parent Process
- name: process_name
type: Process
role:
- Child Process
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.parent_process_name
- Processes.parent_process
- Processes.original_file_name
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_path
- Processes.process_path
- Processes.parent_process_id
risk_score: 25
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/remote_service_create_windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog
update_timestamp: true