BITS Job Persistence


Description

The following analytic detects BITSAdmin configuring a non-NULL notification program with /SetNotifyCmdLine. Adversaries can use a BITS job callback to execute a payload when a transfer completes or enters an error state and retain execution across sessions.

Query · spl

| tstats `security_content_summariesonly`
  count min(_time) as firstTime
        max(_time) as lastTime

FROM datamodel=Endpoint.Processes WHERE

`process_bitsadmin`
Processes.process="*/setnotifycmdline*"

BY Processes.action Processes.dest Processes.original_file_name
   Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
   Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
   Processes.process Processes.process_exec Processes.process_guid
   Processes.process_hash Processes.process_id Processes.process_integrity_level
   Processes.process_name Processes.process_path Processes.user
   Processes.user_id Processes.vendor_product

| `drop_dm_object_name(Processes)`

| rex field=process "(?i)(?:^|\s)/setnotifycmdline[ \t]+(?<bits_job>\"[^\"]*\"|[^\s\"]+)[ \t]+(?<bits_notify_program>\"[^\"]*\"|[^\s\"]+)(?:[ \t]+(?<bits_notify_parameters>[^\r\n]*))?$"

| where isnotnull(bits_notify_program)
        AND
        NOT match(bits_notify_program, "(?i)^(?:\"\"|\"?NULL\"?)$")

| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `bits_job_persistence_filter`

Implementation guide

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

  • Legitimate applications and administrators can configure BITS notification programs. Validate the callback program and job purpose and tune the filter macro using the program, parent process and account together. Setting the callback to NULL clears it and is excluded. Custom headers and ordinary job management are not included.

Analyst notes

Known false positives: Legitimate applications and administrators can configure BITS notification programs. Validate the callback program and job purpose and tune the filter macro using the program, parent process and account together. Setting the callback to NULL clears it and is excluded. Custom headers and ordinary job management are not included.

Raw source BITS Job Persistence · SPL
Esc
Published by splunk/security_content ↗, licensed under Apache 2.0 ↗. Reproduced here unmodified.
name: BITS Job Persistence
id: e97a5ffe-90bf-11eb-928a-acde48001122
version: 14
creation_date: '2021-03-30'
modification_date: '2026-11-10'
author: Michael Haag, Nasreddine Bencherchali, Splunk
status: production
type: Anomaly
description: |-
    The following analytic detects BITSAdmin configuring a non-NULL notification program with /SetNotifyCmdLine.
    Adversaries can use a BITS job callback to execute a payload when a transfer completes or enters an error state and retain execution across sessions.
data_source:
    - Sysmon EventID 1
    - Windows Event Log Security 4688
    - CrowdStrike ProcessRollup2
search: |-
    | tstats `security_content_summariesonly`
      count min(_time) as firstTime
            max(_time) as lastTime

    FROM datamodel=Endpoint.Processes WHERE

    `process_bitsadmin`
    Processes.process="*/setnotifycmdline*"

    BY Processes.action Processes.dest Processes.original_file_name
       Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
       Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
       Processes.process Processes.process_exec Processes.process_guid
       Processes.process_hash Processes.process_id Processes.process_integrity_level
       Processes.process_name Processes.process_path Processes.user
       Processes.user_id Processes.vendor_product

    | `drop_dm_object_name(Processes)`

    | rex field=process "(?i)(?:^|\s)/setnotifycmdline[ \t]+(?<bits_job>\"[^\"]*\"|[^\s\"]+)[ \t]+(?<bits_notify_program>\"[^\"]*\"|[^\s\"]+)(?:[ \t]+(?<bits_notify_parameters>[^\r\n]*))?$"

    | where isnotnull(bits_notify_program)
            AND
            NOT match(bits_notify_program, "(?i)^(?:\"\"|\"?NULL\"?)$")

    | `security_content_ctime(firstTime)`
    | `security_content_ctime(lastTime)`
    | `bits_job_persistence_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: |-
    Legitimate applications and administrators can configure BITS notification programs.
    Validate the callback program and job purpose and tune the filter macro using the program, parent process and account together.
    Setting the callback to NULL clears it and is excluded. Custom headers and ordinary job management are not
    included.
references:
    - https://attack.mitre.org/techniques/T1197/
    - https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bitsadmin
    - https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1197/T1197.md#atomic-test-3---persist-download--execute
    - https://lolbas-project.github.io/lolbas/Binaries/Bitsadmin/
    - https://github.com/redcanaryco/atomic-red-team/blob/388942adbd9641f4dfdcf079d7efe9a75ec0ac43/atomics/T1197/T1197.yaml#L51
    - https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/bitsadmin-setnotifycmdline
drilldown_searches:
    - name: View the detection results for - "$user$" and "$dest$"
      search: '%original_detection_search% | search  user = "$user$" dest = "$dest$"'
      earliest_offset: $info_min_time$
      latest_offset: $info_max_time$
    - name: View risk events for the last 7 days for - "$user$" and "$dest$"
      search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$", "$dest$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
      earliest_offset: 7d
      latest_offset: "0"
intermediate_findings:
    entities:
        - field: dest
          type: system
          score: 20
          message: An instance of [$parent_process_name$] spawning [$process_name$] was identified on endpoint [$dest$] by user [$user$] attempting to configure a BITS notification program with command line [$process$].
threat_objects:
    - field: parent_process_name
      type: parent_process_name
    - field: process_name
      type: process_name
analytic_story:
    - BITS Jobs
    - Living Off The Land
asset_type: Endpoint
atomic_guid:
    - 62a06ec5-5754-47d2-bcfc-123d8314c6ae
mitre_attack_id:
    - T1197
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: endpoint
security_domain: endpoint
tests:
    - name: True Positive Test
      attack_data:
        - data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1197/atomic_red_team/windows-sysmon.log
          source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
          sourcetype: XmlWinEventLog
      test_type: unit
    - name: True Positive Test
      attack_data:
        - data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1197/atomic_red_team/crowdstrike_falcon.log
          source: crowdstrike
          sourcetype: crowdstrike:events:sensor
      test_type: unit

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.