---
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


---

# High assurance

# High assurance session with continuous authentication {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Establish a high assurance session with ServiceNow continuous authentication.

A high assurance session is a security measure to establish a secure and trusted connection with the identities (users) who access data and are verified with a high degree of confidence.

ServiceNow provides high assurance through robust authentication methods that enforce re-authentication using methods such as Multi-factor Authentication (MFA) and Single Sign On (SSO) while the users
try to access sensitive data.

When the user re-authenticates or performs step-up authentication (MFA), there's a high assurance session that is established, which provides the ability for the users to access the data protected by the continuous authentication (CA) administrator based on the
CA policy configuration.

Following are the re-authentication methods used to establish High-assurance based on the type of login:

* [High Assurance for SSO login](https://www.servicenow.com/docs/TkWIRdWigDu9pqJDTtb71Q "Establish a high assurance session for SSO login with ServiceNow continuous authentication.")
* [High Assurance for non-SSO login](https://www.servicenow.com/docs/O2UeynGhsVl6qbsude3GWQ "Establish a high assurance session for non-SSO logins (local or LDAP) with ServiceNow continuous authentication.")

{#high-assurance-ca__ul_ztz_kk2_ddc}

High assurance session created by the user is valid based on the High Assurance session length (glide.zta.high_assurance.session.timeout) determined by the CA administrator.

The high assurance session can be customized based on your requirements by setting the High Assurance system properties.
{#high-assurance-ca__table_tfb_2l2_ddc__entry__2}

| Field | Description |
|-|-|
| High Assurance session length (glide.zta.high_assurance.session.timeout) | Length of the high assurance session, after which end-users must re-authenticate. Default: 30 minutes. Note: The value must be between 1 and 480. |
| Default high-assurance session length upon login | Duration in minutes for the default high-assurance session length upon user login. Default value: 5 minutes. Note: This property is only applicable for non-SSO logins. |
| Configure end-user display message (glide.zta.high_assurance.session.message) | Message displayed to end-users for re-authentication. Default message: <kbd class="ph userinput">One or more resources require additional authentication due to a policy created by your administrator</kbd>. |
| Total times failed authentication before user account lock-out (glide.zta.high_assurance.session.max.login.failed_attempts) | Maximum failed authentication attempts before users are logged out. Note: The value must be between 3 and 10. |
[Table 1. High assurance system properties]

{#high-assurance-ca__table_tfb_2l2_ddc}

## High assurance session as a preemptive measure {#high-assurance-ca__section_hwl_g32_d2c}

Users who work with high privilege data such as financial transactions, government information, personally identifiable information (PII), can establish a high assurance session as a
preemptive measure to avoid frequent authentication notification during their logged in session.

High assurance session can be created by themselves. To create a high assurance session, select User ProfileProfile. In the Related Links section, select Create High-Assurance Session. Verify your identity to create a high assurance session.
**Related concepts**   

* [Exploring Continuous Authentication](https://www.servicenow.com/docs/_kJBRfk~J9nZC3TujI~svQ "ServiceNow's continuous authentication (CA) enables you to re-verify and authenticate a user if they access resources that are protected by you.")
* [Pre-work for Continuous Authentication](https://www.servicenow.com/docs/u_DQ6kp5x6tkpvHnAatKKw "Perform the following pre-work before using Continuous Authentication (CA).")  
**Related tasks**   

* [Configure Continuous Authentication](https://www.servicenow.com/docs/35wTHNadPCtuuTNpq7qEiA "Configure continuous authentication (CA) policies to re-authenticate the users if there's an attempt to access resources that are protected by you.")

*[\>]: and then