Cisco Cisco Security Manager 4.3 Notas de publicación

Support for IPv6 Extension Header on ASA 8.4(2) and later.

Support for IPv6 static routes.

Support for ICMP code in IPv4 and IPv6 access rules, service objects, and object groups.

Support for the following additional PAT Pool options:

Flat Port Range—Enables use of the entire 1024 to 65535 port range (or 0-65535 if the 
include-reserve option is configured) when allocating ports.

Extended PAT Table—Enable extended PAT, which uses 65535 ports per service, as opposed to 
per IP address, by including the destination address and port in the translation information.

Support for the Cisco ASA-5500 Series Adaptive Security Appliance (support for ASA version 
8.6.1) 

Support for the Cisco IPS 4300 Series Sensors [IPS Version 7.1(3) onwards]

Support for the Cisco ASA 5500 Series IPS Security Services Processor [IPS Version 7.1(3) 
onwards]

Enhancements to IPS updates

IPv6 support for IPS

Support for IPS 7.1(3)

IPS package bundling for simpler downloading

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. It is available at 

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

You can install Security Manager server software directly, or you can upgrade the software on a 
server where Security Manager is installed. The 

 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.

Before you can successfully upgrade to Security Manager 4.3 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 

 for 

this release contains complete instructions on the steps required for preparing the database for 
upgrade.