--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-xanadu-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zx bundleId : - delta3zx --- # Combined Configuration Compliance release notes for upgrades from Xanadu to Zurich # Combined Configuration Compliance release notes for upgrades from Xanadu to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 19 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 Combined Configuration Compliance Release Notes for Upgrades from Xanadu to Zurich This consolidated release note provides key information for ServiceNow customers upgrading Configuration Compliance from the Xanadu through Yokohama to the Zurich release. It summarizes new features, changes, deprecations, and upgrade guidance essential for maintaining compliance and optimizing vulnerability and remediation workflows. Show full answer Show less The document emphasizes preparation tasks, highlights integration changes especially with Wiz and third-party vulnerability tools, and introduces configuration improvements to enhance visibility, automation, and performance. ## Important Upgrade Information * If not upgrading to Unified Security Exposure Management (USEM), install Configuration Compliance versions below v30.x for compatibility with supported third-party integrations. * The Wiz Missing Assets table is deprecated; after upgrading to version 1.1, existing Wiz integrations must be backdated by three days and rerun to ensure data consistency. * Refer to the Vulnerability Response Compatibility Matrix and Release Schema Changes for detailed compatibility and integration support with Zurich. ## New Features and Enhancements * **Wiz Integration Enhancements:** Ability to identify and select Wiz Resource Types for import, activation of default Wiz Backfill Integrations for missing assets, and improved import of host test results and issues. * **Properties Module:** Introduced a new Properties module under Administration to allow direct editing of system properties from the interface for easier configuration management. * **Flexible Duration Calculations:** Customize calculation basis for Age and Age Closed durations of test results using Created, Opened, or First Found dates. * **Qualys Test Group Association:** Enable association of Qualys Tests with Test Groups to differentiate test results sharing the same Test ID but belonging to different groups. * **Remediation Target Date Customization:** Configure remediation task target dates calculated relative to the Last Opened date for improved scheduling accuracy. * **Workspace Enhancements:** * Automatic opening of search results in Vulnerability Manager or IT Remediation Workspaces based on user roles. * Ability to hide record counts on list views for improved performance. * Enable automatic refresh of Home page dashboard widgets in Vulnerability Manager Workspace. * Bulk edit capabilities for test results including assignment, exception requests, and marking false positives. * Re-evaluate remediation properties (assignments, tasks, exceptions, risk scores) in bulk. * Visibility of CI compliance and test results compliance percentages on Test Groups. * Control import of test results for Qualys Test Groups within the workspace. * **Remediation Task Rule Execution Modes:** Introduced "Match First" mode to apply only the first matching remediation rule during ingestion for clearer task assignment, alongside the existing "Match All" mode. * **Optimized Tenable.io Integration:** Replaced the single Compliance Results integration with separate Fixed and Open Compliance Results integrations to improve ingestion performance and scalability. * **Unified Microsoft Defender Integration:** Consolidated Microsoft Defender for Cloud and Threat and Vulnerability Management plugins into a single integration with added container image vulnerability ingestion. * **Qualys API Upgrades:** Support for newer API versions, additional data fields including vulnerability detection source and cloud metadata, and a new parameter to select API versions for PCRS integrations. * **Test Result Granularity:** Configure Tenable and Qualys Configuration Test Results to split into unique findings per instance, enhancing visibility into individual patching efforts. * **Improved State Management:** Enhanced accuracy and automation in remediation task state transitions, including handling mixed item states and false positives based on scanner results. * **UI Improvements:** Limit maximum rows in related lists to improve readability and system performance. * **Risk Score Tracking:** Optionally log risk score changes in work notes for auditability. ## Changes and Deprecated Features * Deprecated removal of "Reason" field and "Close" button for remediation tasks across classic UI and workspaces. * Deprecated the privilege for admins to delete test results; now controlled by a dedicated granular role. * Deprecated the Wiz Missing Assets table and the old "isignored" column replaced by "isresultignored". * Backfill integrations for Wiz are enabled by default and will become unnecessary after data backdating and rerunning integrations. ## Activation and Installation Configuration Compliance and related third-party integrations are available through the ServiceNow Store. Customers should request installation or upgrades via the store and review the cumulative version history for detailed version-specific notes. ## Additional Information for Customers * No new browser or accessibility requirements were introduced in these releases, though the new Coral theme includes a dark mode option to enhance usability. * Quick Start Tests are available after upgrades or new deployments to verify Configuration Compliance functionality; customers with customizations should adapt these tests accordingly. * For customers planning to upgrade to Unified Security Exposure Management (USE Consolidated page of all release notes for Configuration Compliance from Xanadu to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Configuration Compliance release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Zurich. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Configuration Compliance to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-configurationcompliance-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Upgrade information : If you are currently using Configuration Compliance, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Configuration Compliance and for upgrades to supported third-party integration applications. The Missing Assets \[sn_vul_wiz_missing_asset\] table used for storing assets imported by the backfill integrations for the [Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) is deprecated. If you are currently using the Vulnerability Response with Wiz integrations, after updating to version 1.1, you must backdate any of your existing Wiz primary integrations by three days and run them. Please review more information about the Wiz integration at [SecOps articles on the Security Operations Community](https://www.servicenow.com/community/secops-articles/announcement-wiz-integration-with-servicenow-secops/ta-p/3325055). For more information about the released versions of the Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Zurich release, see the [Vulnerability Response Compatibility Matrix and Release Schema Changes \[KB0856498\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base. | [ ] ## New features Between your current release family and Zurich, new features were introduced for Configuration Compliance. {#dfrn3-configurationcompliance-summary__entry__10} | Release | Release notes | |-|-| | Xanadu | [Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=xanadu&ft:locale=en-US) : Identify the Resource Types (assets) reported by Wiz in your environment on the Wiz Integration Resource Type configuration page in your ServiceNow AI Platform instance that you want to import. The Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration. [Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=xanadu&ft:locale=en-US) : Retrieve and process data stored on the Wiz Missing Assets \[sn_vul_wiz_missing_asset\] table for missing assets that were not processed by the primary compliance integrations with specialized Wiz Backfill Integrations. * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration The Wiz Backfill Integrations are activated by default. [Wiz Host Test Result Vulnerability Integration](https://www.servicenow.com/docs/access?context=wiz-host-test-result-tab-filters&family=xanadu&ft:locale=en-US) : Import test results associated with the resource type, VIRTUAL MACHINE with the Wiz Host Test Result Vulnerability Integration. This integration is activated by default. [New Properties module](https://www.servicenow.com/docs/access?context=installed-with-config-compliance&family=xanadu&ft:locale=en-US) : Starting with v15.1 of Configuration Compliance, a new Properties module has been added to the navigation menu under the Administration section. This module enables direct modification of the values, offering a user-friendly method to manage and update system properties directly from the interface. [Customize the calculation of Age and Age closed durations of a test result](https://www.servicenow.com/docs/access?context=view-vuln-config-compl-test-results&family=xanadu&ft:locale=en-US) : Starting with v15.1 of Configuration Compliance, the Age and Age Closed durations of a test result can be configured to be calculated from the date in the Created, Opened, or First Found fields. [Associating a Qualys Test with its Test Group](https://www.servicenow.com/docs/access?context=Qualys-cc-Integration&family=xanadu&ft:locale=en-US) : You can associate a Qualys Test with its Test Group by enabling the **sn_vulc.add_policy_as_key** system property. This helps you to identify the Test Group to which a Test Result belongs to and differentiate Test records with the same Test id that are associated with different Test Groups. [Calculate the remediation target date of a remediation task with respect to the Last Opened date](https://www.servicenow.com/docs/access?context=cc-remed-target-rules&family=xanadu&ft:locale=en-US) : Starting with v15.1 of Configuration Compliance, you can customize the calculation of the remediation target date of a remediation task to be calculated with respect to the Last Opened date. Open the search results in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-change-app-scope-search&family=xanadu&ft:locale=en-US) or [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-change-app-scope-search&family=xanadu&ft:locale=en-US) rather than the Classic UI : Starting with v24.0.6 of Vulnerability Response, automatically open your search results in the Vulnerability Manager Workspace or IT Remediation Workspace rather than the Classic UI, by adjusting the application scope in the unified navigation bar to Vulnerability Manager Workspace or IT Remediation Workspace respectively. These application scopes are available to you based on your assigned role. [Vulnerability Manager Workspace access to the sn_vulc.read role](https://www.servicenow.com/docs/access?context=installed-with-config-compliance&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, as a user with the sn_vulc.read role, you can view the test results in the Vulnerability Manager Workspace. Navigate to the List page in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-list-page&family=xanadu&ft:locale=en-US) or [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-list-page&family=xanadu&ft:locale=en-US) by selecting the links from the All menu : Starting with v24.0.6 of Vulnerability Response, when you enable the 'sn_vul_cmn_ws.navigate_to_workspace' system property, selecting predefined filter links in the Configuration Compliance module from the 'All' menu will automatically open these links in the List page in the Vulnerability Manager Workspace or IT Remediation Workspace based on your role. Hide the record count on the lists in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-list-page&family=xanadu&ft:locale=en-US) and [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-list-page&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, you can hide the record count on the lists in the List page of the Vulnerability Manager Workspace and IT Remediation Workspace by adding the table names to the glide.ui.list.seismic.omit.count system property. [Enable automatic refresh for the Home page dashboard in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-home-page-create-filter&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, when creating and editing filters on the Configuration Test Results tab on the Home page of the Vulnerability Manager Workspace, you can configure the widgets to refresh automatically. Otherwise, you can manually refresh the widgets by selecting the Refresh button on the Configuration Test Results tab. [Re-evaluating remediation properties for all records in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-reevaluate-remediation-parameters&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, you can evaluate the remediation properties for all the test results from the Configuration Test Results list by selecting the All items in the Record selection field of the Re-evaluate remediation properties modal in the Vulnerability Manager Workspace. [Re-evaluate remediation properties for test results in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-reevaluate-remediation-parameters&family=xanadu&ft:locale=en-US) : Select the test results conditionally for reevaluating the following remediation properties in Vulnerability Manager Workspace: * Assignments * Remediation tasks * Remediation target date * Exceptions (Vulnerability Response v24.0.6) * Risk score [Using bulk edit for test results in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-bulk-edit-overview&family=xanadu&ft:locale=en-US) : Perform the following tasks on multiple test results simultaneously or a remediation task in Vulnerability Manager Workspace: * [Assign test results to an assignment group for remediation](https://www.servicenow.com/docs/access?context=vmws-bulk-edit-assign&family=xanadu&ft:locale=en-US). * [Request an exception in bulk](https://www.servicenow.com/docs/access?context=vmws-bulk-edit-request-exception&family=xanadu&ft:locale=en-US). * [Mark test results as false positive in bulk](https://www.servicenow.com/docs/access?context=vmws-bulk-edit-request-false-positive&family=xanadu&ft:locale=en-US). [Populating additional information for the test results](https://www.servicenow.com/docs/access?context=view-vuln-config-compl-test-results&family=xanadu&ft:locale=en-US) : The Age, Age closed, Closed date, Active, and Last open date columns have been added in the test results table.The test results that aren't in the Closed state are marked as true in the Active field. The Active field replaces the Result and State fields in the filter conditions of the default-saved filters across the All menu, Configuration Compliance Overview, Unified, Cybersecurity Executive, and Health dashboards. [CI compliance and test results compliance on a Test Group in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-list-page&family=xanadu&ft:locale=en-US) : View the percentage of CI compliance and test results compliance on a Test Group in Vulnerability Manager Workspace. [Enabling or disabling the test results import for a Qualys test group in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=enable-disable-imports-qualys&family=xanadu&ft:locale=en-US) : Enable or disable the import of test results for a Qualys test group in Vulnerability Manager Workspace. [Updating Rollup weights section in the roll up calculators](https://www.servicenow.com/docs/access?context=v11create-rollup-calc&family=xanadu&ft:locale=en-US) : Other than the script format, an alternative approach of adding the weights in the Rollup Weights section for the rollup calculators has been introduced. [Percentage test result compliance in the Discovered Items table](https://www.servicenow.com/docs/access?context=discovered-items-fields&family=xanadu&ft:locale=en-US) : The percentage of test results compliance of a CI is populated in the % Test Results Compliance column of the Discovered Item. To populate this value in the % Test Results Compliance column, set `calcTRComplianceForCI` to `true` in the Update remediation metrics scheduled job. [Quick Start Tests for Configuration Compliance](https://www.servicenow.com/docs/access?context=available-quick-start-tests&family=xanadu&ft:locale=en-US) : After upgrades and deployments of new applications or integrations, run quick start tests to verify that Configuration Compliance works as expected. If you customized Configuration Compliance, copy the quick start tests and configure them for your customizations. | | Yokohama | [Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=yokohama&ft:locale=en-US) : Identify the Resource Types (assets) reported by Wiz in your environment on the Wiz Integration Resource Type configuration page in your ServiceNow AI Platform instance that you want to import. The Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration. [Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=yokohama&ft:locale=en-US) : Retrieve and process data stored on the Wiz Missing Assets \[sn_vul_wiz_missing_asset\] table for missing assets that were not processed by the primary compliance integrations with specialized Wiz Backfill Integrations. * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration The Wiz Backfill Integrations are activated by default. [Wiz Host Test Result Vulnerability Integration](https://www.servicenow.com/docs/access?context=wiz-host-test-result-tab-filters&family=yokohama&ft:locale=en-US) : Import test results associated with the resource type, VIRTUAL MACHINE with the Wiz Host Test Result Vulnerability Integration. This integration is activated by default. [Create remediation tasks manually in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-create-remediation-task&family=yokohama&ft:locale=en-US) : With the sn_vulc.admin role, you can create remediation tasks manually by selecting some or all the records in the Configuration Test Results lists in the Vulnerability Manager Workspace. These records are grouped into one or more remediation tasks according to the grouping criteria selected while creating remediation tasks. [Create remediation tasks manually in the IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-create-remediation-task&family=yokohama&ft:locale=en-US) : With the sn_vulc.remediation_owner role, you can create remediation tasks manually by selecting desired records in the Configuration Test Results lists in the IT Remediation Workspace. These records are grouped into one or more remediation tasks according to the grouping criteria selected while creating remediation tasks. [View risk score details of a test result in the Work notes section](https://www.servicenow.com/docs/access?context=config-compliance-calculator-rules&family=yokohama&ft:locale=en-US) : Starting with v15.2.1 of Configuration Compliance, the system property sn_sec_cmn.risk_score_changes_add_worknotes is inactive by default. If you enable it, only then you can see all the changes related to the risk score of a test result in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. [Quick Start Tests for Configuration Compliance](https://www.servicenow.com/docs/access?context=available-quick-start-tests&family=yokohama&ft:locale=en-US) : After upgrades and deployments of new applications or integrations, run quick start tests to verify that Configuration Compliance works as expected. If you customized Configuration Compliance, copy the quick start tests and configure them for your customizations. | | Zurich | [Remediation task rule execution mode](https://www.servicenow.com/docs/access?context=sem-grouping-multiple-findings-remediation-tasks-processing&family=zurich&ft:locale=en-US) : You can now choose how remediation task rules are evaluated during ingestion. The new Match First execution mode evaluates rules sequentially and applies only the first matching rule, assigning each finding to exactly one remediation task. The default Match All mode continues to evaluate all applicable rules. [Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=zurich&ft:locale=en-US) : Starting with v 6.1.3, the Tenable.io Compliance Results Integration is replaced by the Tenable.io Fixed Compliance Results Integration and Tenable.io Open Compliance Results Integration. Compliance results are now imported based on their status, optimizing ingestion performance and scalability for environments with large volumes of compliance data while keeping remediation and compliance tracking aligned with the current state of findings. [Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=ms-defender-sem&family=zurich&ft:locale=en-US) : The Microsoft Defender for Cloud and Microsoft Defender Threat and Vulnerability Management (MS TVM) plugins are now consolidated into a single plugin: Microsoft Defender Integration for Security Exposure Management. This consolidation deprecates the standalone Microsoft Defender for Cloud plugin. The unified plugin also introduces container image vulnerability ingestion from Microsoft Defender for Cloud, creating Container Vulnerable Items on your instance. A guided migration path is available to transfer existing data from the deprecated applications to the unified plugin. [Qualys Integration -- API enhancements](https://www.servicenow.com/docs/access?context=qualys-rest-messages-cc&family=zurich&ft:locale=en-US) : Qualys Integration has been upgraded to support newer Qualys API versions across Host Detection, Host List, Knowledgebase, PC Controls, PC Policies, and PCRS integrations. The integrations now ingest additional data fields, including vulnerability detection source, authentication privilege status, active status for controls and policies, and cloud metadata, giving you better visibility into your vulnerability and compliance data. Use the new `posture_api_version` integration instance parameter to choose between the default v2.0 APIs or the newer v5.0 streaming APIs for the PCRS Policy Host and PCRS Test Results integrations. [Enhancements to the Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) : The Missing Assets \[sn_vul_wiz_missing_asset\] is deprecated. After updating to version 1.1, you must backdate your existing primary Wiz integrations by three days and run them. The backfill integrations are activated by default. After you backdate and run your integrations, the following backfill integrations are no longer required: * Host Vulnerability Backfill Integration * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration The \[is_ignored\] column is deprecated for the Host Test Results and Test Results Integrations. This column was replaced by the \[is_result_ignored\] column. Source severity is mapped to the Priority column on the Test Results \[sn_vulc_result\] table. Resource type filters are on the Test Results, Issues, and Host Test Results configuration tabs on the Wiz Configuration page. You can add any of the resource types listed. Note: If you configure resource types on the Resource Type Configuration tab, and you choose to configure parameters on the integration instance records, your configurations on integration instance take precedence over your settings on the Resource Type Configuration tab. See [Identify Wiz Resource types](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=zurich&ft:locale=en-US) for more information. Additional attributes imported from Wiz that are not stored in the Discovered items \[sn_sec_cmn_src_ci\] table are stamped with Asset Attributes in this table. Test results from the Host misconfiguration integration are classified as result type 'host_misconfiguration'. Data for resources that have the validated_at_runtime flag set to 'yes' is imported and populated on detections. The is_ignored column is deprecated on the Host Test Results and Test Results Integrations. This column was replaced by the is_result_ignored column. The CMDB internet-facing field on the discovered item is mapped to Limited Internet Exposure on findings. Column length for the descriptions in the Host Vulnerability import table has been increased. [Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=zurich&ft:locale=en-US) : Identify the Resource Types (assets) reported by Wiz in your environment on the Wiz Integration Resource Type configuration page in your ServiceNow AI Platform instance that you want to import. The Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration. [Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=zurich&ft:locale=en-US) : Retrieve and process data stored on the Wiz Missing Assets \[sn_vul_wiz_missing_asset\] table for missing assets that were not processed by the primary compliance integrations with specialized Wiz Backfill Integrations. * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration The Wiz Backfill Integrations are activated by default. [Wiz Host Test Result Vulnerability Integration](https://www.servicenow.com/docs/access?context=wiz-host-test-result-tab-filters&family=zurich&ft:locale=en-US) : Import test results associated with the resource type, VIRTUAL MACHINE with the Wiz Host Test Result Vulnerability Integration. This integration is activated by default. [Qualys parameter to ignore passed test results](https://www.servicenow.com/docs/access?context=Qualys-cc-Integration&family=zurich&ft:locale=en-US) : Starting with v15.2.5 of Configuration Compliance, the ignore_passed_result integration instance parameter for the Qualys Integration for Security Operations has been added. This parameter is set to false by default so that passed test results imported by Qualys are not ignored. Set the parameter to true to ignore passed test results on import. Note: If activated, this parameter does not impact closure of the test results. For example, if you activate the parameter, and a failed test result from a previous import has since passed, it will be closed correctly. [The Wiz Configuration Compliance (Test Results) and Issues Integrations](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) : * Import configuration test results with the Wiz Configuration Compliance Integration (Wiz Test Results) to detect non-compliant cloud configurations. Findings are mapped to cloud test results (CTRs) in the Configuration Compliance application to help you enforce security policies and standards across your cloud environment. * Import data with the Wiz Issues Integration that can help you identify assets that are involved in toxic combinations of vulnerabilities and misconfigurations. These findings are also mapped to CTRs with Wiz Issues labeled as the source to help you track and remediate assets that may pose complex multi-vector risks. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Configuration Compliance features. {#dfrn3-configurationcompliance-summary__entry__18} | Release | Release notes | |-|-| | Xanadu | [Test result and remediation task state transitions](https://www.servicenow.com/docs/access?context=spc-findings-state-transition&family=xanadu&ft:locale=en-US) : Enhancements to policy audits for Security Posture Control verify that retired assets are not evaluated by activated policies. If the state of an asset transitions from Retired back to Active, it is included in the next policy evaluation. [Non-zero risk score for passed test results](https://www.servicenow.com/docs/access?context=cc-rollupcalc-example&family=xanadu&ft:locale=en-US) : The risk score is calculated for passed test results to determine how much risk is mitigated. [Deprecated the privilege to delete a test result for the Admin role](https://www.servicenow.com/docs/access?context=installed-with-config-compliance&family=xanadu&ft:locale=en-US) : As an admin with the sn_vulc.admin role, you can't delete a test result. This privilege is now given to the sn_vulc.delete granular role. [Updates to the Risk Score calculation for a Remediation Task](https://www.servicenow.com/docs/access?context=v11create-rollup-calc&family=xanadu&ft:locale=en-US) : The average risk score of all the test results in a Remediation Task is considered for the risk score calculation of a Remediation task. | | Yokohama | No updates for this release. | | Zurich | [Remediation task rule execution mode](https://www.servicenow.com/docs/access?context=sem-grouping-multiple-findings-remediation-tasks-processing&family=zurich&ft:locale=en-US) : You can now choose how remediation task rules are evaluated during ingestion. The new Match First execution mode evaluates rules sequentially and applies only the first matching rule, assigning each finding to exactly one remediation task. The default Match All mode continues to evaluate all applicable rules. [Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=zurich&ft:locale=en-US) : Starting with v\[VERSION\], the Tenable.io Compliance Results Integration is replaced by the Tenable.io Fixed Compliance Results Integration and Tenable.io Open Compliance Results Integration. Compliance results are now imported based on their status, optimizing ingestion performance and scalability for environments with large volumes of compliance data while keeping remediation and compliance tracking aligned with the current state of findings. Optimized Tenable.io Compliance Results ingestion : Starting with v\[VERSION\], the Tenable.io Compliance Results Integration is deprecated and replaced by the Tenable.io Fixed Compliance Results Integration and Tenable.io Open Compliance Results Integration. Compliance results are now imported based on their status, optimizing ingestion performance and scalability for environments with large volumes of compliance data while keeping remediation and compliance tracking aligned with the current state of findings. [Qualys Integration -- API enhancements](https://www.servicenow.com/docs/access?context=qualys-rest-messages-cc&family=zurich&ft:locale=en-US) : Qualys Integration has been upgraded to support newer Qualys API versions across Host Detection, Host List, Knowledgebase, PC Controls, PC Policies, and PCRS integrations. The integrations now ingest additional data fields, including vulnerability detection source, authentication privilege status, active status for controls and policies, and cloud metadata, giving you better visibility into your vulnerability and compliance data. Use the new `posture_api_version` integration instance parameter to choose between the default v2.0 APIs or the newer v5.0 streaming APIs for the PCRS Policy Host and PCRS Test Results integrations. [Configure Test Result Granularity](https://www.servicenow.com/docs/access?context=cc-tenable-tr-granularity&family=zurich&ft:locale=en-US) : Starting with v15.6.1, you can configure the granularity of Tenable Configuration Test Results (CTRs) to split results into unique findings. For example, if a database has five instances, the system generates five distinct test results, one per instance, providing improved visibility into individual patching efforts. [Configure Test Result Granularity](https://www.servicenow.com/docs/access?context=cc-qualys-tr-granularity&family=zurich&ft:locale=en-US) : Starting with v15.4.3, you can configure the granularity of Qualys Configuration Test Results (CTR) in configuration compliance and split CTRs into unique findings. For example, if a database has five instances, the system generates five distinct test results, one per instance, providing improved visibility into individual patching efforts. [Configure maximum rows in related lists](https://www.servicenow.com/docs/access?context=vr-max-rows-rel-list&family=zurich&ft:locale=en-US) : To improve readability and performance, you can now limit the number of rows shown in related lists on forms by setting the system property sn_vul_cmn.related_list.set_max_row. [Improved state management for remediation tasks and vulnerable items](https://www.servicenow.com/docs/access?context=vr-rt-states&family=zurich&ft:locale=en-US) : State management logic for roll down of state from remediation tasks (RTs) to findings and roll up of state from findings to RTs has been refined across all modules. Updates improve accuracy by handling mixed item states (a combination of Deferred and Closed), supporting closure of tasks in sub-states like In-Review, and reopening tasks based on the Assigned To field. The update also improves handling of False Positive state transitions based on scanner results as source of truth. These enhancements reduce manual effort, clarify task ownership, and streamline remediation workflows. | [ ] ## Removed Between your current release family and Zurich, some Configuration Compliance features or functionality were removed. {#dfrn3-configurationcompliance-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | * The Reason field in the Resolve modal has been removed for a remediation task in the classic UI, Vulnerability Manager Workspace, and IT Remediation Workspace. * The Close button has been removed for a remediation task, in the classic UI, Vulnerability Manager Workspace, and IT Remediation Workspace. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some Configuration Compliance features or functionality were deprecated. {#dfrn3-configurationcompliance-summary__entry__34} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Activation information Review information on how to activate Configuration Compliance. {#dfrn3-configurationcompliance-summary__entry__42} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | Activation information : Install Configuration Compliance by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Configuration Compliance is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Configuration Compliance and third-party integrations by requesting them from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: Configuration Compliance is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Configuration Compliance we have noted them here. {#dfrn3-configurationcompliance-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Configuration Compliance we have noted them here. {#dfrn3-configurationcompliance-summary__entry__58} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Configuration Compliance, such as specific requirements or compliance levels. {#dfrn3-configurationcompliance-summary__entry__66} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | [ ] ## Localization information If there are specific localization considerations for Configuration Compliance we have noted them here. {#dfrn3-configurationcompliance-summary__entry__74} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Configuration Compliance we have noted them here. {#dfrn3-configurationcompliance-summary__entry__82} | Release | Release notes | |-|-| | Xanadu | * Reevaluate the risk score, assignments, remediation target date, exceptions, and remediation task for a set of test results in Vulnerability Manager Workspace. * View the percentage of CI compliance and test results compliance on a Test Group in Vulnerability Manager Workspace. See [Configuration Compliance](https://www.servicenow.com/docs/access?context=vr-config-compliance-landing&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * With the sn_vulc.admin role, create remediation tasks manually in the Vulnerability Manager Workspace. * With the sn_vulc.remediation_owner role, create remediation tasks manually in the IT Remediation Workspace. See [Configuration Compliance](https://www.servicenow.com/docs/access?context=vr-config-compliance-landing&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * If you are currently using Configuration Compliance and you want to upgrade to Unified Security Exposure Management (USEM), see [Unified Security Exposure Management release notes](https://www.servicenow.com/docs/access?context=secops-sem-rn&family=zurich&ft:locale=en-US) for more information about USEM and the Unified Security Exposure Management migration. * Import Wiz issues and configuration test results from the Wiz scanners into test results in the Configuration Compliance application with the Vulnerability Response Integration with Wiz. * With the sn_vulc.remediation_owner role, create remediation tasks manually in the IT Remediation Workspace. * With the sn_vulc.admin role, create remediation tasks manually in the Vulnerability Manager Workspace. See [Configuration Compliance](https://www.servicenow.com/docs/access?context=vr-config-compliance-landing&family=zurich&ft:locale=en-US) for more information. | [ ]