Feedback
|
Table Of Contents
Release Notes for Cisco Security Manager 4.0
Supported Component Versions and Related Software
Service Pack 1 Download and Installation Instructions
Resolved Caveats—Release 4.0 Service Pack 1
Resolved Caveats—Releases Prior to 4.0
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Security Manager 4.0
Published: June 17, 2010
Revised: October 6, 2010These release notes are for use with the Cisco Security Manager (Security Manager), Release 4.0.
Release 4.0 is now available. Registered SMARTnet users can obtain release 4.0 from the Cisco support website by going to http://www.cisco.com/go/csmanager and clicking Download Software in the Support box.
This chapter contains the following topics:
•
Supported Component Versions and Related Software
•
Service Pack 1 Download and Installation Instructions
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
Note
Use this document in conjunction with the documents identified in Product Documentation. The online versions of the user documentation are also occasionally updated after the initial release. As a result, the information contained in the Cisco Security Manager end-user guides on Cisco.com supersedes any information contained in the context-sensitive help included with the product. For more information about specific changes, please see Where to Go Next.
This document contains release note information for the following:
•
Cisco Security Manager 4.0 (Including Service Pack 1)—Cisco Security Manager (Security Manager) enables you to manage security policies on Cisco security devices. Security Manager supports integrated provisioning of firewall, VPN, and IPS services across IOS routers, PIX and ASA security appliances, IPS sensors and modules, and some services modules for Catalyst 6500 switches and some routers. (You can find complete device support information under Cisco Security Manager Compatibility Information on Cisco.com.) Security Manager also supports provisioning of many platform-specific settings, for example, interfaces, routing, identity, QoS, logging, and so on.
Security Manager efficiently manages a wide range of networks, from small networks consisting of a few devices to large networks with thousands of devices. Scalability is achieved through a rich feature set of device grouping capabilities and objects and policies that can be shared.
•
Auto Update Server 4.0—The Auto Update Server (AUS) is a tool for upgrading PIX security appliance software images, ASA software images, PIX Device Manager (PDM) images, Adaptive Security Device Manager (ASDM) images, and PIX security appliance and ASA configuration files. Security appliances with dynamic IP addresses that use the auto update feature connect to AUS periodically to upgrade device configuration files and to pass device and status information.
•
Performance Monitor 4.0—Performance Monitor is a browser-based tool that monitors and troubleshoots the health and performance of services that contribute to network security. It helps you to isolate, analyze, and troubleshoot events in your network as they occur, so that you can increase service availability. Supported service types are remote-access VPN, site-to-site VPN, firewall, Web server load-balancing, and proxied SSL.
Note
Before using Cisco Security Manager 4.0, we recommend that you read this entire document. In addition, it is critical that you read the Important Notes, the Installation Notes, and the Installation Guide for Cisco Security Manager 4.0 before installing or upgrading to Cisco Security Manager 4.0.
This document lists the ID numbers and headlines for issues that may affect your operation of the product. This document also includes a list of resolved problems. If you accessed this document from Cisco.com, you can click any ID number, which takes you to the appropriate release note enclosure in the Bug Toolkit. The release note enclosure contains symptoms, conditions, and workaround information.
Supported Component Versions and Related Software
The Cisco Security Management Suite of applications includes several component applications plus a group of related applications that you can use in conjunction with them. The following table lists the components and related applications, and the versions of those applications that you can use together for this release of the suite. For a description of these applications, see the Installation Guide for Cisco Security Manager 4.0.
Note
For information on the supported software and hardware that you can manage with Cisco Security Manager, see the Supported Devices and Software Versions for Cisco Security Manager online document under Cisco Security Manager Compatibility Information on Cisco.com.
What's New
Cisco Security Manager 4.0 Service Pack 1
Security Manager 4.0 Service Pack 1 provides support for changes to the mechanism used for downloading sensor and signature updates from Cisco.com.
Security Manager 4.0 Service Pack 1also provides fixes for various problems. For more information, see Resolved Caveats—Release 4.0 Service Pack 1.
Cisco Security Manager 4.0
In addition to resolved caveats, this release includes the following new features and enhancements:
•
New Event Viewer feature enables you to selectively monitor, search, view, and examine events from ASA and IPS devices. You can filter the stream of events to quickly select the view--or even the particular event or value--you require at the moment. Further, the view criteria you select can be saved and recalled as needed.
•
The applications now require CiscoWorks Common Services 3.3, which is included in the Security Manager installation program.
•
The Security Manager installation program no longer performs a mandatory backup. Although you are provided the option of performing a backup during installation, we recommend that you perform the backup before running the installation program, and verify that the backup completed successfully.
•
Support for ASA Software version 8.3. If you upgrade a device to ASA 8.3, ensure that you delete it from the Security Manager inventory and then add it back in so that newly-converted policies are discovered correctly.
•
ASA 8.3 support includes features that can help when converting from Checkpoint to ASA:
–
Global access rules—Instead of creating access rules for each interface, you can create global rules once. These rules are applied to every interface and are processed after any interface-specific access rules.
–
Object group search—Available as a firewall access control setting, object group search optimizes ACL performance without expanding object groups. However, you should use this only on memory constrained devices. You also cannot use the hit count tool if you configure object group search.
•
The release of ASA version 8.3 provides a simplified approach to configuring network address translation (NAT), as compared to earlier ASA versions and other devices. All NAT rules on the device—static NAT, dynamic PAT, and dynamic NAT—are presented in a single table, and the same dialog box is used to configure all NAT rules. The NAT rules are interface independent (that is, interfaces are optional), meaning the rules are independent of security levels also.
•
ASA 8.3+ includes new features for network and service objects that contain single values. You can also use the network objects to configure NAT. Security Manager supports these features as follows:
–
The network/host policy object now has four types: group, host, network, address range. The group object is the same as the network/host object that exists in all Security Manager 3.x releases. The host, network, and address range types allow single values (of the appropriate type), and also allow NAT configuration. Although these objects are designed for use with ASA 8.3+, you can use them with all operating systems; any NAT configuration is ignored for non-ASA-8.3+ devices.
–
The service policy object now has two types: group and object. The group object is the same as the service object in Security Manager 3.x releases. The service "object" allows a single service designation. As with the network/host object, you can use the new service object on any operating system; how it is provisioned to the device simply differs for ASA 8.3 devices.
•
Support for FWSM Software versions 4.1(1), 4.0(7-11), 3.1(16, 17), 3.2(14-17).
•
Support for the 1002 Fixed Router model of the Cisco ASR 1000 Series Aggregation Services Routers.
•
Support for ASR Version 2.4 software, called Cisco IOS Software version 12.2(33)XND.
•
Support for shared port adapters (SPAs) in Cisco ASR 1000 Series Aggregation Services Routers. Support includes all Ethernet (all speeds, including Ten Gigabit Ethernet), Serial, ATM, and Packet over Sonet (POS) SPAs, but not services SPAs. If you configured ATM, PVC, or dialer related policies on ASRs you managed with previous versions of Security Manager, you should rediscover policies on those devices to bring these policies into Security Manager.
•
The IPS Event Viewer application is no longer included in the Security Manager package. When you upgrade to Security Manager 4.0, any installation of the IPS Event Viewer that was installed by previous versions of Security Manager is removed. To view IPS events, use the event viewer integrated into Security Manager 4.0.
•
Activity lock messages now include the username and activity name that has obtained a lock that prevents you from performing an action.
•
You can now delete more than one device at a time.
•
You can now rediscovery policies on more than one device at a time.
•
You can now detect whether devices have out of band changes (changes to the device configuration made outside of Security Manager) before you deploy configurations. This gives you the opportunity to update the device policies in Security Manager to recreate those changes.
Note
Out-of-band change detection is not available for IPS appliances.
•
In previous releases, you could select which types of policy to manage on Cisco IOS routers. You can now also select which policies to manage on ASA, PIX, and FWSM firewall devices.
•
Packet tracer allows you to troubleshoot active policies running on ASA and PIX firewall devices running 7.2.1 and higher that are not operating in transparent mode.
•
ASA 8.3 devices use the original, or real, IP address when evaluating traffic in firewall rules (such as access rules) rather than NAT-translated addresses. Ensure that you use the original address when configuring firewall rules for ASA 8.3 devices.
•
You can now automatically block blacklisted traffic based on the threat level using the Botnet Traffic Filter on ASA 8.2(2)+ devices. You can also treat greylisted traffic as blacklisted traffic for action purposes.
•
You can now inspect IP options in inspection rules on ASA 8.2(2)+ devices. IP options inspection allows you to pass IP packets that have end of options list, no operation, or router alert options configured in the IP packet header.
•
You can now configure or use the following features for Group Encrypted Transport (GET) VPNs: fail-close mode to protect VPN traffic prior to successful group member registration; passive mode configured on group members; RSA key generation and synchronization among the key servers.
•
You can now explicitly configure DMVPN phase 2 connections between spokes, so that spoke to spoke connections go through regional hubs, and routing protocol updates from hubs to spokes are not summarized.
•
Support for Cisco Secure Access Control Server (ACS) 4.2.
•
The Security Manager online help and user guide have been reorganized into parts with smaller chapters, and reference information has been moved along side of conceptual and procedural information. Large sections of the document have been rewritten and simplified, with more examples added.
•
Security Manager now discovers and deploys object groups for devices running Cisco IOS Software release 12.4(20)T and higher. In previous releases, object groups were supported only for ASA, PIX, and FWSM.
Installation Notes
All customers need to procure a new license (or licenses) for Security Manager 4.0 irrespective of whether they have a valid license for any of the (older) Security Manager 3.x releases. With the exception of incremental licenses, existing Security Manager 3.x licenses are not valid for Security Manager 4.0.
Do not modify casuser (the default service account) or directory permissions that are established during the installation of the product. Doing so can lead to problems with your being able to do the following:
•
Logging in to the web server
•
Logging in to the client
•
Performing successful backups of all databases
Internet Explorer 8 is supported, but only in Compatibility View. To use Compatibility View, open Internet Explorer 8, go to Tools > Compatibility View Settings, and add the Security Manager server as a "website to be displayed in Compatibility View."
You can install Security Manager server software directly, or you can upgrade the software on a server where Security Manager is installed. The Installation Guide for Cisco Security Manager for this release of the product explains which previous Security Manager releases are supported for upgrade and provides important information regarding server requirements, server configuration, and post-installation tasks.
We do not support installation of Security Manager on a server that is running any other web server or database server (for example, IIS or MS-SQL). Doing so might cause unexpected problems that may prevent you from logging into or using Cisco Security Manager.
Before you can successfully upgrade to Security Manager 4.0 from a prior version of Security Manager, you must make sure that the Security Manager database does not contain any pending data, in other words, data that has not been committed to the database. If the Security Manager database contains pending data, you must commit or discard all uncommitted changes, then back up your database before you perform the upgrade. The Installation Guide for Cisco Security Manager for this release contains complete instructions on the steps required for preparing the database for upgrade.
For the Installation Guide for Cisco Security Manager 4.0, go to the list of Cisco Security Manager installation and upgrade guides on Cisco.com.
Be aware of the following important points before you upgrade:
•
Ensure that all applications that you are upgrading are currently functioning correctly, and that you can create valid backups (that is, the backup process completes without error). If an application is not functioning correctly before an upgrade, the upgrade process might not result in a correctly functioning application.
Note
It has come to Cisco's attention that some users make undocumented and unsupported modifications to the system so that the backup process does not back up all installed CiscoWorks applications. The upgrade process documented in the installation guide assumes that you have not subverted the intended functioning of the system. If you are creating backups that back up less than all of the data, you are responsible for ensuring you have all backup data that you require before performing an update. We strongly suggest that you undo these unsupported modifications. Otherwise, you should probably not attempt to do an inline upgrade, where you install the product on the same server as the older version; instead, install the updated applications on a new, clean server and restore your database backups.
•
If you upgrade from a release earlier than 3.3 to Security Manager 3.3 or higher, and you use Cisco Configuration Engine, you must upgrade Configuration Engine to 3.0 at the same time. Security Manager 3.3 and higher does not work with older versions of Configuration Engine.
•
If you install RME on the same server as Security Manager, do not apply the MDF.zip file available with the RME IDU patch. Applying this file will damage the device support files in Security Manager, and you will need to contact Cisco Technical Support to correct the problem. If you install RME on a server separate from Cisco Security Manager, this restriction does not apply.
Service Pack 1 Download and Installation Instructions
To download and install service pack 1, follow these steps:
Note
You must install the Cisco Security Manager 4.0 FCS build on your server before you can apply this service pack.
Step 1
Go to http://www.cisco.com/go/csmanager, and then click Download Software in the Support box on the right side of the screen.
Step 2
Enter your user name and password to log in to Cisco.com.
Step 3
Click Security Manager (CSM) Software, expand the 4.0 folder under All Releases, and then click 4.0sp1.
Step 4
Download the file fcs-csm-40-sp1-win-k9.exe.
Step 5
To install the service pack, close all open applications, including the Cisco Security Manager Client.
Step 6
Manually stop the Cisco Security Agent service from Start > Settings > Control Panel > Administrative Tools > Services.
Step 7
Run the fcs-csm-40-sp1-win-k9.exe file that you previously downloaded.
Step 8
In the Install Cisco Security Manager 4.0 Service Pack 1dialog box, click Next and then click Install in the next screen.
Step 9
After the updated files have been installed, click Finish to complete the installation.
Step 10
On each client machine that is used to connect to the Security Manager server, you must perform the following steps to apply the service pack before you can connect to the server using that client:
a.
Manually stop the Cisco Security Agent service from Start > Settings > Control Panel > Administrative Tools > Services.
b.
Launch the Security Manager client.
You will be prompted to "Download Service Pack".
c.
Download the service pack and then launch the downloaded file to apply the service pack.
Step 11
(Optional) Go to the client installation directory and clear the cache, for example, <Client Install Directory>/cache.
Important Notes
The following notes apply to the Security Manager 4.0 release:
•
You can use IPv4 addresses only in Security Manager. Although some of the device software Security Manager supports allows you to use IPv6 addresses on commands, Security Manager does not support IPv6 addresses directly. If you want to configure IPv6 features using Security Manager, you can use FlexConfig policies.
•
You cannot use Security Manager to manage an ASA 8.3+ device if you enable password encryption using the password encryption aes command. You must turn off password encryption before you can add the device to the Security Manager inventory.
•
ASA 8.3 ACLs use the real IP address of a device, rather than the translated (NAT) address. During upgrade, rules are converted to use the real IP address. All other device types, and older ASA versions, used the NAT address in ACLs.
•
The device memory requirements for ASA 8.3 are higher than for older ASA releases. Ensure that the device meets the minimum memory requirement, as explained in the ASA documentation, before upgrade. Security Manager blocks deployment to devices that do not meet the minimum requirement.
•
If you have a device that uses commands that were unsupported in previous versions of Security Manager, these commands are not automatically populated into Security Manager as part of the upgrade to this version of Security Manager. If you deploy back to the device, these commands are removed from the device because they are not part of the target policies configured in Security Manager. We recommend that you set the correct values for the newly added attributes in Security Manager so that the next deployment will correctly provision these commands. You can also rediscover the platform settings from the device; however, you will need to take necessary steps to save and restore any shared Security Manager policies that are assigned to the device.
•
A Cisco Services for IPS service license is required for the installation of signature updates on IPS 5.x+ appliances, Catalyst and ASA service modules, and router network modules.
•
Do not connect to the database directly, because doing so can cause performance reductions and unexpected system behavior.
•
Do not run SQL queries against the database.
•
If an online help page displays blank in your browser view, refresh the browser.
•
Cisco Secure ACS 5.0 is not supported by Security Manager 4.0, even though ACS 5.0 is supported by Common Services 3.3.
•
If you do not manage IPS devices, consider taking the following performance tuning step. In $NMSROOT\MDC\ips\etc\sensorupdate.properties, change the value of packageMonitorInterval from its initial default value of 30,000 milliseconds to a less-frequent value of 600,000 milliseconds. Taking this step will improve performance somewhat. [$NMSROOT is the full pathname of the Common Services installation directory (the default is C:\Program Files\CSCOpx).]
Caveats
This section describes the open and resolved caveats with respect to this release.
For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation may be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
Commands are in boldface type.
•
Product names and acronyms may be standardized.
•
Spelling errors and typos may be corrected.
Note
If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
http://www.cisco.com/support/bugtools
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.doThis section contains the following topics:
•
Resolved Caveats—Release 4.0 Service Pack 1
•
Resolved Caveats—Releases Prior to 4.0
Open Caveats—Release 4.0
This section contains information about the problems known to exist in Cisco Security Manager 4.0. The caveats are arranged into the following tables:
•
ASA, PIX, and FWSM Firewall Devices Caveats
•
CSM Client and Server Install Caveats
•
Cisco Catalyst 6000 Device Support Caveats
•
Cisco IOS Router Devices Caveats
•
Cisco IPS and IOS IPS Devices Caveats
•
Device Management, Discovery, and Deployment Caveats
•
VPN Device and Configuration Support Caveats
Note
In some instances, a known problem might apply to more than one area, for example, a PIX device might encounter a problem during deployment. If you are unable to locate a particular problem within a table, expand your search to include other tables. In the example provided, the known problem could be listed in either the Deployment table or the PIX/ASA/FWSM Configuration table.
Resolved Caveats—Release 4.0 Service Pack 1
The following customer found or previously release noted caveats have been resolved in Cisco Security Maanger 4.0 Service Pack 1.
Resolved Caveats—Release 4.0
The following customer found or previously release noted caveats have been resolved in this release.
Resolved Caveats—Releases Prior to 4.0
For the list of caveats resolved in releases prior to this one, see the following documents:
•
http://www.cisco.com/en/US/products/ps6498/prod_release_notes_list.html
Where to Go Next
If you want to: Do this:Install Security Manager server or client software.
Understand the basics.
See the interactive JumpStart guide that opens automatically when you start Security Manager.
Get up and running with the product quickly.
See "Getting Started with Security Manager" in the online help, or see Chapter 1 of User Guide for Cisco Security Manager 4.0.
Complete the product configuration.
See "Completing the Initial Security Manager Configuration" in the online help, or see Chapter 1 of User Guide for Cisco Security Manager 4.0.
Manage user authentication and authorization.
See the following topics in the online help, or see Chapter 2 of User Guide for Cisco Security Manager 4.0.
•
Setting Up User Permissions
•
Integrating Security Manager with Cisco Secure ACS
Bootstrap your devices.
See "Preparing Devices for Management" in the online help, or see Chapter 5 of User Guide for Cisco Security Manager 4.0.
Install entitlement applications.
Your Security Manager license grants you the right to install certain other applications—including specific releases of RME and Performance Monitor—that are not installed when you install Security Manager. You can install these applications at any time. See the Introduction to Component Applications section in Chapter 1 of Installation Guide for Cisco Security Manager 4.0.
Product Documentation
For the complete list of documents supporting this release, see the release-specific document roadmap:
•
Guide to User Documentation for Cisco Security Manager
http://www.cisco.com/en/US/products/ps6498/products_documentation_roadmaps_list.html
Lists document set that supports the Security Manager release and summarizes contents of each document.
•
For general product information, see:
http://www.cisco.com/go/csmanager
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Product Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
Feedback