Enhancement: Rebrands the Valtix solution as Cisco Multicloud Defense. The rebranding also updates the UI to incorporate the Cisco UI standards for look, feel and functionality.
Enhancement: Integrates Cisco Multicloud Defense Controller and Portal into Cisco Defense Orchestrator. Defense Orchestrator is now used for tenant and user management, as well as a launch point into Multicloud Defense Portal. Cisco Defense Orchestrator can also be used for onboarding CSP accounts into Multicloud Defense. Further integration will occur over time.
Enhancement: Provides an enhanced workflow for creating Policy from the Discover Topology view
Fix: Fixes an issue where Advanced Search on Session ID did produce proper results
Fix: Fixes an issue where changing the WAF action from "Allow Log" to "Rule Default" could cause the datapath to restart multiple times
Fix: Fixes an issue where the initial apply of an Advanced Search filter would not apply the filter. Applying the filter a second time would show proper results.
Fix: Fixes an issue where deploying a Gateway into Azure Zone 1 southcentralus Region would result in an error
Fix: Fixes an issue where setting a Log Forwarding Profile onto a newly created Gateway would result in a datapath self-heal
Fix: Fixes an issue where the Controller might not delete old instances after new instances are created through a Gateway upgrade
Fix: Fixes an issue where an invalid Advanced Search would be accepted as a valid search string
Fix: Fixes an issue where a freeform Advanced Search would not result in a filtered view when initially applied
Fix: Fixes an issue where the user would not be able to create an Ingress Forwarding Rule to use a large number of ports (e.g., 0-65535). An Ingress Forwarding Rule is applicable when deploying an Ingress Gateway in an Azure Gateway Load Balancer (GWLB) architecture.
Fix: Fixes an issue where a Gateway Status would show Active when the Gateway Details Instances page would show the instance as Active Pending
Fix: Fixes an issue where an in-use Group FQDN Filtering Profile does not display show the associated Standalone FQDN Filtering in the FQDN Filtering Profile Details view
Fix: Fixes an issue where the Controller could replace a Gateway instance due to health issues, but not delete the unhealthy instance
Fix: Fixes an issue where launching from the Traffic Summary Log into the Policy Rule will not highlight the Rule associated with the traffic session
Fix: Fixes an issue where upgrading an Azure Gateway to 23.04 Gateway release train could fail due to misconfiguration in the Azure Health Checks from the Network Load Balancer (NLB) and the Gateway
Fix: Fixes an issue where view the Azure Poland region was not showing Poland as a friendly name
Fix: Fixes an issue where an onboarded Azure subscription would show a Valid state even if errors exists in the trust relationship between the Controller and the Azure service account
Fix: Fixes the error statement for the Gateway resource limits check performed by the Controller prior to deploying a Gateway
Fix: Fixes an issue where an applied Advanced Search is removed from the search field, but remains applied resulting in a filtered view that does not match the search field
Fix: Fixes an issue where the Gateway Filter dropdown would not populate the full list of Gateways
Fix: Fixes an issue where a user-defined change to CMEK would not initiate a blue/green Gateway replacement
Fix: Fixes an issue where a dynamic Address Object based on Azure Services could not be successfully created
Fix: Fixes an issue where a Gateway would not be fully deleted if the Controller is unsuccessful in deploying would not create the proper Service Endpoint resource
Fix: Fixes an issue where the Controller would not report a misconfiguration that would inhibit Health Checks from the Load Balancer to the Gateway, causing the Gateway to not successfully deploy
Fix: Fixes an issue where the orchestration of a new Gateway in Azure would not properly create a Load Balancer Health Check Rule for an Internet-facing Network Load Balancer (NLB)
Fix: Fixes an issue where the Gateway Status would not represent the true status of the Gateway that is represented by the Gateway -> Details -> Instances view