Detection rules › Splunk

Windows AD Object Owner Updated

Author
Dean Luxton
Source
upstream

AD Object Owner Updated. The owner provides Full control level privileges over the target AD Object. This event has significant impact alone and is also a precursor activity for hiding an AD object.

MITRE ATT&CK coverage

TacticTechniques
Privilege EscalationT1484 Domain or Tenant Policy Modification
Defense EvasionT1222.001 File and Directory Permissions Modification: Windows File and Directory Permissions Modification, T1484 Domain or Tenant Policy Modification

Event coverage

ProviderEvent IDTitle
Security-Auditing5136A directory service object was modified.

Stages and Predicates

Stage 1: search

search EventCode=5136

Stage 2: stats

stats BY ObjectClass, ObjectDN, OpCorrelationID, src_user, SubjectLogonId, DSName

Stage 3: rex

rex field=old_value ...

Stage 4: rex

rex field=new_value ...

Stage 5: where

where old_owner!=

Stage 6: lookup

lookup <lookup> builtin_group_name, builtin_group_string, new_owner_group, new_owner_group_builtin_group

Stage 7: lookup

lookup <lookup> builtin_group_name, builtin_group_string, old_owner, old_owner_group_builtin_group

Stage 8: eval

eval ... using (new_owner, new_owner_group, new_owner_group_builtin_group, new_owner_user, old_owner, old_owner_group, old_owner_group_builtin_group, old_owner_user)

Stage 9: stats

stats BY _time, ObjectClass, ObjectDN, src_user, OpCorrelationID, DSName

Stage 10: search

search `macro`

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
EventCodeeq
  • 5136 corpus 22 (splunk 22)

Neighbors

Stricter alternatives (narrower than this rule)

The rules below may be useful if you find the current rule is too noisy / lacks specificity.