Secure Web Gateway 12.2.20 Release Notes
New Features in the 12.2.x Release
Below is a consolidated list of new features available across the different 12.2.x releases. For issues resolved as a part of this release, see the Resolved Issues section.
For information about how to upgrade to this release, see Upgrading to a new version – Main Release.
Rebranding to Account for Transition
Names of products, components, and other items have been rebranded to account for the transition from McAfee to Secure Web Gateway.
Rebranded SNMP SMI and MIB file with Updated Org OID for Skyhigh Security
As part of the rebranding, a new Object Identifier (OID) has been introduced for Org Skyhigh Security. We are updating the SNMP OID from .1.3.6.1.4.1.1230* to .1.3.6.1.4.1.59732*. You'll need to update your management software accordingly if they are referring to these OID. For more details, see Configure event monitoring with SNMP.
Trellix VX Integration to SWG
The SWG 12.2.0 supports integration with Trellix Virtual Execution (VX). For more details, see Trellix Virtual Execution Integration to SWG.
Detection of OneNote files
New Mediatype detection has been added for OneNote files to detect .one and .onepkg files.
Insecure NETLOGON
Insecure NETLOGON channel is blocked by default. To explicitly allow Insecure NETLOGON, a new checkbox is provided in the Windows Join Domain Dialogue. For more details, see Insecure Netlogon.
TCP Health Check
Prior to this feature, SWG would send live traffic to Next Hop Proxies to determine its health, which resulted in a delayed response in case the Next Hop Proxy is not healthy. With this feature, SWG will have knowledge of the health of the Next Hop Proxies beforehand. For more details, see TCP Health Check for Next Hop Proxy.
Server Chunk Encoding
A new check box option is provided in proxy control event settings, which allows to enforce chunk encoding transfer on server requests from SWG. For more details, see Server Side Chunk Encoding.
Connection Established Response Based on HTTP-Protocol
The Connection Established response message always shows HTTP 1.0 even if the HTTP Protocol header of the request was HTTP 1.1. Now you can configure this under Proxy Control Event, where we can select to send back the Connection Established response text based on the HTTP Protocol version received. For more details, see Configure Connection Established Response based on HTTP Protocol Version.
Support for Pipelined Application/HTTP
A new media type has been added to media type filtering for detection and openers for Pipelined Application/HTTP.
New Properties for Multiline Base64
To support the multiline Base64, new properties are added in SWG.
Support for kdbx and kdb Filetype
A new media type has been added to media type filtering to detect files of the kdbx and kdb types.
Client Certificate Authentication for HTML UI
Client Certificate Authentication is now added for the HTML UI. For more details, see Client Certificate Authentication for HTML UI.
Configurable Size Limit of Single XML Attributes
The configurable size limit of single XML attributes has been increased to reduce errors on startup when having large inline lists.
Known Issues and Workarounds
For a list of issues that are currently known, see SWG 12.x.x Known Issues and Workaround.
Resolved Issues in the 12.2.20 Release
NOTE:
- SWG 12.2.20 is provided as a main release. For information about how to upgrade, see Upgrading to a new version – Main Release.
- If you have configured SWG in Transparent Router mode, ensure that your configuration follows the mandatory steps outlined in the Configure Proxy Settings for a Director Node in Transparent Router Mode before upgrading to SWG version 12.2.9 or later.
- SWG Release 12.2.20 includes all fixes from the earlier deprecated 12.2.19 release. For details on 12.2.19 fixes, see 12.2.19 release notes.
The following table provides a list of Resolved Issues: