# Weak MFA Was Used To Successfully Sign In

Weak forms of multi-factor authentication (MFA) were used. Such methods could include SMS and voice calls, which are susceptible to attacks.

For Okta Identity Engine environments, accounts utilizing weak factors that are solely defined as recovery methods are excluded from this check.

#### **Recommended Actions**

Encourage your users to enroll and authenticate with more secure factors whenever possible. The National Institute of Standards and Technology (NIST) recommends using cryptographic solutions like Duo Security, Google Authenticator, Okta Verify, Microsoft Authenticator, or one-time passwords. If those methods aren't viable for your organization, consider tagging users with administrative privileges in critical services like Okta and Workday, and giving them physical authentication solutions like YubiKey.

#### **Compatibility**

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

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

[Duo](/integrations/duo-security-integration.md)

<figure><img src="/files/594ziiTcjLLNMd7DDcMa" 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-posture-management-insights/weak-mfa-was-used-to-successfully-sign-in.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.