Advanced Secure Gateway 6.7.x Release Notes: Current Version: 6.7.4.9 Document Revision: 8/13/2019

Advanced Secure Gateway
6.7.x Release Notes
Current Version: 6.7.4.9
Document Revision: 8/13/2019

Release Note Directory

These release notes present information about Advanced Secure Gateway 6.7.x. Each section for a specific release
provides feature descriptions, changes, and fixes. Sections about known issues and limitations for Advanced
Secure Gateway 6.7.x are listed separately.
Release Index
n "Advanced Secure Gateway 6.7.4.9 PR" on page 4
n "Advanced Secure Gateway 6.7.4.4 LA" on page 32
n "Advanced Secure Gateway 6.7.4.2 LA" on page 44
n "Advanced Secure Gateway 6.7.4.141 EA" on page 46
n "Advanced Secure Gateway 6.7.3.6 GA" on page 98
-2-
Information About All Releases

n "Advanced Secure Gateway 6.7.x Limitations" on page 138
n "Advanced Secure Gateway 6.7.x Known Issues" on page 140
n "Advanced Secure Gateway Appliance Resources" on page 159
n (Advanced Secure Gateway 6.7.2) "About Security Certification" on page 160
n "Documentation and Other Self-Help Options" on page 162
-3-
Symantec Corporation Advanced Secure Gateway 6.7.x
Advanced Secure Gateway 6.7.4.9 PR

Release Information
n Release Date: August 13, 2019
n Build Number: 240930
Compatible With
n BCAAA: 5.5 and 6.1
n Reporter: 9.5.x; 10.1.x and later
n Management Center: 1.5.x through 1.11.x; 2.x
n ProxyClient: 3.4.x (ADN functionality not supported)
n Unified Agent: 4.7.x and later
n SSL Visibility: 4.1.1.x and later
n Advanced Secure Gateway Appliances:
n S500, S400, S200
See "Advanced Secure Gateway Appliance Resources" on page 159 for links to platform documentation.
Content Analysis
n This release includes Content Analysis version 2.4.x. Refer to Content Analysis documentation on MySymantec for
more information.
Third-Party Compatibility
n For supported Java, operating system, and browser versions, refer to TECH245893:
http://www.symantec.com/docs/TECH245893
Note: Java 8 Update 144 is currently not compatible with Advanced Secure Gateway
releases.
n For information on Java 11 support, refer to TECH252566
4 of 164
Upgrading To/Downgrading From This Release

n After upgrading to Advanced Secure Gateway 6.7.4 and configuring HTTPS forward proxy, some sites that were
allowed in version 6.7.3 are now denied. For details on a workaround, refer to
https://www.symantec.com/docs/TECH254549.
n The Advanced Secure Gateway Upgrade/Downgrade Quick Reference details the supported upgrade/downgrade paths
for this release:
https://www.symantec.com/docs/DOC11230
Fixes in Advanced Secure Gateway 6.7.4.9

n SGOS 6.7.4.9 includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.4.9" on the next page.
n To see any Security Advisories that apply to the version of Advanced Secure Gateway you are running, go to:
https://www.symantec.com/security-center/network-protection-security-advisories
New advisories are published as security vulnerabilities are discovered and fixed.
Limitations
n See "Advanced Secure Gateway 6.7.x Limitations" on page 138 for a description of limitations in this release.
Known Issues
n See "Advanced Secure Gateway 6.7.x Known Issues" on page 140 for a list of all issues that Symantec is aware of in
Advanced Secure Gateway 6.7.x.
5 of 164

Advanced Secure Gateway 6.7.4.9 includes bug fixes. This update:
Access Logging
ID Issue
SG-10547 Addresses an issue where the proxy restarted in process group "PG_ACCESS_LOG" in process:
"ALOGStream:elk_stream [0xc002f" in "libaccess_log.exe.so".
Content Analysis
ID Issue
SG-10009 Fixes an issue where ICAP errors occurred when Kaspersky Enhanced scanning was enabled.
Authentication
ID Issue
SG-3044 Fixes an issue where Internet Explorer did not prompt for credentials if a second consecutive login was
cancelled.
Symantec acknowledges Baskar Borman for reporting this vulnerability.
SG-4795 Fixes an issue where CAC authentication was slow when using an HTTPS console.
SG-4973 Addresses an issue where the the proxy restarted in process group "PG_CFG" in process "IWA Onbox Domain
Trust Refresher" in "liblikewise.exe.so".
Addresses an issue where the proxy restarted in process group "PG_LSA" in process "likewise lwmsg server
SG-5102
worker" in "libknl_api.so".
SG-5123 Addresses an issue where the proxy restarted in process group "PG_POLICY_HTTP" in process "LDAP
Authenticator" in "libopenldap.exe.so".
Fixes an issue where the CPU monitor showed that the LSA (Local Security Authority) was using a high
SG-8302
amount of CPU resources.
SG-9272 Fixes an issue where the error "Error connecting to SG" was seen when logging into the Management
Console.
Fixes an issue where the admin user was unable to authenticate on the Management Console when a cookie
SG-9435
wasn't cleared after the previous log out.
SG-10132 Fixes an issue where a suitable proper error message was not sent when a Kerberos replay attack occurred.
SG-10548 Fixes an issue where rejoining a Windows Domain failed after upgrade to 6.7.4.x from 6.7.3.14.
6 of 164
ID Issue
SG-11002 Fixes an issue where there the Event Log noted that the IWA Direct secure channel (Schannel) had reset
many times.
Fixes an issue where CAPTCHA validation could not be implemented because the CAPTCHA request was
SG-11130
looping on the proxy.
SG-11447 Fixes an issue where an authentication logout exception page was not returned when a SAML realm was
used.
Fixes an issue where the post-setup archive configuration contained the Windows Domain hostname instead
SG-12075
of the default hostname in IWA Direct (system created).
SG-12635 Addresses an issue where the proxy experienced a restart in process "Agent-Admin-CORP-233".
Fixes an issue where, after trying to join the domain, the proxy became unresponsive and stopped passing
SG-12978
traffic. The admin could ping the proxy but could not access the Management Console or SSH CLI.
DNS Proxy
ID Issue
SG-5317 Fixes an issue where the proxy did not accept CNAME as a valid DNS response.
SG-12243 Fixes an issue where DNS resolution failed when EDNS was enabled.
Event Logging
ID Issue
SG-12392 Fixes an issue where the Syslog was flooded by assert messages.
FTP Proxy
ID Issue
SG-8108 Addresses an issue where the proxy restarted in process group "PG_TCPIP" in process "FTP CW
102FEDA8430" in "libstack.exe.so".
HTTP Proxy
ID Issue
SG-9171 Fixes an issue where files could not be downloaded after a successful login to FTP server.
SG-9601 Fixes an issue where client workers maxed out due to DNS (UDP port exhaustion).
SG-9756 Fixes an issue where the proxy experienced a threshold monitor restart after the CPU was high in policy
evaluation.
7 of 164
ID Issue
Addresses an issue where the proxy restarted in process group "PG_DNS" in process "HTTP CW
SG-10873
10EC82F0A40" in "libmemory.so".
SG-10937 Addresses an issue where the proxy restarted in process group "PG_HTTP" in process "HTTP CW
10ADA60BA40" in "kernel.exe".
Addresses an issue where the proxy restarted in process group "PG_HTTP" in process "HTTP Admin" in
SG-11633
"libhttp.exe.so".
Management Console
ID Issue
SG-10839 Fixes an issue where ICAP object names did not appear under Proxy > Statistics > Content Analysis.
SG-11199 Fixes an issue where initial login attempts using the Management Console Launcher did not work.
SSL/TLS and PKI

ID Issue
SG-9276 Fixes an issue where the proxy restarted while adding a keyring to an existing keylist.
Fixes an issue where the proxy restarted after a slow growth in memory pressure in SSL and
SG-12405
Cryptography. This issue occurred when the proxy was operating as a reverse proxy.
SSL Proxy
ID Issue
SG-4434 Fixes an issue where ssl_failed exceptions occurred randomly.
SG-8079 Fixes an issue where the default keyring specified In the keylist did not show up In Sysinfo.
SG-9211 Fixes an issue where exception pages were not served or displayed for blocked websites. This issue occurred
as a result of on-exception SSL-interception not being triggered when expected.
TCP/IP and General Networking

ID Issue
SG-11038 Addresses an issue where the proxy was unable to establish WCCP connectivity to a router that did not
support WCCP v2.01.
SG-10832 Addresses an issue where the proxy restarted in process "stack-bnd-0:0-rxq-0" in "libstack.exe.so".
SG-10181 Fixes an issue where the SOCKS proxy did not preserve the source port for outbound connections, causing
connections to fail.
Addresses an issue where the proxy experienced a page fault restart in process group "PG_DNS" in process
SG-10037
"Mapi.http.worker" when there was a DNS query to the outlook.office365.com domain.
8 of 164
ID Issue
SG-9439 Addresses an issue where the proxy restarted in process group "PG_TCPIP" in process "SSLW
10C2B143FB0" in "libstack.exe.so".
Fixes an issue where CPU usage increased sharply and network throughput degraded when high volumes of
SG-9239
(mostly) bypassed traffic were sent to the proxy.
SG-8569 Fixes an issue where an unknown error response (203) on the proxy occurred when the DNS response was
truncated and contained more than 50 Nameservers.
SG-4333 Fixes an issue where turning on/off EDNS support on the appliance was not reflected in the event log.
SG-11481 Fixes an issue where the proxy did not adhere to the configured TCP window size, which intermittently caused
download slowness.
URL Filtering
ID Issue
SG-5060 Fixes an issue where the proxy was unable to perform Application Classification or Threat Risk Levels lookups
because the Management Console was logged in with a read-only account.
Visual Policy Manager

ID Issue
SG-12464 Fixes an issue where policy updates in the Web VPM were not showing up in the legacy VPM.
9 of 164

Release Information
n Release Date: July 24, 2019
Compatible With
n S500, S400, S200
Content Analysis
n This release includes Content Analysis version 2.3.5. Refer to Content Analysis documentation on MySymantec for
more information.
releases.
10 of 164

for this release:
11 of 164

n SGOS 6.7.4.8 includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.4.8" on the facing page.
Limitations
Known Issues
12 of 164

Content Analysis
ID Issue
SG-11504 Fixes an issue where AV service had high memory utilization.
Environment
ID Issue
SG-12638 Fixes an issue where the appliance stopped responding and host memory utilization was high. This issue
occurred after an upgrade to version 6.7.4.6.
Authentication
ID Issue
SG-9224 Addresses a restart in Process group: "PG_LSA" Process: "likewise lwmsg server worker" in
"liblikewise.exe.so" at .text+0x2b2829 HWE: 0xe, SWE: 0x0.
Health Checks
ID Issue
SG-13643 Fixes an issue where health checks failed or reported that the monitored component was not found. This issue
occurred after upgrading from version 6.6.5.14 to 6.7.4.7.
Fixes an issue where the health check subsystem did not notify the network stack when the internal Content
SG-13078
Analysis health check was set to disabled healthy.
SSL/TLS and PKI
ID Issue
SG-13642 Fixes an issue where the appliance stopped responding after the HSM IP address was changed.

ID Issue
SG-11621 Fixes an issue where client/server-based applications could not communicate via the appliance. PCAPs
showed the appliance responded with RESET for SYN on some connections. This issue occurred after an
upgrade to version 6.7.4.1.
13 of 164
URL Filtering
ID Issue
SG-12947 Fixes an issue where creating or editing an Application Name object in the legacy or web VPM object failed.
This issue occurred after an upgrade to version 6.7.4.5.
Fixes an issue where event logs displayed the error: CFS error: Failed to create PDM trend group
cfs
SG-8740
This issue occurred after an upgrade to version 6.7.4.2.
Web Visual Policy Manager

ID Issue
SG-11654 Fixes an issue where Enable HTTPS Interception was undefined when converting Java-based CPL to web
VPM CPL.
Fixes an issue where installing VPM policy resulted in a "Duplicate definition" error although policy did not
include duplicate definitions. This issue occurred when using Symantec Management Center to create
SG-5050 tenant/landlord policies in the VPM.
Note: This issue was fixed in version 6.7.4.6.
SG-13050 Fixes an issue where it was possible to create multiple identical Client IP Address/Subnet objects.
SG-10965 Fixes an issue where February 29th was not available in Time objects.
14 of 164

Release Information
n Release Date: June 14, 2019
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
15 of 164

for this release:
16 of 164

n SGOS 6.7.4.7 includes a fix. See "Fixes in Advanced Secure Gateway 6.7.4.7" on the next page.
Limitations
Known Issues
17 of 164

Advanced Secure Gateway 6.7.4.7 includes a bug fix. This update:
Authentication
ID Issue
SG-12836 Fixes an issue where the proxy experienced a restart in process group "PG_CFG_PROPRIETOR" in process
"IWA Onbox Domain Trust Refresher" when using IWA Direct in version 6.7.4.6.
18 of 164

Release Information
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
19 of 164

for this release:
20 of 164
Changes in Advanced Secure Gateway 6.7.4.6

By default, IWA-Direct realms list groups using sAMAccountNames. You can now specify that IWA-Direct realm lists groups
using their Common Names. Use the following command:
#(config iwa-direct realm_name)use-cn-group-names {enable|disable}

n SGOS 6.7.4.6 includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.4.6" on the next page.
Limitations
Known Issues
21 of 164

Boot
ID Issue
SG-10409 Fixes an issue where the proxy experienced a restart after upgrading from 6.6.5.17 to 6.7.4.3.
Content Analysis
ID Issue
SG-9047 Fixes an issue on the ASG-S400 and ASG-S200 platforms where Advanced Secure Gateway appliance are
not accessing or updating AV scanners after a re-manufacture or PXE boot.
Authentication
ID Issue
SG-11455 Fixes an issue where the authentication agent rejected a request when using tenant.request_url() in
landlord policy.
IPv6 Stack and IPv6 Proxies

ID Issue
SG-9182 Addresses an issue where the proxy experienced a restart in process "stack-bnd-3:0-rxq-1" in "libstack.exe.so"
when using IPv6.
Policy
ID Issue
SG-9039 Addresses an issue where the proxy experienced a restart in process "Parse exception list" in "libpoli-cy_
enforcement.so" after rebooting.
Addresses an issue where the local database should not accept the installation of policy that had a 'define'
SG-10294
block that does not terminate with 'end'.
Transformer
ID Issue
SG-9589 Addresses an issue where the page transformer corrupted data intermittently when the OCS sent chunked
Transfer Encoding.
22 of 164

ID Issue
SG-10656 Fixes an issue where the Web VPM did not allow comments in category definitions.
Fixes an issue in the Web VPM where adding the Request URL Category object returned an unknown
SG-11034
category error if there was any delay in the network.
23 of 164

Release Information
n Release Date: April 25, 2019
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
24 of 164

for this release:
25 of 164

The following changes were first made in SGOS 6.7.4.4.
This release adds the ability to configure the link aggregation transit delay. The transit delay setting determines how much
settle time link aggregation requires to switch from sending packets from an unlinked port to sending from a linked port.
Configure link aggregation transit delay time with the following CLI command:
#(config interface aggr:number)transit-delay 0-65535
Use this command to configure the transit delay time, in milliseconds (ms), for the specified link aggregate. The default value
is 3000 ms.
Note: During the settle time, all packets for an unlinked port are dropped. The settle time is
required to ensure packets are not received out-of-order when switching to a linked port to send
the traffic. Setting a smaller transit-delay time will reduce the number of packets lost during
the port transition, while increasing the possibility of out-of-order packets.

n Fixes listed in "Fixes in Advanced Secure Gateway 6.7.4.5" on the facing page were first included in SGOS 6.7.4.4.
Limitations
Known Issues
26 of 164

Advanced Secure Gateway 6.7.4.5 includes security advisory (SA) fixes and bug fixes.
Security Advisory Fixes in this Release

Advanced Secure Gateway 6.7.4.5 includes security advisory fixes. This update:
ID Issue
N/A Addresses OpenSSL vulnerabilities (CVE-2018-0739). For details, refer to SYMSA1443.
Security Advisories (SAs) are published as security vulnerabilities are discovered and fixed. To see SAs that apply to the
version of Advanced Secure Gateway you are running, including ones published after this release, go to:
Bug Fixes in this Release

Access Logging
ID Issue
SG-4874 Fixes an issues where the proxy restarted after configuring the access log with an SCP upload client and then
performing an upload log BCReporter operation.
Fixes an issue where the access log could not be retrieved via the CLI or a URL when there was a "." in the log
SG-5340
facility name.
SG-8343 Fixes an issue where the proxy experienced memory pressure when uploading the access log using SSH and
authentication failed.
Authentication
ID Issue
SG-4874 Addresses an issue where the proxy experienced a restart after it received a RADIUS accounting request.
SG-5340 Fixes an issue where LDAP authorization failed when using nested groups.
SG-8361 Fixes an issue where the proxy was unable to join a domain when RC4 encryption type was disabled on the
domain controller.
27 of 164
CLI Consoles
ID Issue
SG-9030 Fixes a slow upgrade issue on the Advanced Secure Gateway appliance when the system image (BCSI file)
was uploaded from the local file system.
28 of 164
Configuration
ID Issue
SG-9126 Fixes an issue on the Advanced Secure Gateway appliance where upgrading to version 6.7.4.3 failed and the
appliance reverted to a previous release.
DNS Proxy
ID Issue
SG-9182 Addresses an issue where the proxy experienced a restart when DNS recursion was enabled.
HTTP Proxy
ID Issue
SG-1308 Addresses an issue where the proxy experienced a restart in PG_TCPIP in process "HTTP CW
208353A5A40".
Addresses an issue where the proxy experienced a restart in process group "PG_TCPIP" in process "tcpip_
SG-4139
protocol_worker_1".
SG-8042 Addresses an issue where the proxy experienced a restart in process group "PG_ACCESS_LOG" in process
"ALOGAdmin:main" in "libhttp.exe.so".
Fixes an issue where the proxy served the whole object to clients for byte-range requests when the
SG-8273 Cachepulse service was enabled. This issue occurred when the byte range header was greater than
14Kbytes.
SG-8805 Addresses an issue where the proxy experienced a restart in process group "PG_HTTP", Process: "HTTP SW
6093C37AA40 for 7091D8E4A40" in "libhttp.exe.so".
Addresses an issue where the proxy experienced a restart in process group "PG_POLICY_FTP" in Process:
SG-8846
"PDW t=1262282600 for=848038BF".
ICAP
ID Issue
SG-8038 Fixes an issue where the exception page is not returned from the Symantec DLP server (in ICAP request
mode) when Use vendor's "virus found" page is enabled for the ICAP service.
Fixes an issue where changes made to the internal ICAP settings were not seen in the configuration file or the
SG-5657
SysInfo even though the changes took effect.
29 of 164
Policy
ID Issue
SG-4123 Fixes an issue where event logs displayed a "Failed to create a new tenant statistics node" error after adding
tenant policy.
Fixes an issue where rules match but sometimes don't execute when they are contained within a define
SG-4869
policy macro.
SG-5359 Fixes an issue where coaching policy did not work when tenant policy was present.
SG-8513 Fixes an issue where the Malware Scanning policy file could not be downloaded.
SSL/TLS and PKI

