FortiSIEM Rules

Account Locked: FortiSIEM

Rule ID


Default Status



Detects system (FortiSIEM) account lockout caused by excessive logon failures






Credential Access

Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.

MITRE ATT&CK® Techniques


Brute Force: Password Guessing

Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.



Data Source

FortiSIEM via Syslog



Remediation Guidance

Identify the source of the incident and the user and make sure that it is a legitimate attempt to log on to FortiSIEM. If your FortiSIEM is exposed to the Internet, then put access controls on FortiSIEM itself or on the firewall to prevent malicious Internet actors from gaining access. Make sure it is not a cached credential from another system while the primary user has changed credential. Make sure there are no other incidents from the source host that may indicate malware trying to gain access to other systems. Make sure there are no vulnerabilities on the source hosts if they are internal to your network.

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

600 seconds

Trigger Conditions

If the following defined pattern/s occur within a 600 second time window.


SubPattern Definitions

SubPattern Name: AOLockout

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


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

srcIpAddr, targetUser, reptDevName

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

 srcIpAddr = AOLockout.srcIpAddr,
 user = AOLockout.targetUser,
 destName = AOLockout.reptDevName,
 incidentCount = AOLockout.COUNT(*)