> 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/rdp-from-an-unmanaged-endpoint-in-a-typically-managed-subnet.md).

# RDP from an unmanaged endpoint in a typically managed subnet

### Synopsis

| Field                | Value                                                                                                       |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                     |
| Training Period      | 30 Days                                                                                                     |
| Test Period          | N/A (single event)                                                                                          |
| Deduplication Period | 1 Day                                                                                                       |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall traffic Logs OR XDR Agent</p> |
| Detector Tags        | Enhanced RDP Analytics                                                                                      |
| ATT\&CK Tactic       | Lateral Movement (TA0008)                                                                                   |
| ATT\&CK Technique    | Remote Services: Remote Desktop Protocol (T1021.001)                                                        |
| Severity             | Low                                                                                                         |

### Description

An RDP connection was established from an unmanaged endpoint in a typically managed subnet, indicating a possible lateral movement.

### Attacker's Goals

Lateral movement to critical assets from an unmanaged host.

### Investigative actions

* Verify if the source endpoint is authorized to perform RDP connections.
* Validate that the source endpoint is managed or unmanaged.
* Investigate the user account used for the RDP connection.

### Variations

<details>

<summary>RDP from an unmanaged endpoint in a typically managed subnet with a significantly higher number of managed endpoints in the subnet</summary>

**Synopsis**

| Field             | Value                                                |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008)                            |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity          | Low                                                  |

**Description**

An RDP connection was established from an unmanaged endpoint in a typically managed subnet, indicating a possible lateral movement. The source subnet has a significantly higher number of managed endpoints compared to the unmanaged ones.

**Attacker's Goals**

Lateral movement to critical assets from an unmanaged host.

**Investigative actions**

* Verify if the source endpoint is authorized to perform RDP connections.
* Validate that the source endpoint is managed or unmanaged.
* Investigate the user account used for the RDP connection.

</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/rdp-from-an-unmanaged-endpoint-in-a-typically-managed-subnet.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.
