FortiSIEM Rules

Windows: Metasploit Or Impacket Service Installation Via SMB PsExec

Rule ID


Default Status



Detects usage of Metasploit SMB PsExec (exploit/windows/smb/psexec) and Impacket by triggering on specific service installation. These tools are one of many examples of powerful penetration testing scripts that enables you to execute remote commands on another machine. This rule is adapted from






Lateral Movement

Lateral Movement consists of techniques that adversaries use to enter and control remote systems on a network. Following through on their primary objective often requires exploring the network to find their target and subsequently gaining access to it. Reaching their objective often involves pivoting through multiple systems and accounts to gain. Adversaries might install their own remote access tools to accomplish Lateral Movement or use legitimate credentials with native network and operating system tools, which may be stealthier.

MITRE ATT&CK® Techniques


Lateral Tool Transfer

Adversaries may transfer tools or other files between systems in a compromised environment. Files may be copied from one system to another to stage adversary tools or other files over the course of an operation. Adversaries may copy files laterally between internal victim systems to support lateral movement using inherent file sharing protocols such as file sharing over SMB to connected network shares or with authenticated connections with SMB/Windows Admin Shares.



Data Source

Windows Security Log via OMI or FortiSIEM Agent



Remediation Guidance

Investigate whether the user needs to really run on the specific host. Typically system administrators need these utilities to do their work. may be bundled with other software. If necessary, rebuild the host from a known, good source and have the user change their password.

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="Win-Security-4697" AND serviceStartType="3" AND serviceType="0x10" AND serviceFileName REGEXP "^%systemroot%\\[a-zA-Z]{8}\.exe$" AND serviceName REGEXP "(^[a-zA-Z]{4}$)|(^[a-zA-Z]{8}$)|(^[a-zA-Z]{16}$)") AND (serviceName!="PSEXESVC")

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

hostName = Filter.hostName,
serviceFileName = Filter.serviceFileName,
serviceName = Filter.serviceName,
serviceStartType = Filter.serviceStartType,
serviceType = Filter.serviceType