> 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/unusual-ssh-activity-that-resembles-ssh-proxy.md).

# Unusual SSH activity that resembles SSH proxy

### 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> |
| ATT\&CK Tactic       | Command and Control (TA0011)                                                                                |
| ATT\&CK Technique    | Proxy: Internal Proxy (T1090.001)                                                                           |
| Severity             | Informational                                                                                               |

### Description

A host initiated and received an unusual SSH connection, which is consistent with being an SSH proxy. This behavior may indicate an attempt to establish covert command and control communication or to exfiltrate data.

### Attacker's Goals

Attackers aim to establish a covert command and control channel or relay communications through a compromised SSH connection.

### Investigative actions

Review the SSH connections to identify any unusual proxy activity or traffic patterns. Investigate the user accounts involved in the SSH connections to determine if credentials were compromised. Additionally, examine logs for any unexpected data transfers or commands that may indicate malicious intent.

### Variations

<details>

<summary>High Volume Unusual SSH activity that resembles SSH proxy</summary>

**Synopsis**

| Field             | Value                             |
| ----------------- | --------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)      |
| ATT\&CK Technique | Proxy: Internal Proxy (T1090.001) |
| Severity          | Low                               |

**Description**

A host initiated and received an unusual SSH connection, which is consistent with being an SSH proxy. This behavior may indicate an attempt to establish covert command and control communication or to exfiltrate data.

**Attacker's Goals**

Attackers aim to establish a covert command and control channel or relay communications through a compromised SSH connection.

**Investigative actions**

Review the SSH connections to identify any unusual proxy activity or traffic patterns. Investigate the user accounts involved in the SSH connections to determine if credentials were compromised. Additionally, examine logs for any unexpected data transfers or commands that may indicate malicious intent.

</details>

<details>

<summary>Suspicious SSH activity that resembles SSH proxy</summary>

**Synopsis**

| Field             | Value                             |
| ----------------- | --------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)      |
| ATT\&CK Technique | Proxy: Internal Proxy (T1090.001) |
| Severity          | Low                               |

**Description**

A host initiated and received an unusual SSH connection, which is consistent with being an SSH proxy. This behavior may indicate an attempt to establish covert command and control communication or to exfiltrate data.

**Attacker's Goals**

Attackers aim to establish a covert command and control channel or relay communications through a compromised SSH connection.

**Investigative actions**

Review the SSH connections to identify any unusual proxy activity or traffic patterns. Investigate the user accounts involved in the SSH connections to determine if credentials were compromised. Additionally, examine logs for any unexpected data transfers or commands that may indicate malicious intent.

</details>

<details>

<summary>Unusual SSH activity that resembles SSH proxy detected</summary>

**Synopsis**

| Field             | Value                             |
| ----------------- | --------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)      |
| ATT\&CK Technique | Proxy: Internal Proxy (T1090.001) |
| Severity          | Low                               |

**Description**

A host initiated and received an unusual SSH connection, which is consistent with being an SSH proxy. This behavior may indicate an attempt to establish covert command and control communication or to exfiltrate data.

**Attacker's Goals**

Attackers aim to establish a covert command and control channel or relay communications through a compromised SSH connection.

**Investigative actions**

Review the SSH connections to identify any unusual proxy activity or traffic patterns. Investigate the user accounts involved in the SSH connections to determine if credentials were compromised. Additionally, examine logs for any unexpected data transfers or commands that may indicate malicious intent.

</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/unusual-ssh-activity-that-resembles-ssh-proxy.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.
