Tutorial: Configure Continuous Authentication for a Table

configure-ca-tutorial-table.md
Raw file

Procedure that describes end-to-end configuration of continuous authentication policy for a table and the impacts to the users due to the configuration changes.

Before you begin

  • Role required: ca_admin

    Note: You must elevate your role to ca_admin.

  • You must install the Zero Trust - Continuous Authentication (com.snc.zero_trust_continuous_authentication) to use CA, which requires a license.

  • Enable the Continuous Authentication (glide.zta.continuous_authentication.enabled) system property. For more information, see Continuous authentication system properties.

  • Activate the Integration - Multiple Provider Single Sign-On Installer (com.snc.integration.sso.multi.installer) plugin.

  • Understand the pre-work that is required before configuring CA for the instance. For more information, see Pre-work for Continuous Authentication.

Procedure

  1. Navigate to All > Continuous Authentication.

  2. Select Policies tab.

  3. Select New.

  4. On the form, fill in the fields:

Field

Description

Policy Name

Name of the policy

Description

Generic description to the policy

Select the resources

Select the Table.Note:

  • In this example, Incident table is selected. You can select as many tables as you need.
  • Table selected with metadata displays an error. You need to check if you actually want to restrict access to the metadata table, since it can impact configuration access to your users.
  • The sys_properties, sys_continuous_auth_policy, sys_user tables are excluded for CA and cannot be added to the CA policy configuration.
\[Omitted image "ca-policy.png"\] Alt text: CA Policy record
**Note:** You can use either of the login methods for the CA policy:

-   **SSO based login**: Specify the fields in the **Continuous Authentication** tab within the Identity Provider record and set the Identity Provider record as **Active**. \[Omitted image "ca-tab.png"\] Alt text: Continuous Authentication - tab information

    To know more about Identity Providers configuration, see [OIDC](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/create-OIDC-configuration-SSO.md) and [SAML](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/t_CreateASAML2Upd1SSOConfigMultiSSO.md).

-   **Non-SSO based login**: By default, if there are no Identity Providers with Continuous Authentication configuration, Multi-factor Authentication \(MFA\) is used as a login method. Make sure the MFA properties are Active and configured based on your requirement. To know more about MFA properties, see [Multi-factor Authentication system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/mfa-properties.md).
  1. Select Save & Activate.

Result

Based on the details provided for the configuration, CA policy is created with Access Control List (ACLs) for the selected table or data class. You can view the details of the ACLs that are created by selecting the View ACLs on the policy page.

[Omitted image "ca-acl-details.png"] Alt text: CA ACL details

The created CA policy prompts the user for authentication to access table (in this case Incident table) that you've protected using the policy. The users can select Authenticate option.

[Omitted image "ca-policy-enforced-tables.png"] Alt text: CA Policy enforced

Perform the authentication based on the following:

  • User who had performed local login to log in to the instance, is displayed with platform MFA for step-up authentication.

    [Omitted image "mobile-screen-mfa.png"] Alt text: MFA-SMS

  • User who had performed SSO login (OIDC or SAML) to log in to the instance is displayed with the SSO for re-authentication.

    [Omitted image "ca-sso-screen.png"] Alt text: SSO - Screen

After successful authentication the table is displayed.

[Omitted image "ca-incident-table-after-login.png"] Alt text: Incident table after successful login

A high assurance session is now established for the user. High assurance session is limited to the High Assurance session length (glide.zta.high_assurance.session.timeout) system property. If the high assurance session time exceeds the property length, the user is prompted for re-authentication or step-up authentication.

Related topics

Configure Continuous Authentication

High assurance session with continuous authentication

Exploring Continuous Authentication

Search documentation
Search document titles and file paths on the australia branch