Windows sc.exe Service Security Descriptor Changes via sdset

Alerts on sc.exe sdset activity that modifies a service security descriptor to grant access to targeted principals.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-02-28
Updated
2026-07-30

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 flags process executions of sc.exe where the command line includes sdset and uses a DACL entry pattern indicating it is granting access (A;). It further narrows matches to cases where the security descriptor targets trustees consistent with interactive users, service logon users, built-in administrators, local system, or everyone—common avenues for overriding existing access restrictions. The detection relies on Windows process creation telemetry, specifically sc.exe identification and command-line contents.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Malicious TinyTurla ServiceDll Registration via svchost Group (via registry_set)
Suspicious ToyMaker LAGTOY Service Creation Masquerading as WmiPrvSV via sc.exe
Malicious Service Creation With Autostart binPath via sc.exe (via process_creation)
Malicious svchost Service Creation for TinyTurla Persistence (via process_creation)
Malicious Service Creation Masquerading as nslookup (via process_creation)
Interactive Service Creation Executing cmd via sc.exe
Malicious Known Vulnerable Driver Load for BYOVD Attack
Malicious ValleyRAT KernelQuick Rootkit Service and Shellcode Store Registry Keys
Windows sc.exe Service Security Descriptor Changes via sdset
Pivot detection · T1543.003 · 9 related

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