> 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/vpn-login-brute-force-attempt.md).
# VPN login Brute-Force attempt
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Global Protect OR Third-Party VPNs
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force (T1110), Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Informational |
### Description
A user account failed to log in to a VPN service multiple times in a short time period. This may indicate a brute-force attack.
### Attacker's Goals
An attacker attempts to gain access to the account.
### Investigative actions
* Verify successful connections by the user account, as these can indicate the attacker managed to guess the credentials.
* Analyze login patterns for abnormal times, locations, or IPs for suspicious activity.
* Look for VPN login attempts from countries where the organization does not typically operate.
* Cross-reference the IP addresses with threat intelligence sources.
* Follow further actions taken by the account.
### Variations
Successful VPN Login Brute Force
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force (T1110), Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Low |
**Description**
A user account failed to log in to a VPN service multiple times in a short time period. This may indicate a brute-force attack.
**Attacker's Goals**
An attacker attempts to gain access to the account.
**Investigative actions**
* Verify successful connections by the user account, as these can indicate the attacker managed to guess the credentials.
* Analyze login patterns for abnormal times, locations, or IPs for suspicious activity.
* Look for VPN login attempts from countries where the organization does not typically operate.
* Cross-reference the IP addresses with threat intelligence sources.
* Follow further actions taken by the account.
VPN login brute-force attempt with suspicious characteristics
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force (T1110), Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Low |
**Description**
A user account failed to log in to a VPN service multiple times in a short time period. This may indicate a brute-force attack.
**Attacker's Goals**
An attacker attempts to gain access to the account.
**Investigative actions**
* Verify successful connections by the user account, as these can indicate the attacker managed to guess the credentials.
* Analyze login patterns for abnormal times, locations, or IPs for suspicious activity.
* Look for VPN login attempts from countries where the organization does not typically operate.
* Cross-reference the IP addresses with threat intelligence sources.
* Follow further actions taken by the account.
---
# 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/vpn-login-brute-force-attempt.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.