FortiSIEM Rules

Windows: Inveigh Execution Artefacts

Rule ID

PH_Rule_SIGMA_1957

Default Status

Enabled

Description

Detects the presence and execution of Inveigh via dropped artefacts. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/file/file_event/file_event_win_hktl_inveigh_artefacts.yml

Severity

9

Category

Security

MITRE ATT&CK® Tactics

Command And Control

MITRE ATT&CK® Techniques


T1219

Remote Access Software

An adversary may use legitimate desktop support and remote access software, such as Team Viewer, Go2Assist, LogMein, AmmyyAdmin, etc, to establish an interactive command and control channel to target systems within networks. These services are commonly used as legitimate technical support software, and may be allowed by application control within a target environment.

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

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-11-FileCreate" AND fileName REGEXP "\\Inveigh-Cleartext\.txt$|\\Inveigh-FormInput\.txt$|\\Inveigh-Log\.txt$|\\Inveigh-NTLMv1Users\.txt$|\\Inveigh-NTLMv1\.txt$|\\Inveigh-NTLMv2Users\.txt$|\\Inveigh-NTLMv2\.txt$|\\Inveigh-Relay\.ps1$|\\Inveigh\.dll$|\\Inveigh\.exe$|\\Inveigh\.ps1$"

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

fileName,hostName

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

fileName = Filter.fileName,
hostName = Filter.hostName