Windows process communicating outbound to unusual ports

Rule ID

PH_Rule_OSQ_WIN_1

Default Status

Enabled

Description

Detects a Windows process communicating to outside public addresses on ports other than common web, dns and mail ports.

Severity

MITRE ATT&CK® Tactics

Execution

Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.

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

MITRE ATT&CK® Techniques

T1129

Shared Modules

Adversaries may abuse shared modules to execute malicious payloads. The Windows module loader can be instructed to load DLLs from arbitrary local paths and arbitrary Universal Naming Convention (UNC) network paths. Adversaries may use this functionality as a way to execute arbitrary code on a victim system.

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

Impacts

Server

Data Source

Windows osquery windows_processes_communicating_outbound_to_public_addresses_on_ports_other_than_80,_443 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 = "PH_OSQUERY_WIN_OUTBOUND_NOT_WEB_DNS_MAIL" AND totalNum >= 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

reptDevName,procName,procId,destIpAddr,destIpPort

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.reptDevName,
procName = Filter.procName,
procId = Filter.procId,
destIpAddr = Filter.destIpAddr,
destIpPort = Filter.destIpPort

FortiSIEM Rules