ID Issue
SG-5162 Addresses an issue where the proxy experienced a restart in the Threshold_Monitor process where the
highest consumers of memory were SSL and cryptography.
SG-5172 Fixes an issue where SSL inspection was inconsistent due to an invalid cache certificate.
SG-5328 Fixes an issue where the proxy reverted to version 6.6.5.17 after attempting to upgrade to version 6.7.4.1.
SG-5346 Fixes an issue where importing a CRL failed with an insufficient memory error.
SG-9067 Fixes an issue where the proxy experienced a restart in process group "PG_SSL_HNDSHK" in process "FTP
CW 4098B026430" in "libcfssl.exe.so" .
Fixes an issue where an expanded archive configuration could not be restored when it contained a CCL that
SG-9252
started with "bluecoat-".
30 of 164

ID Issue
SG-4867 Fixes an issue where packets could be dropped after losing a link aggregate. The following CLI command was
added to fix this issue:
#(config interface aggr:number)transit-delay 0-65535
The default value is 3000 milliseconds (ms).
SG-5079 Fixes an issue where client.interface= CPL returned 255.255 (an invalid adapter / interface).
SG-7863 Fixes an issue where the TCP three-way handshake was failing because S200 models were intermittently not
responding to SYN/ACK.
Addresses an issue where the proxy experienced a restart in process "stack-bnd-2:1-rxq-0" in "libstack.exe.so".
SG-8062
SG-8691 Addresses an issue where the proxy experienced several restarts in process SGRP Worker when using
multicast.
Addresses an issue where the proxy experienced a restart in process "stack-bnd-3:0-rxq-1" in "libstack.exe.so"
SG-8820
when using WCCP.
SG-8924 Addresses an issue where the proxy experienced a restart in process group "PG_TCPIP" in process "stack-api-
worker-1" in "libstack.exe.so".
Fixes an issue where executing a packet capture in a core image (e.g. 'pcap start last capsize XXXX coreimage
SG-9599
YYYY') can cause a monitoring violation (error code 0x5b).
URL Filtering
ID Issue
SG-5333 Fixes an issue where the Threat Risk Level lookup returned unavailable or none.
Addresses an issue where the proxy experienced a restart in process group "PG_OPP" in process "OPP_Wo
SG-8081
0x42b0bcc720" when using WebPulse.
SG-8410 Addresses an issue where the proxy experienced a restart in process "stack-admin" (0x4000cc) at
libstack.exe.so:0x611ddb.

ID Issue
SG-8624 Fixes an issue where the first installation of policy via the Web VPM caused errors in generated CPL. This
issue occurred when condition block names contained quotation marks and whitespace.
Fixes an issue where the Web VPM changed Bandwidth Management objects from limit_
SG-8818
bandwidth.server.inbound(class_name) to limit_bandwidth.server.inbound(no) by default.
31 of 164
Advanced Secure Gateway 6.7.4.4 LA

Release Information
Compatible With
n S500, S400, S200
Important Information About This Release

Advanced Secure Gateway 6.7.4.4 contains an issue that causes some appliances to restart. Symantec recommends
upgrading to "Advanced Secure Gateway 6.7.4.5 PR" on page 24 to resolve this issue. Advanced Secure Gateway 6.7.4.4 is
no longer available for download through MySymantec. Please refer to your Symantec point-of-contact for details.
for this release:
Content Analysis
more information.
32 of 164
releases.
33 of 164
Limitations
Known Issues
34 of 164

Release Information
n Release Date: January 25, 2019
Compatible With
n S500, S400, S200

Advanced Secure Gateway 6.7.4.3 fixes a serious issue where using the new Web Visual Policy Manager caused unintended
policy behavior when applying policy save/changes. For details, refer to SG-8612 in "Fixes in Advanced Secure Gateway
6.7.4.3" on page 40. Symantec recommends upgrading to this release to use the Web VPM without issue.
for this release:
Content Analysis
more information.
35 of 164
releases.

n Advanced Secure Gateway 6.7.4.3 introduces new features and enhancements. See "New Features in Advanced
Secure Gateway 6.7.4.3" on the facing page.

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.4.3" on page 40.
Limitations
Known Issues
36 of 164
New Features in Advanced Secure Gateway 6.7.4.3

Advanced Secure Gateway 6.7.4.3 introduces the following new features.
This release includes the new Web Visual Policy Manager (VPM). The Web VPM allows you to manage your organization's
policies in a redesigned web-based interface. The improved experience of writing and installing policy includes:
n Re-organized and modern look-and-feel in an easy-to-read browser tab
n Ability to compare current policy with deployed policy before saving changes
n Ability to identify and locate all conditions and actions in both generated and current policy
The legacy VPM is still available. Changes to policy using either VPM persist and are reflected in both VPM instances (except
in cases of downgrades).
Minimum Requirements
Supported browsers:
n Google Chrome 60.0.3112 and later
n Mozilla Firefox 57 and later
n Microsoft Edge 42.17134 and later
n Safari 10.1.2 and later
Caution: Microsoft Internet Explorer is not supported. If Internet Explorer is your default

browser (or if you use a supported browser that launches the VPM in Internet Explorer), you
can right-click and copy the Visual Policy Manager link at the top right of the Management
Console. Then, paste the URL into a supported browser.
Display resolution:
n 1366 x 768
In addition, the web-based VPM and all of its functionality are available in Symantec Management version 2.1.1.2. Refer to the
Management Center 2.1 Configuration & Management Guide for details.
n More information:
ProxySG Web Visual Policy Manager WebGuide
37 of 164
Periodic Upload of SysInfo Statistics
You can now configure the appliance to upload SysInfo reports at a set interval. Previously, the appliance supported only
manual uploads of SysInfo reports. The following CLI commands have been added to support this feature:
#(config service-info)periodic count count - Specify the maximum number of SysInfo reports to send.
#(config service-info)periodic disable - Disable the periodic upload of SysInfo reports.
#(config service-info)periodic enable - Enable the periodic upload of SysInfo reports.
#(config service-info)periodic interval interval - Set the interval (in hours) for periodic upload. For example, type
12 to send reports every 12 hours.
#(config service-info)periodic no - Clear the periodic upload parameters.
#(config service-info)periodic sr-number sr_number - Specify an SR number to associate SysInfo reports with a
Support case.
n More information:
Command Line Interface Reference
External Services Access Log Fields
New access log fields have been added to log communication times with external services:
n x-bluecoat-authentication-start-time: Authentication start time offset from the start of the transaction
n x-bluecoat-authentication-time: Time required to authenticate the user
n x-bluecoat-authorization-start-time: Authorization start time offset from the start of the transaction
n x-bluecoat-authorization-time: Time required to authorize the user
n x-bluecoat-ch-start-time: CH evaluation start time offset from the start of the transaction
n x-bluecoat-ci-start-time: CI evaluation start time offset from the start of the transaction
n x-bluecoat-co-start-time: CO evaluation start time offset from the start of the transaction
n x-bluecoat-icap-reqmod-delay-time: Time taken to connect to ICAP reqmod service
n x-bluecoat-icap-reqmod-service-time: Time taken for ICAP reqmod service once connected
n x-bluecoat-nc-start-time: NC evaluation start time offset from the start of the transaction
n x-bluecoat-si-start-time: SI evaluation start time offset from the start of the transaction
n x-bluecoat-so-start-time: SO evaluation start time offset from the start of the transaction
All times are expressed in milliseconds.
38 of 164
n More information:
Content Policy Language Reference
Enhancements from SGOS 6.7.4.1
This release includes the following enhancements from SGOS 6.7.4.1:
n The CLI command #show user has been renamed to #show user-info.
n CA certificates in the browser-trusted CCL have been updated. This updated trust package was posted for appliances
on October 16, 2018. For more information, refer to ALERT2309:
https://www.symantec.com/docs/ALERT2309
n This release includes additional security mechanisms which might result in an error message when using scripts to
send CLI commands to the proxy. To prevent the error "Server requires a valid encrypted token in the request" from
being returned by CLI command scripts, refer to TECH251582:
https://www.symantec.com/docs/TECH251582
39 of 164

Advanced Secure Gateway 6.7.4.3 includes security advisory (SA) fixes and bug fixes.

ID Issue
SG-5747 Addresses OpenSSH vulnerabilities (CVE-2018-15473). For details, refer to SYMSA1469.
SG-5361 Addresses OpenSSH vulnerabilities (CVE-2016-10708). For details, refer to SYMSA1469.

Access Logging
ID Issue
B#264042 Fixes an issue where access log uploaded over SCP upload failed with a no bytes sent from this
queue error code = -1 error. This issue occurred when the appliance stopped responding abruptly, or
SG-6009 had power failures or disk failures.
Content Analysis
ID Issue
SG-8242 Fixes an issue where Symantec Anti-Virus (AV) updates failed.
For details, refer to https://www.symantec.com/docs/ALERT2640.
Authentication
ID Issue
B#265632 Fixes an issue where the proxy stopped responding while performing LDAP authorizations.
SG-5058
40 of 164
ID Issue
B#265768 Fixes an issue where the proxy stopped responding when Nested Groups Support was enabled in LDAP realm
configuration.
SG-5810
B#267470 Fixes an issue where LDAP authorization failed when Nested Groups Support was enabled.
SG-5351
Fixes an issue where the proxy experienced a restart in PG:"PG_LSA", Process: "likewise Lsass_
SG-8425
ADSyncMachinePassword" in "liblikewise.exe.so" at .text+0x3ff5fc.
41 of 164
HTTP Proxy
ID Issue
B#258588 Fixes an issue where HTTP debug log filters did not work unless both client and server IP address filters were
set.
SG-5900
B#266536 Fixes an issue with memory pressure in the HTTP and FTP components when ProxySG policy or
configuration required request body inspection (for example, when performing handoffs from the HTTP proxy,
SG-2503 as with with MAPI or WebEx traffic).
B#265880 Fixes an XSS vulnerability in user-defined exception pages. Exception pages could contain unescaped user
input within the Symantec Site Review URL.
SG-4411
ICAP
ID Issue
B#265722 Fixes an issue where the event log did not display queued connection alert notifications. This issue occurred
when max connections and thresholds were set to minimum values.
SG-6081
Management Console
ID Issue
B#250440 Fixes an issue where the Overview, Content Analysis, and Sandboxing tabs displayed "Access Denied" when
logging in as a read-only user.
SG-5853
B#265634 Fixes an issue where Bandwidth Management statistics incorrectly showed the CurrentBandwidth value in
MBPS whereas the CLI reported values in KBPS.
SG-5834
Policy
ID Issue
B#264770 Fixes an issue where a SAML exception was generated when trying to authenticate a tunnel request.
SG-5074
Fixes an issue where the presence of a server_url= rule in policy, whose condition was not met, prevented
SG-8488
a configured exception in a matching rule from being served.
SSL/TLS and PKI

ID Issue
SG-8429 Fixes an issue where the proxy was unresponsive in HTTP Admin and experienced memory pressure.
42 of 164

ID Issue
B#254032 Addresses an issue where the appliance experienced a restart in process "stack-bnd-2:0-rxq-0" in
"libstack.exe.so" when using IPv6. This issue occurred due to IP fragmentation.
SG-4328
B#261765 Addresses an issue where the appliance restarted in process group "PG_OBJECT_STORE" in process "CEA
Cache Administrator."
SG-5962
B#264551 Fixes an issue with memory pressure in TCP/IP and DNS components when the DNS lookup name had a
trailing dot ('.').
SG-5046
B#267052 Addresses an issue where the appliance stopped responding when a packet capture was started with a
"coreimage" argument and then stopped via a pcap stop command.
SG-6152
B#267347 Addresses an issue where the appliance restarted when /TCP/wccp-routers did not show an IPv6 address
correctly.
SG-6165
B#267052 Fixes an issue where taking a PCAP caused the Management Console to stop responding. This issue
occurred when the buffer size was increased to the last matching 50000 KB.
SG-6152
URL Filtering
ID Issue
B#26618, Fixes an issue where differential updates of the Intelligence Services database caused increased disk load,
B#257744 which then caused delayed responses.
SG-5181, SG-4561

ID Issue
SG-8612 Fixes a serious issue where policy that included a User object was replaced with a Group object when policy
was applied. When this issue occurred, the incorrect policy was applied without compilation errors or
messages.
Fixes a serious issue where viewing policy in the Web VPM caused the policy to be corrupted. This issue
SG-8462
occurred after the policy was first applied in the Web VPM, and then applied again in the legacy Java VPM.
SG-8464 Fixes an issue where the VPM was unable to apply policy where a rule contained a Destination Host/Port
object with no host defined.
Fixes from SGOS 6.7.4.1

Advanced Secure Gateway 6.7.4.2 includes bug fixes from SGOS 6.7.4.1. See Fixes in 6.7.4.1.
43 of 164

Release Information
n Release Date: December 27, 2018
Compatible With
n S500, S400, S200

Advanced Secure Gateway 6.7.4.2 contains an issue where using the new Web Visual Policy Manager causes unintended
policy behavior when applying policy save/changes (SG-8612). Symantec recommends upgrading to "Advanced
Secure Gateway 6.7.4.3 PR" on page 35 to use the Web VPM without issue.
for this release:
Advanced Secure Gateway 6.7.4.2 is no longer available for download through MySymantec, but is available as a Limited
Availability (LA) release. Please refer to your Symantec point-of-contact for details.
Content Analysis
more information.
44 of 164
releases.
Limitations
Known Issues
45 of 164
Advanced Secure Gateway 6.7.4.141 EA

Release Information
n Release Date: October 24, 2018
Note: Advanced Secure Gateway 6.7.4.141 is an Early Availability (EA) release with

new/advanced functionality.
Previously, Symantec released new features in Limited Availability (LA) releases to specific
customers to access new functionality. This meant other customers were not able to access
these new capabilities until the release was General Availability (GA). With Early Availability
releases, all customers under valid support entitlement can gain access to this new
functionality.
Customers running this release should be considered early adopters of Advanced

Secure Gateway 6.7.4 to access new and advanced functionality. Early Availability releases
are supported like any other current Advanced Secure Gateway release. Once the Early
Availability release achieves broader adoption and quality metrics, it will transition to LTR
status.
Advanced Secure Gateway 6.7.4.1 GA was released on October 30, 2018.
Compatible With
n Reporter: 9.5.x; 10.1.x, and later
n Web Isolation: 1.10 and later
46 of 164
n SSL Visibility: 4.2.4.1 and later
o When using TLS offload, Advanced Secure Gateway 6.7.4 is not compatible with SSLV versions prior to 4.2.4.1.
o SSLV 4.2.5.1 and later now supports session reuse with SGOS 6.7.4. SSL session reuse was previously not
supported when using TLS offload with Advanced Secure Gateway 6.7.4 and SSLV 4.2.4.1.
n S500, S400, S200
Content Analysis
more information.
releases.

for this release:

n Advanced Secure Gateway 6.7.4.141 introduces new features and enhancements. See Features in 6.7.4.141 EA for
details.

n This release also includes fixes from SGOS 6.7.4.130. See "Fixes Included from SGOS 6.7.4.130" on page 57.
47 of 164
Limitations
Known Issues
48 of 164

Domain Fronting Detection
You can install policy on the ProxySG appliance to detect attempts at domain fronting. The following VPM Source column
objects are available in the Web Access Layer:
n HTTP Connect Hostname: Tests the hostname (the host value in the first line of the HTTP CONNECT request)
obtained from the original HTTP CONNECT request URL.
CPL condition: http.connect.host=
This object (and underlying condition) supports all substitution variables. For example, you can use the $(url.host)
substitution variable to compare the value of the url.host against the value specified by this object.
n HTTP Connect Port: Tests the port (the port value in the first line of the HTTP connect request) obtained from the
original HTTP CONNECT request URL.
CPL condition: http.connect.port=
You can add the following new access log fields to an access log format to help track possible domain fronting attempts:
n x-http-connect-host
n x-http-connect-port
n More information:
Visual Policy Manager Reference
SGOS Administration Guide
IPv6 Support for WCCPv2
This release includes support for IPv6 for WCCPv2. To use this feature, select 2.0 for the WCCP version (Proxy
> Configuration > Network > WCCP) on the appliance and enable WCCP IPv6 on your routers.
This feature has the following limitations in this release:
n Only L2 redirection is supported.
n Only Mask assignment type is supported; Hash is not supported.
n The default Mask value is 0x3f is not supported; you must specify a different value.
49 of 164
n Only Individual Home Router Addresses are supported; Multicast Home Router is not supported.
n Individual Home Router Addresses must include only IPv4 or only IPv6 addresses within the same Service Group.
n More information:
SGOS Administration Guide
50 of 164
New Features Included from Advanced Secure Gateway 6.7.4.130

This release includes the following features from Advanced Secure Gateway 6.7.4.130:
Include Surrogate Realms to realm= Tests in Policy
This release supports adding a surrogate realm for user authentication. You can use this property in conjunction with the
realm= condition. A realm specified in this property is used for surrogate authentication in addition to any other realms
specified in realm= tests in policy.
The following CPL was added to support this feature:
user.realm.surrogate(isolation_realm_name|no)
where:
n isolation_realm_name is a surrogate authentication realm
n no means not to use a surrogate realm
Consider the following example:
; layer 1
<proxy>
user.realm.surrogate(isolation)
...
; layer 2
<proxy> realm=corporate
category=gambling exception(content_filter_denied)
The proxy evaluates layer 2 as if the layer guard were realm=(corporate,isolation) and applies the content filtering policy
to users in those realms.
If Symantec Web Isolation is deployed upstream, you can include this property in policy for the proxy to authenticate users
based on identity and group membership defined in Web Isolation.
n More information:
Default TCP Window Size Increase
The default TCP window size has been increased from 64k bytes to 256k bytes.
To view the current TCP window size, issue the CLI command:
> show tcp-ip
51 of 164
To change the TCP window size, issue the CLI command:
#(config)tcp-ip window-size value
n More information:
Command Line Interface Reference
SGOS Upgrade/Downgrade WebGuide
Specify Upstream Server CCL for Forwarded Transctions
You can now specify the upstream server CCL certificate for forwarded transactions. Include the existing CPL property
server.certificate.validate.ccl() in the <forward> layer.
n More information:
52 of 164

Authentication
B# Issue
260520 Fixes an issue where the threshold monitor restarted the appliance due to increased memory pressure in SSL
and Cryptography.
Fixes an issue where using the CLI to test Windows SSO authentication with nested groups enabled caused
261934
the appliance to restart.
262567 Fixed an issue where the domain and IWA direct realm had an unhealthy status when the appliance was
functioning properly.
Fixes an issue where the appliance restarted in process "CLI_Worker_1" in "liblikewise.exe.so" when
263768
joining a domain before leaving the current domain.
HTTP Proxy
B# Issue
252242 Fixes an issue where the appliance restarted in process "HTTP CW 1093D428A40" in "libstack.exe.so"
when SSL interception was on.
Fixes an issue where the sc-bytes and cs-bytes values were incorrect in the access log when protocol detect
263076
was enabled.
264217 Fixes an issue where the appliance restarted in process group "PG_POLICY_HTTP" in process "PDW t=58806
for=2C005E9" in "libc.so" when the policy had rules to inspect raw response headers (such as,
response.raw_headers.regex).
ICAP
B# Issue
260165 Fixes an issue where the appliance did not send content to ICAP when the HTTP response header "trailer"
followed chunked data encoding.
Fixed an issue where the appliance restarted after reconfiguring the ICAP service and then changing the
261869
sense-settings feature.
IPv6 Stack and IPv6 Proxies

