splunk-security_content/docs/_posts/2021-11-22-services_lolbas_execution_process_spawn.md

title, excerpt, categories, last_modified_at, toc, toc_label, tags

title	excerpt	categories	last_modified_at	toc	toc_label	tags
Services LOLBAS Execution Process Spawn	Create or Modify System Process , Windows Service	Endpoint	2021-11-22	true		Create or Modify System Process Windows Service Persistence Privilege Escalation Persistence Privilege Escalation Splunk Enterprise Splunk Enterprise Security Splunk Cloud Endpoint

Try in Splunk Security Cloud{: .btn .btn--success}

Description

The following analytic identifies services.exe spawning a LOLBAS execution process. When adversaries execute code on remote endpoints abusing the Service Control Manager and creating a remote malicious service, the executed command is spawned as a child process of services.exe. The LOLBAS project documents Windows native binaries that can be abused by threat actors to perform tasks like executing malicious code. Looking for child processes of services.exe that are part of the LOLBAS project can help defenders identify lateral movement activity.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel: Endpoint- Datasource: Splunk Add-on for Sysmon
• Last Updated: 2021-11-22
• Author: Mauricio Velazco, Splunk
• ID: ba9e1954-4c04-11ec-8b74-3e22fbd008af

Annotations

ATT&CK

ID	Technique	Tactic
T1543	Create or Modify System Process	Persistence, Privilege Escalation

| T1543.003 | Windows Service | Persistence, Privilege Escalation |

Kill Chain Phase

• Exploitation

NIST

CIS20

CVE

Search

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where (Processes.parent_process_name=services.exe) (Processes.process_name IN ("Regsvcs.exe", "Ftp.exe", "OfflineScannerShell.exe", "Rasautou.exe", "Schtasks.exe", "Xwizard.exe", "Dllhost.exe", "Pnputil.exe", "Atbroker.exe", "Pcwrun.exe", "Ttdinject.exe","Mshta.exe", "Bitsadmin.exe", "Certoc.exe", "Ieexec.exe", "Microsoft.Workflow.Compiler.exe", "Runscripthelper.exe", "Forfiles.exe", "Msbuild.exe", "Register-cimprovider.exe", "Tttracer.exe", "Ie4uinit.exe", "Bash.exe", "Hh.exe", "SettingSyncHost.exe", "Cmstp.exe", "Mmc.exe", "Stordiag.exe", "Scriptrunner.exe", "Odbcconf.exe", "Extexport.exe", "Msdt.exe", "WorkFolders.exe", "Diskshadow.exe", "Mavinject.exe", "Regasm.exe", "Gpscript.exe", "Rundll32.exe", "Regsvr32.exe", "Msiexec.exe", "Wuauclt.exe", "Presentationhost.exe", "Wmic.exe", "Runonce.exe", "Syncappvpublishingserver.exe", "Verclsid.exe", "Infdefaultinstall.exe", "Explorer.exe", "Installutil.exe", "Netsh.exe", "Wab.exe", "Dnscmd.exe", "At.exe", "Pcalua.exe", "Msconfig.exe")) by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `services_lolbas_execution_process_spawn_filter`

Macros

The SPL above uses the following Macros:

• security_content_ctime
• security_content_summariesonly

ℹ️ services_lolbas_execution_process_spawn_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

• _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

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints.

Known False Positives

Legitimate applications may trigger this behavior, filter as needed.

Associated Analytic story

• Active Directory Lateral Movement
• Living Off The Land

RBA

Risk Score	Impact	Confidence	Message
54.0	90	60	Services.exe spawned a LOLBAS process on $dest

ℹ️ The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

• https://attack.mitre.org/techniques/T1543/003/
• https://pentestlab.blog/2020/07/21/lateral-movement-services/
• https://lolbas-project.github.io/

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

• https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1543.003/lateral_movement_lolbas/windows-sysmon.log

source | version: 1