> 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-user-account-unlock.md).

# Unusual user account unlock

### 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>Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)</p> |
| Detection Modules    | Identity Analytics                                                                                                            |
| ATT\&CK Tactic       | Initial Access (TA0001)                                                                                                       |
| ATT\&CK Technique    | Valid Accounts (T1078)                                                                                                        |
| Severity             | Informational                                                                                                                 |

### Description

A user unlocked an account. This user does not usually unlock user accounts.

### Attacker's Goals

An attacker may unlock a user account to gain unauthorized access.

### Investigative actions

* Investigate the associated authentication attempts and login failures (e.g. 4625, 4776 events).
* Check if the user is authorized to unlock accounts.
* Confirm that the user unlock was expected.
* Monitor services that may be running with a user's credentials, resulting in lockouts.

### Variations

<details>

<summary>Unusual sensitive user account unlock</summary>

**Synopsis**

| Field             | Value                   |
| ----------------- | ----------------------- |
| ATT\&CK Tactic    | Initial Access (TA0001) |
| ATT\&CK Technique | Valid Accounts (T1078)  |
| Severity          | Low                     |

**Description**

A user unlocked a sensitive account. This user does not usually unlock user accounts.

**Attacker's Goals**

An attacker may unlock a user account to gain unauthorized access.

**Investigative actions**

* Investigate the associated authentication attempts and login failures (e.g. 4625, 4776 events).
* Check if the user is authorized to unlock accounts.
* Confirm that the user unlock was expected.
* Monitor services that may be running with a user's credentials, resulting in lockouts.

</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-user-account-unlock.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.
