> 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/excessive-user-account-lockouts.md).
# Excessive user account lockouts
### 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:
Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Brute Force (T1110), Brute Force: Password Spraying (T1110.003) |
| Severity | Low |
### Description
A high amount of user accounts were locked out from a single source host in a short time period. This may be the result of a brute-force or password spray attack.
### Attacker's Goals
An attacker may be attempting to gain unauthorized access to user accounts.
### Investigative actions
* Investigate the associated authentication attempts and login failures (e.g. 4740, 4625, 4776 events).
* Determine if any programs have stored outdated credentials, causing account lockouts.
* Find the computer responsible for the lockouts and verify if it exists on the domain.
* Monitor services that may be running with a user's credentials.
### Variations
Excessive user account lockouts from a suspicious source
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Brute Force (T1110), Brute Force: Password Spraying (T1110.003) |
| Severity | Medium |
**Description**
A high amount of user accounts were locked out from a single source host in a short time period. This may be the result of a brute-force or password spray attack.
**Attacker's Goals**
An attacker may be attempting to gain unauthorized access to user accounts.
**Investigative actions**
* Investigate the associated authentication attempts and login failures (e.g. 4740, 4625, 4776 events).
* Determine if any programs have stored outdated credentials, causing account lockouts.
* Find the computer responsible for the lockouts and verify if it exists on the domain.
* Monitor services that may be running with a user's credentials.
Excessive account lockouts on suspicious users
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Brute Force (T1110), Brute Force: Password Spraying (T1110.003) |
| Severity | Medium |
**Description**
A high amount of user accounts were locked out from a single source host in a short time period. This may be the result of a brute-force or password spray attack.
**Attacker's Goals**
An attacker may be attempting to gain unauthorized access to user accounts.
**Investigative actions**
* Investigate the associated authentication attempts and login failures (e.g. 4740, 4625, 4776 events).
* Determine if any programs have stored outdated credentials, causing account lockouts.
* Find the computer responsible for the lockouts and verify if it exists on the domain.
* Monitor services that may be running with a user's credentials.
---
# 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/excessive-user-account-lockouts.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.