Windows Remote Management Execute Shell
Description
This analytic detects selected processes spawned directly by Windows Remote Management Host processes winrshost.exe and wsmprovhost.exe. The selected children include shells, scripting hosts, and administrative, discovery, and file-transfer utilities. This target-side process relationship can indicate remote execution, but it can also result from authorized WinRM administration. Investigate the account, target host, available command line, and surrounding remote-logon activity to determine context.
Query · spl
| tstats `security_content_summariesonly`
count min(_time) as firstTime
max(_time) as lastTime
FROM datamodel=Endpoint.Processes WHERE
Processes.parent_process_name IN (
"winrshost.exe",
"wsmprovhost.exe"
)
`windows_shells`
NOT (
Processes.process_name="powershell.exe"
Processes.process="*-Version 5.1 -s -NoLogo -NoProfile"
)
NOT (
Processes.process_name="cmd.exe"
(
(
Processes.process="*powershell -NoLogo -NonInteractive -NoProfile*"
Processes.process IN (
"*Get-CimInstance MSFT_NetAdapter -Namespace *",
"*Get-Command exsetup *",
"*Get-Disk | ForEach-Object*",
"*HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall*",
"*HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Class\\*",
"*HKLM:\\SYSTEM\\CurrentControlSet\\Services\\*",
"*New-Object Management.Automation.Host.Size*"
)
)
OR
Processes.process="* /c net start Veeam*"
)
)
BY Processes.action Processes.dest Processes.original_file_name
Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
Processes.process Processes.process_exec Processes.process_guid
Processes.process_hash Processes.process_id Processes.process_integrity_level
Processes.process_name Processes.process_path Processes.user
Processes.user_id Processes.vendor_product
| `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `windows_remote_management_execute_shell_filter`
Implementation guide
The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents
are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement
this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally,
you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk
Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the Processes node
of the Endpoint data model. Use the Splunk Common Information Model (CIM) to normalize the field names and
speed up the data modeling process.
Known false positives
- Authorized administrators and management software may launch these processes through WinRM. Shell and discovery activity may be routine; evaluate expected accounts, hosts, and workflows before tuning.
Analyst notes
Known false positives: Authorized administrators and management software may launch these processes through WinRM. Shell and discovery activity may be routine; evaluate expected accounts, hosts, and workflows before tuning.