PH_Rule_PolicyViolation_12
Enabled
Detects that multiple (more than 3) accounts were disabled by administrator in a short period of time
9
Security
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.
https://attack.mitre.org/tactics/TA0005No 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.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
AcctDisabled
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 ("Win-Security-629","Win-Security-4725")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevName,user
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(DISTINCT targetUser) >= 3
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 = AcctDisabled.reptDevName,
user = AcctDisabled.user