> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/rare-winrm-session.md).

# Rare WinRM Session

### Synopsis

| Field                | Value                                                  |
| -------------------- | ------------------------------------------------------ |
| Activation Period    | 14 Days                                                |
| Training Period      | 30 Days                                                |
| Test Period          | N/A (single event)                                     |
| Deduplication Period | 1 Day                                                  |
| Required Data        | XDR Agent                                              |
| ATT\&CK Tactic       | Lateral Movement (TA0008)                              |
| ATT\&CK Technique    | Remote Services: Windows Remote Management (T1021.006) |
| Severity             | Informational                                          |

### Description

Windows Remote Management (WinRM) enables users to interact with remote systems in different ways, including running executables on the remote system. WinRM sessions can be established using WinRM/WinRS commands or programs such as PowerShell. Attackers can use WinRM to execute code and move laterally within a compromised network.

### Attacker's Goals

Windows Remote Management (WinRM) enables users to interact with remote systems in different ways, including running executables on the remote endpoint. WinRM sessions can be established using winrm/winrs commands or programs such as PowerShell. Attackers can use WinRM to execute code and move laterally within a compromised network.

### Investigative actions

Investigate the endpoints participating in the session.

### Variations

<details>

<summary>Rare WinRM Session by an RMM actor</summary>

**Synopsis**

| Field             | Value                                                  |
| ----------------- | ------------------------------------------------------ |
| ATT\&CK Tactic    | Lateral Movement (TA0008)                              |
| ATT\&CK Technique | Remote Services: Windows Remote Management (T1021.006) |
| Severity          | Low                                                    |

**Description**

Windows Remote Management (WinRM) enables users to interact with remote systems in different ways, including running executables on the remote system. WinRM sessions can be established using WinRM/WinRS commands or programs such as PowerShell. Attackers can use WinRM to execute code and move laterally within a compromised network. The session was initiated by a Remote Monitoring & Management tool.

**Attacker's Goals**

Windows Remote Management (WinRM) enables users to interact with remote systems in different ways, including running executables on the remote endpoint. WinRM sessions can be established using winrm/winrs commands or programs such as PowerShell. Attackers can use WinRM to execute code and move laterally within a compromised network.

**Investigative actions**

Investigate the endpoints participating in the session.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/rare-winrm-session.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.