> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/non-human-identities-with-no-mfa-configured.md).

# Non-Human Identities with No MFA Configured

Detects non-human identities (NHIs), such as Service Accounts or Shared Mailboxes, that do not have Multi-Factor Authentication (MFA) enabled on all compatible identity sources.

MFA requires an account owner to provide something they know, like a password or PIN, or something they have, like an out-of-band device or a one-time password provider. Organizations should require all NHIs to configure and utilize MFA when accessing the system to protect these accounts against possible attacks, especially since they often have elevated privileges or access to critical resources.

NHIs will not fail this check if they fall within the grace period of 1 day(s).

You can add known NHI domains and logins to either an ignore or include list.

#### Recommended Actions

Enforce and enable MFA on non-human identities whenever possible. Appropriately categorize NHIs that intentionally lack MFA configuration for easy detection and consider implementing other solutions, such as expired passwords, to block access to NHIs that cannot have MFA configured.

Shared Mailboxes that are failing this check have interactive sign-in's enabled. We recommend blocking interactive sign-in's for these mailbox accounts to eliminate the need for a second form of authentication to secure them.

#### Default Check Settings

Grace period for new accounts (days): 1

#### Compatibility

Microsoft Entra ID, Okta, Duo, Google Workspace, GitHub


---

# 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://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/non-human-identities-with-no-mfa-configured.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.