Note Use this document in conjunction with the documents identified in Communications, Services, and Additional Information. 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.
This document contains release note information for the following:
Cisco Security Manager 4.17 —Cisco Security Manager enables you to manage security policies on Cisco security devices. Security Manager supports integrated provisioning of firewall, VPN, ASA security appliances, and several other services modules. (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.
Note From version 4.17, though Cisco Security Manager continues to manage the following devices, it will not provide support for any enhancements:
Cisco Catalyst 6500 and 7600 Series Firewall Services Modules (EOL8184)
Cisco Catalyst 6500 Series Intrusion Detection System Services Module 2 (EOL8843)
Cisco Intrusion Prevention System: IPS 4200, 4300, and 4500 Series Sensors (EOL9916)
Auto Update Server 4.17 —The Auto Update Server (AUS) is a tool for upgrading ASA software images, Adaptive Security Device Manager (ASDM) images, 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.
Note Before using Cisco Security Manager 4.17, 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.17 before installing Cisco Security Manager 4.17.
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.17.
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.
Table 1 Supported Versions for Components and Related Applications
Cisco Security Manager
Auto Update Server
CiscoWorks Common Services
Cisco Security Monitoring, Analysis and Response System (CS-MARS)
Cisco Secure Access Control Server (ACS) for Windows
Cisco Secure ACS Solution Engine 4.1(4) is also supported.
Cisco Secure ACS 5.x is supported for authentication.
You can use other versions of Cisco Secure ACS if you configure them as non-ACS TACACS+ servers. A non-ACS configuration does not provide the granular control possible when you configure the server in ACS mode.
Cisco Configuration Engine
Cisco Security Manager 4.17
In addition to resolved caveats, this release includes the following new features and enhancements:
Support for ASA 9.9 (2) version
BVI interface for HTTP, SSH, or Telnet — Beginning with Cisco Security Manager version 4.17, you can configure BVI interface for HTTP, SSH, or Telnet on ASA 9.9.2 devices and above. However, in multi-context, “Transparent” mode security context only supports BVI interface.
IPv6 Address Support for SNMP Policy — Beginning with Cisco Security Manager version 4.17, IPv6 Address for SNMP policy is supported on ASA 9.9.2 devices and above.
Easy VPN support with BVI — Beginning with version 4.17, Cisco Security Manager provides Easy VPN support with BVI. Typically, Easy VPN determines the highest and lowest security level interfaces during ASA startup.
On ASA5506 platform, the default configuration includes BVI with highest security level interface 100 with security level of its member interfaces also set at level 100, along with an external interface with security level 0 (zero). VPN client rejects two or more interfaces having same highest security level. Easy VPN determines that there are more than two interfaces with same highest security level and hence vpn client is not enabled.
In order to overcome this issue, vpnclient secure interface CLI was introduced for all ASA 5506, 5508, and 5512 [x/h/w] devices from ASA 9.9(2) onwards. Thus, to support the CLI in Cisco Security Manager, starting from version 4.17, a new component “VPN Client Interface” is introduced in Hub and Spoke Topology of type (Easy VPN).
Support for Events from non-management interfaces — Beginning with version 4.17, Cisco Security Manager receives and displays events from non-management interfaces also, with following limitations:
– Only Static IP address Interface is supported.
– The events from cluster devices will not be displayed because cluster pool IP ranges for syslog would be used.
– Only after deployment of syslog server configuration, the device event manager is notified to get the non-managed interface IP. Hence, there can be initial event drop.
– This enhancement is not supported in syslog relay services.
Handling SNMP traps over IPv6 —When a device sends trap message, Cisco Security Manager captures the trap and posts it to the Site to Site Tunnels page in Health and Performance Monitoring application. Till Cisco Security Manager version 4.16, devices used to send the trap messages over IPv4 only. Beginning with Cisco Security Manager 4.17, the SNMP traps are captured using IPv6. Thus, Cisco Security Manager receives the trap messages; maps the IPv6 address of the device to the device details; displays an alert about the trap in Site to Site Tunnels page of the Health and Performance Monitoring application. The status is displayed in the Health and Performance Monitoring application after couple of refresh cycles.
Support for ASA pre-defined Objects — From Cisco Security Manager version 4.17, the ASA predefined objects will be discovered, provided, the device is updated with the object whenever a new predefined service object is added in the ASA. This feature is supported for ASA supporting images across all versions with following exceptions:
– The PPTP predefined object is not supported.
– No activity validation with respect to ASA versions.
– The ICMP and ICMPv6 predefined objects of Cisco Security Manager are converted to device predefined objects. Hence, any usage of Cisco Security Manager’s predefined objects causes negation and re-creation of that policy.
IPv6 support for RADIUS Protocol — Beginning with Cisco Security Manager 4.17, IPv6 hosts for the Radius protocol are supported on ASA 9.9(2) devices onwards. Users can now configure IPv6 Host Address for Radius authentication. Activity Validation is also introduced for unsupported device version.
Policies Supported — Beginning with Cisco Security Manager version 4.17, you can configure and deploy the following policies on ASA multi-context devices running the software version 9.9(2) or later:
– IPSec Proposal policy*
– IKE Proposal policy
– Trusted Pool policy
*IPSec policy was not supported for ASA 9.5(2) Remote Access VPN in Multi-context mode. Beginning with Cisco Security Manager version 4.17, IPSec is supported from ASA 9.9(2) or later multi-context devices.
However, the following attributes under Connection Profile > IPSec tab is not supported for ASA 9.9(2) or later multi-context devices:
– Enable IKEv2 Mobike RRC
– Client Software Update Table
Remote Access Support — Beginning with Cisco Security Manager version 4.17, you can configure remote access authentication on ASA 9.9(2) or later multi-context devices.
Beginning with Cisco Security Manager version 4.17, you can configure VLAN on ASA 9.9(2) or later multi-context devices.
Other Changes in Cisco Security Manager 4.17
No support for IPS, FWSM, PIX, IOS routers, and Catalyst Switches features in Cisco Security Manager — Beginning with version 4.17, though Cisco Security Manager supports IPS, PIX, FWSM, IOS routers, and Catalyst Switches features/functionality. IPS, PIX, FWSM, and Catalyst switches and devices, it does not support any bug fixes or enhancements.
Please refer to the Installation Guide for Cisco Security Manager 4.17 for specific installation instructions and for important information about client and server requirements. Before installing Cisco Security Manager 4.17, it is critical that you read the notes listed in this section and the Important Notes.
The “Licensing” chapter in the installation guide enables you to determine which license you need. (The license you need depends upon whether you are performing a new installation or upgrading from one of several previous versions.) It also describes the various licenses available, such as standard, professional, and evaluation.
The STD-TO-PRO upgrade converts an ST25 license to a PRO50 license and will result in support for 50 devices. If additional devices need to be supported, you need to buy the necessary incremental licenses.
Beginning with Version 4.7 of Security Manager, a temporary license for the API is available from Cisco.
Beginning with Version 4.7 of Security Manager, you can apply incremental licenses to the evaluation version of the Security Manager license.
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
Supported operating systems for the server machine are the following:
– Microsoft Windows Server 2016 Standard— 64-bit
– Microsoft Windows Server 2016 Datacenter—64-bit
– Microsoft Windows Server 2012 R2 Standard—64-bit
– Microsoft Windows Server 2012 Standard—64-bit
– Microsoft Windows Server 2012 R2 Datacenter—64-bit
– Microsoft Windows Server 2012 Datacenter—64-bit
Supported operating systems for the client machine are the following:
– Microsoft Windows 7
– Microsoft Windows 8.1 Enterprise Edition—64-bit and 32-bit
– Microsoft Windows 10 —64-bit and 32-bit
– Microsoft Windows Server 2016 Standard— 64-bit
– Microsoft Windows Server 2016 Datacenter— 64-bit
– Microsoft Windows Server 2012 R2 Standard—64-bit
– Microsoft Windows Server 2012 Standard—64-bit
– Microsoft Windows Server 2012 R2 Datacenter—64-bit
– Microsoft Windows Server 2012 Datacenter—64-bit
Supported browsers are the following for both the server machine and the client machine:
– Internet Explorer 8.x, 9.x, 10.x, or 11.x, but only in Compatibility View
– Firefox 15.0.1 and above supported and recommended
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 4.17 explains which previous Security Manager releases are supported for upgrade and provides important information regarding server requirements, server configuration, and post-installation tasks.
Before you can successfully upgrade to Security Manager 4.17 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 4.17 contains complete instructions on the steps required for preparing the database for upgrade.
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.
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.
– Inline upgrades are not supported for Cisco Security Manager 4.12 SP2. If you are upgrading from 4.12SP2 to 4.13 or 4.14, follow the remote upgrade procedure and refer to the steps given in “Resolving database errors while upgrading from Cisco Security Manager 4.12 SP2” section of the Installation Guide for Cisco Security Manager 4.17 to resolve the database migration issues.
Note This exception is not applicable if you are upgrading from Cisco Security Manager 4.12.
If you log in to a Security Manager server that is running a higher version than your client, a notification will be displayed and you will have the option of downloading the matching client version.
Beginning with Security Manager 4.4, AUS and the Security Manager client are installed in parallel to improve installation time.
CiscoWorks Common Services 4.2.2 is installed automatically when you install Security Manager or AUS.
An error message will pop up if there is any database migration error; this will be at a point where installation can be taken forward without stopping.
It is recommended to do disk defragmentation for every 50 GB increase in the disk size for optimal performance.
Caution Frequent defragmentation will also contribute to bad sectors, eventually leading to disk failure.
Beginning with Version 4.4, Security Manager includes a Windows Firewall configuration script in the server installer. This script automates the process of opening and closing the ports necessary for Windows Firewall to work correctly and securely; its purpose is to harden your Security Manager server.
Service Pack 1 Download and Installation Instructions
To download and install Security Manager 4.17 service pack 1, follow these steps:
Note You must install the Cisco Security Manager 4.17 FCS build on your server before you can apply this service pack.
Before installing this service pack, please back up the following files:
Step 2 Enter your user name and password to log in to Cisco.com.
Step 3 Click Security Manager 4.17 in the rightmost column.
Step 4 Click Security Manager (CSM) Software and then click 4.17sp1 under Latest.
Step 5 Download the file CSM4.17.0Service_Pack1.exe.
Step 6 To install the service pack, close all open applications, including the Cisco Security Manager Client.
Step 7 If Cisco Security Agent is installed on your server, manually stop the Cisco Security Agent service from Start > Settings > Control Panel > Administrative Tools > Services.
Step 8 Run the CSM4.17.0Service_Pack1.exe file that you previously downloaded.
Step 9 In the Install Cisco Security Manager 4.17 Service Pack 1 dialog box, click Next and then click Install in the next screen.
Step 10 After the updated files have been installed, click Finish to complete the installation.
Step 11 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. If Cisco Security Agent is installed on the client, 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 12 (Optional) Go to the client installation directory and clear the cache, for example, <Client Install Directory>/cache.
Step 13 (Optional) Configure SSL Certificates or self-signed certificates for Open SSL:
a. Stop the CSM Daemon service [net stop crmdmgtd]
b. If you have your own SSL certificates configured, you can reconfigure the certificates as per the steps outlined in the link below:
c. For self-signed certificates, from the command prompt navigate to the <CSCOpx>\MDC\Apache directory, and then execute the gencert.bat file. (where <CSCOpx> is your installation directory)
d. Start the CSM Daemon service [net start crmdmgtd]
The following notes apply to the Security Manager 4.17 release:
The following patches are required to run the critical Cisco Security Manager services on the Microsoft Windows Server 2012 R2. Failing to install the patches will bring down the services. Ensure that you have these patches installed on your server, else install the patches in the following order:
b. Run the clearcompressionflag.exe
Note The clearcompressionflag.exe file is part of the cumulative set of security updates. This tool prepares the computer for the Windows Updates in the background. The executable file can be downloaded from the Microsoft site: https://support.microsoft.com/en-in/kb/2919355.
c. KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018
You can also install these patches after installing the Cisco Security Manager to bring up the critical services. To register the services with the windows services, you must run the “RegisterApache.bat” script which is located in “<CSMInstalledDirectory>\CSCOpx\bin”, and then restart the server.
For remote access VPN in multi-context ASA devices running the software version 9.6(2) or later, the device modifies the storage-url configured with flash:/ directory into disk0:/. Since the device modifies the configuration, Security Manager negates the device configuration and pushes the configuration into the device again. This is a limitation of Security Manager version 4.12.
In Policy Object Manager > Access Control List > Unified ACL, if you right-click the ACL which is used in any of the device configuration and select “Find Usage”, the Find Usage option does not show the list of devices that are configured with the Unified Access List.
Cisco Security Manager was using OpenSSL for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. Beginning with version 4.13, Cisco Security Manager replaced OpenSSL version 1.0.2 with Cisco SSL version 6.x. Cisco SSL enables FIPS compliance over full FIPS Validation which results in fast and cost-effective connectivity. The Common Criteria mode in Cisco SSL allows easier compliance. Cisco SSL is feature-forward when compared to OpenSSL. The product Security Baseline (PSB) requirements for CiscoSSL ensures important security aspects such as credential and key management, cryptography standards, anti-spoofing capabilities, integrity and tamper protection, and session, data, and stream management and administration are taken care of. In version 4.17, the SSL 1.0.2N is being used.
Security Manager sends only the delta configuration to the Configuration Engine, where the particular device retrieves it. The full configuration is not pushed to the device. Therefore, the following behaviors are encountered for OSPF, VLAN, and failover for devices.
– OSPF for IOS routers—Security Manager supports OSPF policy for routers running the IOS Software version 12.2 and later. However, Security Manager does not support OSPF policy for Catalyst devices. Therefore when you configure the OSPF policy in a Catalyst device and perform the discovery in Security Manager, the latter removes the ‘no passive-interface <interface number>’ command from the full configuration. Therefore you will see a difference in the Security Manager-generated configuration and the configuration on the device.
– VLAN—Security Manager supports discovery of VLAN command in IOS devices but does not support dynamic behavior of the VLAN command. If there are user driven changes in VLAN policy, Security Manager generates the command in delta and full configuration. In other words, in normal preview or deployment, Security Manager does not generate VLAN command in full configuration. Therefore you will see a difference in the Security Manager-generated configuration and the configuration on the device.
The dynamic behavior of the failover devices such as ASA and IOS, is not supported in Cisco Security Manager. This is because, CSM does not identify the failover LAN unit as primary or secondary. However, after an HA switchover on ASA, the CSM continues to manage the secondary unit with active IP.
The following ASA policies are supported in Security Manager version 4.8 and higher:
Therefore these policies are managed by default in a fresh 4.8 version, or higher, installation. However, if you are upgrading Security Manager from version 4.7 to 4.8, or from version 4.7 to 4.9, by default the said policies will be unmanaged for both inline and remotely upgraded servers.
If you are upgrading from Security Manager 4.7 to 4.9, in addition to the SSL and EIGRP ASA policies, the following ASA policies will also be unmanaged:
– CLI Prompt
– Virtual Access
– AAA Exec Authorization
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.
Note If a route-map is configured on the ASA and the same route-map is used in OSPF policy, after upgrading to Security Manager 4.9 from Security Manager 4.7, the OSPF page will show a red-banner. To overcome this issue, you must rediscover the ASA.
You can also create the Unified ACL object on-the-fly in certain Remote Access VPN policies, such as the Dynamic Access Policy. However, when you create the Unified ACL object on-the-fly, Cisco Security Manager displays an error message. You must add again the created ACL in the Selector window and save the policy.
If PKI specification is chosen for IKEv2 authentication in Site to Site VPN, created using S2S manager and if a trustpoint is chosen for PKI specification. Then the corresponding Trustpoint should be selected in: Remote Access VPN > Public Key Infrastructure also.
If you upgrade an ASA managed by Security Manager to release 8.3(x) or higher from 8.2(x) or lower, you must rediscover the NAT policies using the NAT Rediscovery option (right-click on the device, select Discover Policies on Device(s), and then select NAT Policies as the only policy type to discover). This option will update the Security Manager configuration so that it matches the device configuration while preserving any existing shared policies, inheritance, flex-configs, and so on.
You can also use the rule converter for the other firewall rules like access rules, AAA rules, and inspection rules if you want to manage these policies in unified firewall rules format.
If you upgrade a device that you are already managing in Security Manager from 8.x to 9.0(1) or higher, you must rediscover the device inventory so that Security Manager starts interpreting the device as a 9.x device and then you must rediscover the policies on the device to ensure that Security Manager looks for and discovers the appropriate policy types. Alternatively, you can delete the device from Security Manager and then add the device again.
If you perform one of the following upgrades to a device that you are already managing in Security Manager:
—from 7.x to 8.x
—from any lower version to 8.3(1) or higher
—from 8.3(x) to 8.4(2) or higher
you must rediscover the device in Security Manager. This is required due to significant policy changes between the two releases.
For detailed information on these scenarios, refer to the section titled “Validating a Proposed Image Update on a Device” in the User Guide for Cisco Security Manager 4.17 at the following URL:
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.
For ASA devices in cluster mode, Security Manager treats the entire cluster as a single node and manages the cluster using the main cluster IP address. The main cluster IP address is a fixed address for the cluster that always belongs to the current control unit. If the control node changes, the SNMP engine ID for the cluster also changes. In such a case, Security Manager will regenerate the CLI for all SNMP Server Users that are configured with a Clear Text password. Security Manager will not regenerate the CLI for users that are configured using an Encrypted password.
You can use the Get SNMP Engine ID button on the SNMP page to retrieve the engine ID from the device currently functioning as the cluster control unit.
You cannot use Security Manager to manage an IOS or 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.
Device and Credential Repository (DCR) functionality within Common Services is not supported in Security Manager 4.8 and later versions.
LACP configuration is not supported for the IPS 4500 device series.
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.
Beginning with version 4.9, Security Manager only supports Cisco Secure ACS 5.x for authentication. ACS 4.1(3), 4.1(4), or 4.2(0) is required for authentication and authorization.
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 (x86)\CSCOpx).]
The IPS packages included with Security Manager do not include the package files that are required for updating IPS devices. You must download IPS packages from Cisco.com or your local update server before you can apply any updates. The downloaded versions include all required package files and replace the partial files that are included in the Security Manager initial installation.
From Cisco Security Manager 4.4, the “License Management” link on the CiscoWorks Common Services home page has been removed.
CsmReportServer and CsmHPMServer are now supported with 64-bit JRE.
The “rsh” service has been changed to manual start mode. You can start it manually if you need it.
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products.
Note You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.
Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1721R)
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.