Try in Splunk Security Cloud

Description

The following query identifies Microsoft Background Intelligent Transfer Service utility bitsadmin.exe scheduling a BITS job to persist on an endpoint. The query identifies the parameters used to create, resume or add a file to a BITS job. Typically seen combined in a oneliner or ran in sequence. If identified, review the BITS job created and capture any files written to disk. It is possible for BITS to be used to upload files and this may require further network data analysis to identify. You can use bitsadmin /list /verbose to list out the jobs during investigation.

  • Type: TTP

  • Product: Splunk Behavioral Analytics

  • Last Updated: 2022-02-15
  • Author: Michael Haag, Splunk
  • ID: 1e25e97a-8ea4-11ec-9767-acde48001122

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1197 BITS Jobs Defense Evasion, Persistence
Kill Chain Phase
  • Exploitation
  • Installation
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22



 
| from read_ba_enriched_events() 
| eval timestamp = ucast(map_get(input_event,"time"),"long", null) 
| eval metadata = ucast(map_get(input_event, "metadata"),"map<string, any>", null) 
| eval metadata_uid = ucast(map_get(metadata, "uid"),"string", null) 
| eval process=ucast(map_get(input_event,"process"), "map<string, any>", null) 
| eval process_pid=ucast(map_get(process,"pid"), "string", null) 
| eval process_file=ucast(map_get(process,"file"), "map<string, any>", null) 
| eval process_file_path=ucast(map_get(process_file,"path"), "string", null) 
| eval process_file_name=ucast(map_get(process_file,"name"), "string", null) 
| eval process_cmd_line=ucast(map_get(process,"cmd_line"), "string", null) 
| eval actor=ucast(map_get(input_event,"actor"), "map<string, any>", null) 
| eval actor_user=ucast(map_get(actor,"user"), "map<string, any>", null) 
| eval actor_user_name=ucast(map_get(actor_user,"name"), "string", null) 
| eval actor_process=ucast(map_get(actor,"process"), "map<string, any>", null) 
| eval actor_process_pid=ucast(map_get(actor_process,"pid"), "string", null) 
| eval actor_process_file=ucast(map_get(actor_process,"file"), "map<string, any>", null) 
| eval actor_process_file_path=ucast(map_get(actor_process_file,"path"), "string", null) 
| eval actor_process_file_name=ucast(map_get(actor_process_file,"name"), "string", null) 
| eval device=ucast(map_get(input_event,"device"), "map<string, any>", null) 
| eval device_hostname=ucast(map_get(device,"hostname"), "string", null) 
| where (like(process_cmd_line, "%resume%") OR like(process_cmd_line, "%setcustomheaders%") OR like(process_cmd_line, "%setminretrydelay%") OR like(process_cmd_line, "%setnotifycmdline%") OR like(process_cmd_line, "%setnotifyflags%") OR like(process_cmd_line, "%addfile%") OR like(process_cmd_line, "%create%")) AND process_file_name="bitsadmin.exe" --finding_report--

Macros

The SPL above uses the following Macros:

:information_source: windows_bits_job_persistence_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • process.pid
  • process.file.path
  • process.file.name
  • process.cmd_line
  • actor.user.name
  • actor.process.pid
  • actor.process.file.path
  • actor.process.file.name
  • device.hostname

How To Implement

To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the Endpoint datamodel in the Processes node. In addition, confirm the latest CIM App 4.20 or higher is installed and the latest TA for the endpoint product.

Known False Positives

Limited false positives will be present. Typically, applications will use BitsAdmin.exe. Any filtering should be done based on command-line arguments (legitimate applications) or parent process.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
56.0 70 80 An instance of $parent_process_name$ spawning $process_name$ was identified on endpoint $dest$ by user $dest_user_id$ attempting to persist using BITS.

:information_source: 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

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

source | version: 1