B# Issue
263695 Fixes an issue in process "WCCP_Admin" in "libwccp.exe.so".
53 of 164
Mnanagement Console
B# Issue
260464 Fixes an issue where the bandwidth statistics in the console displayed incorrect statistics for the parent class.
Fixes an issue where attempting to add an existing CA certificate that had a name containing spaces to a CCL
261869
via a Management Console failed.
Policy
B# Issue
262506 Fixes an issue where changing the configured malware scanning from an internal to an external content
analysis service required a manual VPM policy installation when tenant policy was used or pushed from the
Management Center.
Fixes an issue where users could not log in to or join a meeting using Skype for Business when the appliance
262197 was transparently deployed and had an authentication policy that allowed access to specific users and/or
groups.
262711 Fixes an issue where some tenant policies were missing after upgrading to SGOS 6.7.3.x.
Security
B# Issue
262574 Fixes an issue where a malicious server could cause a denial of service attack during a TLS handshake by
sending a large prime number that the client would spend a long time generating a key for.
262706 Fixes an issue where the Advanced Secure Gateway was vulnerable to a denial of service attack.
262907 Fixes an vulnerability in the OpenSSL RSA key generation algorithm where an attacker could have a cache
timing attack during the key generation process to recover the private key.
Services
B# Issue
261499 Fixes an issue where the default listener for TCP Port 514 could not be removed.
Fixes an issue where ADN attributes appeared on the HTTPS proxy service when using HTTPS on an
262653
Advanced Secure Gateway.
SSL/TLS and PKI

B# Issue
261878 Fixes an issue where the threshold monitor restarted the appliance due to increased memory pressure in SSL
Cryptography when SSL traffic was offloaded to an SSLV appliance.
Fixes a memory pressure issue in the SSL Cryptography cache where the license automatically updated every
262151
day.
54 of 164
System Statistics
B# Issue
262919 Fixes a service disruption that occurred after executing a clear statistics persistent CLI command.
55 of 164

B# Issue
256018 Fixes an issue where the appliance restarted in process group "PG_TCPIP" in process "HTTP SW
80F5AE4FA40 for 70FA5135A40" in "libstack.exe.so".
Fixes an issue where the appliance stalled during start-up if the first DNS server in the primary group was
258974
unreachable.
262273 Fixes an issue where the failover did not work correctly if the interface was disabled for the backup appliance.
263272 Fixes an issue where the appliance returned a false attack in the progress status from an SNMP walk.
263341 Fixes an issue that caused a restart in process cookie-monster in libstack.exe.so on edge boxes that
were using ADN after upgrading to 6.7.3.9.
URL Filtering
B# Issue
256952 Fixes an issue that occurred when renaming a category where the previous category name displayed until
rebooting the appliance.
257088 Fixes an issue where the risk level names in the Threat Risk Details UI summary were incorrect.
260887 Fixes an issue where the appliance restarted in process group PG_POLICY_SOCKS in process PDW
t=840754458 for=4002E9 in liburl_filter.exe.so.
Fixes an issue where configuring WebPulse to use a region based domain (for example, webpulse-
263782
us.es.bluecoat.com) added an invalid "service secure enable" which caused an error.
VPM
B# Issue
263518 Fixes an issue where policy could not be added using the VPM, even though it could be added via the CLI or
CPL.
Web Application Firewall

B# Issue
263811 Fixes an issue where the appliance restarted in process group "PG_WAF" in process "HTTP CW 70FAB6B2A40"
in "libwaf.so" when the CPL "engine=injection.command" was used.
Windows Media Proxy

B# Issue
262275 Fixes an issue where RTSP streaming did not work in a reverse proxy deployment.
56 of 164
Fixes Included from SGOS 6.7.4.130

This release includes the following security advisory (SA) fixes and bug fixes from SGOS 6.7.4.130.

B# Issue
258695 Addresses issue where multiple SAML libraries might have allowed authentication bypass via incorrect
XML canonicalization and DOM traversal. Refer to SA167.
SAs are published as security vulnerabilities are discovered and fixed. To see SAs that apply to the version of Advanced
Secure Gateway you are running, including ones published after this release, go to:

Access Logging
B# Issue
259923 Fixes a condition where the cache admin gets overloaded with requests from the access log admin. This
caused HTTP workers to spike out and resulted in delays.
Authentication
B# Issue
260100 Fixes an issue where configuring an LDAPS realm might cause a restart during startup due to a race condition.
Fixes an issue where the appliance is not able to decode SAML assertions, causing SAML authentication to
250240
fail.
258845 Addresses an issue where the appliance restarted in process group PG_LSA in process "likewise Netlogon_
PingCLDAP" in "liblikewise.exe.so".
Fixes an issue where the login dialog was bypassed when accessing the Management Console through port
259915
8082.
259571 Addresses an issue where the proxy restarted in process "likewise lwmsg server worker" in "liblikewise.exe.so"
(IWA Direct).
Fixes an issue where the Federated IDP SLO POST URL item was missing in the #(config)security
259905
saml view-realm CLI command output.
57 of 164
Client Manager
B# Issue
256189 Fixes an issue where an "Invalid archive" error occurred when attempting to upgrade Unified Agent using
the Local File option.
58 of 164
Collaboration
B# Issue
257124 Fixes an issue where client protocol detection policy client.protocol= condition did not match WebEx
operations as expected. Now, the following CPL matches WebEx operations:
client.protocol=https
Documentation
B# Issue
260400 Addresses missing information in the description of response.icap_feedback.force_interactive() in
the Content Policy Language Reference. The section now indicates that the property cannot be used to
override Always check with source before serving object or always-verify-source.
Removes erroneous information in the description of custom upload client for access logs in the
260983 SGOS Administration Guide and online help. The documentation now specifies that the custom client can use
IPv4 addresses only.
HTTP Proxy
B# Issue
259384 Fixes an issue where the Advanced Secure Gateway antivirus engine and pattern update failed when policy
contained a reflect_ip(client) rule that matched the internal Content Analysis subscription update
request. This caused the appliance to attempt to reflect the internal IPv6 address when connecting upstream,
which failed.
257793 Fixes an issue where downloads from www.filefactory.com did not work when CachePulse was enabled.
Licensing
B# Issue
259628 Fixes an issue where the licensing request-key command failed if the password contained special
characters (such as a plus sign or percent symbol) or a space.
Management Console
B# Issue
259239 Fixes a configuration issue that occurred when a user-created CCL name includes a space.
Fixes an issue where a second IPv6 gateway, added via the Management Console, did not appear in the
253734 Management Console. When this issue occurred, the CLI command show ip-default-gateway output
displayed the gateway correctly.
258679 Fixes an issue where the system did not delete the default route from the Management Console, even though it
was deleted from the routing table, when the interface IP address was changed or deleted.
59 of 164
Policy
B# Issue
252541 Restores BlockPopupAds functionality in the VPM. The object can now be used in VPM policy rules without
causing a 'Warning: Unreachable statement' error.
Fixes an issue where the policy parser ignored whether or not an end was present when a definition was at the
259748
end of the policy.
Proxy Forwarding
B# Issue
259850 Fixes an issue where the Active count did not decrement on Statistics > Advanced pages /Forwarding/StatsIP
and /Forwarding/StatsSummary. This issue occurred when a forwarding host was in use and certificate
verification failed during a HTTP/FTP-based document transfer.
SNMP
B# Issue
260655 Fixes an issue where a MIB file could not be loaded into an SNMP monitoring tool that did not support the
Integer64 data type.
SOCKS Proxy
B# Issue
258865 Addresses an issue where the appliance restarted in process group "PG_SOCKS" in process "Socks dpm
proprietor" in "libstack.exe.so".
SSL Proxy
B# Issue
257012 Fixes an issue where the x-cs-server-certificate-key-size access log field erroneously displayed RSA
[1024] in bypass mode.
Addresses an issue where the appliance became unresponsive and failed to intercept traffic when using
258274
STunnel.
258130 Fixes an issue where http.request.apparent_data_type and http.request.data.N policy were not
enforced.
SSL/TLS_and_PKI
B# Issue
260255 Addresses an issue where the appliance failed to import a DER-encoded Certificate Revocation List (CRL)
larger than 64k bytes.
60 of 164
SSLV Integration
B# Issue
256791 Fixes an issue in SSLV offload mode where increasing the TCP window size might have resulted in stalled
connections.
61 of 164
Security
B# Issue
259884 Fixes an issue where the appliance stopped responding due to an authenticated user's specially-crafted
HTTP request to the management service.
258634 Restricts some proxy CLI commands and functionality when logged in as read-only user.
257344 Improves the security posture of Client Manager service on port 8084 by removing weak ciphers and TLS
versions.
Fixes an issue where, under very specific conditions and for a short duration of time, user data was cached
259310
even though the OCS specified not to cache it.
259626 Addresses NULL injection issues in Proxy Management Console request handling.
258121 Extends memory resource allocation for proper regex evaluation by policy code.
256740 Fixes an issue where read-only users could access features and information that should be allowed only to
read-write users.
B# Issue
256543 Fixes an issue where DNS resolution failed when the first server in a custom DNS server list stopped working.
Fixes an issue where auto-linklocal IPv6 addresses could not be deleted when the interface had link-
255057
aggregation set.
258812 Fixes an issue where the client.interface gesture showed an invalid card number (such as 255:255.x) in
the policy trace when WCCP had router affinity set to "both" or “client”.
Addresses an issue where the appliance restarted in process "Threshold_Monitor" after about thirty days of
260856
operation.
259971 Fixes a performance issue with L2 return WCCP and bypass.
Addresses an issue where the appliance experienced a restart in PG_TCPIP in process "SGRP Worker" in
257434 "libstack.exe.so" when the network cable was removed. This issue occurred when SGRP was using the same
multicast address.
259677 Addresses an issue where the appliance experienced a restart in TCP/IP process "stack-admin" in
"libstack.exe.so.
Addresses an issue where the appliance experienced a watchdog restart with hardware exception 0x2 and
260330
software exception 0x11 in process "idler 0" in "kernel.exe".
257272 Fixes an issue where downloads of large files via SOCKS proxy on high-speed networks (speeds of 2 Mbps
and higher) timed out. This issue occurred when the proxy did not update the TCP window size.
62 of 164
URL Filtering
B# Issue
257872 Addresses an issue where the appliance stopped responding during initial bootup.
256858 Fixes an issue where a specific URL took a long time to load when DRTR is running in the background.
255954 Fixes an issue where some SSL websites did not load, even if WebPulse was running in background mode.
Addresses an issue where content filtering consumed high amounts of memory, causing threshold monitor to
256148
stop responding.
246810 Fixes an issue where the local content filtering database did not clear a subscription error after connectivity to
database server was restored.

B# Issue
258598 Fixes an issue where the VPM caused extraneous categories to be appended to the generated policy.
Fixes an issue where the Service Name and Service Group objects were not visible in the Service column in
258187
the Web Request Layer.
63 of 164

Release Information

releases, all customers under valid support entitlement can gain access to this new
functionality.

status.
Compatible With
o Advanced Secure Gateway 6.7.4 is not compatible with SSLV versions prior to 4.2.4.1 when using TLS offload.
o SSL session reuse was previously not supported when using TLS offload with Advanced Secure Gateway 6.7.4
and SSLV 4.2.4.1. SSLV 4.2.5.1 and later now supports session reuse with SGOS 6.7.4.
64 of 164
n S500, S400, S200
Content Analysis
more information.
releases.

for this release:

n This release includes a number of fixes and patch release fixes. See "Fixes in Advanced Secure Gateway 6.7.4.111" on
the next page.
Limitations
Known Issues
65 of 164

Advanced Secure Gateway 6.7.4.111 includes bug fixes and changes included in the 6.7.4.108 EA. This update:
Authentication
B# Issue
259265 Fixes an issue where a RADIUS access request packet showed an incorrect NAS-IP-Address attribute.
SSL Proxy
B# Issue
258994 Addresses an issue where the proxy experienced a restart in process group "PG_CFSSL" in process "SSLW
111DA576FC0" in "libtransactions.exe.so" during error handling.
259171 Fixes an issue where policy trace handoff transaction IDs were incorrect.
66 of 164

Release Information
n Release Date: March 22, 2018

releases, starting with 6.7.4.107, all customers under valid support entitlement can gain
access to this new functionality.

status.
Compatible With
n Reporter: 9.5.x; 10.1.x, and later
67 of 164
o Advanced Secure Gateway 6.7.4 is not compatible with SSLV versions prior to 4.2.4.1 when using TLS offload.
o SSL session reuse was previously not supported when using TLS offload with Advanced Secure Gateway 6.7.4
and SSLV 4.2.4.1. SSLV 4.2.5.1 and later now supports session reuse with SGOS 6.7.4.
n S500, S400, S200
Content Analysis
more information.
releases.

for this release:

n This release introduced a change to how the ProxySG appliance handles HTTPS forward proxy policy. For more
information see KB article TECH254549.

n This release includes a number of fixes and patch release fixes. See "Fixes in Advanced Secure Gateway 6.7.4.107" on
page 70.
68 of 164
Limitations
Known Issues
69 of 164

Advanced Secure Gateway 6.7.4.107 includes the following security advisory fixes and bug fixes.

B# Issue Fixed In
N/A Addresses NTP vulnerabilities. Refer to SA139. 6.7.4.101
N/A Addresses NTP vulnerabilities. Refer to SA147. 6.7.4.101
N/A Addresses OpenSSL vulnerabilities. Refer to SA141. 6.7.4.101
N/A Addresses NSS security vulnerabilities. Refer to SA153. 6.7.4.102
version of (missing or bad snippet) you are running, including ones published after this release, go to:

