> 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/user-added-a-new-device-to-okta-verify-instance.md).

# User added a new device to Okta Verify instance

### 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                               |
| Detector Tags        | Okta Audit Analytics                                 |
| ATT\&CK Tactic       | Persistence (TA0003)                                 |
| ATT\&CK Technique    | Account Manipulation (T1098), Valid Accounts (T1078) |
| Severity             | Informational                                        |

### Description

The user has successfully registered a new device with the Okta Verify application.

### Attacker's Goals

Attackers may exploit the device registration process in Okta by registering unauthorized devices, thereby gaining access to sensitive resources and user accounts within an organization.

### Investigative actions

* Reach out to the user responsible for the device registration to confirm its legitimacy.
* Examine the user's actions preceding and following the activation of the alert.
* Assess the reputation of the IP address along with that of the Autonomous System Number (ASN).
* Make sure the IP address is not showing any abnormal activity.
* Monitor the activity from the new registered device and ensure that it matches the user's normal activity.

### Variations

<details>

<summary>Suspicious device enrollment to Okta</summary>

**Synopsis**

| Field             | Value                                                |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                                 |
| ATT\&CK Technique | Account Manipulation (T1098), Valid Accounts (T1078) |
| Severity          | Low                                                  |

**Description**

A new device was registered on Okta with suspicious characteristics, which increased the alert severity.

**Attacker's Goals**

Attackers may exploit the device registration process in Okta by registering unauthorized devices, thereby gaining access to sensitive resources and user accounts within an organization.

**Investigative actions**

* Reach out to the user responsible for the device registration to confirm its legitimacy.
* Examine the user's actions preceding and following the activation of the alert.
* Assess the reputation of the IP address along with that of the Autonomous System Number (ASN).
* Make sure the IP address is not showing any abnormal activity.
* Monitor the activity from the new registered device and ensure that it matches the user's normal activity.

</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/user-added-a-new-device-to-okta-verify-instance.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.