---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Activate role based multi-factor authentication

# Activate role based multi-factor authentication {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use the glide.authenticate.multifactor property to enforce
role-based multi-factor authentication (MFA) for all users assigned to specific
roles.
The glide.authenticate.multifactor property enforces multi-factor authentication (MFA) based on the roles assigned to the user. When set to true, the platform enforces role-based MFA for all users whose roles are listed in the Multi-factor Criteria \[multi_factor_criteria\] table.

The Multi-factor Criteria \[multi_factor_criteria\] table defines which roles require MFA authentication. If a user has been assigned admin, security_admin or user_admin roles in the multi-factor roles list, MFA is enforced.

Enforcing MFA based on roles strengthens authentication security and aligns with best practices for protecting privileged accounts.

* Navigate to /sys_properties_list.do on the instance and verify that the glide.authenticate.multifactor property exists and is set to <kbd class="ph userinput">true</kbd>.

* Navigate to /multi_factor_criteria_list.do on the instance and verify that the Role based multi-factor authentication record has Active set to true.

{#sc-role-based-multi-factor-authentication__ul_a2y_wpm_hkc}

## More information {#sc-role-based-multi-factor-authentication__section_wc1_cqn_phc}

{#sc-role-based-multi-factor-authentication__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | * glide.authenticate.multifactor system property * Role base multi-factor authentication record on the Multi-factor Criteria \[multi_factor_criteria\] table {#sc-role-based-multi-factor-authentication__ul_fwy_gdh_p3c} |
| Configuration type | * System Properties (/sys_properties_list.do) * Multi-factor Criteria (/multi_factor_criteria_list.do) {#sc-role-based-multi-factor-authentication__ul_k4t_jdh_p3c} |
| Data type | * Boolean * Record configuration {#sc-role-based-multi-factor-authentication__ul_yvt_mdh_p3c} |
| Recommended value | * true * The Multi-factor Criteria \[multi_factor_criteria\] table record with sys_id <kbd class="ph userinput">d427668b73003300fdbd04fbc4f6a7b6</kbd> should be present, with the Active field selected. {#sc-role-based-multi-factor-authentication__ul_iwk_pdh_p3c} |
| Default value | * false * The Multi-factor Criteria \[multi_factor_criteria\] table record with sys_id <kbd class="ph userinput">d427668b73003300fdbd04fbc4f6a7b6</kbd> is shipped in a zbooted instance but is not set to active {#sc-role-based-multi-factor-authentication__ul_default_values} |
| Fallback value | * false * The Multi-factor Criteria \[multi_factor_criteria\] table record with sys_id <kbd class="ph userinput">d427668b73003300fdbd04fbc4f6a7b6</kbd> has the Active field unselected. {#sc-role-based-multi-factor-authentication__ul_mxl_tdh_p3c} |
| Category | [Authentication](https://www.servicenow.com/docs/SZIHG9SfxVh2_gyMf2ec2Q "The authentication category covers the main elements of modern authentication to confirm an entity and its claims are authentic and correct, resistant to impersonation and prevent interception of passwords.") |
| Security risk | * Severity score: 5.7 * CVSS rating: Medium * Security risk details: Enforcing MFA based on roles strengthens authentication security. This approach aligns with best practices for protecting privileged accounts. {#sc-role-based-multi-factor-authentication__ul_g1g_3sf_xwb} |
| Functional impact | Users assigned the admin, security_admin, or user_admin role will be prompted for a second authentication factor at login, and their password. Users without one of these roles are unaffected. |
| Dependencies and prerequisites | For role-based MFA enforcement to take effect, glide.authenticate.multifactor must be set to true and Multi-factor Criteria \[multi_factor_criteria\] must be active. |
[ ]

{#sc-role-based-multi-factor-authentication__table_ajc_b43_3kb}