Advanced Secure Gateway 6.7.4.107 includes bug fixes and fixes from 6.7.4.105 - Patch Release Fixes. This update:
Access Logging
B# Issue Fixed In
251081 Fixes an issue where ProxySG access log configuration copied from an Advanced 6.7.4.101
Secure Gateway appliance and imported to another Advanced Secure Gateway
appliance were not identical. With this fix, the show config output shows any
changes to the mapi-http and DNS log formats.
Fixes an issue where the output for #show config did not indicate that SCP was set
250158 6.7.4.101
as the upload client.
Fixes an issue where the log tail for a selected log in the Management Console 6.7.4.102
250180 (Statistics > Access Logging > Log Tail) displayed the same entries multiple times
when new entries did not appear.
Fixes an issue where continuous access log upload stopped after logging directory
253658 6.7.4.107
slots ran out.
70 of 164
Authentication
B# Issue Fixed In
Fixes an issue where the appliance could contact only DCs in the local Active 6.7.4.105
Directory (AD) site to which the appliance belonged. As a result, because an
253544
appliance requires a read-write domain controller to join a domain, appliances with
only local access to a read-only DC were unable to join the AD domain.
Fixes an issue where Kerberos authentication failed after the appliance's machine
256029 account password was changed in Active Directory and the machine account was 6.7.4.107
enabled for aes-256 bit encryption.
Fixes an issue where the SNMP Schannel configuration stored incorrect CLI 6.7.4.107
252851 commands in the configuration archive, which prevented the configuration from being
restored.
Fixes an issue where the proxy experienced a page fault restart in process "HTTP CW
255299 F95FD4B90" in "libc.so" related to the timing of actions when using the auth/debug log 6.7.4.107
URL.
Fixes an issue where the domain controller (DC) reset the connection when the 6.7.4.107
253745
appliance sent an SMB1 Echo Request in an SMB2 environment.
Fixes an issue where AES authentication with Kerberos failed if the Kerberos load
254717 6.7.4.107
balancer username contained an upper-case letter.
CLI Consoles
B# Issue Fixed In
Fixes an issue where issuing the #show config command might have caused the 6.7.4.107
255576 appliance to restart if the URL set using #(config)statistics-export config-
path was invalid.
Configuration
B# Issue Fixed In
CAS-5024 Fixes an issue where the Sender e-mail address field in e-mail server configuration 6.7.4.105
restricted the top-level domain to six characters.
Content Analysis
B# Issue Fixed In
255592 Fixes an issue where scanning of some archive files in Advanced Secure Gateway 6.7 6.7.4.105
was slower than it was in version 6.6.
71 of 164
Health Monitoring
B# Issue Fixed In
Fixes an issue where the power supply severity setting (alert severity sensor 6.7.4.107
254545
power-supply) did not persist after an upgrade.
Management Console
B# Issue Fixed In
Fixes an issue where the Management Console did not accept system image
254660 6.7.4.107
download URLs consisting of more than 227 characters.
72 of 164
MAPI Proxy
B# Issue Fixed In
249746 Fixes an issue where email attachment scan results were cached, but subsequent 6.7.4.105
attachment downloads were sent to the ICAP server again instead of using previously
cached data.
Services
B# Issue Fixed In
254395 Addresses performance issues with AV scanning compressed files. 6.7.4.105
255120 Fixes issue where Symantec AV did not block sample test file (eicar) in REQMOD test. 6.7.4.105
SSL Proxy
B# Issue Fixed In
252087 Fixes an issue where the appliance did not use the SNI extension in the server-side 6.7.4.105
connection, which was required by some servers to respond with the correct server
certificate in the TLS handshake.
SSL/TLS and PKI
B# Issue Fixed In
250120 Fixes an issue where you could not create a new HTTPS Reverse Proxy service in the 6.7.4.105
Management Console (Configuration > Services > Proxy Services > New Service).
B# Issue Fixed In
252086 Fixes an issue where the appliance might have experienced a restart in PG_TCPIP 6.7.4.107
when Virtual IP was configured in failover mode.
Fixes an issue where the appliance sent gratuitous ARPs showing a Sender MAC
Address containing only zeroes (00:00:00:00:00:00). This occurred when the
255453 6.7.4.107
appliance was set as Master in a failover configuration and both aggregate interfaces
and VLAN were configured.
URL Filtering
B# Issue Fixed In
254474 Fixed an issue where differential database updates for Intelligence Services were 6.7.4.107
causing increased loads on disks, which caused delayed responses.
73 of 164
B# Issue Fixed In
Fixes an issue where the WebPulse tab (Configuration > Threat Protection
249253 > WebPulse) did not display database download status if Intelligence Services was 6.7.4.105
enabled.
256160 Fixes an issue where WebPulse did not categorize websites in a child/parent 6.7.4.107
configuration when a valid forwarding host was not supplied.
248868 Fixes an issue where enabling the Application Classification service took longer. 6.7.4.107
B# Issue Fixed In
255321 Fixes an issue where the appliance sent an invalid_request exception error page if 6.7.4.107
you logged out of the Management Console and then tried to access the consent
banner URL again with same browser.
74 of 164

Release Information
n Release Date: September 24, 2018
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
75 of 164

for this release:

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.3.12" on the facing page.
Limitations
Known Issues
76 of 164

Content Analysis
B# Issue
262990 Fixes an issue where the scanned object status is showed as 'No scanner available' when using the
Symantec AV engine.
SSL Proxy
B# Issue
265084 Fixes an issue where the cache size for the SSL session was limited to 48000 sessions, regardless of available
memory space.
77 of 164

Release Information
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
78 of 164

n See B#262122 in "Advanced Secure Gateway 6.7.x Known Issues" on page 140 for details on a 6.6.x downgrade issue
and workaround.
The Advanced Secure Gateway Upgrade/Downgrade Quick Reference details the supported upgrade/downgrade paths
for this release:

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.3.11" below.
Limitations
Known Issues

Authentication
B# Issue
258695 Fixes CVE-2018-5241.
Fixes an issue where the appliance restarted in process "CLI_Worker_1" in "liblikewise.exe.so" when
263768
joining a domain before leaving the current domain.
79 of 164
B# Issue
253544 Fixes an issue where the appliance was not able to join the active directory (AD) domain if it only had access to
a local, read-only domain controller (RODC). This issue occurred because the appliance needs a read-write
domain controller (RWDC) to join an AD domain. In prior versions, the appliance could contact other RWDCs in
remote locations to join.
The fix is a newCLI command that allows you to configure “Active Directory Site Awareness” under "security
windows-domains". By default, it is enabled. If disabled, a site name will not be returned for the domain, even if
one exists. Please see http://www.symantec.com/docs/TECH247930 for more information.
262019 Fixes an issue where the appliance was unresponsive after HTTP workers spiked.
CLI_Consoles
B# Issue
254410 Fixed an issue where the proxy restarted in process group "PG_CLI" in process "CLI_Worker_2" in "libc.so"
when the "(config ssh-client known-hosts)fetch-host-key" command was executed in the CLI.
HTTP Proxy
B# Issue
257452 Fixes a software restart in process group "PG_CFSSL" in process "HTTP SW 3B4CB2CB50 for 2E394F2B50".
Fixes an issue where the appliance restarted in process "HTTP CW 1093D428A40" in "libstack.exe.so"
252242
when SSL interception was on.
264217 Fixes an issue where the appliance restarted in process group "PG_POLICY_HTTP" in process "PDW t=58806
for=2C005E9" in "libc.so" when the policy had rules to inspect raw response headers (such as,
response.raw_headers.regex).
SSLV Integration
B# Issue
258714 Fixes a case of websocket connection failure that occurred when SSLV offload was setup.
80 of 164

B# Issue
256018 Fixes an issue where the appliance restarted in process group "PG_TCPIP" in process "HTTP SW
80F5AE4FA40 for 70FA5135A40" in "libstack.exe.so".
260654 Fixes an issue where a unit with a 10Gb fiber NIC stopped processing packets.
URL Filtering
B# Issue
254474 Fixes an issue where Intelligence Services differential database updates caused increased disk load, which
sometimes caused delayed responses.
81 of 164

Release Information
n Release Date: August 10, 2018
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
82 of 164

n See B#262122 in "Advanced Secure Gateway 6.7.x Known Issues" on page 140 for details on a 6.6.x downgrade issue
and workaround.
The Advanced Secure Gateway Upgrade/Downgrade Quick Reference details the supported upgrade/downgrade paths
for this release:

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.3.10" on the next page.
Limitations
Known Issues
83 of 164

Authentication
B# Issue
262567 Fixes an issue where the domain and IWA direct realm displayed as unhealthy when the system was
functioning properly.
Fixes an issue where configuring an LDAPS realm might have caused a restart during start-up due to a race
260100
condition.
260520 Fixed an issue where the threshold monitor restarted the proxy due to increased memory pressure in SSL and
Cryptography.
Policy
B# Issue
262711 Fixes an issue where some tenant policies were missing after upgrading to 6.7.3.x.
SSL/TLS and PKI

B# Issue
261878 Fixes an issue where the threshold monitor restarted the appliance due to an increase in memory pressure in
SSL Cryptography. The increase in pressure occurred when the appliance was offloading SSL traffic to an
SSLV appliance.

B# Issue
263341 Fixes a restart in process "cookie-monster" in "libstack.exe.so" on edge boxes that use ADN. This issue
occurred after upgrading to 6.7.3.9.
84 of 164

Release Information
Compatible With
n S500, S400, S200
Content Analysis
more information.
releases.
85 of 164

for this release:

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.3.9" on the facing page.
Limitations
Known Issues
86 of 164

ASG/CAS
B# Issue
262021 Fixes an ASG issue where antivirus updates were unable to update when the /encrypted-data partition was
full.
Authentication
B# Issue
255998 Fixes an issue where the appliance hung when the Windows SSO realm was performing self-authorization. A
CLI command (return-ldap-dn) was added to enable or disable the retrieval of the user's LDAP FQDN from
Active Directory. By default, this command is enabled for backward compatibility.
HTTP Proxy
B# Issue
258976 Fixes an issue where a webpage did not load and a 503 error was returned.
Proxy Forwarding
B# Issue
259850 Fixes an issue where the 'Active' count did not decrement on advanced-URL pages "/Forwading/StatsIP"
and "/Forwarding/StatsSummary". This issue occurred when a forwarding host was used and the certificate
verification failed during an HTTP/FTP-based document-transfer process.
SSLV Integration
B# Issue
261964 Fixes an issue where the appliance restarted after it received a TLS1.3 cipher suite value in the emulated
server handshake from an SSLV appliance.

B# Issue
259460 Fixes an issue where the appliance restarted in process group "PG_TCPIP" in process "stack-bnd-2:0-rxq-
0" in "libstack.exe.so".
87 of 164
URL Filtering
B# Issue
246810 Fixes an issue where the local content-filter database did not clear a subscription error after connectivity to the
database server was restored.
88 of 164
VPM
B# Issue
258187 Fixes an issue in the Web Request Layer where the service name or service group objects were not displayed
in the service column.
89 of 164

Release Information
Compatible With
n S500, S400, S200
Content Analysis
more information.

for this release:
90 of 164
releases.

Limitations
Known Issues
91 of 164

Content Analysis
B# Issue
257842 Fixes an issue where the "/cache-data" partition, used for updating AV engine patterns and definitions, might
have run out of space if the partition was too small.

B# Issue
260856 Fixes an issue where the proxy restarts in Threshold_Monitor in "" at .text+0x0 where the TCPIP component is
the biggest consumer of memory.
92 of 164

Release Information
n Release Date: May 1, 2018
Compatible With
n Unified Agent: 4.7.x andlater
n S500, S400, S200
Content Analysis
more information.
releases.
93 of 164

for this release:

n This release includes a number of fixes. See "Fixes in Advanced Secure Gateway 6.7.3.7" below.
Limitations
Known Issues


B# Issue
253827 Addresses security vulnerabilities. Refer to SA162.

94 of 164
Authentication
B# Issue
254934 Improves the performance of a proxy operating in a heavily utilized IWA direct environment using KCD.
Collaboration
B# Issue
251617 Fixes an issue where a proxy may experience a restart in process "WebExWorker" in "libforwarding.exe.so"
when WebEx Proxy connections were forwarded to different hosts or proxies.
Content Analysis
B# Issue
255592 Fixes an issue where, on some occasions, scanning archive files was slower than in Advanced Secure
Gateway 6.6.
Event Logging
B# Issue
253715 Fixes an issue where the proxy experienced a restart in SNMP due to memory pressure. This issue occurred
when the mail server was not reachable but mail requests continued to be added to the queue.
95 of 164
HTTP Proxy
B# Issue
256743 Fixes an issue the proxy experienced a restart at 0x7fff0003 in process "HTTP CW 84E43DB50" when
implementing a "request.icap_mirror(yes)" policy on a specific ICAP server.
Fixes an issue where, under very specific conditions and for a short duration of time, user data was cached
259310
even though the OCS specified not to cache it.
Management Console
B# Issue
253734 Fixes an issue where a subsequent IPv6 gateway added through the Management Console was not displayed
in the Management Console; however, the show ip-default-gateway CLI command output did display the
gateway.
Fixes an issue where the default route was not removed from the Management Console even though it was
258679
deleted from the routing table when the interface IP address was changed or deleted.
SOCKS Proxy
B# Issue
251496 Fixes an issue where the SOCKS UDP Associate failed to work with certain applications.
SSL Proxy
B# Issue
252087 Fixes an issue where the appliance did not use the SNI extension in server-side connections. The extension is
required by some servers in order to respond with the correct server certificate in the TLS handshake.
258274 Fixes an issue where the proxy became unresponsive and failed to intercept traffic when using STunnel.

B# Issue
256543 Fixes an issue where DNS resolution failed when the first listed server in a custom DNS group stopped
working.
Fixes an issue where the appliance became slow due to packets that were not processed within the queues
257053
associated with each NIC.
257272 Fixes an issue where attempts to download large files via SOCKS proxy on high-speed networks (2Mbps+
speed) timed out. This issue occurred because the proxy did not update the TCP window size.
Fixes an issue where the proxy experienced a restart in PG_TCPIP in process "SGRP WOrker" in
257434
"libstack.exe.so" when the network cable was removed while SGRP was using the same multicast address.
96 of 164
B# Issue
258812 Fixes an issue where the client.interface property showed an invalid card number (such as 255:255.x) in
the policy trace. This issue occurred when WCCP had router affinity set to "both" or “client”.
Fixes an issue where the proxy experienced slowness on a model with an ixgbe driver when using VLAN,
258918
bridging, and bypass.
259677 Fixes an issue where the proxy experienced a restart in TCP/IP process "stack-admin" in "libstack.exe.so.
URL Filtering
B# Issue
256148 Fixes an issue where the proxy experienced a Threshold Monitor restart with content filtering consuming the
highest amount of memory.
Fixes an issue where WebPulse did not categorize websites in a child/parent configuration when a valid
256160
forwarding host was not supplied.

B# Issue
255321 Fixes an issue where a user who logs out of the Management Console, and then tries to access the consent
banner URL again, receives an invalid_request exception error page.
97 of 164
Advanced Secure Gateway 6.7.3.6 GA

Release Information
n Release Date: March 30, 2018
Compatible With
n S500, S400, S200
Content Analysis
more information.

for this release:
98 of 164
releases.

Limitations
Known Issues
99 of 164

Advanced Secure Gateway 6.7.3.6 includes the following bug fixes. This update:
Access Logging
B# Issue
253658 Fixes an issue where continuous access log upload stopped after logging directory slots ran out.
The workaround for this issue was to reset the log facility slots by deleting the log objects using the commands
delete-logs CLI command.
Authentication
B# Issue
256029 Fixes an issue where Kerberos authentication failed after the appliance's machine account password was
changed in Active Directory and the machine account was enabled for AES-256 bit encryption.
CLI Consoles
B# Issue
255358 Addresses an issue where the Advanced Secure Gateway appliance under load might have experienced a
restart in process "tenable@ssh" in "libcli.exe.so".
Fixes an issue where issuing the #show config command might have caused the appliance to restart if the
255576
URL set using #(config)statistics-export config-path was invalid.
ICAP
B# Issue
257787 Fixes an issue where restoring defaults reset the Advanced Secure Gateway internal ICAP max connections to
25. Refer to ALERT2558 for details:
http://www.symantec.com/docs/ALERT2558
Kernel
B# Issue
252191 Fixes an issue where policy might not have installed when it included non-existent groups.
100 of 164

B# Issue
255453 Fixes an issue where where the Advanced Secure Gateway appliance sent gratuitous ARPs showing a Sender
MAC Address containing only zeroes (00:00:00:00:00:00). This occurred after the appliance was set as
Master in a failover configuration and when both aggregate interfaces and VLAN are configured.
101 of 164

Release Information
n Release Date: February 13, 2018
Compatible With
n S500, S400, S200
Content Analysis
more information.

for this release:
102 of 164
releases.

n You can now track policy setting updates for diagnostics purposes. The event log tracks the changes with the text
"Policy update settings from...".

Limitations
Known Issues
103 of 164

Advanced Secure Gateway 6.7.3.5 includes the following bug fixes. This update:
Access Logging
B# Issue
256116 Fixes an issue where the ProxySG appliance occasionally failed to boot. In this state, the appliance was not
accessible using the Management Console but was accessible via SSH console.
Authentication
B# Issue
257199 Addresses an issue where the ProxySG might have restarted in Process: "LDAP Authenticator" in
"libopenldap.exe.so" when follow referrals were enabled on the LDAP realm.
Content Analysis
B# Issue
255693 Fixes an issue where a Content Analysis process consumed an unexpected amount of memory which may
have caused the Advanced Secure Gateway appliance to restart.
ICAP
B# Issue
255415 Fixes an issue where the #(config icap service_name)defer-threshold and #(config icap
service_name)max-conn commands could not be set for the bluecoat-local-request and bluecoat-
local-response services.
Kernel
B# Issue
256335 Addresses an issue where the ProxySG appliance might have restarted in process "SSLW 10A271CA060" in
"libservices.exe.so".
MAPI Proxy
B# Issue
251762 Fixes an issue where the ProxySG appliance might have restarted in Process: "EPM Worker" when MAPI was
enabled.
104 of 164
Management Console
B# Issue
255167 Fixes an issue where adding an "Authentication required" comment in policy in version 6.7.3.1 caused the
Management Console to automatically log out after a successful policy installation.
Policy
B# Issue
254751 Fixes a memory leak in configuration (Process group PG_CFG).
SSL Proxy
B# Issue
253406 Fixes an issue causing increased SSL memory utilization.
Fixes an issue where accessing an HTTPS site failed with an error "Client certificate not received" due to the
254374
appliance being unable to send the imported client certificate.
255468 Addresses an issue where the appliance might have restarted in Process group: "PG_CFSSL"in process "HTTP
SW 1097B7B5A40 for 10968ABBA40".

B# Issue
255536 Fixes an issue where bandwidth management did not work correctly when used in a nested class.
Fixes an issue where Connection Forwarding (CCM) may cause the appliance to restart in Process "NIC I/O
255540
0:0-em_n 0 Deallocation worker" when forwarding a connection to another ProxsySG appliance via IPIP.
256204 Fixes an issue where the appliance might have restarted in Process: "cookie-monster" in "libmemory.so" when
CCM (Connection Forwarding) is enabled.
Fixes an issue where the appliance restarted when starting or stopping a packet capture (PCAP) with filters and
256213
the PCAP reaches its limit.
256391 Fixes an issue where the appliance might have restarted in Process: "stack-bnd-2:0-rxq-0" in "libstack.exe.so"
with encapsulated IPv6 traffic.
256718 Fixes a memory leak In TCP/IP when port spoofing was configured.
105 of 164

