Secure Web Gateway 10.2.09 Release Notes
What's new in the 10.2 release
Releases can introduce new features and enhancements or update platform support.
Improvements for Proxy HA mode
Several options are now available that allow for improved performance and handling when running Secure Web Gateway in Proxy High Availability (Proxy HA) network mode.
- An inactivity timeout, a load balancing algorithm, and sticky sessions can be configured, as well as egress IP addresses to increase the number of simultaneously active connections to cluster nodes scanning web traffic.
- Filtering traffic coming in under the SOCKS protocol is supported.
For more information, see the Proxy HA mode section of the Secure Web Gateway Product Guide.
More protocol versions for secure ICAP
Different versions of the TLS and SSL protocols can now be selected when running Web Gateway in a secure ICAP server configuration.
For more information, see the ICAP server section of the Secure Web Gateway Product Guide.
Property for troubleshooting ATD issues
The Antimalware.MATD.Error.MessageDetails string-type property has been added to the list of properties for use in web security rules. It provides details of an Advanced Threat Defense error message, such as timeouts, missing values, or network problems.
For more information, see the Properties - A section of the Secure Web Gateway Product Guide.
More media types detected
More media types are detected by the functions for media type filtering on Web Gateway, including:
- Visio files with the following extensions: vsdm, vsdx, vssm, vssx, vstm, vstx
- CAD files
More efficiency in internal processing
- Several internal processes have been improved on Web Gateway as follows.
- For users working with the WebSwing version of the user interface, the individual IP addresses of their client systems are recorded in the audit log when requests come in from these clients. The common 127.0.0.1 address is no longer in use here.
This address had been logged for all users due the role as a remote desktop that WebSwing took from the point of view of the Java user interface.
A commercial WebSwing version has also been implemented to overcome some limitations of the open source versions.
- More efficient methods of identifying customers, clients, and connections involved in issues that occurred are now used when reading core files stored in a temp folder.
- Some enhancements have been implemented for the consistency checking tool, which identifies unused settings and lists on Web Gateway.
- The feedback file that is evaluated on the master node in a cluster of Web Gateway appliances now provides the current version of the appliance software for each cluster node.
- Processing lists with entries in Regex format performs better due to an improvement of the diagnostic tool.
What's new in update 10.2.1
This release introduces several enhancements.
SmartMatch optimization
Performance has been optimized for SmartMatch lookups by improving the way lists are handled when searching for matches.
Kerberos authentication with improved logging
When the Kerberos authentication method is used, error logging has been improved, for example, by writing client IP addresses in the log.
Handling of HTTP2 statistics improved
HTTP2 statistics, which are also shown on the Secure Web Gateway dashboard, are provided under the Simple Network Management Protocol (SNMP) to be read by an external SNMP manage poll.
Known Issues and Workaround
For a list of issues that are currently known, see SWG 10.x.x Known Issues and Workaround
Resolved issues in update 10.2.9
This release resolves known issues.
NOTE: Secure Web Gateway 10.2.9 is provided as a main release.
For upgrade information, see the Upgrading to a new version provided as a main release section of the Secure Web Gateway Installation Guide.
The JIRA issue number is provided in the reference column.
Network communication
| Reference | Description |
|---|---|
| WP-4145 | POST commands running while HTTP tunneling is enabled do not lead to a failure of the core process on Secure Web Gateway anymore. |
| WP-4541 | Processing of cluster messages sent by the Notification plugin that is implemented in the core process has been improved. |
| WP-4558 | When the data threshold of 10 GB is reached on an ICAP connection, the connection is shut down to avoid overload issues. |
| WP-4559 | Memory can be reserved for advance usage while reading messages on Secure Web Gateway, so the length of the response is already known early, which avoids memory reallocation. |
Web filtering
| Reference | Description |
|---|---|
| WP-4459 | File scanning now extracts text from PDFs, which had failed before, as the scanning process went into a loop causing CPU consumption to reach 100%. |
Other
| Reference | Description |
|---|---|
| WP-4362 | The Secure Web Gateway rule set for file scanning scans nested archives files now that caused issues before. |
| WP-4556 | Coordinator crashes that led to a shutdown on a Secure Web Gateway appliance do not occur anymore. |
| WP-4567 | The SmartCache default size value has been increased from 100 to 1000 MB. |
| WP-4584 | Response time for CStorageJob backup and restore activities has been improved. |
Vulnerabilities Fixed
| Reference | Description |
|---|---|
|
WP-4432, WP-4454, WP-4591
|
This Secure Web Gateway release includes updates addressing publicly disclosed CVEs, regardless of whether a CVE has been shown to impact customers. The following medium and higher-level CVEs (CVSS 3.0 >= 4) were involved:
For more information about these CVEs and their impact, see the Red Hat CVE portal. |