> 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-admin-privilege-assignment.md).

# Okta admin privilege assignment

### 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)                                  |
| ATT\&CK Technique    | Account Manipulation: Additional Cloud Credentials (T1098.001) |
| Severity             | Informational                                                  |

### Description

A user assigned admin privileges to a new user or group.

### Attacker's Goals

An attacker is attempting to gain access to sensitive information or systems, while privilege escalation involves their attempt to increase control and access within the system or network.

### 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.
* Analyze the actions carried out by the user responsible for granting permission.

### Variations

<details>

<summary>Abnormal Okta admin privilege assignment with suspicious characteristics</summary>

**Synopsis**

| Field             | Value                                                          |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004)                                  |
| ATT\&CK Technique | Account Manipulation: Additional Cloud Credentials (T1098.001) |
| Severity          | Low                                                            |

**Description**

A suspicious user assignment of admin privileges to a new user or group.

**Attacker's Goals**

An attacker is attempting to gain access to sensitive information or systems, while privilege escalation involves their attempt to increase control and access within the system or network.

**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.
* Analyze the actions carried out by the user responsible for granting permission.

</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-admin-privilege-assignment.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.
