> 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-api-token-created.md).
# Okta API Token Created
### 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 | Privilege Escalation (TA0004), Execution (TA0002), Persistence (TA0003) |
| ATT\&CK Technique | Access Token Manipulation: Make and Impersonate Token (T1134.003), Command and Scripting Interpreter: Cloud API (T1059.009), Account Manipulation: Additional Cloud Credentials (T1098.001) |
| Severity | Informational |
### Description
A user created a new API token in Okta.
### Attacker's Goals
An attacker's goal is to gain unauthorized access, compromise user accounts, and perform malicious actions within an organization's systems, potentially leading to data breaches, account takeovers, and the escalation of privileges.
### Investigative actions
* Review the actions taken by the user that created the token.
* Follow the operations made using this API token by the ID token.
* Contact the user who created the API token and ensure that the API token is needed.
### Variations
An Okta API token was generated with suspicious characteristics
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004), Execution (TA0002), Persistence (TA0003) |
| ATT\&CK Technique | Access Token Manipulation: Make and Impersonate Token (T1134.003), Command and Scripting Interpreter: Cloud API (T1059.009), Account Manipulation: Additional Cloud Credentials (T1098.001) |
| Severity | Low |
**Description**
A user created a new API token in Okta with suspicious conditions.
**Attacker's Goals**
An attacker's goal is to gain unauthorized access, compromise user accounts, and perform malicious actions within an organization's systems, potentially leading to data breaches, account takeovers, and the escalation of privileges.
**Investigative actions**
* Review the actions taken by the user that created the token.
* Follow the operations made using this API token by the ID token.
* Contact the user who created the API token and ensure that the API token is needed.
---
# 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-api-token-created.md?ask=&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.