[Rule Tuning] SeDebugPrivilege Enabled by a Suspicious Process

[Mikaayenson]

Resolves elastic/ia-trade-team#1071

Reduces noise from standard Windows system utilities that commonly request SeDebugPrivilege during normal operation. Adds exclusions for tasklist.exe, NETSTAT.EXE, AutoModeDetect.exe, taskkill.exe (both System32 and SysWOW64), dllhost.exe, powershell_ise.exe, w3wp.exe, wsmprovhost.exe, netsh.exe, explorer.exe, SystemPropertiesAdvanced.exe, and SCNotification.exe. PowerShell is intentionally retained as it remains the primary abuse vector for SeDebugPrivilege-based privilege escalation.

---

Full telemetry triage, analytics links, and KQL verification: see linked ia-trade-team issue.

[github-actions]

Rule: Tuning - Guidelines

These guidelines serve as a reminder set of considerations when tuning an existing rule.

Documentation and Context

• Detailed description of the suggested changes.
• Provide example JSON data or screenshots.
• Provide evidence of reducing benign events mistakenly identified as threats (False Positives).
• Provide evidence of enhancing detection of true threats that were previously missed (False Negatives).
• Provide evidence of optimizing resource consumption and execution time of detection rules (Performance).
• Provide evidence of specific environment factors influencing customized rule tuning (Contextual Tuning).
• Provide evidence of improvements made by modifying sensitivity by changing alert triggering thresholds (Threshold Adjustments).
• Provide evidence of refining rules to better detect deviations from typical behavior (Behavioral Tuning).
• Provide evidence of improvements of adjusting rules based on time-based patterns (Temporal Tuning).
• Provide reasoning of adjusting priority or severity levels of alerts (Severity Tuning).
• Provide evidence of improving quality integrity of our data used by detection rules (Data Quality).
• Ensure the tuning includes necessary updates to the release documentation and versioning.

Rule Metadata Checks

• updated_date matches the date of tuning PR merged.
• min_stack_version should support the widest stack versions.
• name and description should be descriptive and not include typos.
• query should be inclusive, not overly exclusive. Review to ensure the original intent of the rule is maintained.

Testing and Validation

• Validate that the tuned rule's performance is satisfactory and does not negatively impact the stack.
• Ensure that the tuned rule has a low false positive rate.

[elastic-vault-github-plugin-prod]

⛔️ Test failed

Results

• ❌ SeDebugPrivilege Enabled by a Suspicious Process (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[Copilot]

Pull request overview

Tunes the existing Windows EQL rule “SeDebugPrivilege Enabled by a Suspicious Process” to reduce alert noise by expanding the allowlist of common legitimate executables that enable SeDebugPrivilege during normal operations.

Changes:

• Updated the rule metadata updated_date to 2026/08/13.
• Expanded the winlog.event_data.ProcessName exclusion list with additional common Windows/SCCM/IIS utilities and services.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[eric-forte-elastic]

Just double checking this can be used as a LOLBin right? Are we sure we want to have such a broad exclusion on it for this rule?

[terrancedejesus]

agreed.

[terrancedejesus]

Suggested change

"?:\\Windows\\System32\\dllhost.exe",

[terrancedejesus]

Same thing here. w3wp.exe is IIS. Plausible a webapp RCE is exploited with a chain to set SeDebugPrivilege if app pool identities are misconfigured or overly permissive.

[terrancedejesus]

Suggested change

"?:\\Windows\\System32\\inetsrv\\w3wp.exe",

[terrancedejesus]

Approving not to block. Suggestions added as comments.