FortiSIEM Rules

Windows: Pass the Hash Activity 2

Rule ID


Default Status



Detects the attack technique pass the hash which is used to move laterally inside the network. This rule is adapted from






Defense Evasion

Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.

MITRE ATT&CK® Techniques


Use Alternate Authentication Material: Pass the Hash

Adversaries may "Pass the hash" using stolen password hashes to move laterally within an environment, bypassing normal system access controls. Pass the hash (PtH) is a method of authenticating as a user without having access to the user's cleartext password. Valid password hashes for an account are captured using a Credential Access technique and can be used with PtH to authenticate as that user. Once authenticated, PtH may be used to perform actions on local or remote systems.



Data Source

Windows Security Log via OMI or 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="Win-Security-4624" AND ((securityId="S-1-0-0" AND winLogonType=3 AND winLogonProc="NtLmSsp" AND msgLen IS NULL) OR (winLogonType=9 AND winLogonProc="seclogo"))) AND (user!="ANONYMOUS LOGON")

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,
msgLen = Filter.msgLen,
winLogonProc = Filter.winLogonProc,
securityId = Filter.securityId,
user = Filter.user,
winLogonType = Filter.winLogonType