> 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/ssh-authentication-brute-force-attempts.md).

# SSH authentication brute force attempts

### Synopsis

| Field                | Value                      |
| -------------------- | -------------------------- |
| Activation Period    | 14 Days                    |
| Training Period      | 30 Days                    |
| Test Period          | 15 Minutes                 |
| Deduplication Period | 3 Hours                    |
| Required Data        | XDR Agent                  |
| Detection Modules    | Identity Analytics         |
| ATT\&CK Tactic       | Credential Access (TA0006) |
| ATT\&CK Technique    | Brute Force (T1110)        |
| Severity             | Informational              |

### Description

A user attempted to authenticate via SSH an excessive number of times in a short period. This may indicate a brute force attack.

### Attacker's Goals

Attackers attempt to log in to a remote host.

### Investigative actions

Verify any successful authentication by the user account referenced by the alert, as these can indicate the attacker managed to guess the credentials.

### Variations

<details>

<summary>Successful SSH Brute Force</summary>

**Synopsis**

| Field             | Value                      |
| ----------------- | -------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006) |
| ATT\&CK Technique | Brute Force (T1110)        |
| Severity          | Low                        |

**Description**

A user successfully authenticated via SSH after an excessive number of failures in a short period.

**Attacker's Goals**

Attackers attempt to log in to a remote host.

**Investigative actions**

Verify any successful authentication by the user account referenced by the alert, as these can indicate the attacker managed to guess the credentials.

</details>

<details>

<summary>Possible SSH Brute Force</summary>

**Synopsis**

| Field             | Value                      |
| ----------------- | -------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006) |
| ATT\&CK Technique | Brute Force (T1110)        |
| Severity          | Low                        |

**Description**

A user attempted to authenticate via SSH an excessive number of times in a short period. This may indicate a brute force attack.

**Attacker's Goals**

Attackers attempt to log in to a remote host.

**Investigative actions**

Verify any successful authentication by the user account referenced by the alert, as these can indicate the attacker managed to guess the credentials.

</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/ssh-authentication-brute-force-attempts.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.
