--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-zurich-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3bz bundleId : - delta3bz --- # Combined Configuration Compliance release notes for upgrades from Zurich to Brazil # Combined Configuration Compliance release notes for upgrades from Zurich to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 17 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 Zurich to Brazil This consolidated guide provides ServiceNow customers with essential information about upgrading Configuration Compliance from the Zurich release family to Brazil. It includes key new features, changes, upgrade considerations, and integration updates across releases from Zurich and Australia to Brazil. The document is designed to facilitate a smooth upgrade process and help customers leverage new capabilities while maintaining compatibility with existing integrations and workflows. Show full answer Show less ## Important Upgrade Information * If you are not upgrading to Unified Security Exposure Management (USEM), install Configuration Compliance versions below v30.x and ensure compatibility with supported third-party integrations. * The **Missing Assets \[snvulwizmissingasset\]** table used in Vulnerability Response Integration with Wiz is deprecated. After upgrading to version 1.1, backdate existing Wiz primary integrations by three days and execute them to ensure data consistency. * ServiceNow Otto® replaces Now Assist for Vulnerability Response branding, aligning with Unified Security Exposure Management products without changes to entitlements. * Australia Patch 5 initiates deprecation of Now Assist for Vulnerability Response; it will be hidden on new instances but remains supported on existing ones. ## Key Features Introduced * **Remediation Task Rule Execution Modes:** Choose between "Match First" mode, which applies only the first matching remediation task rule per finding, and the default "Match All" mode that applies all applicable rules. * **Optimized Tenable.io Compliance Results Ingestion:** The original integration is replaced by separate Fixed and Open Compliance Results integrations that import data based on status to improve performance and scalability. * **Unified Microsoft Defender Integration:** Consolidates Microsoft Defender for Cloud and MS Threat \& Vulnerability Management plugins into a single plugin, adding container image vulnerability ingestion and providing a guided migration path. * **Enhanced Qualys Integration:** Upgraded to support newer API versions, ingest additional data fields (e.g., vulnerability detection source, authentication status, cloud metadata), and offers a parameter to select API streaming versions. * **Vulnerability Response Integration with Wiz Enhancements:** Deprecated certain tables and columns, introduced resource type filtering, new attribute mappings, and improved handling of AI-related security findings, providing better visibility and future AI-specific workflows. * **AWS Integration for Security Exposure Management:** Supports AWS Inspector and AWS Security Hub, enabling import of host, container vulnerabilities, and misconfigurations for comprehensive cloud security posture management. * **Granularity Configuration for Test Results:** Allows splitting Tenable and Qualys configuration test results into unique findings per instance, offering improved visibility into patching and compliance efforts. * **Configure Maximum Rows in Related Lists:** System property added to limit rows in related lists on forms, enhancing readability and performance. * **Improved State Management:** Refined logic for remediation tasks and findings to handle mixed states, sub-state closures, reopening rules, and false positive transitions, reducing manual intervention. ## Changes * Deprecation and replacement of previous integrations and tables to improve ingestion performance and data accuracy. * New parameters introduced for integrations to customize import behavior (e.g., ignoring passed test results in Qualys integration). * Some configuration fields are no longer mandatory, simplifying integration setup (e.g., Resource Type in Wiz integration). ## Activation and Compatibility * Configuration Compliance and related third-party integrations must be requested and installed via the ServiceNow Store. * Compatibility matrices and release schema change articles provide detailed information on supported versions and integrations for Zurich and Australia releases. * Customers should review entitlement access to features, especially with the transition to ServiceNow Otto branding and USEM migration paths. ## Additional Notes * No features or functionality were removed or deprecated specifically in the Brazil release. * No additional browser, localization, or accessibility requirements have changed from previous releases. * Dark theme support introduced with the Coral theme (Zurich release) enhances user experience but is not specific to Brazil. * For customers upgrading to USEM, separate Unified Security Exposure Management release notes should be consulted. ## Practical Recommendations for ServiceNow Customers * Before upgrading to Brazil, thoroughly review pre- and post-upgrade tasks, especially related to deprecated tables and integration backfills with Wiz. * Leverage new remediation task rule execution modes to optimize remediation workflows according to your organizational needs. * Utilize updated integration capabilities with Qualys, Tenable.io, Microsoft Defender, AWS Inspector, and AWS Security Hub for improved vulnerability and compliance visibility. * Configure test result granularity to gain detailed insights into compliance status at the instance level. * Monitor and adjust related list row limits to maintain optimal UI performance. * Plan for migration to unified plugins where applicable, such as Microsoft Defender, to ensure continued support and feature availability. Consolidated page of all release notes for Configuration Compliance from Zurich to Brazil. ## 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 Zurich to Brazil. 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 Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-configurationcompliance-summary__entry__2} | Release | Release notes | |-|-| | 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. | | Australia | Upgrade information : If you're currently using Configuration Compliance, and you don't intend to upgrade to Unified Security Exposure Management (USEM), install a version previous v30.x of Configuration Compliance and for upgrades to supported third-party integration applications. Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. 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=australia&ft:locale=en-US) is deprecated. If you're currently using the Vulnerability Response with Wiz integrations, after updating to version 1.1, backdate any of your existing Wiz primary integrations by three days and run them. See 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 and the third party and ServiceNow applications that are compatible with the Australia 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. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Configuration Compliance. {#dfrn3-configurationcompliance-summary__entry__10} | Release | Release notes | |-|-| | 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. | | Australia | [Activate the Wiz Asset Integration and identify resource types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=australia&ft:locale=en-US) : Enhancements to the Wiz integration include: * Starting with version 32.1 (USEM) and version 4.1 (non-USEM), the Asset integration is deactivated by default. It is not a mandatory prerequisite for the other Wiz integration imports. If you choose to activate it, the Asset integration will retrieve assets for all resource types if you don't specify the ones you want on the Asset Integration Configuration tab. To avoid importing vulnerability data you don't need, identify only the resources (assets) that you want to import with this integration. * Resource Type is no longer a mandatory field for configuring the Vulnerability Response Integration with Wiz. You can now save Wiz configurations for the integrations without specifying a Resource Type, simplifying setup for use cases where specifying a Resource Type isn't appropriate. [Compliance test uniqueness key](https://www.servicenow.com/docs/access?context=cc-tenable-compliance-test-uniqueness-key&family=australia&ft:locale=en-US) : You can now configure which identifier the system uses to uniquely match incoming Tenable conformance test records. Previously, conformance tests were identified by the check_id field, which caused records to be overwritten when multiple tests shared the same control identifier. You can now select the identifier that best matches how your Tenable data is structured (compliance_control_id, check_id, or compliance_functional_id), ensuring test records are accurately preserved during ingestion. [AWS Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=aws-integration-for-security-exposure-management-overview&family=australia&ft:locale=en-US) : The AWS Integration for Security Exposure Management supports integrations with the following AWS services: * AWS Inspector is an automated vulnerability management service that continuously scans EC2 instances, ECR container images, and Lambda functions for software vulnerabilities (CVEs) and unintended network exposure. The Vulnerability Response integration with AWS Inspector imports host and container vulnerability findings from AWS Inspector. * AWS Security Hub is a security service that is used to centralize and update security checks across AWS accounts. It provides a unified view of security alerts and conformance status by integrating with various AWS services. The Vulnerability Response integration with AWS Security Hub imports host, container vulnerabilities, and misconfigurations from AWS Security Hub. [Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenableIntegration&family=australia&ft:locale=en-US) : Starting with v 6.1.3, the Tenable.io conformance Results Integration is replaced by the Tenable.io Fixed conformance Results Integration and Tenable.io Open conformance Results Integration. conformance results are now imported based on their status, optimizing ingestion performance and scalability for environments with large volumes of conformance data while keeping remediation and conformance tracking aligned with the current state of findings. [Qualys Integration -- API enhancements](https://www.servicenow.com/docs/access?context=c_QualysVulnIntegration&family=australia&ft:locale=en-US) : The Qualys Vulnerability 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 conformance 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. [Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=ms-defender-sem&family=australia&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. [Remediation task rule execution mode](https://www.servicenow.com/docs/access?context=sem-grouping-multiple-findings-remediation-tasks-processing&family=australia&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. Enhancements to the Vulnerability Response Integration with Wiz : Enhancements to the Wiz integration that imports cloud configuration findings as Test Results in Configuration Compliance. Configuration issues related to AI assets, such as AI models and agents are routed into AI security exposure management tables (AI posture findings). This enhancement helps with better visibility within AI Control Tower and for any AI-specific remediation workflows to be added in the future. The 'Send AI security findings to AI security exposure management' configuration setting has been added to the Wiz Test Results integration configuration page so that AI security findings are routed into AI security exposure management. [Qualys parameter to ignore passed test results](https://www.servicenow.com/docs/access?context=Qualys-cc-Integration&family=australia&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 aren't 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. | | Brazil | No updates for this release. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Configuration Compliance features. {#dfrn3-configurationcompliance-summary__entry__18} | Release | Release notes | |-|-| | 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. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some Configuration Compliance features or functionality were removed. {#dfrn3-configurationcompliance-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Configuration Compliance features or functionality were deprecated. {#dfrn3-configurationcompliance-summary__entry__34} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate Configuration Compliance. {#dfrn3-configurationcompliance-summary__entry__42} | Release | 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. | | Australia | 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) 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=australia&ft:locale=en-US). Important: Configuration Compliance is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Brazil | No updates for this release. | [ ] ## 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | 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. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Configuration Compliance we have noted them here. {#dfrn3-configurationcompliance-summary__entry__74} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | 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. | | Australia | * The AWS Integration for Security Exposure Management supports integrations with AWS Inspector and AWS Security Hub. * If you're currently using Configuration Compliance and you want to upgrade to Unified Security Exposure Management (USEM), see [Unified Security Exposure Management (USEM) release notes](https://www.servicenow.com/docs/access?context=secops-sem-rn&family=australia&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=australia&ft:locale=en-US) for more information. | | Brazil | No updates for this release. | [ ]