Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
---
title: "Multi-factor authentication"
sidebarTitle: "MFA"
description: "Learn how to secure your Infisical account with MFA."
---
MFA requires users to provide multiple forms of identification to access their account.
## Email 2FA
If 2-factor authentication is enabled in the Personal settings page, email will be used for MFA by default.

## Mobile authenticator 2FA
You can use any mobile authenticator app (Authy, Google Authenticator, Duo, etc.) to secure your account. After registration with an authenticator, select **Mobile Authenticator** as your 2FA method.

## MFA for SSO logins
If your organization enforces MFA and your users sign in through [SAML or OIDC SSO](/documentation/platform/sso/overview), you can let the MFA they completed at your identity provider count, so Infisical doesn't prompt them again. Password, LDAP, and Google, GitHub, or GitLab logins are always prompted, so a break-glass account keeps Infisical MFA. The setting only takes effect while your organization enforces MFA, and then it also covers users who turned on MFA for their own account.
Infisical trusts a login only if the identity provider's signed response says MFA was completed:
- For OIDC, the ID token's `amr` claim includes `mfa`
- For SAML, the assertion's authentication context is a two-factor class, such as `MobileTwoFactorContract` or `SmartcardPKI`, or the MFA attribute includes `mfa` or `multipleauthn` (Infisical reads `authnmethodsreferences` for Entra ID and `amr` for every other provider)
Without a signal, Infisical prompts as usual. The `user-login` event in the [audit log](/documentation/platform/audit-logs#event-types) shows the values the identity provider sent, so you can see why a login was or wasn't prompted.
<Steps>
<Step>
Configure your identity provider to send the signal. Okta OIDC and Entra ID send it without extra configuration. For Okta SAML, add an attribute statement named `amr` with the value `session.amr`, as described in [Okta SAML](/documentation/platform/sso/okta).
</Step>
<Step>
In your organization, go to **Settings** > **Security** and turn on **Enforce MFA**.
</Step>
<Step>
Go to **Settings** > **Single Sign-On (SSO)** and, in the **Enforcement** card, turn on **Trust IdP MFA**.
</Step>
</Steps>
<Note>
If your identity provider lists the methods under another name, change **MFA claim name** in your OIDC configuration or **MFA attribute name** in your SAML configuration. If it uses other values or authentication contexts for MFA, add them under **Additional MFA claim values** or **Additional MFA authentication contexts**.
</Note>
## Entra ID MFA
<Note>
Before proceeding make sure you've enabled [SAML SSO for Entra ID](./sso/azure).
We also encourage you to have your team download and setup the
[Microsoft Authenticator App](https://www.microsoft.com/en-us/security/mobile-authenticator-app) prior to enabling MFA.
</Note>
<Steps>
<Step title="Open your Infisical Application in the Microsoft Entra Admin Center">

</Step>
<Step title="Tap on Conditional Access under the Security Tab">

</Step>
<Step title="Tap on Create New Policy from Templates">

</Step>
<Step title="Select Require MFA for All Users and Tap on Review + Create">

<Note>
By default all users except the configuring admin will be setup to require
MFA. Microsoft encourages keeping at least one admin excluded from MFA to
prevent accidental lockout.
</Note>
</Step>
<Step title="Set Policy State to Enabled and Tap on Create">

</Step>
<Step title="MFA is now Required When Accessing Infisical">

<Note>
If users haven't setup MFA for Entra / Azure they will be prompted to do
so at this time.
</Note>
</Step>
</Steps>