--- sourceDocument: Zurich Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/platform-security Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # MFA enforcement timeline # MFA enforcement timeline {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of MFA enforcement timeline This content explains the multi-factor authentication (MFA) enforcement timeline for ServiceNow internal users logging in with local or LDAP authentication. It details the self-enrollment period for MFA setup, how enforcement occurs post-upgrade, and options for administrators to adjust timelines and messaging related to MFA enforcement. Show full answer Show less ## Key Features * **Self-enrollment period:** Eligible internal users have a default 30-day window to complete MFA setup after their first successful login. This period is controlled by the system property **glide.authenticate.multifactor.selfenrolmentperiod** and can be adjusted from 0 up to 90 days. * **Immediate enforcement after upgrade:** After 90 days from upgrading to Yokohama or later releases, new internal users logging in for the first time with local or LDAP authentication must complete MFA immediately without a self-enrollment window. This enforcement timing is governed by **glide.authenticate.multifactor.enforcement.maxrelaxationperiod**, which can be set up to 270 days. * **Admin control over enforcement timelines:** Administrators can customize the self-enrollment window and enforcement delay by updating the respective system properties to fit organizational security policies. * **User notifications:** End users receive informational messages on login and in their profiles about MFA enrollment requirements. Admin users see a distinct message until one admin acknowledges it by setting **glide.authenticate.multifactor.enforcement.acknowledged** to true. * **Control over messaging:** Admins can disable end-user MFA enrollment messages by setting **glide.authenticate.multifactor.enforcement.showuserinfomessage** to false and can stop admin informational messages by acknowledging the enforcement. * **Existing adaptive authentication policies:** If an instance already has an active MFA adaptive authentication policy, the default secure MFA enforcement policy does not override it. ## Key Outcomes * ServiceNow customers can ensure internal users comply with MFA requirements within a defined timeframe, enhancing security. * Administrators have flexibility to tailor MFA enforcement timelines and communication to align with their organizational needs. * Clear user messaging helps drive compliance without interrupting access during the self-enrollment period. * The enforcement mechanism integrates smoothly with existing adaptive authentication policies, avoiding conflicts. FAQ related to MFA enforcement timelines and why it's important. 1. When is MFA enforced?According to the MFA policy, eligible users who haven't completed the MFA setup has a 30-day self-enrollment period. The behavior is controlled using the system property `glide.authenticate.multifactor.self_enrolment_period`. The property's default value is 30 days. It can be updated to a maximum of 90 days. All internal users (users who don't have a `snc_external` role) logging in with local or LDAP authentication must set up MFA within 30 days of their first successful login. During this time, you can log in normally but see a message at the time of login to enroll in MFA. After 90 days of upgrading to Yokohama or a later release, if an internal user (user without the `snc_external` role) logs in with local or LDAP authentication for the first time, they'll be required to use MFA immediately. You don't have the 30-day MFA self-enrollment window. This period is governed by a system property:` glide.authenticate.multifactor.enforcement.max_relaxation_period`. The maximum value for this property is 270 days. 2. How can the MFA enforcement timeline adjusted? * By updating the value of the property `glide.authenticate.multifactor.self_enrolment_period`, admins can provide a smaller or larger self-enrollment window. Set the property value to 0. The users are required to complete the MFA setup after their first login attempt with local or LDAP login after upgrading to Yokohama or a later release. The maximum duration of the self-enrollment window can be 90 days. Property value set higher than 90 will be treated as 90. * By updating the value of the property `glide.authenticate.multifactor.enforcement.max_relaxation_period` admin can decide how many days post upgrade to the Yokohama or a later release you get the MFA self-enrollment window. {#faq-mfa-enforcement-timeline__ul_kpy_y1j_jdc} 3. How are end users informed about this upcoming change?End users performing local or LDAP authentication who will be enforced with MFA will see an information message after logging in. The same message is available when users visit their profile. {#faq-mfa-enforcement-timeline__table_ypx_dwf_b2c__entry__2} | On the User Profile | On Employee Service Center | |-|-| | | | [Table 1. Enforcement Message] {#faq-mfa-enforcement-timeline__table_ypx_dwf_b2c} This message won't appear for non-admin users performing SSO logins. The admin role will see a different information message after a successful login irrespective of the authentication method used for logging in. This message continues to be displayed until one of the admins acknowledges the update by setting the `glide.authenticate.multifactor.enforcement.acknowledged` property value to true. 4. How to turn off the message displayed to end users about completing the MFA setup when they log in?Admins can update the value of the `glide.authenticate.multifactor.enforcement.show_user_info_message` system property to false to turn off the MFA enrollment information message shown to end users after login. 5. How to turn off the message displayed to administrators about the MFA enforcement?The information message regarding MFA enforcement shown to admin users after login, stops appearing when one of the admins acknowledges it by updating the value of the `glide.authenticate.multifactor.enforcement.acknowledged` system property to true. 6. There's already an MFA policy defined using adaptive authentication based on the security needs of my organization in the instance. Is the policy impacted by the mandate?No, if the instance already has an active Adaptive authentication---MFA context policy, the new default secure MFA policy isn't enforced. If the instance had MFA property enabled (`glide.authenticate.multifactor`) but the MFA policy wasn't active, then the default secure MFA policy for enforcing MFA for all internal users (users who don't have `snc_external` role) performing user name and password-based local or LDAP login is enabled. {#faq-mfa-enforcement-timeline__ol_pfr_zfz_3dc}