--- sourceDocument: Australia Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # Exploring CA # Exploring Continuous Authentication {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](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 Exploring Continuous Authentication ServiceNow's Continuous Authentication (CA) is a security feature that re-verifies a user's identity throughout their session, enhancing security by adhering to a zero trust access model. It ensures that users are explicitly authenticated and authorized for every action, regardless of their initial login status. Show full answer Show less ## Key Features * **Step-Up Authentication:** Administrators can implement multi-factor authentication (MFA) or re-authentication when users access sensitive data, such as Personally Identifiable Information (PII). * **Policy Creation:** Security policies can be configured at both the table and data class level. * **Roles:** Specific roles are defined for managing CA, including CA Admin, Policy Admin, and Auditor, each with unique permissions for policy management and monitoring. * **Modules:** CA includes various modules such as Policies, Metrics, and System Properties for comprehensive management and customization. ## Key Outcomes Implementing Continuous Authentication provides enhanced security by continuously verifying user identities, significantly reducing the risk of account takeover. It allows organizations to enforce strict access controls, ensuring that sensitive data remains protected even during user sessions. ServiceNow's continuous authentication (CA) enables you to re-verify and authenticate a user if they access resources that are protected by you. ServiceNow's continuous authentication is a security mechanism designed to verify a user's identity not just at the initial login, but throughout the user's entire session. CA is built on ServiceNow's zero trust access security architecture that aims to enhance security by ensuring that the user remains who they claim to be, even after the initial authentication process. CA works on the following zero trust access principles: * Verify explicitly: No implicit trust for any user, device, or system within a network, regardless of location. Every user and device must be explicitly authenticated and authorized, regardless of location or past access. * Use least privilege access: Grant only the minimum access or permissions needed to perform specific tasks and limit potential damage from compromised accounts or systems." * Assume breach: Instead of relying only on prevention, assume breach and focus on proactive detection, containment, and response. {#explore-continuous-auth__ul_ufd_gj2_d2c} CA provides the ability to enforce step-up authentication or re-authentication based on the data users are accessing and activities they are performing​. It be opted by administrators for creating security policies at a table or data class level. You can enforce step-up authentication (MFA) or re-authentication (SSO - SAML or OIDC) within a logged-in session whenever there is an attempt by the user to access Personally Identifiable Information (PII) and sensitive data. Note: You must install the Zero Trust - Continuous Authentication (`com.snc.zero_trust_continuous_authentication`) for opting CA which requires a license. ## Benefits {#explore-continuous-auth__section_emj_sy5_xcc} Following are the some of the benefits of using CA: * Enhanced Security: By continuously verifying the user's identity, the system can detect and respond to potential security threats more quickly. * Reduced Risk of Account Takeover: Even if an attacker gains access to a user's session, continuous authentication can help prevent them from accessing confidential data. {#explore-continuous-auth__ul_vzs_5y5_xcc} ## Use cases {#explore-continuous-auth__section_kbv_lvd_pcc} Following are some of the use cases for using CA: * Enforce re-authentication before allowing access to sensitive data using different policies. * Enforce periodic re-authentication or step-up authentication using different policies: * Use re-authentication that can include IdP's MFA, IdP's SSO. * Use step up authentication with ServiceNow's MFA. {#explore-continuous-auth__ul_l1h_nvd_pcc} ## Roles in CA {#explore-continuous-auth__section_cmr_yvz_scc} CA has the following roles: * CA Admin (ca_admin): Ability to create, edit, and view CA policies. Configure CA properties and view dashboards (Metrics) of CA. * Policy Admin (ca_policy_admin): Ability to create, edit, and view CA policies.. * Auditor (ca_auditor): Ability to view dashboards (Metrics) of CA. And policies, and logs of CA. {#explore-continuous-auth__ul_j4k_nxj_zcc} To configure CA you must elevate your role to ca_admin and perform the policy configurations. Note: All these 3 roles are elevated roles. ## Modules in CA {#explore-continuous-auth__section_uyq_2pc_tcc} Following are the different modules within CA: * [Policies](https://www.servicenow.com/docs/G2MTr6WM1ID4IEJHRxJSrw "View the different continuous authentication policies that are created."): View the different continuous authentication policies that are created. * [Metrics](https://www.servicenow.com/docs/QyoqRdMBZB9Ol~RItpfEGA "View the different metrics for continuous authentication."): View the different metrics for continuous authentication for KPI purposes and understand the usage of CA within your organization. * [System Properties](https://www.servicenow.com/docs/Zn4qEA7TctbeuNFTRGgf0Q "Use system properties to enable and customize continuous authentication (CA) to meet your zero trust access security requirements."): Use system properties to enable and customize continuous authentication (CA) to meet your zero trust access security requirements. {#explore-continuous-auth__ul_gc2_gpc_tcc} **Related concepts** * [Policies](https://www.servicenow.com/docs/G2MTr6WM1ID4IEJHRxJSrw "View the different continuous authentication policies that are created.") * [Metrics](https://www.servicenow.com/docs/QyoqRdMBZB9Ol~RItpfEGA "View the different metrics for continuous authentication.") * [System properties](https://www.servicenow.com/docs/Zn4qEA7TctbeuNFTRGgf0Q "Use system properties to enable and customize continuous authentication (CA) to meet your zero trust access security requirements.") * [Pre-work for Continuous Authentication](https://www.servicenow.com/docs/6km49l37dEDySCckbBFWFQ "Ensure to perform the following pre-work before using Continuous Authentication (CA).") * [High Assurance session with Continuous Authentication](https://www.servicenow.com/docs/J~u3s5W8BAkvVYIplJLy8Q "Establish high assurance session for with ServiceNow's continuous authentication.") **Related tasks** * [Activating Continuous Authentication](https://www.servicenow.com/docs/aWiMDRbg3rP0fiWk9F1NzQ "For activating the Continuous Authentication feature on your instance, install the Zero Trust - Continuous Authentication (com.snc.zero_trust_continuous_authentication) plugin.") * [Configuring Continuous Authentication](https://www.servicenow.com/docs/pY~dSwjnvuBUwhvotVbznQ "Configure continuous authentication (CA) policies to re-authenticate the users if there's an attempt to access resources that are protected by you.")