> 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/potential-okta-access-limit-breach.md).

# Potential Okta access limit breach

### Synopsis

| Field                | Value                                                |
| -------------------- | ---------------------------------------------------- |
| Activation Period    | 14 Days                                              |
| Training Period      | 30 Days                                              |
| Test Period          | N/A (single event)                                   |
| 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       | Collection (TA0009), Initial Access (TA0001)         |
| ATT\&CK Technique    | Automated Collection (T1119), Valid Accounts (T1078) |
| Severity             | Informational                                        |

### Description

A user surpassed Okta's rate limit, leading to an access limit violation. This could suggest a potential account takeover attempt.

### Attacker's Goals

An adversary may attempt to use a compromised account in an unusual way to harvest as much data as possible, which could result in exceeding the access limit policy.

### Investigative actions

* Reach out to the user responsible for the alert to confirm the legitimacy of the activity.
* Examine the user's actions preceding and following the activation of the alert.
* Investigate abnormal logins, reported suspicious activities, new processes run, and recent configuration changes for any indicators of potential compromise.
* Assess the reputation of the IP address along with that of the Autonomous System Number (ASN).

### Variations

<details>

<summary>A breach in access limits within Okta, accompanied by suspicious characteristics</summary>

**Synopsis**

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

**Description**

The user exceeded the access threshold in Okta, triggering a violation alert.

**Attacker's Goals**

An adversary may attempt to use a compromised account in an unusual way to harvest as much data as possible, which could result in exceeding the access limit policy.

**Investigative actions**

* Reach out to the user responsible for the alert to confirm the legitimacy of the activity.
* Examine the user's actions preceding and following the activation of the alert.
* Investigate abnormal logins, reported suspicious activities, new processes run, and recent configuration changes for any indicators of potential compromise.
* Assess the reputation of the IP address along with that of the Autonomous System Number (ASN).

</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/potential-okta-access-limit-breach.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.