Windows: PUA - Seatbelt Execution

Rule ID

PH_Rule_SIGMA_2472

Default Status

Enabled

Description

Detects the execution of the PUA/Recon tool Seatbelt via PE information of command line parameters. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_pua_seatbelt.yml

Severity

MITRE ATT&CK® Tactics

Discovery

Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.

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

MITRE ATT&CK® Techniques

T1526

Cloud Service Discovery

An adversary may attempt to enumerate the cloud services running on a system after gaining access. Many services exist throughout the various cloud providers and can include Continuous Integration and Continuous Delivery (CI/CD), Lambda Functions, Azure AD, etc. Adversaries may attempt to discover information about the services enabled throughout the environment. Azure tools and APIs, such as the Azure AD Graph API and Azure Resource Manager API, can enumerate resources and services, including applications, management groups, resources and policy definitions, and their relationships that are accessible by an identity.

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

Impacts

Server

Data Source

Windows Sysmon via 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="Win-Sysmon-1-Create-Process" AND ((procName REGEXP "\\Seatbelt\.exe$" OR srcFileName="Seatbelt.exe" OR description="Seatbelt" OR command REGEXP ".* CertificateThumbprints.*|.* ChromiumBookmarks.*|.* ChromiumHistory.*|.* ChromiumPresence.*|.* CloudCredentials.*|.* CredEnum.*|.* CredGuard.*|.* DpapiMasterKeys.*|.* FirefoxHistory.*|.* InterestingFiles.*|.* InterestingProcesses.*|.* ProcessCreationEvents.*") OR (command REGEXP ".* -group=all.*|.* -group=chromium.*|.* -group=misc.*|.* -group=remote.*|.* -group=slack.*|.* -group=system.*|.* -group=user.*" AND command REGEXP ".* -outputfile=.*"))

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

command,description,hostName,procName,srcFileName

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

command = Filter.command,
description = Filter.description,
hostName = Filter.hostName,
procName = Filter.procName,
srcFileName = Filter.srcFileName

FortiSIEM Rules