Cisco Cisco Web Security Appliance S380

 lists the known issues in this release of AsyncOS for Web. 

69388

Previously, the Policy Trace feature erroneously matched transactions with the Global 
Access policy under the following circumstances:

An Identity included authenticated users in the “Domain Local” group in Active 
Directory, and an Access Policy group used that Identity.

In the Policy Trace tool you entered a user in the “Domain Local” group.

Instead of matching the Access Policy that uses the Identity configured above, users 
matched the Global Access Policy in the Policy Trace. (However, the Web Proxy 
assigned the correct Access Policy to users accessing the Internet.) This no longer 
occurs. 

56418

Previously, when you clicked the Export link on the Monitor > URL Categories page, 
the exported .csv file did not contain any information in the “bandwidth saved by 
blocking” column. This no longer occurs. 

56418

Previously, when you clicked the Export link on the Monitor > URL Categories page, 
the exported .csv file did not contain any information in the “bandwidth saved by 
blocking” column. This no longer occurs. 

44031

Previously, the policy trace feature did not display a web reputation score when 
authentication was enabled. 

82852

Choosing no bandwidth limit for a particular application does not work as 
expected 

When a bandwidth limit is applied to an application type, and then you configure a 
particular application in that type to have no bandwidth limit, the bandwidth limits are 
still applied to that application. 

84487

Web Security appliance performance is affected when the Default Proxy Logs are 
configured at debug or trace logging level.

Workaround: Change the logging level of the Default Proxy Logs to something higher 
than Debug, such as Information.