Disable weaker MFA factors in factor enrollment policies

An Okta admin can configure MFA at the organization level or application level. When MFA is enabled for either, end users are prompted to confirm their credentials with factors both when signing in to Okta and when accessing an application. Strong factors have better resistance to phishing and man-in-the-middle attacks.

HealthInsight: Why is this task recommended?


This feature is a HealthInsight security task. For more security recommendations from Okta, see HealthInsight.

Enable strong MFA factors to improve resistance to phishing and man-in-the-middle attacks.

Security impact: High

End-user impact: High

Okta recommends: Update factor enrollment policies based on the following:

  • Enable as primary factors: Okta Verify (with Push if available), Google Authenticator, WebAuthn
  • Do not enable as secondary factors: Security Questions and SMS/Email/Voice

 

End-user experience and impact


When signing in to their org, end users will be prompted to enroll in required factors and may enroll in any factors set to optional. Factors that have been disabled are not visible to end users.

 

Procedure


To enable strong factors for factor enrollment:

  1. From the admin console, navigate to Security > Multifactor.
  2. Click Factor Enrollment.
  3. Click Edit to modify the enrollment policy of your choice.
  4. Set the factor of your choice to Required, Optional, or Disabled.

    Blacklisting an IP zone from the admin console.

Note: The factor must be disabled in all factor enrollment policies before the factor type can be deactivated from the Factor Type tab.

Related topics