> 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/multiple-alerts-associated-with-a-single-rdp-connection.md).
# Multiple alerts associated with a single RDP connection
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 3 Hours |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Platform Alerts OR Third-Party Alerts
|
| Detector Tags | Enhanced RDP Analytics |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Informational |
### Description
Multiple alerts associated with a single RDP connection were triggered.
### 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
Multiple elevated severity alerts associated with a single RDP connection
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Medium |
**Description**
RDP-related alerts include at least one medium or higher severity alert.
**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.
Multiple alerts associated with a single RDP connection - high risk-processes
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
RDP-related alerts involve high-risk processes (service management, offensive tools, or script execution).
**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.
Diverse alerts associated with a single RDP connection
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
RDP-related alerts show diverse post-connection activity across multiple attack stages.
**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.
Pre-connection activity alongside abnormal RDP connection
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Remote Desktop Protocol (T1021.001) |
| Severity | Low |
**Description**
Suspicious activity was detected before an abnormal RDP session was established.
**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/multiple-alerts-associated-with-a-single-rdp-connection.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.