Cisco Cisco Web Security Appliance S690 릴리즈 노트

If the Web Security appliance currently uses IronPort URL Filters, we advise you to migrate to Cisco 
IronPort Web Usage Controls. To migrate, you must first obtain a license key for it before upgrading 
to the current version. If you do not yet have a license for Cisco IronPort Web Usage Controls, contact 
your Cisco sales representative or reseller. After migrating and upgrading, you might need to edit 
existing policies to use the new URL categories as necessary. 

For more information about migrating and obtaining a license, read the following announcement:

http://www.cisco.com/web/ironport/docs/IronPort_URL_Filtering_EoL.pdf

Note There are no changes if the appliance used IronPort URL Filters before upgrading.

The set of URL categories for Cisco IronPort Web Usage Controls changed in AsyncOS 7.5 for Web. If 
you are upgrading from a pre-7.5 version, these changes may modify or disable existing policies. To 
understand, prepare for, control, and respond to these changes, see “Managing Updates to the Set of URL 
Categories” in the “URL Filters” chapter of the Cisco IronPort AsyncOS for Web User Guide.

See the 7.5 release notes for a table listing the changes to the set of URL categories that will occur when 
you upgrade to AsyncOS 7.7 for Web from a pre-7.5 version. For descriptions of the new categories, see 
the “URL Category Descriptions” section in the “URL Filters” chapter of the Cisco IronPort AsyncOS 
for Web User Guide.

Support for SSH 1 has been removed for this release. Therefore, before upgrade, you should do the 
following: 

Any remote host keys which use SSH 1 should be changed to SSH 2. Use the logconfig >  hostkeyconfig 
command in the CLI to make this change. 

For any log subscriptions that are configured to use SSH 1 as the protocol for SCP log push, choose SSH 
2 instead.

Change the access protocol or add a new SSH 2 key for any users configured to use only SSH 1. Use the 
sshconfig command in the CLI to make this change. 

Disable SSH 1 using the sshconfig > setup command in the CLI. 

Familiarize yourself with known issues and limitations before you upgrade AsyncOS for Web using 
these resources: