> 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-attempted-to-bypass-okta-mfa.md).

# A user attempted to bypass Okta MFA

### 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       | Credential Access (TA0006)                                                                    |
| ATT\&CK Technique    | Modify Authentication Process (T1556), Multi-Factor Authentication Request Generation (T1621) |
| Severity             | Low                                                                                           |

### Description

A user may have attempted to bypass Okta MFA.

### Attacker's Goals

An attacker is attempting to gain access to an account secured with MFA.

### Investigative actions

* Contact the user who attempted to bypass MFA and ensure the request was legitimate.
* Check if the user successfully authenticated after the event.

### Variations

<details>

<summary>A successful bypass of Okta MFA</summary>

**Synopsis**

| Field             | Value                                                                                         |
| ----------------- | --------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)                                                                    |
| ATT\&CK Technique | Modify Authentication Process (T1556), Multi-Factor Authentication Request Generation (T1621) |
| Severity          | Low                                                                                           |

**Description**

Suspicious MFA bypass attempt in Okta.

**Attacker's Goals**

An attacker is attempting to gain access to an account secured with MFA.

**Investigative actions**

* Contact the user who attempted to bypass MFA and ensure the request was legitimate.
* Check if the user successfully authenticated after the event.

</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-attempted-to-bypass-okta-mfa.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.