Release Information
n Release Date: 12/12/2017
n Build Number:211137
Compatible With
n Management Center: 1.5.x through 1.11.x
n S500, S400, S200
Content Analysis
n This release includes Content Analysis version 2.2.x. Refer to Content Analysis documentation on MySymantec
for more information.

n The Advanced Secure Gateway Upgrade/Downgrade Quick Reference details the supported upgrade/downgrade
paths for this release:
releases.
- 106 -

n Advanced Secure Gateway 6.7.3.2 introduces the following new CLI to allow you to configure the defer threshold
and maximum connections:
#(config)content-analysis
#(config content-analysis)edit bluecoat-local-request
#(config icap bluecoat-local-request)max-conn <number_of_connections>
ok
#(config icap bluecoat-local-request)exit
#(config content-analysis)edit bluecoat-local-response
#(config icap bluecoat-local-response)defer-threshold <threshold_as_percentage>
ok
#(config icap bluecoat-local-response)max-conn <number_of_connections>
ok
Note the following about the commands:
n max-conn<number_of_connections> applies to both request and response service.
n defer-threshold <threshold_as_percentage> applies to only the response service.
Note: These settings are not persistent across reboots. This limitation will be addressed in
a future release.

Limitations
Known Issues
n See "Advanced Secure Gateway 6.7.x Known Issues" on page 140 for a list of all issues that Symantec is aware
of in Advanced Secure Gateway 6.7.x.
- 107 -

B# Issue
253748 Fixes an issue where the appliance might have restarted in process "cookie-monster" due to a small race
condition affecting connections that were required to retransmit packets over a long period.
Fixes an issue where the appliance might have become unresponsive during the upgrade to 6.7.3.1 when
254461
IWA Direct authentication was used.
- 108 -

Release Information
n Release Date: 11/21/2017
Compatible With
n S500, S400, S200
Content Analysis
releases.

- 109 -


Limitations
Known Issues
- 110 -

Content Analysis Features

Symantec Antivirus
This release offers support for the Symantec antivirus engine.
Symantec antivirus is available with a subscription-based license. Configure antivirus scanning configuration in the
Management Console (Content Analysis > Services > AV Scanning Behavior).
n Full information:
Advanced Secure Gateway 6.7.x Help — Set AV Scanning Behavior Options
Symantec Advanced Machine Learning
By combining deep knowledge of threats and files with state-of-the-art machine learning, Symantec Advanced Machine
Learning (AML) is able to understand characteristics of files and create a probability score to determine whether a file is
safe. Rather than using signatures to match patterns, machine learning uses proven, well-tested, statistical methods to
learn about files. Using this approach, new and previously unknown threats can be stopped. Even when the attack
changes--through replication mechanisms, distribution mechanisms or the payload itself--AML works to stop threats
effectively.
After scanning a file to understand its characteristics, the AML algorithm computes the probability of a file being
malicious. This probability score determines what Content Analysis should do next with the file.
n Files with a high probability of being malicious will be blocked outright (convicted).
n Files with a low probability of being a threat are tagged "clean" and allowed for normal use (exonerated).
n Suspicious files will be sent to configured AV engines for further analysis.
Symantec Advanced Machine Learning is included with antivirus subscriptions. It is activated when you activate the
Symantec Antivirus license.
n Full information:
Advanced Secure Gateway 6.7.x Help — Improve Malware Scanning Results with Predictive Analysis
Symantec Cloud Sandboxing
Symantec offers a cloud-based dynamic malware analysis service that provides the ability to detect advanced threats. In
addition to detonating and detecting malware on virtual machines, Symantec Cloud Sandboxing uses a suite of analysis
technologies, coupled with Symantec global intelligence and analytics data, to accurately detect malicious code.
In addition, Cloud Sandboxing uses a behavioral analysis system that monitors files as they run, comparing the behaviors
of the program to the behaviors of the billions of malicious samples Advanced Secure Gateway has analyzed over the
years. As opposed to signatures, Cloud Sandboxing employs behavioral profiles and file reputation data to accurately
identify files as benign or malicious.
- 111 -
The Symantec Cloud Sandbox service is subscription-based and requires no configuration other than activating the
license and enabling the service (Sandboxing > Settings).
n Full information:
Advanced Secure Gateway 6.7.x Help — Configure Sandbox General Settings
Proxy Features
Policy for Specifying Cookie Persistence in Authentication
You can now control cookie persistence during user authentication. The following CPL action was added:
authenticate.persist_cookies(auto|no|yes)
where:
n auto means that the cookie persistency value configured in the realm will be used.
n no means that the session cookie will be used in authentication in this transaction.
n yes means that the persistent cookie will be used in authentication in this transaction.
n Full information:
Specify the Client Certificate Validation CCL via VPM
A Set Client Certificate Validation CCL object is available in the Visual Policy Manager (VPM). Use this object to
specify the client certificate list (CCL) to use for matching intercepted SSL connections.
This policy object generates the following CPL (the condition was added in version 6.7.2):
client.certificate.validate.ccl(CCL_ID)
To use the policy object, add a rule to the SSL Intercept Layer and select Set Client Certificate Validation CCL from
the Action column.
n Full information:
Visual Policy Manager Reference
Enhancements and Changes in Advanced Secure Gateway 6.7.3.1
Advanced Secure Gateway 6.7.3.1 introduces the following enhancements and changes:
Configurable Port for Symantec Malware Analysis Sandboxing
This release allows you to configure the port for communication with Symantec Malware Analysis. When you add or edit a
Malware Analysis server, the Add Server dialog shows a new Port field. This enhancement allows integration with
an external Content Analysis 2.1 server, which includes Malware Analysis. By default, the port value is 443.
n For integration with Content Analysis on-box sandboxing, specify port 8082 (requires CA v2.1 or later).
n For integration with standalone Malware Analysis, use the default port 443.
- 112 -
SSL Intercept and DNS Layers Supported in Tenant Policy
SSL Intercept and DNS transactions now evaluate tenant determination policy in the landlord policy file. This allows
<ssl-intercept> and <dns> layers to be defined and executed in tenant-specific policy. Previously, these layers were
supported in the default tenant policy only.
ICAP Outbound Source IP Selection
When a network interface on the appliance is configured to use multiple IP addresses, the outbound source IP address
used in the connection from the Advanced Secure Gateway appliance to the ICAP server is now selected in a round-robin
manner. This selection process helps prevent port saturation under heavy load, especially when the connection is not
persistent.
Data Leak Exception Page
Users now see a data leak exception page when HTTP/HTTPS POST requests are sent to Symantec DLP and a policy
violation occurs.
HTTP Log Shows Reasons for Non-Cacheable Transaction
The HTTP log now indicates the reason(s) that a transaction is not cacheable. The information is logged as follows:
"Server response made transaction Non-Cacheable:reason(s)=<set of reasons>"
OpenLDAP Upgrade
This release supports OpenLDAP version 2.4.44.
- 113 -


B# Issue
N/A Addresses NTP vulnerabilities. Refer to SA139.
N/A Addresses NTP vulnerabilities. Refer to SA147.
N/A Addresses OpenSSL vulnerabilities. Refer to SA141.
N/A Addresses NSS security vulnerabilities. Refer to SA153.

Access Logging
B# Issue
251081 Fixes an issue where ProxySG access log configuration copied from an Advanced Secure Gateway
appliance and imported to another Advanced Secure Gateway appliance were not identical. With this fix,
the show config output shows any changes to the mapi-http and DNS log formats.
Fixes an issue where the output for #show config does not indicate that SCP was set as the upload
250158
client.
Fixes an issue where the log tail for a selected log in the Management Console (Statistics > Access
250180
Logging > Log Tail) displayed the same entries multiple times when new entries did not appear.
Authentication
B# Issue
251438 Setting the windows-domains LDAP ping protocol as UDP might cause the appliance to restart.
CLI Consoles
B# Issue
250624 Fixes an issue where exceptions viewed via the Management Console (exceptions_config.html) had links
that did not show current exceptions.
- 114 -
Collaboration
B# Issue
252297 Fixes an issue where a failure during handoff caused the WebEx proxy to restart in process
"WebExWorkerManager" in "libc.so".
Fixes an issue where the Details field in Active Sessions didn't display information for 'symc.webex.com'
249338
connections.
HTTP Proxy
B# Issue
247731 Fixes an issue where pipelined requests did not follow routing domain rules.
Kernel
B# Issue
246322 Fixes an issue where the appliance restarted due to a page fault at 0xffffffffffffffc0 in process group "PG_
CFSSL" in process "HTTP CW 3D18931B50" in "kernel.exe".
Fixes an issue where the appliance was unresponsive until it was rebooted. The issue was caused by a
250933
large memory allocation from CFS downloader.
- 115 -
Policy
B# Issue
250453 Fixes an issue where the CPU0 usage was high when policy was updated in a multi-tenant policy
configuration.
Fixes an issue where the exceptions file (Configuration > Exceptions > View > Exceptions Configuration)
250179 did not show currently-defined exceptions. Clicking any link of a known exception displayed the message
"No exception found called '<exception_name>'".
SSL Proxy
B# Issue
252794 Fixes an issue where the RSA public exponent was always 3 for emulated certificates. For best security,
the public exponent now copies the existing public exponent for RSA server certificates.
SSL/TLS and PKI
B# Issue
248792 Fixes an issue where the threshold monitor restarted the proxy. This issue occurred when the SSL and
crypto memory usage were high.

B# Issue
249805 Fixes an issue where both proxies in a failover group reported as master. This issue occurred when the
group was configured with link aggregate (LAG) interfaces.
252709 Fixes an issue where the proxy stopped sending requests to the origin content server (OCS).
251889 Fixes an issue where Bandwidth Management Class with a child configured stopped a TCP
connection. This issue occurred when the parent's maximal bandwidth was reached.
Fixes an issue where packets might have exited an incorrect interface in IPv6 configuration when static
244784
routes were configured.
- 116 -

Release Information
n Release Date: November 14, 2017
Compatible With
n Reporter: 9.5.x and 10.1.x
n Unified Agent: 4.7.x and 4.8.x
n SSL Visibility: 4.1.1 and later
n S500, S400, S200
Content Analysis

n An incompatibility exists between Advanced Secure Gateway 6.7.2 and older versions of vsftpd FTPS server
using weak ciphers. Refer to TECH246741 for details:
- 117 -
Fixes in Advanced Secure Gateway 6.7.2.3 PR

n For fixes in this release, see "Fixes in Advanced Secure Gateway 6.7.2.3 PR" on the facing page.
Limitations
Known Issues
- 118 -

SSL Proxy
B# Issue
253377 Fixes an issue where random HTTPS pages did not load when SSL Proxy was used. Refer to
TECH248154 for details:

B# Issue
250616 Fixes an issue where the appliance might have restarted in Process group: "PG_TCPIP", Process: "stack-
bnd-2:0-rxq-0" in "libstack.exe.so". This issue occurred when delayed intercept was enabled.
Fixes an issue where the appliance might have restarted in Process group: "PG_TCPIP" in Process: "stack-
250637
api-worker-0" in "libmemory.so". This issue occurred when dynamic bypass was enabled.
- 119 -

Release Information
Compatible With
n S500, S400, S200
Content Analysis

- 120 -

n For fixes in this release, see "Fixes in Advanced Secure Gateway 6.7.2.2 PR" on the next page.
Limitations
Known Issues
- 121 -

Advanced Secure Gateway 6.7.2.2 is a patch release that includes the following bug fixes.

HTTP Proxy
B# Issue
250638 ProxySG may restart in Process: "HTTP SW 100C7373A40 for 4062EB83A40" in "libce_admin.exe.so"
when FSH caching is enabled, disk is full and reinitializing.
SSL Proxy
B# Issue
251011 When running SGOS 6.7.2.1, accessing some HTTPS sites will fail with Chrome or Fire Fox, when Protocol
Detection is enabled or SSL Interception is not enabled.
SG may restart in process: "CFSSL Cert Proprietor" in deployments with hundred(s) of CCL's and 600+
250323
certificates.

B# Issue
250732 Bandwidth Management may stop working after a while for higher limits (range of 100 Mbps and up).
ProxySG may experience a software exception code: 0x810001 in Process group: "PG_TCPIP" in Process:
250495
"stack-admin" causing the unit to restart when Bandwidth Management is enabled.
- 122 -

Release Information
Compatible With
n S500, S400, S200
Content Analysis

n The following are the supported upgrade/downgrade paths for this release:
o Upgrade to Advanced Secure Gateway 6.7.2.1 from version 6.6.5.7 or later.
o Downgrade from Advanced Secure Gateway 6.7.2.1 to version 6.6.5.7 or later.
n After upgrading or downgrading to this release, clear the browser cache to ensure you are displaying the correct
version of Content Analysis help topics.
n After an upgrade or downgrade, the current list of ciphers and the current list of HMACs—as shown in view
- 123 -
subcommand output—may change. If you modify the current list using the add, remove, and set subcommands,
the changes persist after system upgrades, downgrades, and reboots; however, the current list will not be identical
to the list prior to upgrade/downgrade if the system must consider deprecated ciphers and HMACs. (B#241332)
To understand the behavior after upgrade/downgrade, refer to #(config ssh-console)ciphers and #(config
ssh-console)hmacs in the "Privileged Mode Configure Commands" chapter in the SGOS Command Line
Interface Reference.


n Because this is the inaugural 6.7.x release, Symantec is reporting only security-related fixes for Advanced Secure
Gateway 6.7.2.1. See "Fixes in Advanced Secure Gateway 6.7.2.1" on page 136.
Limitations
Known Issues
- 124 -

Content Analysis Features

