# Weak MFA Manually Activated and Utilized

Alerts on successful access via a newly registered SMS factor (that was not configured by the end user directly). A common account takeover pattern adversaries use involves leveraging social-engineering techniques to fool service desk representatives into changing a targeted account's MFA method to a factor that is controlled by the adversary, such as an SMS phone number.

#### **Recommended Actions**

Confirm with the end user that they had requested a change to their MFA and that this is a phone number that they recognize.

#### **Default Check Settings**

Evaluation period days: 7

Exclude good known IPs: false

#### **Compatibility**

[Okta](/integrations/okta-data-integration.md)

[Microsoft Entra ID](/integrations/azure-active-directory-integration.md)

<figure><img src="/files/FPBgNLb5BhFNU5x1jt2K" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.oort.io/understanding-check-failures/oort-insights/identity-threat-detection-insights/weak-mfa-manually-activated-and-utilized.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.