FortiSIEM Rules

Windows: Remote PowerShell Session Network

Rule ID


Default Status



Detects remote PowerShell connections by monitoring network outbound connections to ports 5985 or 5986 from a non-network service account. This rule is adapted from







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.

MITRE ATT&CK® Techniques


Command and Scripting Interpreter: PowerShell

Adversaries may abuse PowerShell commands and scripts for execution. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code.



Data Source

Windows Sysmon via FortiSIEM Agent



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.


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-Sysmon-3-Network-Connect.*" AND (destIpPort IN (5985,5986) AND initiated="true") AND ((user NOT REGEXP ".*NETWORK SERVICE.*|.*NETZWERKDIENST.*|.*SERVICIO DE RED.*|.*SERVIZIO DI RETE.*" AND user NOT REGEXP ".*SERVICE R.*" OR user NOT REGEXP ".*SEAU.*" AND srcIpAddr NOT IN (,::1) AND procName NOT IN ("C:\\Program Files (x86)\\Avast Software\\Avast\\AvastSvc.exe","C:\\Program Files\\Avast Software\\Avast\\AvastSvc.exe")) AND (srcIpAddr NOT IN (,::1) OR destIpAddr NOT IN (,::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


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

destIpAddr = Filter.destIpAddr,
destIpPort = Filter.destIpPort,
hostName = Filter.hostName,
initiated = Filter.initiated,
procName = Filter.procName,
srcIpAddr = Filter.srcIpAddr,
user = Filter.user