Skip to content
Start with Identity
Concept

Authentication Policy

An authentication policy is an identity provider rule that decides which authentication methods a user must satisfy to reach a given application, based on conditions such as group membership, network location, device state and risk. It is where "require MFA" becomes specific: which factors count, for whom, for which app, and how recently.

Vendors name and scope it differently. In Okta Identity Engine, app sign-in policies "define how a user must authenticate to gain access to an app" using conditions like group, IP zone and risk level. In Microsoft Entra, Conditional Access combines conditions with an authentication strength, which "specifies which combinations of authentication methods users can use to access a resource", for example only phishing-resistant methods for a sensitive app. The practical point from SWI's Phishing-Resistant MFA Support Matrix 2026 is that 77 of 95 business SaaS apps (81.1%) offer SSO but cannot require phishing-resistant MFA themselves, so the IdP's authentication policy is the only place to enforce it. A policy that says "MFA required" without naming the method still lets an attacker pick the weakest factor the user has enrolled.

See also: conditional access, phishable MFA, step-up authentication, SSO enforcement, conditional access policies guide, MFA matrix

Last reviewed By SWI Community TeamSuggest a correctionHow we research