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

# Okta account unlock

### Synopsis

| Field                | Value                                         |
| -------------------- | --------------------------------------------- |
| Activation Period    | 14 Days                                       |
| Training Period      | 30 Days                                       |
| Test Period          | 1 Hour                                        |
| Deduplication Period | 3 Hours                                       |
| Required Data        | Okta Audit Log                                |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection |
| Detector Tags        | Okta Audit Analytics                          |
| ATT\&CK Tactic       | Initial Access (TA0001)                       |
| ATT\&CK Technique    | Valid Accounts (T1078)                        |
| Severity             | Informational                                 |

### Description

Okta user account was unlocked.

### Attacker's Goals

The attacker's goal is to gain unauthorized access to sensitive information or resources and to gain control over the locked account.

### Investigative actions

* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Examine the user's actions preceding and following the activation of the alert.
* Initiate contact with the user to verify the authenticity of the account unlock action.
* Check account the user successfully authenticated after the event.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.

### Variations

<details>

<summary>Okta account unlock with suspicious characteristics</summary>

**Synopsis**

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

**Description**

Okta user account was unlocked.

**Attacker's Goals**

The attacker's goal is to gain unauthorized access to sensitive information or resources and to gain control over the locked account.

**Investigative actions**

* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Examine the user's actions preceding and following the activation of the alert.
* Initiate contact with the user to verify the authenticity of the account unlock action.
* Check account the user successfully authenticated after the event.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.

</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/okta-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.