Windows: RottenPotato Like Attack Pattern

Rule ID

PH_Rule_SIGMA_89

Default Status

Enabled

Description

Detects logon events that have characteristics of events generated during an attack with RottenPotato and the like. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/account_management/win_security_susp_rottenpotato.yml

Severity

MITRE ATT&CK® Tactics

Collection

Collection consists of techniques adversaries may use to gather information and the sources information is collected from that are relevant to following through on the adversary's objectives. Frequently, the next goal after collecting data is to steal (exfiltrate) the data. Common target sources include various drive types, browsers, audio, video, and email. Common collection methods include capturing screenshots and keyboard input.

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

MITRE ATT&CK® Techniques

T1557.001

Man-in-the-Middle: LLMNR/NBT-NS Poisoning and SMB Relay

Adversaries may attempt to position themselves between two or more networked devices using a man-in-the-middle (MiTM) technique to support follow-on behaviors such as Network Sniffing or Transmitted Data Manipulation. By responding to Link-Local Multicast Name Resolution (LLMNR) and NetBIOS Name Service (NBT-NS) network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system. This activity may be used to collect or relay authentication materials.

https://attack.mitre.org/techniques/T1557/001

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="Win-Security-4624" AND winLogonType=3 AND user="ANONYMOUS LOGON" AND computer IS NULL AND srcIpAddr IN (127.0.0.1,::1)

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

computer,hostName,srcIpAddr,user,winLogonType

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

computer = Filter.computer,
hostName = Filter.hostName,
srcIpAddr = Filter.srcIpAddr,
user = Filter.user,
winLogonType = Filter.winLogonType

FortiSIEM Rules