Windows Security: SeEnableDelegationPrivilege Enabled via AD User Right (Event 4704)

Alerts when Event ID 4704 assigns SeEnableDelegationPrivilege, enabling control over other AD user objects.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
@neu5ron (SigmaHQ), DRL 1.1
Published
2017-07-30
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies when an account is granted the SeEnableDelegationPrivilege user right in Active Directory. That privilege can enable an attacker to delegate permissions in ways that may allow control of other AD user objects, making it a high-impact persistence or privilege-escalation vector. It relies on Windows Security auditing event 4704 and matches the PrivilegeList field containing SeEnableDelegationPrivilege.

Related detections9 linkedT1098 — drag to rearrange
Suspicious Azure Key Vault Access Policy Modification
Malicious Cluster-Admin Role Binding Creation (via audit)
Malicious User Password Change Using Current Hash Password - ChangeNTLM - Mimikatz (via security)
Suspicious Account Password Set to Never Expire. (via security)
Malicious Modification of a Computer Account SPN (via security)
Suspicious Massive Group Membership Changes (via security)
Malicious High Risk Active Directory Group Membership Change (via security)
Malicious Account Marked as Sensitive and Cannot Be Delegated Had Its Protection Removed (via security)
Malicious Host Constrained Delegation Settings Changed for Potential Abuse (Rubeus) - Kerberos Only (via security)
Windows Security: SeEnableDelegationPrivilege Enabled via AD User Right (Event 4704)
Pivot detection · T1098 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.