FortiSIEM Rules

Windows: BITS Transfer Job Download From File Sharing Domains

Rule ID

PH_Rule_SIGMA_1112

Default Status

Enabled

Description

Detects BITS transfer job downloading files from a file sharing domain. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/bits_client/win_bits_client_new_transfer_via_file_sharing_domains.yml

Severity

7

Category

Security

MITRE ATT&CK® Tactics

Defense Evasion

Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.

https://attack.mitre.org/tactics/TA0005

MITRE ATT&CK® Techniques


T1197

BITS Jobs

Adversaries may abuse Windows Background Intelligent Transfer Service (BITS) jobs to persistently execute or clean up after malicious payloads. BITS is a low-bandwidth, asynchronous file transfer mechanism exposed through Component Object Model. BITS is commonly used by updaters, messengers, and other applications preferred to operate in the background. The interface to create and manage BITS jobs is accessible through PowerShell. Adversaries may abuse BITS to download, execute, and even clean up after running malicious code. BITS upload functionalities can also be used to perform Exfiltration Over Alternative Protocol.

https://attack.mitre.org/techniques/T1197

Impacts

Server

Data Source

Windows Security log via OMI or FortiSIEM Agent

Detection

Correlation

Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.

Filter

SubPattern Definitions

SubPattern Name: Filter

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType REGEXP "Win-.*-16403[^\d]*" AND targetName  REGEXP ".*\.ghostbin\.co/.*|.*\.hastebin\.com.*|.*\.paste\.ee.*|.*anonfiles\.com.*|.*cdn\.discordapp\.com/attachments/.*|.*ddns\.net.*|.*gist\.githubusercontent\.com.*|.*mediafire\.com.*|.*mega\.nz.*|.*paste\.ee.*|.*pastebin\.com.*|.*pastebin\.pl.*|.*pastetext\.net.*|.*privatlab\.com.*|.*privatlab\.net.*|.*raw\.githubusercontent\.com.*|.*send\.exploit\.in.*|.*sendspace\.com.*|.*storage\.googleapis\.com.*|.*transfer\.sh.*|.*ufile\.io.*"

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

hostName,targetName

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern

hostName = Filter.hostName,
targetName = Filter.targetName