> 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-enumeration.md).

# Okta account enumeration

### Synopsis

| Field                | Value                                          |
| -------------------- | ---------------------------------------------- |
| Activation Period    | 14 Days                                        |
| Training Period      | 30 Days                                        |
| Test Period          | 10 Minutes                                     |
| Deduplication Period | 1 Day                                          |
| Required Data        | Okta                                           |
| Detection Modules    | Identity Threat Module, SaaS Threat Detection  |
| ATT\&CK Tactic       | Discovery (TA0007), Credential Access (TA0006) |
| ATT\&CK Technique    | Account Discovery (T1087), Brute Force (T1110) |
| Severity             | Informational                                  |

### Description

Multiple distinct Okta accounts enumerated from the same source IP in a short period of time. This may indicate that an attacker is enumerating valid Okta accounts.

### Attacker's Goals

An adversary may enumerate valid Okta accounts in the organization, which can aid in follow-on behavior such as password spraying, spear-phishing or brute force attacks.

### Investigative actions

* Review the source IP and determine whether it is associated with legitimate users or known infrastructure.
* Investigate whether any of the enumerated users had a successful authentication from this IP.
* Check if the source IP is associated with an anonymized proxy or a rare country for the organization.

### Variations

<details>

<summary>Okta account enumeration from a risky IP</summary>

**Synopsis**

| Field             | Value                                          |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic    | Discovery (TA0007), Credential Access (TA0006) |
| ATT\&CK Technique | Account Discovery (T1087), Brute Force (T1110) |
| Severity          | Medium                                         |

**Description**

Multiple distinct Okta accounts experienced failed authentication attempts from a source IP flagged as risky (SPUR anonymous tunnel / known proxy/VPN operator, or an authentication from a country or ASN never seen in the organization), and at least one successful authentication. The combination of risky infrastructure with high-volume / partially successful enumeration is a strong indicator of a deliberate credential discovery attack.

**Attacker's Goals**

An adversary may enumerate valid Okta accounts in the organization, which can aid in follow-on behavior such as password spraying, spear-phishing or brute force attacks.

**Investigative actions**

* Review the source IP and determine whether it is associated with legitimate users or known infrastructure.
* Investigate whether any of the enumerated users had a successful authentication from this IP.
* Check if the source IP is associated with an anonymized proxy or a rare country for the organization.

</details>

<details>

<summary>Suspicious Okta account enumeration</summary>

**Synopsis**

| Field             | Value                                          |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic    | Discovery (TA0007), Credential Access (TA0006) |
| ATT\&CK Technique | Account Discovery (T1087), Brute Force (T1110) |
| Severity          | Low                                            |

**Description**

The enumeration was followed by at least one successful authentication. This may indicate a credential discovery or successful guessing attempt.

**Attacker's Goals**

An adversary may enumerate valid Okta accounts in the organization, which can aid in follow-on behavior such as password spraying, spear-phishing or brute force attacks.

**Investigative actions**

* Review the source IP and determine whether it is associated with legitimate users or known infrastructure.
* Investigate whether any of the enumerated users had a successful authentication from this IP.
* Check if the source IP is associated with an anonymized proxy or a rare country for the organization.

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