PH_Rule_Access_67
Enabled
Detects that an account was created, used and then deleted within a short period of time. This is highly unusual activity and must be thoroughly investigated.
9
Security
Suspicious Activity
No Technique Specified
Server
Windows Security Log via OMI or FortiSIEM Agent
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
3600 seconds
If the following defined pattern/s occur within a 3600 second time window.
AccountCreated FOLLOWED_BY LogonSuccess FOLLOWED_BY AccountDeleted
This defines how two or more distinct events are related in a time-series based action. e.g. An event occurs followed by another event if the source IP, user, and messageId are the same
AccountCreated.targetUser = LogonSuccess.user AND LogonSuccess.user = AccountDeleted.targetUser AND LogonSuccess.reptDevName = AccountDeleted.reptDevName
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN (Group@PH_SYS_EVENT_AccountCreated)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
user,targetUser,reptDevName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
Operator Rank: 0 Operator Type: FOLLOWED_BY
This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN (Group@PH_SYS_EVENT_HostLogonSuccess,Group@PH_SYS_EVENT_DomainLogonSuccess)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
user,reptDevName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
Operator Rank: 1 Operator Type: FOLLOWED_BY
This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN (Group@PH_SYS_EVENT_AccountDeleted)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
targetUser,reptDevName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
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
user = AccountCreated.user,
targetUser = AccountCreated.targetUser,
destName = AccountCreated.reptDevName