> 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/uncommon-reverse-ssh-tunnel-to-external-domain-ip.md).
# Uncommon reverse SSH tunnel to external domain/ip
### 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 | Abnormal Communication Analytics |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Protocol Tunneling (T1572) |
| Severity | Low |
### Description
An uncommon reverse SSH tunnel might have been created.
### Attacker's Goals
Attackers may use SSH to create an encrypted tunnel to allow an attacker to covertly connect to an internal host.
### Investigative actions
* Review the external ip/domain.
* Investigate the causality of the process.
### Variations
Uncommon reverse SOCKS proxy SSH tunnel to external domain/ip
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Protocol Tunneling (T1572) |
| Severity | Medium |
**Description**
An uncommon reverse SSH tunnel might have been created.
**Attacker's Goals**
Attackers may use SSH to create an encrypted tunnel to allow an attacker to covertly connect to an internal host.
**Investigative actions**
* Review the external ip/domain.
* Investigate the causality of the process.
Uncommon reverse SSH tunnel to external domain/ip to a sensitive port via a non-default bind port
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Protocol Tunneling (T1572) |
| Severity | Medium |
**Description**
An uncommon reverse SSH tunnel might have been created.
**Attacker's Goals**
Attackers may use SSH to create an encrypted tunnel to allow an attacker to covertly connect to an internal host.
**Investigative actions**
* Review the external ip/domain.
* Investigate the causality of the process.
Uncommon reverse SSH tunnel to external domain/ip using a sensitive port
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Protocol Tunneling (T1572) |
| Severity | Low |
**Description**
An uncommon reverse SSH tunnel might have been created.
**Attacker's Goals**
Attackers may use SSH to create an encrypted tunnel to allow an attacker to covertly connect to an internal host.
**Investigative actions**
* Review the external ip/domain.
* Investigate the causality of the process.
---
# 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/uncommon-reverse-ssh-tunnel-to-external-domain-ip.md?ask=&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.