> 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-reset-password-attempt.md).

# Okta account reset password attempt

### Synopsis

| Field                | Value                                         |
| -------------------- | --------------------------------------------- |
| Activation Period    | 14 Days                                       |
| Training Period      | 30 Days                                       |
| Test Period          | 1 Hour                                        |
| Deduplication Period | 1 Day                                         |
| 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

A user used a weak factor to reset their Okta password.

### Attacker's Goals

The attacker might deceive the victim into resetting their password, a common tactic in account takeover schemes.

### Investigative actions

* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Reach out to the user to confirm the legitimacy of the recent password reset activity.
* Examine the IP address and assess its reputation.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.

### Variations

<details>

<summary>Suspicious Okta account reset password attempt</summary>

**Synopsis**

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

**Description**

A user used a weak factor to reset their Okta password.

**Attacker's Goals**

The attacker might deceive the victim into resetting their password, a common tactic in account takeover schemes.

**Investigative actions**

* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Reach out to the user to confirm the legitimacy of the recent password reset activity.
* Examine the IP address and assess its reputation.
* 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-reset-password-attempt.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.