Detect Create or Modify System Process in Splunk
Adversaries may create or modify system-level processes to repeatedly execute malicious payloads as part of persistence. When operating systems boot up, they can start processes that perform background system functions. On Windows and Linux, these system processes are referred to as services. On macOS, launchd processes known as Launch Daemon and Launch Agent are run to finish system initialization and load user specific parameters. Adversaries may install new services, daemons, or agents that can be configured to execute at startup or a repeatable interval in order to establish persistence. Similarly, adversaries may modify existing services, daemons, or agents to achieve the same effect. Services, daemons, or agents may be created with administrator privileges but executed under root/SYSTEM privileges. Adversaries may leverage this functionality to create or modify system processes in order to escalate privileges.
MITRE ATT&CK
- Tactic
- Persistence Privilege Escalation
- Technique
- T1543 Create or Modify System Process
- Canonical reference
- https://attack.mitre.org/techniques/T1543/
SPL Detection Query
index=wineventlog (
(sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1)
OR (sourcetype="WinEventLog:Security" EventCode IN (4697, 7045))
OR (sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode IN (12, 13, 14))
)
| eval DetectionBranch=case(
EventCode=1 AND (match(Image, "(?i)\\\\sc\.exe$") AND match(CommandLine, "(?i)(create|config)")), "sc_exe_service_create",
EventCode=1 AND match(Image, "(?i)\\\\(powershell|pwsh)\.exe$") AND match(CommandLine, "(?i)(New-Service|Set-Service)"), "powershell_new_service",
EventCode IN (4697, 7045), "security_service_install",
EventCode IN (12, 13, 14) AND match(TargetObject, "(?i)SYSTEM\\\\CurrentControlSet\\\\Services"), "registry_service_modification",
true(), null()
)
| where isnotnull(DetectionBranch)
| eval ServiceName=case(
EventCode=4697, mvindex(split(Message, "\n"), 0),
EventCode=7045, ServiceName,
EventCode=1, replace(CommandLine, ".*?(?:create|New-Service)\\s+([\\w-]+).*", "\\1"),
EventCode IN (12,13,14), replace(TargetObject, ".*Services\\\\([^\\\\]+).*", "\\1"),
true(), "unknown"
)
| eval SuspiciousPath=if(
match(coalesce(ServiceFileName, CommandLine, RegistryValueData, ""),
"(?i)(\\\\temp\\\\|\\\\appdata\\\\|\\\\downloads\\\\|\\\\public\\\\|%temp%|%appdata%)"),
1, 0
)
| eval LOLBinService=if(
match(coalesce(ServiceFileName, CommandLine, RegistryValueData, ""),
"(?i)(powershell\.exe|cmd\.exe|wscript\.exe|cscript\.exe|mshta\.exe|rundll32\.exe|regsvr32\.exe|certutil\.exe)"),
1, 0
)
| eval UnusualParent=if(
EventCode=1 AND match(ParentImage,
"(?i)(winword|excel|powerpnt|outlook|wscript|cscript|mshta|rundll32)\.exe"),
1, 0
)
| eval RiskScore=SuspiciousPath + LOLBinService + UnusualParent
| eval SuspicionFlags=mvappend(
if(SuspiciousPath=1, "suspicious_path", null()),
if(LOLBinService=1, "lolbin_service", null()),
if(UnusualParent=1, "unusual_parent", null())
)
| table _time, host, User, DetectionBranch, ServiceName, CommandLine, ParentImage,
ParentCommandLine, SuspiciousPath, LOLBinService, UnusualParent, RiskScore, SuspicionFlags
| sort - _timeDetects Windows service creation and modification using Security Event IDs 4697 and 7045 (service installation), Sysmon Event ID 1 for sc.exe or PowerShell invocations, and Sysmon registry events (12/13/14) targeting the Services registry key. Assigns a risk score based on suspicious binary paths (writable user directories), LOLBin usage as the service executable, and unusual parent processes. Covers both direct API-based service creation (4697/7045) and command-line-based creation (sc.exe, New-Service).
Data Sources
Required Sourcetypes
False Positives & Tuning
- Legitimate software installers (MSI packages, vendor setup.exe) that register services during installation — typically identified by msiexec.exe or setup.exe as parent process
- IT management tools such as SCCM, Ansible, or Puppet that create or modify services as part of configuration management workflows
- Security products (EDR agents, AV engines, backup software) that install kernel-level or user-mode services during deployment or updates
- Software developers testing or deploying Windows services locally, particularly from development directories that may match suspicious path patterns
- System administrators manually configuring services via sc.exe or PowerShell during maintenance windows — correlate with change management tickets
Other platforms for T1543
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Create Malicious Windows Service via sc.exe
Expected signal: Security Event ID 4697 and System Event ID 7045: New service 'ArgusTestSvc' installed with ServiceFileName containing cmd.exe. Sysmon Event ID 1: sc.exe process creation with CommandLine containing 'create ArgusTestSvc'. Sysmon Event ID 13: Registry value set at HKLM\SYSTEM\CurrentControlSet\Services\ArgusTestSvc\ImagePath.
- Test 2Create Persistent Service via PowerShell New-Service
Expected signal: Sysmon Event ID 1: powershell.exe process creation with CommandLine containing 'New-Service'. Security Event ID 4697 and System Event ID 7045: service 'ArgusTestPSSvc' installed with ServiceFileName = powershell.exe. Sysmon Event ID 13: registry modification at HKLM\SYSTEM\CurrentControlSet\Services\ArgusTestPSSvc\.
- Test 3Service Installed in User-Writable Path
Expected signal: Sysmon Event ID 11: file created at %TEMP%\svchost32.exe (copy of cmd.exe). Sysmon Event ID 1: sc.exe execution with TEMP path in command line. Security Event ID 4697 / System Event ID 7045: new service with ServiceFileName in user Temp directory. Sysmon Event ID 13: ImagePath registry value containing \Temp\ path.
- Test 4Modify Existing Service Binary Path (Service Hijacking)
Expected signal: Sysmon Event ID 1: sc.exe with 'config' and 'binPath' in command line targeting 'wuauserv'. Sysmon Event ID 13: registry value modification at HKLM\SYSTEM\CurrentControlSet\Services\wuauserv\ImagePath. Security Event ID 4697 may fire depending on Windows version and audit policy. Note: this test modifies a real service — run only in isolated test environments.
References (9)
- https://attack.mitre.org/techniques/T1543/
- https://technet.microsoft.com/en-us/library/cc772408.aspx
- https://learn.microsoft.com/en-us/windows/win32/services/service-control-manager
- https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1543.003/T1543.003.md
- https://www.mandiant.com/resources/blog/iocs-yellow-liderc-imaploader
- https://www.cisa.gov/sites/default/files/2024-04/aa24-109a-stopransomware-akira_0.pdf
- https://www.sans.org/white-papers/33492/
- https://github.com/SigmaHQ/sigma/tree/master/rules/windows/registry/registry_set
Unlock Pro Content
Get the full detection package for T1543 including response playbook, investigation guide, and atomic red team tests.