Skip to main content

Check out Interactive Visual Stories to gain hands-on experience with the SSE product features. Click here.

Skyhigh Security

Secure Web Gateway 12.1.1 Release Notes

New Features in the 12.1 Release 

Configure Proxy Control X-Cache Header 

A configurable option is now available to either add or remove the Proxy Control X-Cache header in the response. The new setting is located at Policy > settings > proxy control, and the checkbox is called Override X-Cache Header. The setting is enabled by default. For more details, Configure the X-Cache Header in the Response.

TCP Half Close support for TCP Proxy and SOCKS Proxy  

TCP Half Close refers to a TCP connection that is half-closed. So if one participant in a TCP connection has initiated FIN in one direction, then it can still receive data from another participant until the second FIN is received from the other direction. TCP Half Close support is provided for SWG acting as TCP Proxy or SOCKS Proxy. For details, see TCP Half Close for TCP or SOCKS Proxy.

Configure Separate Passwords for SNMPv3 Auth and Encryption 

You can now configure separate passwords for Authentication and Encryption for the SNMPv3 messages. For details, see Configure Event Monitoring with SNMP

Return To Sender 

This feature allows outgoing traffic of SWG to skip default kernel routing. Each reply packet going out

  1. will have same source mac as destination mac in the request packet.
  2. will have same destination mac as source mac in the request packet.
  3. If the reply going out on different interface it came from,  the reply will be redirected to the same interface on which the request came from.
MediaType Detection for InDesign Files  

Media Type can detect InDesign INDD and INDT files and templates. For these file types, the MediaType.EnsuredTypes property contains application/x-indesign. For details, see Media Type Detection for InDesign.

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 .* to .*. 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.

Resolved Issues in the 12.1.1 Release   

This release resolves known issues.

NOTE: Secure Web Gateway 12.1.1 is provided as a controlled release.      

For information about how to upgrade to this release, see Upgrading to a New Version - Controlled Release.

JIRA issue numbers are provided in the reference columns.

Upgrade from 12.1.0 to 12.1.1

  1. yum install  kernel --downloadonly  --downloaddir=/root/
  2. rpm -i --force kernel-4.19.256-3.2.mlos3.mwg.x86_64.rpm
  3. mwg-switch-repo 12.1.1
  4. yum upgrade yum
  5. yum upgrade
  6. reboot

SWG Release version 12.1.0 was rolled back due to an identified performance Issue. Therefore, the List of Issues fixed in the aforementioned Version is available as resolved in the Current Release Version.

Reference Description
WP-5067 Sub rule sets are no longer deleted when importing a rule set via REST API.
WP-5108 Core dump issue related NHP and connection timeout has been fixed.
WP-5170 Parallel events can be handled again properly when the rule engine on Secure Web Gateway is called from a temporary proxy process transaction.

Fixed the following scenarios when secure NHP is used for plain HTTP requests:

  1. If multiple NHP’s are configured and TLS handshake or certificate verification fails, then next nhp in the list is not tried.
  2. If multiple requests are received over persistent client connection, then SWG switches to switches to non-secure NHP when server sends close notify alert.
WP-5225 When mirroring decrypted traffic with the SSL Tap feature, the source and destination IP addresses are not reversed.
WP-5226 Fixed performance and slowness issues caused due to an update in Kerberos package.

Vulnerabilities Fixed          

Reference Description


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:

  • CVE-2023-22809
  • Was this article helpful?