> 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/failed-login-for-locked-out-account.md).

# Failed Login For Locked-Out Account

### 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       | Stealth (TA0005)                                                                                            |
| ATT\&CK Technique    | Valid Accounts (T1078)                                                                                      |
| Severity             | Informational                                                                                               |

### Description

A locked-out user account (event ID 4725 or 4740) was used in a Kerberos TGT pre-authentication attempt.

### Attacker's Goals

Authenticate using the principal in the TGT, not knowing that it has been revoked.

### Investigative actions

* Check whether you have issues with your Cloud Identity Engine failing to sync data from Active Directory.
* Check whether the attempt to use the principals (user accounts) specified in the alert are legitimate. For example, a user or a script that was not updated that the account has been revoked.
* The lockout can be temporary, for example, in the case of too many login attempts, and may not be visible after the account was released.
* Search for Windows Event Log 4740 to ascertain whether the account was locked out during the time of the alert.


---

# 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/failed-login-for-locked-out-account.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.