Windows Security Event 5136 for Changes to Default Domain and Default Domain Controllers GPOs

Flags EventID 5136 modifications to Default Domain or Default Domain Controllers GPO containers in Windows AD.

FreeReviewedSigma · Medium · v2
Product
windows
Service
security
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-22
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Event ID 5136 events where the changed object is a groupPolicyContainer whose ObjectDN starts with the GUIDs for the Default Domain Policy or Default Domain Controllers Policy. Attackers may target these default GPOs to push malicious or weakening configurations across the domain. It relies on Windows Security auditing telemetry that records directory service changes along with the object class and distinguished name prefix.

Related detections9 linkedT1484.001 — drag to rearrange
Suspicious Modification of a Sensitive Group Policy - GPO (via security)
Suspicious Group Policy File System Path Redirection via Directory Service Change
Malicious GPO Permission Abuse via SharpGPOAbuse
Suspicious Executable Launched from SYSVOL Share
Malicious SharpGPOAbuse GPO Modification Tool from Public Directory
Suspicious Permissions Changed on a Group Policy - GPO (via security)
Suspicious Executable Launched from Domain Netlogon Share (via process_creation)
Windows Process: GPME Used to Modify Default Domain and Default Domain Controllers GPOs
Windows: GPO Modification Adds Startup/Logon Script References
Windows Security Event 5136 for Changes to Default Domain and Default Domain Controllers GPOs
Pivot detection · T1484.001 · 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.