--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined Container Vulnerability Response release notes for upgrades from Australia to Brazil # Combined Container Vulnerability Response release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 11 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 Container Vulnerability Response Release Notes for Upgrades from Australia to Brazil This consolidated guide provides ServiceNow customers with essential information on upgrading Container Vulnerability Response from the Australia release family to the Brazil release family. It highlights new features, changes, deprecations, and activation instructions relevant to these releases, helping you prepare for a smooth upgrade and leverage enhanced container security capabilities. Show full answer Show less ## Key Features * **ServiceNow Otto Rebranding:** The AI experience brand has been renamed ServiceNow Otto, affecting product names such as Now Assist for Vulnerability Response, now called ServiceNow Otto for Unified Security Exposure Management (USEM). Your product entitlements remain unchanged. * **Enhanced Container Vulnerability Data:** Upgrades enable enriched container vulnerability data imports from third-party scanners, improving visibility on container images, findings, and vulnerable items. A full data import post-upgrade is recommended to access new features. * **Wiz Integration Enhancements:** * Activation of Wiz Asset Integration now optional and deactivated by default starting Australia Patch 5 and Brazil releases. * Ability to specify resource types for import to avoid unnecessary data ingestion. * Configurable Image Vulnerability Keys enable precise creation of container vulnerable items (CVITs) using UUID detection keys from Wiz. * Support for AWS ECS and EKS container environments with selection between Scanner or Discovery data sources. * Introduction of chained integrations in Brazil release, including Wiz Container Grouped Vulnerability and Deployment Context integrations for comprehensive vulnerability and deployment data. * **AWS Integration for Security Exposure Management:** Supports automatic import of host and container vulnerabilities from AWS Inspector and AWS Security Hub, centralizing vulnerability data from AWS services. * **Unified Microsoft Defender Integration:** Consolidates Microsoft Defender for Cloud and Microsoft Defender TVM plugins into a single integration that supports container image vulnerability ingestion and provides a guided migration path. * **Now LLM Service Update:** Introduction of Gemma 4 model in September 2026 release enhances AI capabilities within ServiceNow Otto, with older models remaining available for existing configurations but not new developments. ## Important Upgrade Considerations * **Deprecation Notice:** Now Assist for Vulnerability Response is being prepared for deprecation; it will be hidden and not installed on new instances starting Australia Patch 5 but remains supported. * **Data Migration and Reliability:** Brazil release improves handling of Wiz API error codes with clearer notifications and enhances reliability of Wiz data migration. * **Path Column Change:** Path tracking moved from Container Image Package table to Container Image Finding table to ensure accurate path and image association for Palo Alto Networks Prisma Cloud Compute and Wiz integrations. * **Scheduling Recommendations:** When using Discovery as data source for AWS ECS and EKS, schedule third-party integrations at least four hours after the daily Populate image relationships job to ensure data availability. * **Version Compatibility:** Customers not upgrading to USEM should use Container Vulnerability Response versions below v30.x and ensure compatibility with third-party integrations as per the Vulnerability Response Compatibility Matrix. ## Activation and Additional Information * Container Vulnerability Response and associated third-party integrations are available for installation via the ServiceNow Store. * No new browser, accessibility, or localization requirements were introduced between Australia and Brazil releases. * Roles such as `snvulcontainer.vulnerabilityanalyst`, `snvulcontainer.vulnerabilityadmin`, and `snvulcontainer.remediationowner` enable manual creation of container remediation tasks in Vulnerability Manager Workspace and IT Remediation Workspace. ## Next Steps for ServiceNow Customers * Review and complete pre- and post-upgrade tasks outlined in the release notes to ensure readiness. * Perform a full data import after upgrading to view enhanced container vulnerability data. * Check entitlements to verify access to new features under the ServiceNow Otto brand. * Consider the impact of deprecated features and adjust integrations accordingly, especially for Wiz and Palo Alto Networks Prisma Cloud Compute users. * Plan scheduling of integration jobs carefully to maximize data integrity, especially for AWS ECS/EKS discovery sources. Consolidated page of all release notes for Container Vulnerability Response from Australia to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Container Vulnerability Response release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Australia 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 Container Vulnerability Response to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-containervulnerabilityresponse-summary__entry__2} | Release | Release notes | |-|-| | Australia | Upgrade information : 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. Enhancements to Container Vulnerability Response permit you to see enriched container vulnerability data on data imports from your third-party scanners. After you upgrade, perform a full import to view the features on discovered container image, container image finding, and container vulnerable item records that are described in the following New in the Australia release section. If you're currently using Container Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Container Vulnerability Response and for upgrades to supported third-party integration applications. For more information about the released versions of the Container Vulnerability Response application as well as 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 | Upgrade information : 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. Enhancements to Container Vulnerability Response permit you to see enriched container vulnerability data on data imports from your third-party scanners. After you upgrade, perform a full import to view the features on discovered container image, container image finding, and container vulnerable item records that are described in the following New in the Brazil release section. If you're currently using Container Vulnerability Response, and you don't intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Container Vulnerability Response and for upgrades to supported third-party integration applications. For more information about the released versions of the Container Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Brazil 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 Brazil, new features were introduced for Container Vulnerability Response. {#dfrn3-containervulnerabilityresponse-summary__entry__8} | Release | Release notes | |-|-| | 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: * A link lets you navigate from the Wiz configuration module directly to the Configure VI Granularity module where you can configure the keys that generate Container Vulnerability Response findings. * Starting with version 32.1 (USEM) and version 4.1 (non-USEM), the Asset integration is deactivated by default and 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. [Configure Image Vulnerability keys for Container Vulnerability Response CVIT creation](https://www.servicenow.com/docs/access?context=cvr-configuring-findings-key-granularity&family=australia&ft:locale=en-US) : Configure records on the Configure Image Vulnerability Keys \[sn_vul_container_image_vulnerability_keys\] table in your ServiceNow AI Platform® instance for the Image Vulnerability Keys that create container vulnerable items (CVIT)s. * The Universally Unique Identifier (UUID) provided by Wiz is now mapped as the detection key for the Wiz Host Vulnerability integration. * AWS ECS (Elastic Container Service) and AWS EKS (Elastic Kubernetes Service) environments are supported. * Cluster and Service are supported for AWS ECS environments. * Namespace, Registry, and Service are supported for AWS EKS environments. * Choose either Scanner (third-party scanners) or Discovery (Configuration Management Database (CMDB)) as sources for data import for AWS ECS and AWS EKS. Note: If you choose Discovery as the data source, the Populate image relationships scheduled job runs daily to pre-import cluster and service details, and you should schedule your third-party integration runs at least 4 hours after this scheduled job is completed to verify that the pre-import data is available. This job is activated by default, but you must set the schedule so it runs before your scheduled third-party integration runs. For new customers only: The system property, sn_vul_container.image_relationship_mapping_months sets the number of previous months (1-12) that you want your third-party integration to look for container image updates when processing relationship mappings. This data is used to filter images by the sys_updated_on field. The default setting is three months. After you configure the integration run, relationship mapping is created for images which have been scanned in the last 90 days and present in discovered container images. * Column labels on the Container Vulnerable item \[sn_vul_container_image_vulnerable_item\] table are updated to support the scanner and discovery options, depending on your choice on the Configure Image Vulnerability Keys configuration page: * Cluster (Scanner) Namespace (scanner), and Service (scanner) for scanner data * Cluster (Discovery), Namespace (Discovery) and Service (Discovery) for Discovery [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 compliance 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. [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. | | Brazil | [Enhancements to the Wiz Vulnerability Response Integration](https://www.servicenow.com/docs/access?context=wiz-container-runtime-exposure-cvr&family=brazil&ft:locale=en-US) : Two new chained integrations for the Wiz container vulnerability pipeline: * The Wiz Container Grouped Vulnerability Integration that retrieves vulnerability findings from Wiz that are grouped by image. * The Wiz Container Deployment Context Integration that retrieves the complete deployment/execution context that includes clusters, namespaces, services for each image. * View both integrations in your Vulnerability Integrations list alongside the existing Wiz Container Vulnerability Integration. The integrations are installed automatically and are activated by default. Note: To disable this integration chain, set the sn_vul_wiz.deployment_context_gate_writes system property to 'false'. This deactivates the Wiz Container Grouped Vulnerability and Wiz Container Deployment Context integrations so that container vulnerable item creation remains based on your existing settings with the Wiz Container Vulnerability Integration integration. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Container Vulnerability Response features. {#dfrn3-containervulnerabilityresponse-summary__entry__14} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | Container Vulnerability Response : * Enhancements to improve handling of Wiz API error codes that include clearer notifications directing users to contact the Wiz support team when a vendor-side error occurs. * Enhancements to improve the reliability of the data migration for Wiz Container Vulnerability Response. | [ ] ## Removed Between your current release family and Brazil, some Container Vulnerability Response features or functionality were removed. {#dfrn3-containervulnerabilityresponse-summary__entry__20} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Container Vulnerability Response features or functionality were deprecated. {#dfrn3-containervulnerabilityresponse-summary__entry__26} | Release | Release notes | |-|-| | Australia | * The Path Column in the Container Image Package \[sn_vul_container_image_package\] table for the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute and [Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=australia&ft:locale=en-US) third-party integrations. Path tracking has been moved to the Path Column on the Container Image Finding \[sn_vul_container_image_findings\] table to support accurate and consistent path and image association. If you use these integrations you must refer to the Path column available on the Container Image Finding \[sn_vul_container_image_findings\] table. * 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, you must 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). | | Brazil | Now LLM Service : Starting with the September 2026 release, Gemma 4 joins our growing portfolio of open-weight models available through Now LLM Service. The latest industry advancements are available alongside sovereignty-focused options. All models are hosted and governed by ServiceNow with the same infrastructure and data protections. Older models will remain available for existing published AI skills, agents, and agentic workflows, but will no longer be available for new development or configuration. For details, see the [KB3066214: ServiceNow Otto Model Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3066214) article in the Now Support Knowledge Base. | [ ] ## Activation information Review information on how to activate Container Vulnerability Response. {#dfrn3-containervulnerabilityresponse-summary__entry__32} | Release | Release notes | |-|-| | Australia | Activation information : Install Container Vulnerability Response 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: Container Vulnerability Response is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Brazil | Activation information : Install Container Vulnerability Response 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=brazil&ft:locale=en-US). Important: Container Vulnerability Response 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 Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__38} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__44} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Container Vulnerability Response, such as specific requirements or compliance levels. {#dfrn3-containervulnerabilityresponse-summary__entry__50} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__56} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__62} | Release | Release notes | |-|-| | Australia | * The AWS Integration for Security Exposure Management supports integrations with AWS Inspector and AWS Security Hub. * If you're currently using Container Vulnerability Response 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 container image vulnerability data from the Wiz scanners into container vulnerable items (CVITs) with the Vulnerability Response Integration with Wiz. * With the sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin role, create container remediation tasks manually in the Vulnerability Manager Workspace. * With the role sn_vul_container.remediation_owner, create container remediation tasks manually in the IT Remediation Workspace. See [Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-landing&family=australia&ft:locale=en-US) for more information. | | Brazil | * If you're currently using Container Vulnerability Response 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=brazil&ft:locale=en-US) for more information about USEM and the Unified Security Exposure Management migration. * Import container image vulnerability data from the Wiz scanners into container vulnerable items (CVITs) with the Vulnerability Response Integration with Wiz. * With the sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin role, create container remediation tasks manually in the Vulnerability Manager Workspace. * With the role sn_vul_container.remediation_owner, create container remediation tasks manually in the IT Remediation Workspace. See [Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-landing&family=brazil&ft:locale=en-US) for more information. | [ ]