huntrule

Windows Security Log: Member Removed from Security-Enabled Global Group

Flags Windows Security Log events showing a member was removed from a security-enabled global group.

FreeReviewedSigma · Low · v2
Product
windows
Service
security
Author
Alexandr Yampolskyi, SOC Prime (SigmaHQ), DRL 1.1
Published
2023-04-26
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies when a member is removed from a security-enabled global group using Windows Security Log events. Attackers may use group membership changes to remove access or reduce visibility by altering privileges tied to global groups. The detection relies on matching EventID 633 and 4729 records in the Windows Security log.

Reporting behind it

Related detections9 linkedT1098 — drag to rearrange
Malicious Domain and Enterprise Admins Group Addition via net group Domain Add (via process_creation)
Suspicious Route53 Domain Transfer Lock Disabled via Scattered Spider Technique
Suspicious Domain Admin Account Creation via net (via process_creation)
Suspicious Guest Account Privilege Escalation (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious dMSA Object Access with Migration AccessMask
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
Suspicious Compute Instance Metadata Modification in GCP
Suspicious Azure AD Authentication Method Registration for Account Takeover (via azure)
Windows Security Log: Member Removed from Security-Enabled Global Group
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.