Integration with Symantec Endpoint Protection Manager
This Advanced Secure Gateway release supports integration with Symantec Endpoint Protection Manager (SEPM). After
configuring SEPM, the system sends administrators a threat alert when sandbox analysis determines a file to be
malicious. Administrators can then add the file hash to a file fingerprint hast list (blacklist) on the SEPM. Once the SEPM
knows about the threat, no other end users will be able to run the blacklisted file; this stops the lateral spread of a
malicious file on the network. In addition, administrators can use SEPM remediation policy to clean up the initial infection.
To configure this feature, select Settings > Endpoint Integration in the Sandboxing module.
n Full information:
Content Analysis 2.1 WebGuide — Integrate with Symantec Endpoint Protection Manager
Send Sandboxing Results to Reporter
After the Advanced Secure Gateway appliance sends Content Analysis files to be executed in a configured sandbox, it
receives a report on that activity and the data is visualized in the Overview and Content Analysis modules. The appliance
can also forward this data to Reporter, where it is matched with ProxySG data (based on the connection's transaction ID)
to create a set of reports for visualization in Symantec Management Center.
To configure content analysis uploads to Reporter, select Settings > Reporter in the Content Analysis module. To
configure ProxySG log uploads to Reporter, select Configuration > Access Logging > Logs > Upload Client in the
Proxy module.
Note: This feature requires the following additional software versions:

- Reporter version 10.4.1 and later
- Management Center version 1.6.1 and later
n Full information:
Content Analysis 2.1 WebGuide — Send Sandboxing Results to Symantec Reporter
SGOS Administration Guide — Configuring the Access Log Upload Client
- 125 -
Proxy Features
Support for Universal Policy
Universal policy is a set of global rules that you create in Symantec Management Center and apply to users in any
location. The policy can include global rules that apply to both on-premises and Web Security Service (WSS) users, as
well as individual rules that apply to only one or the other. It can also include location-specific policy when necessary. In
essence, universal policy comprises the various rules that reflect your organization’s acceptable use policy. Using
Management Center to distribute the policy to on-premises devices and the WSS makes it easy to apply the relevant
policy to all users in your organization.
To support universal policy, this release of SGOS allows you do the following on the appliance:
n Specify and change enforcement domains in the ProxySG Visual Policy Manager.
n Designate sections of policy as being appliance- or WSS-specific using the #if enforcement=appliance and
#if enforcement=wss variables, respectively.
n Specify the ICAP service type in the Management Console or in the CLI.
n Configure the enforcement classification file in the CLI.
Caution: Universal policy settings are not retained after a downgrade if you install VPM
policy in the downgraded version. For example, if you enable enforcement domains,
downgrade to a previous version of Advanced Secure Gateway (that does not support
universal policy), install VPM policy, and then upgrade to 6.7.x again, enforcement
domains are disabled and universal policy is lost. If you do not install VPM policy in the
downgraded version, however, universal policy settings are preserved if you upgrade to
6.7.x. This is expected behavior.
n Full information:
Visual Policy Manager Reference — The Visual Policy Manager
Content Policy Language Reference — Overview of the Content Policy Language
Command Line Interface Reference— Standard and Privileged Mode Commands and Privileged Mode
Configure Commands
Cloud Policy Configuration in Management Console
You can now configure cloud policy in the Proxy module (Configuration > Cloud Configuration > Cloud Registration);
previously, only CLI commands were available. See the Auto Policy Synchronization Quick Reference.
Detection and Improved Handling for Invalid Characters
In this release, support has been added for:
n Detecting invalid characters in HTTP response header lines
n Converting alternate whitespace characters in headers to standard spaces
n Improved handling of invalid characters at the beginning of header and HTTP 0.9 responses
- 126 -
n Detecting invalid HTTP version strings in HTTP response headers
n Improved handling of invalid/missing response codes
n Unfolding of normal and empty continuation lines in HTTP response headers
n Improved handling for different variations of chunked encoded responses
Tip: Symantec thanks Steffen Ullrich and his HTTP Evader tool for helping to identify
these issues.
DNS Access Logging
A new DNS access log for the DNS proxy was added as a default access log:
n dns is included in the #(config access-log) default-logging command.
n To configure the DNS access log, go to Proxy > Configuration > Access Logging > Upload Client. To trigger
log transfers to the client, go to Proxy > Configuration > Access Logging > Upload Schedule.
n IPv6 is not supported at this time.
n On downgrade, the DNS default log facility remains visible in the Management Console, though logging will not
work. Issue the #restore-defaults factory-defaults command to remove DNS access log objects.
SSLV Offload
In this release, you can connect one or more appliances to an SSL Visibility appliance running version 4.1.1 and later to
offload SSL/TLS traffic processing. Configuring SSLV offload requires that you identify the Advanced Secure Gateway
and SSLV appliances to each other using their respective serial numbers.
Configure SSLV offload on the appliance using one of the following methods:
n Managing SSLV appliances in the Proxy module (Configuration > SSL > SSLV Offload )
n Issuing the #(config ssl)sslv-offload command
You must also add Advanced Secure Gateway appliance information to the SSLV appliance(s). Refer to the following
documentation for complete steps.
n Full information:
SSL Visibility Appliance Administration & Deployment Guide
SGOS Administration Guide — Managing the SSL Proxy
Command Line Interface Reference— Privileged Mode Configure Commands
Routing Domains Configuration in Management Console
Routing Domains allow you to route traffic for unique networks through the same appliance, where each network has its
own gateway and DNS server. This release introduces this feature as a configurable option in the Proxy module
(Configuration > Network > Routing > Routing Domains).
- 127 -
Network HSM Failover
Hardware security module (HSM) failover applies to HSM keyrings contained in an HSM keygroup. If the appliance
encounters an error when attempting to use an HSM keyring, it is flagged as failed. The signing operations will be tried on
another member of the HSM keygroup, if applicable. The appliance will periodically attempt to see if the error has been
corrected. Once it has been, the HSM keyring will be put back into service.
n Full information:
Intercepting SSL with the SafeNet Java HSM
IWA Direct Feature Enhancements
n Previously, the appliance sent LDAP pings for domain controller discovery over the TCP protocol. In this release,
you can specify UDP or TCP as the protocol using the following command:
#(config security windows-domains)ldap-ping-protocol {tcp | udp}
When upgrading to this release, the TCP setting is preserved for existing Windows domains and the default for
new domains is UDP.
n By default, the appliance now uses the SMB2 protocol for connecting to the Active Directory server. If the server
still uses the SMB1 protocol, issue the following command:
#(config security windows-domains)smb2 disable
User Email Address Reporting
The appliance can report on the email address of an authenticated SAML or IWA Direct user. This allows you to include
the email address in:
n HTTP/S requests to the Elastica Cloud Access Security Broker (CASB) Gateway
n Access log formats, using the new field x-cs-user-email-address
n Exception pages and policy, using the new $(user.email_address) substitution variable
For unsupported authentication realms, the field returns an empty string.
Refer to TECH246128 for an example of how to send the email address in requests to the CASB service.
The following CLI subcommands were added for IWA Direct:
#(config iwa-direct realm_name)email-address enable
Enable the feature to report on the user's email address. Use in conjunction with the email-attribute subcommand.
#(config iwa-direct realm_name)email-attribute attribute
Specifies the attribute that represents the user's email address. Enable retrieval of this attribute with the email-address
enable subcommand.
The following CLI subcommand was added for SAML:
#(config saml realm_name)email-address-attribute attribute
Specifies the attribute that represents the user's email address and retrieves the value of the attribute.
- 128 -
Note: Map the SAML email address attribute to the relevant field on the IDP. For example,
if your IDP is Shibboleth, map the emailAddress attribute to the mail field.
n Full information:
Support article TECH246128: http://www.symantec.com/docs/TECH246128

Command Line Interface Reference — Privileged Mode Configure Commands
SGOS Administration Guide — Access Log Formats
Client Certificate Emulation
To facilitate choosing signing certificates for the client in a reverse proxy deployment, this release includes client
certificate emulation. When this feature is enabled:
n The appliance requests a certificate from the client.
n If the client returns a certificate, the appliance copies the certificate attributes to a new client certificate (so that it
appears to originate from the client). Emulation does not occur if the client does not return a certificate.
n The appliance presents the certificate during the SSL/TLS handshake when an OCS requests a client certificate.
The following CPL action was added to support this feature:
server.connection.client_issuer_keyring(no|<keyring_id>|
<hsm_keyring_id>|<hsm_keygroup_id>)
where:
n no disables client certificate emulation; this is the default setting
n <keyring_id> means to use the specified keyring for client certificate emulation. This must be a valid keyring,
specified on the appliance with a CA certificate.
n <hsm_keyring_id> means to use the specified HSM keyring for client certificate emulation.
n <hsm_keygroup_id> means to use the specified HSM keygroup for client certificate emulation.
n Full information:
SGOS Administration Guide- Managing X.509 Certificates
Content Policy Language Reference— Action Reference
TLS and Cipher Changes
New Defaults
On an initial upgrade to version 6.7.x, TLS 1.1 and 1.2 are the default protocol selections for the Management Console
and the SSL device profiles. TLS 1.1 will be used if 1.2 is not available. TLS 1.0 has been disabled by default. The default
ciphers suites have been correspondingly updated as well.
If the default protocols (TLS 1.0, 1.1, and 1.2) for the SSL device profile (as with the HTTPS Console service) were
selected previously, only TLS 1.1 and 1.2 are selected by default now. If the SSL device profile protocols were changed
from the defaults previously, the selections do not change.
- 129 -
n The predefined SSL passive-attack-protection device profile can be used by many services, such as
Authentication, Access-log, ICAP, Secure ADN, and OCSP.
n Interoperability issues may arise if a default or user-configured device profile is used to connect to a remote
service that does not understand TLS 1.1 or 1.2.
n Management Console will no longer connect to browsers that do not support TLS 1.1 or 1.2 (Chrome before v21,
Firefox before v23, Internet Explorer 8 and 9).
n If an SSL device profile uses a custom cipher suite, that cipher suite will be overwritten on upgrade.
n BCAAA may or may not support TLS 1.1. or 1.2. If the BCAAA connection fails, enable TLS 1.0 on the default SSL
device profile.
Notes:
o Windows XP and Windows Server 2003 do not support TLS 1.1 or TLS 1.2.
o Windows Vista and Windows Server 2008 do not support TLS 1.1 or TLS 1.2.
o If you are using a Windows version later than those listed here, do not edit the default SSL device profile.
n User-configured SSL device profiles and Management Console settings retain their previous settings. Symantec
strongly recommends updating the settings as soon as possible. If Management Center attempts to copy a
configuration containing these older protocols to a different device, the operation will fail, as the client device treats
copied device profiles as new profiles.
n The reverse proxy is unchanged. The defaults are TLS 1.0, 1.1, and 1.2 enabled. SSLv3 and SSLv3 are options.
n For the forward proxy, SSLv2 and v3 are disabled by default.
n SSLv2 and SSLv3 have been removed from the CLI for the Management Console and SSL device protocol;
attempting to use them will generate errors.
n On a downgrade from version 6.7.x , your selections do not change (whether you kept the default selections or
changed them).
Any subsequent upgrades to 6.7.x, for example after a downgrade, do not change the protocol selections; the protocols
selected prior to the subsequent upgrade are retained.
AES-GCM and SHA384 Ciphers Support
The appliance now supports the following cipher suites for SSL forward proxy, reverse proxy, Management Console, SSL
device profiles, and the SSL client as well as the existing forward proxy support:
n AES128-GCM-SHA256
n AES256-GCM-SHA384
n DHE-RSA-AES128-GCM-SHA256
n DHE-RSA-AES256-GCM-SHA384
n ECDHE-RSA-AES256-SHA384
n ECDHE-RSA-AES256-GCM-SHA384
- 130 -
ECDSA Signed Certificate Support
The appliance can now verify ECDSA certificates during the SSL handshake, as well as DSA and RSA.
Increased Key Sizes for Emulated Server Certificates
The key size supported for emulated DSA and ECDSA server certificates has been increased to 2048 bits. The key size
for emulated RSA server certificates is now matched up to a maximum of 4096 bits. For example, when the appliance
intercepts a 4k RSA server certificate, it will emulate a 4k certificate.
On downgrade, the previous RSA 2k and DSA/ECDSA 1k limits will be enforced.
Caution: High volumes of intercepting web sites with 4K RSA keys might affect
performance on smaller-scale models such as the SG-S200 series. For details and a
workaround for this issue, refer to TECH253498:
https://www.symantec.com/docs/TECH253498
n Full information:
SGOS Administration Guide — Configuring Management Services, Authenticating a ProxySG
Appliance, Managing SSL Traffic, Managing the SSL Proxy
SGOS Command Line Interface Guide — Privileged Mode Configure Commands
Authenticate Outbound SSH Connections
You can add host keys, select ciphers, and select HMACs to use for outbound SSH connections, such as the SCP
upload client for access logs. See "Configure SCP Upload Client " below for details.
To configure host keys, ciphers, and HMACs in the Management Console, select Configuration > Authentication >
SSH Outbound Connections in the Proxy module.
To obtain a host key from a remote host, use the Management Console (Configuration > Authentication > SSH
Outbound Connections > Known Hosts in the Proxy module).
The following CLI commands were added to support this feature:
#(config ssh-client)ciphers
#(config ssh-client)hmacs
#(config ssh-client)known-hosts
n Full information:
SGOS Administration Guide — Controlling Access to the Internet and Intranet
Configure SCP Upload Client
SGOS supports the secure copy protocol (SCP) upload client for access log uploads. To configure SCP for access log
upload, select Proxy > Configuration > Access Logging > Logs > Upload Client. Select SCP for the Client type.
The following commands were added to support this feature:
#(config log log_name)client-type scp
- 131 -
#(config log log_name)scp-client
Note: Before you can configure the SCP upload client, you must add host keys and select
ciphers and HMACs for outbound SSH connections, as described in " Authenticate
Outbound SSH Connections " on the previous page.
Kerberos Constrained Delegation
In deployments where the User Principal Name (UPN) is not included in client certificates, configure Kerberos
Constrained Delegation (KCD) to use the authorization username for authentication. Use the following CLI command:
#(config)security iwa-direct edit-realm realm_name

#(config iwa-direct realm_name)kcd-use-authz-name enable
where realm_name is your IWA realm name.
n Full information:
Using Kerberos Authentication in a Reverse Proxy Environment
Support for Application Groups
This release introduces CASB policy that organizes similar web applications into named groups. This feature improves
ease of use by providing you with the ability to write policy for groups of similar applications instead of writing multiple
rules for individual applications. In addition, note that:
n Applications can belong to more than one group.
n As new application are added, removed, or modified, the group information automatically reflects the change.
Application group policy and reporting are also updated.
To use this feature:
n Ensure that the appliance has a valid subscription for the CASB Audit AppFeed for SG. Modifications to CASB
data are automatically provided in database updates via the subscription feed.
n Enable the Application Classification service.
n Select Intelligence Services as the content filtering data source.
The following were added to support this feature:
n The ability to look up application groups for a URL and display the list of groups (in the Management Console,
Proxy > Configuration > Application Classification > General).
n In the bcreportermain_v1 and bcsecurityanalytics_v1 access log formats, an x-bluecoat-application-

groups field.
n An Application Group VPM object used to apply policy actions to a specified application group.
n A CPL condition request.application.group= to test the specified application group for a URL
- 132 -
n A CLI subcommand that displays supported application groups or the groups to which the specified application
belongs:
#(config application-classification)view groups [application <application_name>]
n Full information:
SGOS Administration Guide — Filtering Web Content, Creating Custom Access Log Formats, and
Access Log Formats
Visual Policy Manager Reference — The Visual Policy Manager
Content Policy Language Reference — Condition Reference
Possible Values of Application Attributes
Note: The data feed for this feature will be in Advanced Secure Gateway 6.7.4. To use this
feature, upgrade to 6.7.4 when that release is available.
This release introduces a CLI subcommand to display possible values for a specified application attribute:
n #(config application-attributes)view possible-values <attribute_name>
If an attribute name contains spaces, enclose it in double quotation marks ("). When writing policy that includes the
request.application.<attribute_name>= condition, use this subcommand to ensure that the CPL parameters
are valid.
To use this feature:
n Ensure that the appliance has a valid subscription for CASB Audit AppFeed for SG. Modifications to CASB data
are automatically provided in database updates via the subscription feed.
n Enable the Application Classification and Application Attributes services.
n Select Intelligence Services as the content filtering data source.
n Full information:
Enhancements and Changes in Advanced Secure Gateway 6.7.2.1
Advanced Secure Gateway 6.7.2.1 introduces the following enhancements and changes:
Pipelining Disabled by Default for Better Network Performance
Due to recent advances in web browsers, pipelining provides limited benefits and can increase CPU utilization in certain
workloads. Thus, in a new installation of 6.7.x, or upon an upgrade to this release, pipelining is disabled by default.
- 133 -
Ability to Add Kafka MessageSet Headers to Access Logs
If an access log has Kafka client and gzip file type selected, you can configure the appliance to add a MessageSet header
to the compressed log files so that the Kafka broker processes the data correctly as gzip-compressed data.
Use the following command to enable/disable the header (by default, the setting is disabled):
#(config log log_name)kafka-client [no] message-set-codec
Refer to the Command Line Interface Reference for details on this command.
Making any change to an access log's upload client configuration that reverses the previous MessageSet header state
(that is, the header's presence or absence in the log files) can cause future log uploads to fail. You must take additional
steps to ensure that logs are processed correctly; for details, refer to the SGOS Administration Guide.
Cipher and HMAC Support in FIPS Mode
After booting the appliance in FIPS mode, issue the following CLI commands to view the default cipher/HMAC lists,
current selections, and available ciphers/HMACs:
#(config ssh-console)view ciphers

#(config ssh-console)view hmacs
#(config ssh-client ciphers)view
#(config ssh-client hmacs)view
Enhanced CCL Policy
This release adds support for configuring the CA Certificate List (CCL) to use for a specific IP address or hostname.
When this object is not used, the default server certificate validation CCL is applied.
n Full information:
n SGOS Administration Guide - Specifying an Issuer Keyring and CCL Lists for SSL Interception
n Visual Policy Manager Reference - The Visual Policy Manager
n Content Policy Language Reference - Properties Reference
Skype for Business Support
In previous versions of SGOS, some Skype For Business and Microsoft Lync application connections failed when the
appliance intercepted SSL traffic on port 443 and UDP port 5061 was firewall-restricted. Some issues occurred with
logging in, joining meetings, meeting audio, and starting presentations. Issues occurred due to the following limitations:
n Lack of OCSP stapling/Certificate Revocation List (CRL) distribution point support
n Partial support for Session Initiation Protocol (SIP)
n Lack of support for Microsoft Traversal Using Relay NAT (MS-TURN) protocol
To restore chat client communications, this SGOS release supports:
n CRL distribution points on emulated certificates, which you configure in the SSL proxy service
n SIP and MS-TURN protocol detection and policy control, which you configure in the <ssl-access> layer
n Full information:
- 134 -
n Office 365 Integration & Best Practices WebGuide - Skype/Lync Fix: SGOS Configuration
n SGOS Administration Guide - Managing Outlook 365 Applications
n Visual Policy Manager Reference - The Visual Policy Manager
n Content Policy Language Reference - Conditions Reference and Properties Reference
n Command Line Interface Reference - Privileged Mode Configure Commands
- 135 -


B# Issue
N/A Patches vulnerable code. For details, refer to the Advisory Details section in SA117.
N/A Patches vulnerable code.For details, refer to the Advisory Details section in SA105.
N/A Patches vulnerable code. For details, refer to the Advisory Details section in SA132.

Security
B# Issue
235633 Fixes an issue where auto-complete was not disabled on password fields in forms on policy exception
pages.
After an upgrade to version 6.7.x, the system does not pick up the changes automatically; you must edit
your current exceptions manually to get the changes. Refer to the "Update Exceptions Manually" topic in
the SGOS Upgrade/Downgrade WebGuide for instructions.
Fixes an issue where a specially-crafted HTTP message could cause the appliance to stop responding
242427
when certain policy gestures were used.
HTTP Proxy
B# Issue
244110 Fixes an issue where HTTP(S) proxy upstream requests didn't have Host header canonicalized per
RFC7230.
Management Console
B# Issue
249339 Fixes an issue where using links (for example, from your site's internal webpages) to ProxySG advanced
URLs could result in "400 Bad Request" errors.
- 136 -
Advanced Secure Gateway 6.7.x Reference Information
Advanced Secure Gateway 6.7.x Reference

Information
The following sections provide reference and compatibility information for the Advanced Secure Gateway 6.6.x software
series.
n "Advanced Secure Gateway 6.7.x Limitations" on the next page
n "Advanced Secure Gateway 6.7.x Known Issues" on page 140
n "Advanced Secure Gateway Appliance Resources" on page 159
n "Documentation and Other Self-Help Options" on page 162
- 137 -
Advanced Secure Gateway 6.7.x Limitations

Symantec is aware of the following limitations. These are issues that are not fixable because of an interaction with third-
party products or other reasons, or they are features that work as designed but might cause an issue.
Authentication
The CLI might display the following message when you issue the rejoin command to re-join the appliance to the
Windows domain:
#(config security windows-domains)rejoin <domain_alias> <name> <password>
% The password is incorrect for the given account
The CLI responds with the message if you attempt a rejoin soon after using the join or rejoin command to join the
appliance to the same domain before all domain controllers (DCs) have synchronized. If this occurs, allow time for all
DCs to synchronize and attempt the rejoin again.
CASB AppFeed Uses Default BRR

When writing policy rules based on Business Readiness Rating (BRR), note that the CASB AppFeed applies its own
Default BRR; it does not apply tenants' BRR modified from Symantec CloudSOC. TECH247736 describes this behavior:
Dynamic Categorization in Secure Mode

The CLI command to enable secure mode for dynamic categorization is not available in verson 6.7.x.
Before upgrading, enable secure mode in 6.5.x. If you have already upgraded, downgrade to version 6.5.x, enable secure
mode, and upgrade again.
This deprecation was previously documented as B#237090.
Front Panel Configuration
The appliance supports only a static message on the LCD display on the front bezel. Configuration, status, or other
details typically available on the front panel display are not available.
Use the serial console to perform initial configuration steps, use SSH or the serial console to view current status and
appliance information.
Limited Signed Image Support

Installing images from HTTPS servers with a certificate signed by private CAs or with self-signed certificates is not
possible.
Install upgrade images using the link provided by the download page at MySymantec, from an HTTP-based server, or
from an HTTPS server with a certificate signed by a public CA.
Non-Functional Application Attributes Command

Advanced Secure Gateway 6.7.2.1 added the following CLI:
- 138 -
#(config application-attributes)view groups [attribute <attribute_name>]
This subcommand is visible in CLI output if you issue the ? help parameter; however, this CLI is non-functional. Do not
use this subcommand.
Note: This CLI was removed in version 6.7.4.
- 139 -
Advanced Secure Gateway 6.7.x Known Issues

Symantec is aware of the following issues in Advanced Secure Gateway 6.7.x.
Access Logging
ID Issue Fixed In
Workaround (if available) (when applicable)

The output for #show config does not indicate that SCP is set as the upload client "Fixes in Advanced
B#250158 (through either the CLI or the Management Console). Secure Gateway 6.7.3.1"
on page 114
The log tail for a selected log in the Management Console (Statistics > Access
Logging > Log Tail) displays the same entries multiple times when new entries do not "Fixes in Advanced
B#250180 appear. This issue occurs when there is a burst of traffic through the appliance, Secure Gateway 6.7.3.1"
followed by no traffic or very slow traffic. This issue does not occur if traffic through the on page 114
appliance is continuous.
Continuous access log upload stops after logging directory slots run out. "Fixes in Advanced
Secure Gateway 6.7.4.107"
on page 70
B#253658
"Fixes in Advanced
on page 100
SG-5340 Access log objects are not created when the name includes a period (".")
B#267383
Authentication
ID Issue Fixed In

SG-9435 Admin authentication does not work when a BCSI-AC cookie is present in the
browser.
B#261934 When testing Windows SSO authentication from the CLI and when nested groups are
enabled, the appliance might restart. Fixes in 6.7.4.140
SG-5812
140 of 164
ID Issue Fixed In

A fix for a previous issue (B#246848) was implemented to prevent latency/firewall- "Fixes in Advanced
related issues while contacting domain controllers (DCs) in remote geographical Secure Gateway 6.7.4.107"
locations. on page 70
B#253544
The fix introduced an issue where the appliance can contact only DCs in the local
Active Directory (AD) site to which the appliance belongs. As a result, because an
appliance requires a read-write domain controller to join a domain, appliances with
only local access to a read-only DC are unable to join the AD domain.
Kerberos authentication fails after the appliance's machine account password is "Fixes in Advanced
B#256029 changed in Active Directory and the machine account is enabled for AES-256 bit Secure Gateway 6.7.3.6"
encryption. on page 100
The SNMP Schannel configuration stores incorrect CLI commands in the "Fixes in Advanced
B#252851 configuration archive, which prevents the configuration from being restored. Secure Gateway 6.7.4.107"
on page 70
The proxy experiences a page fault restart in process "HTTP CW F95FD4B90" in "Fixes in Advanced
B#255299 "libc.so" related to the timing of actions when using the auth/debug log URL Secure Gateway 6.7.4.107"
on page 70
The domain controller (DC) resets the connection when the appliance sends an "Fixes in Advanced
B#253745 SMB1 Echo Request in an SMB2 environment. Secure Gateway 6.7.4.107"
on page 70
AES authentication with Kerberos fails if the Kerberos load balancer username "Fixes in Advanced
B#254717 contains an upper-case letter. Secure Gateway 6.7.4.107"
on page 70
Boot
ID Issue Fixed In

Issue: Downgrading from Advanced Secure Gateway 6.7.4.x to 6.6.x fails in the
following cases:
B#262122
n The restore-defaults command was performed on version 6.7.4.x
SG-5971
n The appliance was manufactured with version 6.7.4.x
Workaround: Downgrade to version 6.7.3.x before downgrading to version 6.6.x.
141 of 164
CLI Consoles
ID Issue Fixed In
B#255576 Issuing the #show config command might cause the appliance to restart if the URL "Fixes in Advanced
set using #(config)statistics-export config-path is invalid. Secure Gateway 6.7.3.6"
SG-6637 on page 100
Content Analysis
ID Issue Fixed In

SG-14222 The Advanced Secure Gateway appliance can experience one or
more silent host side restarts when a mini context is saved. This affects
Advanced Secure Gateway 6.7.4.9 and later, which uses Content
Analysis 2.4.x. There is no impact on the operation of the appliance.
Issue: Kaspersky anti-virus patterns in version 6.7.4.141 are not

compatible with older Advanced Secure Gateway releases.
CAS-6281
Workaround: After a downgrade from version 6.7.4.141, force an
update of the Kaspersky pattern files. In Services > AV Patterns, click
Force Update Now.
CAS-3156 When Content Analysis is integrated with Security Analytics, and

SNMP trap alerts are enabled for the Sandboxing Threat Admin Alert
(Asynchronous), the Security Analytics report URL does not show in
the trap message.
CAS-3190 Historical connections do not persist and are cleared upon shutdown.
CAS-2813 Content Analysis is able to decompress/extract files from archives that

have been compressed with gzip, bzip2, xz, lzip, and several other
popular compression algorithms. If the archive uses a supported
compression algorithm, Content Analysis is able to decompress the
archive and send files within the archive to configured sandboxes for
analysis. For zip and tar files with alternate compression algorithms
(Lzma, ppmd, deflate), Content Analysis is unable to decompress the
file but sends the archive to the sandbox if Content Analysis is
configured to send this file type. Whether the sandbox application or
service can decompress the archive and analyze its contents depends
on the capabilities of the program. In the case of Symantec Malware
Analysis, archives bypass sandbox analysis.
B#222291 In very rare instances, the appliance does not detect the file system in
a timely manner during bootup. When this issue occurs, the appliance
SG-2903 reboots. The subsequent bootup sequence is successful.
142 of 164
ID Issue Fixed In

B#222104 Issue: In rare cases, the Content Analysis configuration can be cleared
B#249720 during reboot. The frequency of occurrence is very low. If this issue
does happen, the Content Analysis configuration must be restored.
SG-2900
Workaround: As a preventative measure, save the Content Analysis
configuration in a secure location and ensure it is available.
B#231967 The "cas-audit" log feature available in standalone Content Analysis

B#256510 1.3.6.1 is not available in Content Analysis on the appliance.
SG-2897
B#215932 Content Analysis doesn't send email notifications when it's restarted,
even if E-mail is configured for the Reboot notification type.
SG-5382
OWA and Office Online (Office 365) URLs are treated as streaming This issue is resolved.
traffic.
Install the following policy to bypass
scanning of long-lived HTTP requests:
<Cache>
server_url.path=/owa/ev.owa2
server_url.query.regex="
(.*)ns=PendingRequest
B#237010 (.*)ev=PendingNotificationRequest
(.*)"
response.icap_service(no)
response.icap_service(proxyav,
fail_closed)
Note: You can specify

outlook.office365.com or
outlook.office.com.
B#238672 Email notifications for Content Analysis statistics are not working
correctly:
SG-5427
n Attachments are omitted.
n If using Java Web Start, the report title does not display the
Content Analysis appliance name.
Virus definition count isn't displayed for the Symantec AV engine. This
B#254218
graphical issue has no impact on the AV engine's performance.
B#255006 Kaspersky might fail with an antivirus_engine_error (26:0x80070057) if Fixes in 6.7.4.140

the OCS sends non-RFC2616 characters in file names.
143 of 164
Documentation
ID Issue Fixed In

The SGOS Administration Guide and Proxy online help incorrectly state that you can Fixed in February 2018.
B#253226 specify a hostname for the custom access log upload client. In both the Management
Console and the CLI, only an IP address is supported.
144 of 164
Event Logging
ID Issue Fixed In

B#215932 Content Analysis fails to send email notifications after a restart, even if E-mail is
configured for Reboot notification type.
SG-5382
FTP Proxy
ID Issue Fixed In

B#258715 When ICAP REQMOD mirroring is enabled for the FTP proxy, the s-action access
log field is occasionally not populated.
SG-4623
HTTP Proxy
B# Issue Fixed In

247731 Pipelined requests do not follow routing domain rules. "Fixes in Advanced
on page 114
HTTP debug log filters do not work unless both client and server IP filters are set. "Fixes in Advanced
258588 Secure Gateway 6.7.4.3"
on page 40
145 of 164
ICAP
ID Issue Fixed In

B#219269 Issue: Adding an ICAP server to or removing an ICAP server from a load balancing
group can, under some circumstances, cause the ProxySG appliance to stop
SG-2750 responding.
Workaround: Temporarily disable the health check for the ICAP object to reduce the
chances of this issue occurring. Symantec recommends that you do the following:
1. In the Management Console, select Configuration > Health Checks > General.
2. Select the health check for the ICAP object and click Edit. The console displays
an Edit Health Check dialog.
3. For Enabled state, select Disabled: Unhealthy.
4. Click OK > Apply to save your changes.
5. Add or remove the ICAP server to/from the load balancing group.
6. Repeat steps 1 -2. Then, re-enable the health check and save your changes.
Restoring defaults resets the Advanced Secure Gateway internal ICAP max
"Fixes in Advanced
connections to 25. Refer to ALERT2558 for details:
B#257787 Secure Gateway 6.7.3.6"
on page 100
http://www.symantec.com/docs/ALERT2558
SG-5657 The configuration file or SysInfo records do not reflect changes made successfully to Fixes in 6.7.4.4
internal ICAP settings.
263858
The exception page from the DLP server (request modifier) is not displayed when the
SG-8038 Fixes in 6.7.4.4
ICAP service is configured to use the vendor's 'virus found' page.
Initialization
ID Issue Fixed In

Issue: On the Advanced Secure Gateway, the birth certificate does not persist when
B#263609 the appliance is reinitialized from the bootloader.
SG-5650 Workaround: Use the CLI command “request-appliance-certificate” to request a birth

certificate.
146 of 164
Management Console
ID Issue Fixed In

B#260464 Issue: In the GUI, the bandwidth stats displays incorrect statistics for the parent class.
Workaround:To view bandwidth management statistics, view the CLI output (show
bandwitdh-management statistics) or access the JavaMC via the HTTP-Console.
B#217492 When you manually configure link settings for a link aggregation member interface,
the dialog provides an option to select Half under Link Settings. Half-duplex is not
SG-2794 available for aggregate interfaces.
Issue: A link aggregation member interface might display an incorrect state after you
B#217732 delete an aggregate link.
SG-2804 Workaround: To display the correct link state, refresh the Management Console page
in the browser.
B#249339 Using links (for example, from your site's internal webpages) to ProxySG advanced "Fixes in Advanced
URLs might result in "400 Bad Request" errors. Secure Gateway 6.7.2.1"
on page 136
B#222815 The Threats count on the ASG Overview tab shows -1 before any threats are
detected.
SG-2923
B#222816 The Files Blocked, Websites Blocked, and Blocked by Sandboxing metrics on the
Overview tab sometimes show -1 until they are populated with observed values.
SG-2924
B#222887 The web browser used to load the Management Console can occasionally restart if
the Management Console window is idle for a prolonged period of time.
SG-5389
B#223044 The value of Files Blocked by Policy on the Overview tab does not reflect the number
of files blocked by type when policy that uses free form entry rather than radio button
SG-2928 list is used.
The Overview, Content Analysis, and Sandboxing tabs display an "Access Denied" "Fixes in Advanced
B#250440 message when you are logged in as a read-only user. Secure Gateway 6.7.4.3"
on page 40
SG-5853
B#254660 The Management Console does not accept system image download URLs consisting "Fixes in Advanced
of more than 227 characters. Secure Gateway 6.7.3.6"
on page 100
B#260464 Statistics > Bandwidth Mgmt shows incorrect statistics for parent class. Fixes in 6.7.4.140
B#261869 Adding an existing CA certificate whose name contains spaces to a CCL fails when Fixes in 6.7.4.140
using the Management Console.
SG-7026
147 of 164
MAPI Proxy
ID Issue Fixed In

B#249746 Email attachment scan results are cached, but subsequent attachment downloads "Fixes in Advanced
are sent to the ICAP server again instead of using previously cached data. Secure Gateway 6.7.4.107"
on page 70
Performance
ID Issue Fixed In

B#242394 The appliance experiences performance degradation if CPU usage is greater than
70% and the appliance is in transparent bridging mode with a significant portion of
SG-3672 traffic being bridged.
B#234568 Higher DNS utilization occurs under heavy load conditions. This was discovered in
some internal performance tests.
SG-3252
Policy
ID Issue Fixed In

B#262506 If changing malware scanning from an internal to an external content analysis service Fixes in 6.7.4.140
and tenant policy is used or pushed from Management Center, you must manually install
a VPM policy.
In a transparent deployment, if authentication policy allows access for specific

B#262197 users/groups, users might not be able to join a meeting or log-in with Skype for Fixes in 6.7.4.140
Business.
B#236676 Issue: Disabling multi-tenant policy without first clearing tenant policy causes the
appliance to stop logging the request body although http.request.log_details
SG-3349 (header,body) exists in policy.
Workaround: Re-enable multi-tenancy, clear the tenant and landlord policy files, and
disable multi-tenancy again.
Issue: Users on mobile devices receive an Invalid Certificate Authority error when
B#242737 connecting to Google +. The issue occurs when using Google Chrome, Mozilla Firefox,
Internet Explorer, and the device's default web browser.
SG-2969
Workaround: Install the ProxySG appliance's SSL certificate on the mobile device.
148 of 164
ID Issue Fixed In

B#231634 When multitenant policy exists, the http.request.body.inspection_size()
property setting for the default tenant is always in effect, even if non-default tenants have
SG-2852 different settings for the property. For example, if tenant A's body inspection size is 12 KB
and the default tenant's is 10 KB, a request body size of 11 KB triggers an inspection
even if tenant A's policy applies to the transaction. When this issue occurs, however,
tenant A's http.request.detection.other.threshold_exceeded() setting is
respected and applies correctly to the transaction.
Consider the following example:
; default tenant policy

; inspect up to 10 KB of the HTTP request body
; monitor requests larger than 10 KB
<proxy>
http.request.body.inspection_size(10000) \
http.request.detection.other.threshold_exceeded(monitor)
; tenant A policy
; inspect up to 12 KB of the HTTP request body
; block requests larger than 12 KB
<proxy>
http.request.body.inspection_size(12000) \
http.request.detection.other.threshold_exceeded(block)
Given these rules:
n A request that is subject to tenant A policy and with body size of 11 KB should be
inspected in its entirety and not blocked. The request body’s first 10 KB are
inspected and the request is blocked.
n A request that is subject to tenant A policy and with body size of 13 KB should be
inspected up to the first 12 KB and blocked. The request body’s first 10 KB are
inspected and the request is blocked.
149 of 164
ID Issue Fixed In

Issue: When policy includes multiple forms of county names (such as short names, ISO
codes, and full names), IP addresses in geographical regions are allowed or denied as
intended, but policy traces show regions with an incorrect verdict. For example, consider
the following CPL:
<proxy>
supplier.allowed_countries[uS, US, "Us", Ca, "United States"]
B#249884 (deny)
SG-4058 This policy results in denials of IP addresses in Canada and the United States, but a
policy trace shows that "United States" is denied whereas "uS" is allowed.
Workaround: Do not use multiple formats for country names in policy. Use a consistent
format for all instances of country names, as follows:
<proxy>
supplier.allowed_countries["United States", Canada] (deny)
B#250179 The exceptions file (Configuration > Exceptions > View > Exceptions Configuration) "Fixes in Advanced
does not show currently-defined exceptions. Clicking any link of a known exception Secure Gateway
displays the message "No exception found called '<exception_name>'". 6.7.3.1" on page 114
B#251992 Policy performance is adversely affected when policy includes a large number of
categories assigned to a single URL. Fixes in 6.7.4.140
SG-4129
B#252806 Changing base user-defined exception fields does not update a policy-defined
exception.
SG-4248
Rules with a BlockPopupAds object result in a 'Warning: Unreachable statement' error "Fixes Included from
B#252541 when installing VPM policy. SGOS 6.7.4.130" on
page 57
The $(cs-categories) and $(cs-category) substitutions do not display the correct

SG-7926 Fixes in 6.7.4.4
URL rating on the coaching (NotifyUser) page.
SG-5359 Coaching policy does not work when tenant policy is installed.
B#267518
Serviceability
ID Issue Fixed In

SG-8213 Enabling monitor also unexpectedly enables periodic uploads. Fixes in 6.7.4.4
150 of 164
Services
ID Issue Fixed In

B#261499 You might not be able to remove the default TCP Port 514 listener. Fixes in 6.7.4.140
When using HTTPS, ADN attributes might appear on the HTTPS proxy service. Note
B#262653 Fixes in 6.7.4.140
that attributes can be ignored, except when restoring the configuration archive.
151 of 164
SSL Proxy
ID Issue Fixed In

SG-9211 Issue: SSL intercept policy set to on_exception does not work when policy includes
any of the following:
n server.certificate.hostname.category=
n malware scanning policy
The issue occurs because these policies involve server certificate category lookups.
Workaround: Use full SSL interception for URLs or categories that should be blocked.
The appliance does not use the SNI extension in the server-side connection, which is "Fixes in Advanced
B#252087 required by some servers to respond with the correct server certificate in the TLS Secure Gateway
handshake. 6.7.4.107" on page 70
B#220528 Issue: If you remove external certificates from the external certificate list (ECL) and then
delete those external certificates through the Management Console, the ECL state
SG-2866 becomes inconsistent on the appliance.
Workaround: Remove the external certificates from the ECL and apply the changes.
Then, delete the external certificates.
Issue: #show config output does not enclose the issuer-keyring name in quotation
marks. When the name includes spaces, subsequent attempts to apply the saved
B#225793 configuration fail.
SG-2985 Workaround: Copy and paste the relevant sections of #show config output into a text
editor. In the text editor, add the quotation marks around the keyring name manually, and
re-apply the inline configuration.
B#225611 When you change the SSL protocol version for a SSL device profile, the appliance
selects compatible ciphers from the list of previously selected ciphers instead of selecting
SG-2970 all the available ciphers for the new SSL protocol version.
Threshold monitor restarts occur with high memory usage by SSL connections. Partial fix available in
version 6.7.3. The
behavior is improved in
this release.
B#248792
"Fixes in Advanced
Secure Gateway
6.7.3.1" on page 114
152 of 164
ID Issue Fixed In

B#227420 Some versions of Management Center cannot connect to an appliance running in FIPS This issue is resolved.
mode.
Add one of the
Note: Advanced Secure Gateway 6.7.x introduces changes to how the appliance following ciphers to the
handles ciphers upon upgrade. Refer to the security fix for B#241332 to learn about this managed device:
behavior change.
n aes256-ctr
n aes192-ctr
n aes128-ctr
B#252450 In STunnel and Bypass modes, the x-cs-session-id and x-cs-server-

certificate-key-size access log fields are not populated.
SG-4320
B#253905 The appliance stops responding when the CRL distribution point host name field
(Proxy > Configuration > Proxy Settings > SSL Proxy) includes special characters.
SG-3605
B#253926 In some cases, the appliance creates a certificate with the OCS IP address in
the SAN DNS Name field when providing the client with a server-side TCP error
SG-4323 message.
B#255423 On a resumed connection, the x-cs-server-certificate-key-size access log field

always displays RSA[1024].
SG-4373
B#257012 In bypass mode, the x-cs-server-certificate-key-size access log field displays "Fixes Included from
RSA[1024]. In bypass mode, this information is not available and the field should not be SGOS 6.7.4.130" on
SG-6902 populated. page 57
B#257835 When adding a keyring through the CLI, whitespaces in field values are not ignored. This
issue does not occur when creating keyrings through the Management Console.
SG-4574
http.request.apparent_data_type and http.request.data.N policy are not "Fixes Included from

B#258130 enforced. SGOS 6.7.4.130" on
page 57
B#258141 Issue: Setting the Client Certificate Validation CCL or Server Certificate Validation CCL
object in the SSL Intercept Layer in the VPM results in the error "Invalid action for <ssl-
SG-4598 intercept> layer", and policy does not compile.
Workaround: These gestures have been moved to the <ssl> layer. Write the policy in
CPL instead, as follows:
<ssl>
server.certificate.validate.ccl(CertList)
153 of 164
ID Issue Fixed In

After upgrading to ASG 6.7.4.2 , when SSL traffic is not intercepted by policy, SSL
SG-6161 attributes (such as negotiated cipher or TLS version) are not available for use in policy
conditions and access log fields.
B#267269
Refer to TECH253316 for more information on this issue.
SSL/TLS and PKI
ID Issue Fixed In

B#250120 You cannot create a new HTTPS Reverse Proxy service in the Management Console "Fixes in Advanced
(Configuration > Services > Proxy Services > New Service). Secure Gateway
6.7.4.107" on page 70
B#221218 A newly-created certificate displays "Not yet valid" for Certificate expiry (Proxy
> Configuration > SSL> Keyrings). This issue occurs when the appliance's clock is
SG-2885 ahead of the clock on the client running the Management Console.
B#220453 If you issue the #(config ssl)create signing-request command and the
certificate signing request fails, issuing the command again causes CLI to stop
SG-2861 responding.
B#225612 When changing the SSL protocol version for an SSL device profile, the appliance
selects compatible ciphers from the list of previously-selected ciphers instead of the list
SG-2971 of all available ciphers.
B#248731 In the access log for the SSL reverse proxy service, client-side negotiated-
cipher fields are populated incorrectly when GCM or SHA384 ciphers are used.
SG-3988
Random HTTPS pages do not load when SSL Proxy is used. Refer to TECH248154 for
B#253377
details:
6.7.2.3 PR
B#256750 In Skype for Business, video calling and screen sharing do not work. Fixes in 6.7.4.1
SG-4462
You receive the following error when uploading a signed configuration file that was just
downloaded:
B#257920
% Attempt to load configuration failed: signature verification failed: The message did
SG-4583 not match the PKCS7 signature.
The error occurs when any signing keyrings are set on the appliance.
B#256750 Skype for Business Video calling and screen sharing do not work. Fixes in 6.7.4.1
SG-4462
154 of 164
SSLV Integration
ID Issue Fixed In

B#242864 When SSL connections are denied using a server-negotiated cipher policy, access
log values for negotiated cipher, negotiated cipher strength, and negotiated cipher
SG-3692 size are not populated.
B#256905 In SSLV offload mode, the x-cs-session-id access log field displays incorrect
session ID values and the x-cs-server-certificate-key-size field always
SG-4482 returns RSA[1024] for key size.
With SSLV offload enabled and policy enforcing cipher based properties, some SSL
B#258272
cipher access log fields present SSLV values instead of ProxySG appliance values.
For example, instead of displaying AES256-SHA a field shows RSA-AES256-CBC-
SG-4612
SHA.
B#256791 In SSLV offload mode, Symantec recommends using the default TCP window size of "Fixes Included from
65535. Increasing the TCP window size might result in stalled connections. SGOS 6.7.4.130" on
page 57
155 of 164
System Statistics
ID Issue Fixed In

B#262919 When the appliance is experiencing a heavy load, running the clear-statistics Fixes in 6.7.4.140
persistent CLI command might cause the appliance to stop passing traffic.
SG-4890
ID Issue Fixed In

B#258974 When booting up the appliance, if the first DNS server in the primary group is Fixes in 6.7.4.140
unreachable, the appliance might stop booting.
SG-4633
B#263272 The appliance might return a false attack in progress status from an SNMP walk.
Fixes in 6.7.4.140
SG-7127
B#257272 Downloads of large files via SOCKS proxy on high-speed networks (2Mbps+ speed) "Fixes Included from
time out. SGOS 6.7.4.130" on
page 57
"Fixes in Advanced
on page 94
B#244784 Packets might exit an incorrect interface in IPv6 configuration when static routes are "Fixes in Advanced
configured. Secure Gateway 6.7.3.1"
on page 114
B#253548 Restart occurs due to high volume of IPv6 network traffic.
SG-4155
B#250616 The appliance might have restarted in Process group: "PG_TCPIP", Process: "stack- 6.7.2.3 PR
bnd-2:0-rxq-0" in "libstack.exe.so". This issue occurred when delayed intercept was
enabled.
The appliance might have restarted in Process group: "PG_TCPIP" in Process: "stack-
B#250637 api-worker-0" in "libmemory.so". This issue occurred when dynamic bypass was 6.7.2.3 PR
enabled.
B#255319 The appliance might experience a restart in process "HTTP SW 40047170A40 for
30F29CC2A40" in "libstack.exe.so".
SG-6805
B#249425 The default gateway cannot be removed unless it is reachable from a configured
interface's IP address.
SG-4032
156 of 164
ID Issue Fixed In

B#255291 Enabling and disabling EDNS support is not reflected in the event log.
SG-4333
After the appliance is set as Master in a failover configuration, it sends gratuitous "Fixes in Advanced
ARPs showing a Sender MAC Address containing only zeroes Secure Gateway
(00:00:00:00:00:00). This occurs when both aggregate interfaces and VLAN are 6.7.4.107" on page 70
configured.
B#255453 "Fixes in Advanced
on page 100
B#252086 The appliance might experience a restart in PG_TCPIP when Virtual IP is configured "Fixes in Advanced
in failover mode. Secure Gateway
6.7.4.107" on page 70
You cannot delete auto-linklocal IPv6 addresses when the interface has link- "Fixes Included from
B#255057 aggregation set. SGOS 6.7.4.130" on
page 57
B#259669 The proxy does not fail over when the DNS server fails in a custom DNS group. "Fixes in Advanced
B#256543 on page 94
URL Filtering
ID Issue Fixed In

Issue: Occasionally the WebPulse service is not able to recover automatically when it
gets into a state where all of the services are reporting that they are sick. This results
B#232047
in the following event log message, "Dynamic categorization error: No service
SG-5404 specified to use."
Workaround: Disable and re-enable the WebPulse service.
B#249253 The WebPulse tab (Configuration > Threat Protection > WebPulse) does not display "Fixes in Advanced
database download status if Intelligence Services is enabled. Secure Gateway 6.7.4.107"
on page 70
Issue: Some SSL websites do not load, even if WebPulse is running in background
mode.
"Fixes Included from
B#255954 SGOS 6.7.4.130" on
Workaround: Perform a drt.rating_servic service health check. In the Management
page 57
Console (Configuration > Health Checks > General), select drt.rating_service and
click Perform health check.
157 of 164
ID Issue Fixed In

B#256515 When the content filtering categorization and Application Classification providers are
both disabled, the Statistics > Category Details page does not load.
SG-4437
A specific URL takes a long time to load when DRTR is running in the background. "Fixes Included from
B#256858 SGOS 6.7.4.130" on
page 57
B#256952 After downloading an updated content filtering database with changed category Fixes in 6.7.4.140
names, previous category names are still visible when you view the categories list.
B#257351 The #show system-resource-metrics CLI output shows empty statistics for
custom local databases that are not defined.
SG-4536
B#257872 During an initial boot of the appliance, a page fault might occur in Process Group "Fixes Included from
"PG_CFS" Process:"Subscription.download_worker" in "liburl_filter.exe.so". SGOS 6.7.4.130" on
Rebooting the appliance usually resolves the issue. page 57
WebPulse is not categorizing websites in a child/parent configuration when a valid "Fixes in Advanced
forwarding host is not supplied. Secure Gateway 6.7.4.107"
on page 70
B#256160
"Fixes in Advanced
Secure Gateway 6.7.3.7" on
page 94
B#259289 When using the Configuration > Content Filtering > General > Test URL function,
URLs with Unicode characters do not match against local database-defined
SG-4670 categories. Matching works with live traffic.
ID Issue Fixed In

B#255321 The appliance sends an invalid_request exception error page if you log out of the "Fixes in Advanced
Management Console and then try to access the consent banner URL again with Secure Gateway 6.7.4.107"
same browser. on page 70
Service Name and Service Group objects are not visible in the Service column in the "Fixes Included from
B#258187 Web Request Layer. SGOS 6.7.4.130" on
page 57
158 of 164
Advanced Secure Gateway Appliance Resources
This page provides information about supported platforms for this release and where to go for additional hardware information and
procedures. Advanced Secure Gateway 6.7.x is not supported on any platform not listed here.
Platforms Resources Comments

ASG-S500 https://support.symantec.com/content/unifiedweb/en_US/article.DOC10385.html PDF version of the Quick Start
ASG-S400 https://support.symantec.com/content/unifiedweb/en_US/article.DOC10136.html Guide included in the package for all
ASG-S200 https://support.symantec.com/content/unifiedweb/en_US/article.DOC10394.html ASG appliances
Additional Resources
Subject Resources Comments

Diagnostics http://www.symantec.com/docs/DOC9795 S-Series Maintenance
and Upgrade Guide
About Security Certification

Advanced Secure Gateway 6.7.2.102 is designed for FIPS 140-2 validation. The following hardware platforms are FIPS-
certified:
n ProxySG: S400-20/30/40 and S500-10/20/30
n Reverse Proxy: S400-20/30/40 and S500-10/20/30
n Advanced Secure Gateway: S400-20/30/40 and S500-10/20
To meet the security requirements of our customers, Symantec maintains Federal Information Processing Standard (FIPS)
140-2 and Common Criteria certifications on Symantec appliances. For more information about the current FIPS and Common
Criteria certifications, refer to the Using FIPS Mode on the ProxySG document:
http://www.symantec.com/docs/DOC10145
Cryptographic Algorithms in FIPS Mode

In FIPS mode, the appliance can use only the cryptographic algorithms and functions listed below for security relevant and
administrative actions (proxy operations are not limited):
n Advanced Encryption Standard (AES) 128-,192- and 256-bit key sizes
n Triple-DES
n Diffie-Hellman: SHA-1, SHA-256
n Rivest Shamir Adleman (RSA):
o RSA sizes for keys created by the appliance: 2048-bit
o RSA sizes for keys imported by the appliance: 1024-, 2048-, 3072-, 4096-, 8192-bit
n Secure Hash Algorithm (SHA-1):
n SHA-1 is used where permitted for protocol and signature verification purposes.
n SHA-224, SHA-256, SHA-384, SHA-512
n Keyed-Hash Message Authorization Code (HMAC):
n HMAC with SHA-1
n HMAC with SHA-2
160 of 164
n Random Number Generation
n NIST SP 800-90A CTR Deterministic Random Bit Generator
n ANSI x9.31 Appendix A.2.4 Pseudo Random Number Generator
Updated FIPS Mode Restrictions

n Windows domain configuration for IWA Direct is enabled in FIPS mode.
n Keyrings containing legacy RSA keys of less than 2048-bits may be imported and used.
n In the event a power up self test (software or hardware) fails, the appliance presents options to reboot and retry the self
test, and to boot into the last successfully booted release.
161 of 164
Documentation and Other Self-Help Options
Symantec provides technical and solution documentation in different formats. This section provides a resource locator as well as
a record of documentation changes.
Product Documentation and Articles
n Search for articles and downloads at MySymantec:
https://support.symantec.com/
n Refer to MySymantec for product documentation:
ProxySG: https://support.symantec.com/content/unifiedweb/en_US/Documentation.html?prodRefKey=1145522
Content Analysis: https://support.symantec.com/content/unifiedweb/en_US/Documentation.html?prodRefKey=1145459
n Access online help from within the Advanced Secure Gateway Management Console; however, note that documentation
posted on MySymantec supersedes online help.
Security Advisory Fixes
n Security Advisories (SAs) are published as security vulnerabilities are discovered and fixed. To see any SAs that apply to
the version of Advanced Secure Gateway you are running, including ones that were published after this release, go to:
Symantec Connect Forums
n Connect with other users at Symantec Connect Forums:
https://www.symantec.com/connect/
Documentation Changes
Advanced Secure Gateway:
n Starting with this release, Symantec is discontinuing the Advanced Secure Gateway Proxy Administration
documentation. For proxy-related information, refer to the equivalent version of SGOS documentation. For content
analysis-related information, refer to the appropriate Content Analysis documentation:
For Advanced Secure Gateway version Refer to Content Analysis documentation version
6.7.2.x 2.1.x
6.7.3.x 2.2.x
6.7.4.x 2.3.x
SSL Visibility
Provide Feedback
n Send any questions or comments about documentation:
documentation_inbox@symantec.com
n For Customer Care requests, send email to:
NP_customercare@symantec.com
163

Advanced Secure Gateway 6.7.x Release Notes: Current Version: 6.7.4.9 Document Revision: 8/13/2019

Uploaded by

Copyright:

Available Formats

Advanced Secure Gateway 6.7.x Release Notes: Current Version: 6.7.4.9 Document Revision: 8/13/2019

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Advanced Secure Gateway 6.7.x Release Notes: Current Version: 6.7.4.9 Document Revision: 8/13/2019

Uploaded by

Copyright:

Available Formats

Advanced Secure Gateway

6.7.x Release Notes

Current Version: 6.7.4.9

Document Revision: 8/13/2019

Release Note Directory

n "Advanced Secure Gateway 6.7.4.8 PR" on page 10

n "Advanced Secure Gateway 6.7.4.7 PR" on page 15

n "Advanced Secure Gateway 6.7.4.6 PR" on page 19

n "Advanced Secure Gateway 6.7.4.5 PR" on page 24

n "Advanced Secure Gateway 6.7.4.4 LA" on page 32

n "Advanced Secure Gateway 6.7.4.3 PR" on page 35

n "Advanced Secure Gateway 6.7.4.2 LA" on page 44

n "Advanced Secure Gateway 6.7.4.141 EA" on page 46

n "Advanced Secure Gateway 6.7.4.111 EA" on page 64

n "Advanced Secure Gateway 6.7.4.107 EA" on page 67

n "Advanced Secure Gateway 6.7.3.12 PR" on page 75

n "Advanced Secure Gateway 6.7.3.11 PR" on page 78

n "Advanced Secure Gateway 6.7.3.10 PR" on page 82

n "Advanced Secure Gateway 6.7.3.9 PR" on page 85

n "Advanced Secure Gateway 6.7.3.8 PR" on page 90

n "Advanced Secure Gateway 6.7.3.7 PR" on page 93

n "Advanced Secure Gateway 6.7.3.6 GA" on page 98

n "Advanced Secure Gateway 6.7.3.5 GA" on page 102

n "Advanced Secure Gateway 6.7.3.2 GA" on page 106

n "Advanced Secure Gateway 6.7.3.1 GA" on page 109

n "Advanced Secure Gateway 6.7.2.1 GA" on page 123

Information About All Releases

n "Advanced Secure Gateway 6.7.x Known Issues" on page 140

n "Advanced Secure Gateway Appliance Resources" on page 159

n (Advanced Secure Gateway 6.7.2) "About Security Certification" on page 160

n "Documentation and Other Self-Help Options" on page 162

Advanced Secure Gateway 6.7.4.9 PR

n Build Number: 240930

n Reporter: 9.5.x; 10.1.x and later

n Management Center: 1.5.x through 1.11.x; 2.x

n ProxyClient: 3.4.x (ADN functionality not supported)

n Unified Agent: 4.7.x and later

n SSL Visibility: 4.1.1.x and later

n Advanced Secure Gateway Appliances:

n S500, S400, S200

n For information on Java 11 support, refer to TECH252566

Upgrading To/Downgrading From This Release

Fixes in Advanced Secure Gateway 6.7.4.9

Fixes in Advanced Secure Gateway 6.7.4.9

Symantec acknowledges Baskar Borman for reporting this vulnerability.

SSL/TLS and PKI

TCP/IP and General Networking

Visual Policy Manager

Advanced Secure Gateway 6.7.4.8 PR

n Build Number: 239880

n Reporter: 9.5.x; 10.1.x and later

n Management Center: 1.5.x through 1.11.x; 2.x

n ProxyClient: 3.4.x (ADN functionality not supported)

n Unified Agent: 4.7.x and later

n SSL Visibility: 4.1.1.x and later

n Advanced Secure Gateway Appliances:

n S500, S400, S200

n For information on Java 11 support, refer to TECH252566