| \n\nYokohama\n\n | \n\n- **[Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=yokohama&ft:locale=en-US)**\n\nIdentify 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.\n\nThe Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration.\n\n- **[Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=yokohama&ft:locale=en-US)**\n\nRetrieve 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.\n\n - Test Results Backfill Integration\n - Host Test Results Backfill Integration\n - Issues Backfill Integration\nThe Wiz Backfill Integrations are activated by default.\n\n- **[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)**\n\nImport test results associated with the resource type, `VIRTUAL MACHINE` with the Wiz Host Test Result Vulnerability Integration. This integration is activated by default.\n\n\n - **[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)**\n\nWith 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.\n\n- **[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)**\n\nWith 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.\n\n- **[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)**\n\nStarting 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.\n\n- **[Quick Start Tests for Configuration Compliance](https://www.servicenow.com/docs/access?context=available-quick-start-tests&family=yokohama&ft:locale=en-US)**\n\nAfter 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.\n\n\n |
| \n\nZurich\n\n | \n\n- **[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)**\n\nYou 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.\n\n- **[Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=zurich&ft:locale=en-US)**\n\nStarting 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.\n\n- **[Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=ms-defender-sem&family=zurich&ft:locale=en-US)**\n\nThe 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.\n\n\n - **[Qualys Integration – API enhancements](https://www.servicenow.com/docs/access?context=qualys-rest-messages-cc&family=zurich&ft:locale=en-US)**\n\nQualys 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.\n\n\n - **[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)**\n\nThe 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.\n\nThe backfill integrations are activated by default.\n\nAfter you backdate and run your integrations, the following backfill integrations are no longer required:\n\n - Host Vulnerability Backfill Integration\n - Test Results Backfill Integration\n - Host Test Results Backfill Integration\n - Issues Backfill Integration\nThe \\[is\\_ignored\\] column is deprecated for the Host Test Results and Test Results Integrations. This column was replaced by the \\[is\\_result\\_ignored\\] column.\n\nSource severity is mapped to the Priority column on the Test Results \\[sn\\_vulc\\_result\\] table.\n\nResource 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.\n\n**Note:**\n\nIf 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.\n\nAdditional 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.\n\nTest results from the Host misconfiguration integration are classified as result type 'host\\_misconfiguration'.\n\nData for resources that have the validated\\_at\\_runtime flag set to 'yes' is imported and populated on detections.\n\nThe is\\_ignored column is deprecated on the Host Test Results and Test Results Integrations. This column was replaced by the is\\_result\\_ignored column.\n\nThe CMDB internet-facing field on the discovered item is mapped to Limited Internet Exposure on findings.\n\nColumn length for the descriptions in the Host Vulnerability import table has been increased.\n\n\n - **[Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=zurich&ft:locale=en-US)**\n\nIdentify 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.\n\nThe Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration.\n\n- **[Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=zurich&ft:locale=en-US)**\n\nRetrieve 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.\n\n - Test Results Backfill Integration\n - Host Test Results Backfill Integration\n - Issues Backfill Integration\nThe Wiz Backfill Integrations are activated by default.\n\n- **[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)**\n\nImport test results associated with the resource type, `VIRTUAL MACHINE` with the Wiz Host Test Result Vulnerability Integration. This integration is activated by default.\n\n\n - **[Qualys parameter to ignore passed test results](https://www.servicenow.com/docs/access?context=Qualys-cc-Integration&family=zurich&ft:locale=en-US)**\n\nStarting with v15.2.5 of Configuration Compliance, the ignore\\_passed\\_result integration instance parameter for the Qualys Integration for Security Operations has been added.\n\nThis parameter is set to `false` by default so that passed test results imported by Qualys are not ignored.\n\nSet the parameter to **true** to ignore passed test results on import.\n\n**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.\n\n- **[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)**\n - 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.\n - 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.\n\n |
| \n\nAustralia\n\n | \n\n- **[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)**\n\nEnhancements to the Wiz integration include:\n\n - 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.\n\nIf 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.\n\n - 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.\n\n - **[Compliance test uniqueness key](https://www.servicenow.com/docs/access?context=cc-tenable-compliance-test-uniqueness-key&family=australia&ft:locale=en-US)**\n\nYou 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.\n\n\n - **[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)**\n\nThe AWS Integration for Security Exposure Management supports integrations with the following AWS services:\n\n - 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.\n - 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.\n- **[Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenableIntegration&family=australia&ft:locale=en-US)**\n\nStarting 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.\n\n- **[Qualys Integration – API enhancements](https://www.servicenow.com/docs/access?context=c_QualysVulnIntegration&family=australia&ft:locale=en-US)**\n\nThe 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.\n\n- **[Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=ms-defender-sem&family=australia&ft:locale=en-US)**\n\nThe 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.\n\n- **[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)**\n\nYou 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.\n\n\n - **Enhancements to the Vulnerability Response Integration with Wiz**\n\nEnhancements 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\\).\n\nThis 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.\n\n- **[Qualys parameter to ignore passed test results](https://www.servicenow.com/docs/access?context=Qualys-cc-Integration&family=australia&ft:locale=en-US)**\n\nStarting with v15.2.5 of Configuration Compliance, the ignore\\_passed\\_result integration instance parameter for the Qualys Integration for Security Operations has been added.\n\nThis parameter is set to `false` by default so that passed test results imported by Qualys aren't ignored.\n\nSet the parameter to **true** to ignore passed test results on import.\n\n**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.\n\n\n |
\n