The sub-techniques beta is now live! Read the release blog post for more info.

Windows Remote Management

Windows Remote Management (WinRM) is the name of both a Windows service and a protocol that allows a user to interact with a remote system (e.g., run an executable, modify the Registry, modify services). [1] It may be called with the winrm command or by any number of programs such as PowerShell. [2]

ID: T1028
Tactic: Execution, Lateral Movement
Platform: Windows
System Requirements: WinRM listener turned on and configured on remote system
Permissions Required: User, Administrator
Data Sources: File monitoring, Authentication logs, Netflow/Enclave netflow, Process monitoring, Process command-line parameters
Supports Remote:  Yes
Version: 1.1
Created: 31 May 2017
Last Modified: 15 October 2019

Procedure Examples

Name Description
Cobalt Strike

Cobalt Strike can use WinRM to execute a payload on a remote host.[4]

Threat Group-3390

Threat Group-3390 has used WinRM to enable remote execution.[5]


Mitigation Description
Disable or Remove Feature or Program

Disable the WinRM service.

Network Segmentation

If the service is necessary, lock down critical enclaves with separate WinRM infrastructure and follow WinRM best practices on use of host firewalls to restrict WinRM access to allow communication only to/from specific devices.[3]

Privileged Account Management

If the service is necessary, lock down critical enclaves with separate WinRM accounts and permissions.


Monitor use of WinRM within an environment by tracking service execution. If it is not normally used or is disabled, then this may be an indicator of suspicious behavior. Monitor processes created and actions taken by the WinRM process or a WinRM invoked script to correlate it with other related events. [6]