> 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/a-user-observed-and-reported-unusual-activity-in-okta.md).

# A user observed and reported unusual activity in Okta

### 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  |
| Detector Tags        | Okta Audit Analytics    |
| ATT\&CK Tactic       | Initial Access (TA0001) |
| ATT\&CK Technique    | Valid Accounts (T1078)  |
| Severity             | Informational           |

### Description

A user observed and reported unusual activity in Okta.

### Attacker's Goals

An attacker tries infiltrating an Okta account to gain unauthorized access to valuable resources.

### Investigative actions

* Investigate the original event that was reported as suspicious.
* Contact the user and understand why he reported the activity as suspicious.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Follow further actions done by the account.

### Variations

<details>

<summary>Multiple users have reported the same suspicious activity</summary>

**Synopsis**

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

**Description**

Unusual activity in Okta reported about an IP not linked to an EDR agent, the operation is rare and flagged by multiple users.

**Attacker's Goals**

An attacker tries infiltrating an Okta account to gain unauthorized access to valuable resources.

**Investigative actions**

* Investigate the original event that was reported as suspicious.
* Contact the user and understand why he reported the activity as suspicious.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Follow further actions done by the account.

</details>

<details>

<summary>Unusual activity in Okta was reported by a user along with suspicious characteristics</summary>

**Synopsis**

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

**Description**

A user observed and reported unusual activity in Okta.

**Attacker's Goals**

An attacker tries infiltrating an Okta account to gain unauthorized access to valuable resources.

**Investigative actions**

* Investigate the original event that was reported as suspicious.
* Contact the user and understand why he reported the activity as suspicious.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Follow further actions done by the account.

</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-user-observed-and-reported-unusual-activity-in-okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.