> 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/an-uncommon-rdp-session-from-a-managed-host.md).
# An uncommon RDP session from a managed host
### 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 |
| Detector Tags | Enhanced RDP Analytics |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Informational |
### Description
An RDP session was established with uncommon parameters from a managed host.
### Attacker's Goals
Adversaries may use RDP for initial access or lateral movement within a network.
### Investigative actions
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
### Variations
An uncommon RDP session initiated by a chained RDP client
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
An RDP session was established by a process that is itself an RDP client, which is uncommon behavior.
**Attacker's Goals**
Adversaries may use RDP for initial access or lateral movement within a network.
**Investigative actions**
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
An uncommon RDP session initiated by a globally rare RDP client
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
An RDP session was established by a process hash that has not been seen globally, which is uncommon.
**Attacker's Goals**
Adversaries may use RDP for initial access or lateral movement within a network.
**Investigative actions**
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
An uncommon RDP session initiated by a rare RDP client
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
An RDP session was established by a process hash that is rare in the environment.
**Attacker's Goals**
Adversaries may use RDP for initial access or lateral movement within a network.
**Investigative actions**
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
An uncommon RDP session from a host that rarely initiates RDP
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
An RDP session was initiated from a host that does not typically establish RDP connections.
**Attacker's Goals**
Adversaries may use RDP for initial access or lateral movement within a network.
**Investigative actions**
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
An uncommon RDP session initiated by a process with rare causality
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
An RDP session was established by a process with an uncommon parent process relationship.
**Attacker's Goals**
Adversaries may use RDP for initial access or lateral movement within a network.
**Investigative actions**
* Investigate the source and destination of the RDP communication.
* Check if this communication is legitimate and expected.
* Analyze the user and process that initiated the RDP connection.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/an-uncommon-rdp-session-from-a-managed-host.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.