2.9 Gateway Releases¶

2.9-09 - 2022-01-13¶

Fix: Fixes an issue where the use of a CIDR in Rule Suppression of a WAF Profile would result in a 403 response code

Fix: Fixes an issue where AWS Services traffic processed by a Forwarding rule is not classified by the Application ID engine as a Cloud Service category

Fix: Fixes an issue with the HTTP header presented by the Gateway to remove any reference to Valtix
Fix: Fixes an issue where the Gateway would not send policy status after a policy change was made
Fix: Fixes a potential datapath crash and self heal in various traffic scenarios for Egress use-case

Fix: Fixes an issue where a user-defined Address Group with 0.0.0.0/0 membership and applied to an Egress Gateway causes the Gateway to not pass traffic
Fix: Fixes an issue where an IDS/IPS threat is detected when Application ID is enabled, but no IDS/IPS profile is configured
Fix: Fixes an issue where TLS proxy configured in a Service Object applied to an Ingress Gateway causes a datapath self-heal under certain traffic scenarios
Fix: Enhances stability related to various stress scenarios for all use-cases

Fix: Fixes an issue where the use of Dynamic Address Objects in a Forward Proxy Policy Ruleset Rule can cause the traffic processed by the Rule to be forwarded rather than proxied

Fix: Fixes an issue where traffic protected by an Egress/East-West Gateway could be incorrectly processed by a Rule that shares the same Service Object used by other Rules in the same Ruleset

Fix: Fixes a datapath issue related to mixed-mode (forward-proxy, forwarding) scenarios for Egress/East-West use-case
Fix: Fixes a long running (slow) memory leak for Egress/East-West use-case
Fix: Fixes a memory corruption issue in atypical high load scenarios for Ingress use-case
Fix: Improves debug logging in datapath hitless restarts
Fix: Enhances stability related to various stress scenarios
Fix: Improves CPU efficiency to enhance datapath performance

Enhancement: Added Forward Proxy support for applications/services that use Websockets protocol (e.g. AWS SSM/EC2Messages) to Egress/East-West Gateway
Fix: Fixes an issue where the datapath would process Forwarding traffic as Forward Proxy under certain mixed Forwarding and Forward Proxy scenarios
Fix: Enhances throughput performance for IPS and WAF security profiles
Fix: Optimizes memory-based auto-scaling
Fix: Fixes stability issues related to various stress scenarios
Fix: Reduces overall memory consumption for all scenarios

Enhancements / Fixes: General release of 2.9 to enhance and improve capability, usability and stability
Enhancement: Enhanced messaging for certain System Log messages sent by the Gateway that were difficult to read and less actionable
Enhancement: Enhanced diagnostic messages when there are issues with the Valtix Gateway fetching a datapath certificate from the Valtix Controller
Enhancement: Enhanced Malicious IP protection to support both Ingress and Egress use-cases
Enhancement: Enhances the ability to change from one Security Policy Ruleset to another Security Policy Ruleset on a running Valtix Gateway without having to disable the Gateway
Fix: Fixes an issue in the datapath rule engine to enhance stability for certain high-volume, mixed traffic scenarios
Fix: Fixes an issue with the datapath FQDN processing when attempting to parse and process a non-FQDN
Fix: Fixes an issue with WAF processing that could result in a 504 (request timeout)
Fix: Fixes an issue with the datapath that occurs rarely where ARP packets are not processed properly
Fix: Fixes an issue in a WAF profile where a Trustwave rule detects malicious activity, but does not block the offending activity
Fix: Fixes an issue where certain changes to the WAF profile are not applied to the Valtix Gateway