Table Of Contents
Release Notes for Cisco Intrusion Prevention System 7.0(1)E3
Contents
IPS 7.0(1)E3 File List
Supported Platforms
Supported Servers
ROMMON and TFTP
IPS Management and Event Viewers
New and Changed Information
The Sensor and Jumbo Packet Frame Size
The IDM and JRE 1.7
MySDN Decommissioned
Cisco Security Intelligence Operations
Before Upgrading to Cisco IPS 7.0(1)E3
Perform These Tasks
Backing Up and Restoring the Configuration File Using a Remote Server
Obtaining Software on Cisco.com
IPS Software Versioning
Software Release Examples
Upgrading to Cisco IPS 7.0(1)E3
Upgrade Notes and Caveats
Upgrading to IPS 7.0(1)E3
After Upgrading to Cisco IPS 7.0(1)E3
Comparing Configurations
Importing a New SSL Certificate
Logging In to the IDM
Licensing the Sensor
Understanding the License
Service Programs for IPS Products
Obtaining and Installing the License Key
Installing or Upgrading Cisco IME and Migrating Data In to the IME
Restrictions and Limitations
Recovering the Password
Understanding Password Recovery
Recovering the Appliance Password
Using the GRUB Menu
Using ROMMON
Recovering the IDSM2 Password
Recovering the AIP SSM Password
Recovering the AIM IPS Password
Recovering the NME IPS Password
Disabling Password Recovery
Verifying the State of Password Recovery
Troubleshooting Password Recovery
Caveats
Resolved Caveats
Known Caveats
Related Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Intrusion Prevention System 7.0(1)E3
Published: April 22, 2009, OL-18483-01
Revised: October 28, 2013
Contents
•
IPS 7.0(1)E3 File List
•Supported Platforms
•Supported Servers
•ROMMON and TFTP
•IPS Management and Event Viewers
•New and Changed Information
•The Sensor and Jumbo Packet Frame Size
•The IDM and JRE 1.7
•MySDN Decommissioned
•Cisco Security Intelligence Operations
•Before Upgrading to Cisco IPS 7.0(1)E3
•Upgrading to Cisco IPS 7.0(1)E3
•After Upgrading to Cisco IPS 7.0(1)E3
•Installing or Upgrading Cisco IME and Migrating Data In to the IME
•Restrictions and Limitations
•Recovering the Password
•Caveats
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Caution
The BIOS on Cisco IPS sensors is specific to Cisco IPS sensors and must only be upgraded under instructions from Cisco with BIOS files obtained from the Cisco website. Installing a non-Cisco or third-party BIOS on Cisco IPS sensors voids the warranty.
IPS 7.0(1)E3 File List
The following files are part of Cisco IPS 7.0(1)E3:
•Readme
–IPS-7.0-1-E3.readme.txt
•Major Version Upgrade File
–IPS-K9-7.0-1-E3.pkg
–IPS-AIM-K9-7.0-1-E3.pkg
–IPS-NME-K9-7.0-1-E3.pkg
•System Image Files
–IPS-4240-K9-sys-1.1-a-7.0-1-E3.img
–IPS-4255-K9-sys-1.1-a-7.0-1-E3.img
–IPS-4260-K9-sys-1.1-a-7.0-1-E3.img
–IPS-4270_20-K9-sys-1.1-a-7.0-1-E3.img
–IPS-IDSM2-K9-sys-1.1-a-7.0-1-E3.bin.gz
–IPS-SSM_10-K9-sys-1.1-a-7.0-1-E3.img
–IPS-SSM_20-K9-sys-1.1-a-7.0-1-E3.img
–IPS-SSM_40-K9-sys-1.1-a-7.0-1-E3.img
–IPS-AIM-K9-sys-1.1-a-7.0-1-E3.img
–IPS-NME-K9-sys-1.1-a-7.0-1-E3.img
•Recovery Image Files
–IPS-K9-r-1.1-a-7.0-1-E3.pkg
–IPS-AIM-K9-r-1.1-a-7.0-1-E3.pkg
–IPS-NME-K9-r-1.1-a-7.0-1-E3.pkg
For More Information
For the procedure for obtaining these files on Cisco.com, see Obtaining Software on Cisco.com.
Supported Platforms
Note All IPS platforms allow ten concurrent CLI sessions.
Note The AIM IPS and the NME IPS do not support the IPv6 features, because the router in which they are installed does not send them IPv6 data. IPv6 inspection may work on the IDSM2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface.
Cisco IPS 7.0(1) is supported on the following platforms:
•IPS 4240 Series Sensor Appliances
•IPS 4255 Series Sensor Appliances
•IPS 4260 Series Sensor Appliances
•IPS 4270-20 Series Sensor Appliances
•WS-SVC-IDSM2 Series Intrusion Detection System Modules (IDSM2)
•ASA-SSM-AIP-10 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-10)
•ASA-SSM-AIP-20 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-20)
•ASA-SSM-AIP-40 Series Cisco ASA Advanced Inspection and Prevention Security Service Modules (AIP SSM-40)
•Intrusion Prevention System Advanced Integration Modules (AIM IPS)
•Intrusion Prevention System Network Modules (NME IPS)
Supported Servers
The following FTP servers are supported for IPS software updates:
•WU-FTPD 2.6.2 (Linux)
•Solaris 2.8
•Sambar 6.0 (Windows 2000)
•Serv-U 5.0 (Windows 2000)
•MS IIS 5.0 (Windows 2000)
The following HTTP/HTTPS servers are supported for IPS software updates:
•CMS - Apache Server (Tomcat)
•CMS - Apache Server (JRun)
ROMMON and TFTP
ROMMON uses TFTP to download an image and launch it. TFTP does not address network issues such as latency or error recovery. It does implement a limited packet integrity check so that packets arriving in sequence with the correct integrity value have an extremely low probability of error. But TFTP does not offer pipelining so the total transfer time is equal to the number of packets to be transferred times the network average RTT. Because of this limitation, we recommend that the TFTP server be located on the same LAN segment as the sensor. Any network with an RTT less than a 100 milliseconds should provide reliable delivery of the image. Be aware that some TFTP servers limit the maximum file size that can be transferred to ~32 MB.
For More Information
•For the procedure for downloading IPS software updates from Cisco.com, see Obtaining Software on Cisco.com.
•For the procedure for configuring automatic updates, for the CLI refer to Configuring Automatic Updates, for the IDM refer to Configuring Automatic Update, and for the IME refer to Configuring Automatic Update.
IPS Management and Event Viewers
Note IDM 7.0.1 is included within IME 7.0.1. You can use IME 7.0.1 to configure IPS 6.1, 6.2, and 7.0 sensors.
Note IME 7.0.1 now supports 10 devices.
Use the following tools for configuring Cisco IPS 7.0(1) sensors:
•Cisco IDM 7.0.1
•Cisco IME 7.0.1
•IPS CLI 7.0
•ASDM 5.2 and later
•CSM 3.2
Use the following tools for monitoring Cisco IPS 7.0(1) sensors:
•Cisco IME 7.0.1
•CSM 4.0 and later
Note You may need to configure viewers that are already configured to monitor the Cisco IPS 6.2 sensors to accept a new SSL certificate for the Cisco IPS 7.0(1) sensors.
New and Changed Information
Cisco IPS 7.0 contains the following new features:
•Global correlation
IPS 7.0 contains a new security capability, Cisco Global Correlation, which uses the immense security intelligence that we have amassed over the years. At regular intervals, Cisco IPS receives threat updates from the Cisco SensorBase Network, which contain detailed information about known threats on the Internet, including serial attackers, Botnet harvesters, Malware outbreaks, and dark nets. The IPS uses this information to filter out the worst attackers before they have a chance to attack critical assets. It then incorporates the global threat data in to its system to detect and prevent malicious activity even earlier.
•IME 7.0(1) introduces support for the global correlation features:
–Support for configuring the global correlation features on sensors running IPS 7.0(1).
–Support for viewing and monitoring alerts from IPS 7.0(1) sensors containing global correlation data.
–Support for generating global correlation reports.
•10GE interface card
The 10GE interface card (part numbers IPS-2X10GE-SR-INT and IPS-2X10GE-SR-INT=) provides two 10000 Base-SX (fiber) interfaces. The IPS 4260 supports one 10GE interface card for a total of two 10GE fiber interfaces. The IPS 4270-20 supports up to two 10GE interface cards for a total of four 10GE fiber interfaces.
Note Support for the 10GE interface card has been added to IPS 6.1(2), 6.2(1), and 7.0(1).
•We deprecated the RDEP event server service in IPS 6.1 and we removed it in IPS 7.0(1). We added the SDEE event server service to IPS 5.0 as a replacement for the RDEP event server service. We supported both the SDEE event server and RDEP event server through IPS 5.0, 5.1, 6.0, and 6.1 to allow time for monitoring tools to transition to using the SDEE event server for retrieval of events. With IPS 7.0(1), monitoring tools must use the SDEE event server service for the retrieval of events.
•7.0(1)E3 includes the S388 signature update and the E3 signature engine, which includes the following:
–Signature date and type
The signature date represents the date at which the signature was first created. The date is stored in the format YYYYMMDD. The signature type represents the category in which a specific signature falls. Signatures are broadly classified as vulnerability, exploit, anomaly, component, or other. The default is other.
–Duplicate packet detector statistics
Duplicate packet statistics are now added to the TCP Normalizer Stage Statistics section of the show statistics virtual sensor command output. Large numbers of duplicate packets being reported by the Normalizer can aid in the detection of sensor deployment and configuration problems. Duplicate packets are often seen in situations where a single virtual sensor is monitoring two or more networks, and is seeing a TCP connection crossing two or more of these networks. In this situation you can reconfigure the sensor to monitor each network using a different virtual sensor. If both networks must be monitored by a single virtual sensor, configure the virtual sensor with the inline-TCP-session-tracking-mode parameter set to either interface-and-vlan or vlan-only.
–UDP length parameter in Atomic engines
A new parameter to match a specific UDP length was added. This engine parameter is added in the Atomic IP Advanced and Atomic IP engine for l4-protocol UDP. The purpose of this parameter is to check if UDP total length falls within a specific range.
For More Information
•For detailed information about global correlation, for the CLI refer to Configuring Global Correlation, for the IDM refer to Configuring Global Correlation, and for the IME refer to Configuring Global Correlation.
•For more information about the 10GE interface card, refer to Installing and Removing Interface Cards in Cisco IPS 4260 and IPS 4270-20.
•For detailed information about SDEE, refer to System Architecture.
The Sensor and Jumbo Packet Frame Size
For IPS standalone appliances with 1 G and 10 G fixed or add-on interfaces, the maximum jumbo frame size is 9216 bytes.
Note A jumbo frame is an Ethernet packet that is larger than the standard maximum of 1518 bytes (including Layer 2 header and FCS).
The IDM and JRE 1.7
Symptom Cannot launch the IDM.
Conditions When the IDM is running under JRE 1.7 and the IPS version is 7.1.5 or earlier.
Workaround Use JRE 1.6 or enable the SSL 2.0-compatible ClientHello format in the Java settings in the Control Panel.
Note For IPS 7.1(6) and later, the IDM functions with JRE 1.7.
Symptom
MySDN Decommissioned
Because MySDN has been decommissioned, the URL in older versions of the IDM and the IME is no longer functional. If you are using IPS 6.0 or later, we recommend that you upgrade your version of the IDM and the IME.
You can upgrade to the following versions to get the functioning MySDN URL:
•IDM 7.0.3
•IME 7.0.3
•IPS 7.0(4), which contains IDM 7.0.4
If you are using version IPS 5.x, you must look up signature information manually at this URL:
http://tools.cisco.com/security/center/search.x
For More Information
For detailed information on MySDN, for the IDM refer to MySDN and for the IME refer to MySDN.
Cisco Security Intelligence Operations
The Cisco Security Intelligence Operations site on Cisco.com provides intelligence reports about current vulnerabilities and security threats. It also has reports on other security topics that help you protect your network and deploy your security systems to reduce organizational risk.
You should be aware of the most recent security threats so that you can most effectively secure and manage your network. Cisco Security Intelligence Operations contains the top ten intelligence reports listed by date, severity, urgency, and whether there is a new signature available to deal with the threat.
Cisco Security Intelligence Operations contains a Security News section that lists security articles of interest. There are related security tools and links.
You can access Cisco Security Intelligence Operations at this URL:
http://tools.cisco.com/security/center/home.x
Cisco Security Intelligence Operations is also a repository of information for individual signatures, including signature ID, type, structure, and description.
You can search for security alerts and signatures at this URL:
http://tools.cisco.com/security/center/search.x
Before Upgrading to Cisco IPS 7.0(1)E3
This section describes the actions you should take before upgrading to Cisco IPS 7.0(1)E3. It contains the following topics:
•Perform These Tasks
•Backing Up and Restoring the Configuration File Using a Remote Server
•Obtaining Software on Cisco.com
•IPS Software Versioning
•Software Release Examples
Perform These Tasks
Before you upgrade your sensors to IPS 7.0(1)E3, make sure you perform the following tasks:
•Made sure you have a valid Cisco Service for IPS service contract per sensor so that you can apply software upgrades.
•Created a backup copy of your configuration.
•Saved the output of the show version command.
If you need to downgrade a signature update, you will know what version you had, and you can then apply the configuration you saved when you backed up your configuration.
For More Information
•For more information on how to obtain a valid Cisco Service for IPS service contract, see Service Programs for IPS Products.
•For the procedure for creating a backup copy of your configuration, see Backing Up and Restoring the Configuration File Using a Remote Server.
•For the procedure for finding your Cisco IPS software version, for the CLI refer to Displaying Version Information, for the IDM refer to IDM Home Window, and for the IME refer to Sensor Information Gadget.
•For the procedure for downgrading signature updates on your sensor, refer to Upgrading, Downgrading, and Installing System Images.
Backing Up and Restoring the Configuration File Using a Remote Server
Note We recommend copying the current configuration file to a remote server before upgrading.
Use the copy [/erase] source_url destination_url keyword command to copy the configuration file to a remote server. You can then restore the current configuration from the remote server. You are prompted to back up the current configuration first.
The following options apply:
•/erase—Erases the destination file before copying.
This keyword only applies to the current-config; the backup-config is always overwritten. If this keyword is specified for destination current-config, the source configuration is applied to the system default configuration. If it is not specified for the destination current-config, the source configuration is merged with the current-config.
•source_url—The location of the source file to be copied. It can be a URL or keyword.
•destination_url—The location of the destination file to be copied. It can be a URL or a keyword.
•current-config—The current running configuration. The configuration becomes persistent as the commands are entered.
•backup-config—The storage location for the configuration backup.
The exact format of the source and destination URLs varies according to the file. Here are the valid types:
•ftp:—Source URL for an FTP network server. The syntax for this prefix is:
ftp://[[username@]location][/relativeDirectory]/filename
ftp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password.
•scp:—Source URL for the SCP network server. The syntax for this prefix is:
scp://[[username@]location][/relativeDirectory]/filename
scp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password. You must add the remote host to the SSH known hosts list.
•http:—Source URL for the web server. The syntax for this prefix is:
http://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file.
•https:—Source URL for the web server. The syntax for this prefix is:
https://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file. The remote host must be a TLS trusted host.
Caution
Copying a configuration file from another sensor may result in errors if the sensing interfaces and virtual sensors are not configured the same.
Backing Up the Current Configuration to a Remote Server
To back up your current configuration to a remote server, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Back up the current configuration to the remote server.
sensor# copy current-config scp://user@192.0.2.0//configuration/cfg current-config
Warning: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
Step 3 Enter
yes to copy the current configuration to a backup configuration.
cfg 100% |************************************************| 36124 00:00
Restoring the Current Configuration From a Backup File
To restore your current configuration from a backup file, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Back up the current configuration to the remote server.
sensor# copy scp://user@192.0.2.0//configuration/cfg current-config
Warning: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
Step 3 Enter
yes to copy the current configuration to a backup configuration.
cfg 100% |************************************************| 36124 00:00
Warning: Replacing existing network-settings may leave the box in an unstable state.
Would you like to replace existing network settings
(host-ipaddress/netmask/gateway/access-list) on sensor before proceeding? [no]:
Step 4 Enter no to retain the currently configured hostname, IP address, subnet mask, management interface, and access list. We recommend you retain this information to preserve access to your sensor after the rest of the configuration has been restored.
For More Information
For the procedure for adding trusted hosts, for the CLI refer to Adding TLS Trusted Hosts, for the IDM refer to Configuring Trusted Hosts, and for the IME refer to Adding Trusted Hosts.
Obtaining Software on Cisco.com
Note You must have an active IPS maintenance contract, a Cisco.com password, and an IPS subscription service license to download software. You must be logged in to Cisco.com to download software. You must have a sensor license to apply signature updates.
You can find major and minor updates, service packs, signature and signature engine updates, system and recovery files, firmware upgrades, and readmes on the Download Software site on Cisco.com. Signature updates are posted to Cisco.com approximately every week, more often if needed. Service packs are posted to Cisco.com as needed. Major and minor updates are also posted periodically. Check Cisco.com regularly for the latest IPS software.
Downloading IPS Software
To download software on Cisco.com, follow these steps:
Step 1 Log in to Cisco.com.
Step 2 From the Support drop-down menu, choose Download Software.
Step 3 Under Select a Software Product Category, choose Security Software.
Step 4 Choose Intrusion Prevention System (IPS).
Step 5 Enter your username and password.
Step 6 In the Download Software window, choose IPS Appliances > Cisco Intrusion Prevention System and then click the version you want to download.
Step 7 Click the type of software file you need. The available files appear in a list in the right side of the window. You can sort by file name, file size, memory, and release date. And you can access the Release Notes and other product documentation.
Step 8 Click the file you want to download. The file details appear.
Step 9 Verify that it is the correct file, and click Download.
Step 10 Click Agree to accept the software download rules. The first time you download a file from Cisco.com, you must fill in the Encryption Software Export Distribution Authorization form before you can download the software.
•Fill out the form and click Submit. The Cisco Systems Inc. Encryption Software Usage Handling and Distribution Policy appears.
•Read the policy and click I Accept. The Encryption Software Export/Distribution Form appears.
If you previously filled out the Encryption Software Export Distribution Authorization form, and read and accepted the Cisco Systems Inc. Encryption Software Usage Handling and Distribution Policy, these forms are not displayed again. The File Download dialog box appears.
Step 11 Open the file or save it to your computer.
Step 12 Follow the instructions in the Readme to install the update.
Note Major and minor updates, service packs, recovery files, signature and signature engine updates are the same for all sensors. System image files are unique per platform.
For More Information
•For detailed information about IPS maintenance contracts, see Service Programs for IPS Products.
•For the procedure for obtaining and installing the sensor license, see Obtaining and Installing the License Key.
IPS Software Versioning
When you download IPS software images from Cisco.com, you should understand the versioning scheme so that you know which files are base files, which are cumulative, and which are incremental.
Major Update
A major update contains new functionality or an architectural change in the product. For example, the Cisco IPS 7.0 base version includes everything (except deprecated features) since the previous major release (the minor update features, service pack fixes, and signature updates) plus any new changes. Major update 7.0(1) requires 5.1(6) and later. With each major update there are corresponding system and recovery packages.
Note The 7.0(1) major update is used to upgrade 5.1(6) and later sensors to 7.0(1) If you are reinstalling 7.0(1) on a sensor that already has 7.0(1) installed, use the system image or recovery procedures rather than the major update.
Minor Update
A minor update is incremental to the major version. Minor updates are also base versions for service packs. The first minor update for 7.0 is 7.1(1). Minor updates are released for minor enhancements to the product. Minor updates contain all previous minor features (except deprecated features), service pack fixes, signature updates since the last major version, and the new minor features being released. You can install the minor updates on the previous major or minor version (and often even on earlier versions). The minimum supported version needed to upgrade to the newest minor version is listed in the Readme that accompanies the minor update. With each minor update there are corresponding system and recovery packages.
Service Pack
A service pack is cumulative following a base version release (minor or major). Service packs are used for the release of defect fixes with no new enhancements. Service packs contain all service pack fixes since the last base version (minor or major) and the new defect fixes being released. Service packs require the minor version. The minimum supported version needed to upgrade to the newest service pack is listed in the Readme that accompanies the service pack. Service packs also include the latest engine update. For example, if service pack 7.0(3) is released, and E3 is the latest engine level, the service pack is released as 7.0(3)E3.
Patch Release
A patch release is used to address defects that are identified in the upgrade binaries after a software release. Rather than waiting until the next major or minor update, or service pack to address these defects, a patch can be posted. Patches include all prior patch releases within the associated service pack level. The patches roll into the next official major or minor update, or service pack.
Before you can install a patch release, the most recent major or minor update, or service pack must be installed. For example, patch release 7.0(1p1) requires 7.0(1).
Note Upgrading to a newer patch does not require you to uninstall the old patch. For example, you can upgrade from patch 7.0(1p1) to 7.0(1p2) without first uninstalling 7.0(1p1).
Figure 1 illustrates what each part of the IPS software file represents for major and minor updates, service packs, and patch releases.
Figure 1 IPS Software File Name for Major and Minor Updates, Service Packs, and Patch Releases
Signature Update
A signature update is a package file containing a set of rules designed to recognize malicious network activities. Signature updates are released independently from other software updates. Each time a major or minor update is released, you can install signature updates on the new version and the next oldest version for a period of at least six months. Signature updates are dependent on a required signature engine version. Because of this, a req designator lists the signature engine required to support a particular signature update.
Figure 2 illustrates what each part of the IPS software file represents for signature/virus updates.
Figure 2 IPS Software File Name for Signature Updates
Signature Engine Update
A signature engine update is an executable file containing binary code to support new signature updates. Signature engine files require a specific service pack, which is also identified by the req designator.
Figure 3 illustrates what each part of the IPS software file represents for signature engine updates.
Figure 3 IPS Software File Name for Signature Engine Updates
Recovery and System Image Files
Recovery and system image files contain separate versions for the installer and the underlying application. The installer version contains a major and minor version field. The major version is incremented by one of any major changes to the image installer, for example, switching from .tar to rpm or changing kernels. The minor version can be incremented by any one of the following:
•Minor change to the installer, for example, a user prompt added.
•Repackages require the installer minor version to be incremented by one if the image file must be repackaged to address a defect or problem with the installer.
Figure 4 illustrates what each part of the IPS software file represents for recovery and system image files.
Figure 4 IPS Software File Name for Recovery and System Image Files
Software Release Examples
Table 1 lists platform-independent Cisco IPS 7.x software release examples. Refer to the Readmes that accompany the software files for detailed instructions on how to install the files.
Table 1 Platform-Independent Release Examples
|
Release
|
Target Frequency
|
Identifier
|
Example Version
|
Example Filename
|
Signature update1 |
Weekly |
sig |
S353 |
IPS-sig-S353-req-E3.pkg |
Signature engine update2 |
As needed |
engine |
E3 |
IPS-engine-E3-req-7.0-1.pkg |
Service packs3 |
Semi-annually
or as needed |
— |
7.0(3) |
IPS-K9-7.0-3-E3.pkg |
Minor version update4 |
Annually |
— |
7.0(1) |
IPS-K9-7.0-1-E3.pkg Note IPS-AIM-K9-7.0-1-E3.pkg is the minor version update for AIM IPS. IPS-NME-K-9-7.0-1-E3.pkg is the minor version update for NME IPS. |
Major version update5 |
Annually |
— |
7.0(1) |
IPS-K9-7.0-1-E3.pkg |
Patch release6 |
As needed |
patch |
7.0(1p1) |
IPS-K9-patch-7.0-1pl-E3.pkg |
Recovery package7 |
Annually or as needed |
r |
1.1-7.0(1) |
IPS-K9-r-1.1-a-7.0-1-E3.pkg |
Table 2 describes platform-dependent software release examples.
Table 2 Platform-Dependent Release Examples
|
Release
|
Target Frequency
|
Identifier
|
Supported Platform
|
Example Filename
|
System image1 |
Annually |
sys |
Separate file for each sensor platform |
IPS-4240-K9-sys-1.1-a-7.0-1-E3.img |
Maintenance partition image2 |
Annually |
mp |
IDSM2 |
c6svc-mp.2-1-2.bin.gz |
Bootloader |
As needed |
bl |
AIM IPS
NME IPS |
pse_aim_x.y.z.bin
pse_nm_x.y.z.bin
(where x, y, z is the release number) |
Mini-kernel |
As needed |
mini-kernel |
AIM IPS
NME IPS |
pse_mini_kernel_1.1.10.64.bz2 |
Table 3 describes the platform identifiers used in platform-specific names.
Table 3 Platform Identifiers
|
Sensor Family
|
Identifier
|
IPS-4240 series |
4240 |
IPS-4255 series |
4255 |
IPS-4260 series |
4260 |
IPS 4270-20 series |
4270_20 |
IDS module for Catalyst 6K |
IDSM2 |
IPS network module |
AIM
NME |
Adaptive security appliance modules |
SSM_10
SSM_20
SSM_40 |
Upgrading to Cisco IPS 7.0(1)E3
This section provides information on upgrading to Cisco IPS 7.0(1)E3, and contains the following topics:
•Upgrade Notes and Caveats
•Upgrading to IPS 7.0(1)E3
Upgrade Notes and Caveats
The following upgrade notes and caveats apply to upgrading to 7.0(1)E3:
•The minimum required version for upgrading to 7.0(1)E3 is 5.1(6) or later.
•You must have a valid Cisco Service for IPS Maintenance contract per sensor to receive and use software upgrades from Cisco.com.
•Use IPS-AIM-K9-7.0-1-E3.pkg to upgrade the AIM IPS and IPS-NME-K9-7.0-1-E3 to upgrade the NME IPS. For all other supported sensors, use the IPS-K9-7.0-1-E3.pkg upgrade file.
•After you upgrade any IPS software on your sensor, you must restart the IDM to see the latest software features.
•Using automatic upgrade:
–When you upgrade the AIM IPS or the NME IPS using automatic update, you must disable heartbeat reset on the router before placing the upgrade file on your automatic update server. After the AIP IPS and the NME IPS have been updated, you can reenable heartbeat reset. If you do not disable heartbeat reset, the upgrade can fail and leave the AIM IPS and the NME IPS in an unknown state, which can require a system reimage to recover.
–If you are using automatic update with a mixture of AIM IPS, NME IPS, and other IPS appliances or modules, make sure you put both the 7.0(1)E3 upgrade file (IPS-K9-7.0-1-E3.pkg), the AIM IPS upgrade file (IPS-AIM-K9-7.0-1-E3.pkg), and the NME IPS upgrade file (IPS-NME-K9-7.0-1-E3) on the automatic update server so that the AIM IPS and the NME IPS can correctly detect which file needs to be automatically downloaded and installed. If you only put the 7.0(1)E3 upgrade file (IPS-K9-7.0-1-E3.pkg) on the server, the AIM IPS and the NME IPS will download and try to install the wrong file.
•Using manual upgrade:
–If you want to manually update your sensor, copy the 7.0(1)E3 update files to the directory on the server that your sensor polls for updates.
–When you upgrade the AIM IPS or the NME IPS using manual upgrade, you must disable heartbeat reset on the router before installing the upgrade. You can reenable heartbeat reset after you complete the upgrade. If you do not disable heartbeat reset, the upgrade can fail and leave the AIM IPS or the NME IPS in an unknown state, which can require a system reimage to recover.
•Global correlation health status defaults to red and changes to green after a successful global correlation update. Successful global correlation updates require a DNS server or an HTTP proxy server. Because DNS and HTTP proxy server configuration features are new to IPS 7.0(1)E3, they are unconfigured after an upgrade to 7.0(1)E3. As a result, global correlation health and overall sensor health status are red until you configure a DNS or HTTP proxy server on the sensor. If the sensor is deployed in an environment where a DNS or HTTP proxy server is not available, you can address the red global correlation health and overall sensor health status by disabling global correlation and configuring sensor health status to exclude global correlation health status.
For More Information
•For more information on Cisco Service for IPS Maintenance contracts, see Service Programs for IPS Products.
•For the procedure for configuring automatic update, refer to Configuring Automatic Upgrades.
•For the procedure for manually updating your sensor, refer to Upgrading the Sensor.
•For the procedures for reimaging sensors, refer to Installing System Images.
•For the procedure for enabling and disabling heartbeat reset, for the AIM IPS refer to Enabling and Disabling Heartbeat Reset, and for the NME IPS refer to Enabling and Disabling Heartbeat Reset.
•For the procedure for disabling global correlation, for the CLI refer to Disabling Global Correlation, for the IDM refer to Disabling Global Correlation, and for the IME refer to Disabling Global Correlation.
•For the procedure for configuring sensor health to exclude global correlation health, for the CLI refer to Configuring Health Status Information, for the IDM refer to Configuring Sensor Health, and for the IME refer to Configuring Sensor Health.
Upgrading to IPS 7.0(1)E3
Caution
You must log in to Cisco.com using an account with cryptographic privileges to download software. The first time you download software on Cisco.com, you receive instructions for setting up an account with cryptographic privileges.
Caution
Do not change the filename. You must preserve the original filename for the sensor to accept the update.
To upgrade the sensor, follow these steps:
Step 1 Download the appropriate file (for example, IPS-K9-7.0-1-E3.pkg) to an FTP, SCP, HTTP, or HTTPS server that is accessible from your sensor.
Step 2 Log in to the CLI using an account with administrator privileges.
Step 3 Enter configuration mode.
sensor# configure terminal
Step 4 Upgrade the sensor.
sensor(config)# upgrade url/IPS-K9-7.0-1-E3.pkg
The URL points to where the update file is located, for example, to retrieve the update using FTP, enter the following:
sensor(config)# upgrade ftp://username@ip_address//directory/IPS-K9-7.0-1-E3.pkg
Step 5 Enter the password when prompted.
Step 6 Enter yes to complete the upgrade.
Note Major updates, minor updates, and service packs may force a restart of the IPS processes or even force a reboot of the sensor to complete installation.
Note The operating system is reimaged and all files that have been placed on the sensor through the service account are removed.
For More Information
•For the procedure for locating software on Cisco.com and obtaining an account with cryptographic privileges, see Obtaining Software on Cisco.com.
•For the procedure for reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.
After Upgrading to Cisco IPS 7.0(1)E3
This section provides information about what to do after you install IPS 7.02(1)E3. It contains the following topics:
•Comparing Configurations
•Importing a New SSL Certificate
•Logging In to the IDM
•Licensing the Sensor
Comparing Configurations
Compare your backed up and saved IPS 6.2 configuration with the output of the show configuration command after upgrading to 7.0(1)E3 to verify that all the configuration has been properly converted.
Caution
If the configuration is not properly converted, check the caveats for IPS 7.0(1)E3. or check Cisco.com for any upgrade issues that have been found. Contact the TAC if no DDTS refers to your situation.
For More Information
For a list of the caveats associated with this release, see Caveats.
Importing a New SSL Certificate
If necessary import the new SSL certificate for the upgraded sensor in to each tool being used to monitor the sensor.
For More Information
For the procedures for configuring TLS/SSL, for the CLI refer to Configuring TLS, for the IDM refer to Configuring Trusted Hosts, and for the IME refer to Configuring Trusted Hosts.
Logging In to the IDM
IDM is a web-based, Java Web Start application that enables you to configure and manage your sensor. The web server for IDM resides on the sensor. You can access it through Internet Explorer or Firefox web browsers.
To log in to IDM, follow these steps:
Step 1 Open a web browser and enter the sensor IP address. A Security Alert dialog box appears.
https://sensor_ip_address
Note The IDM is already installed on the sensor.
Note The default IP address is 192.168.1.2/24,192.168.1.1, which you change to reflect your network environment when you initialize the sensor. When you change the web server port, you must specify the port in the URL address of your browser when you connect to the IDM in the format https://sensor_ip_address:port (for example, https://10.1.9.201:1040).
Step 2 Click Yes to accept the security certificate. The Cisco IPS Device Manager Version 7.0 window appears.
Step 3 To launch the IDM, click Run IDM. The JAVA loading message box appears, and then the Warning - Security dialog box appears.
Step 4 To verify the security certificate, check the Always trust content from this publisher check box, and click Yes. The JAVA Web Start progress dialog box appears, and then the IDM on ip_address dialog box appears.
Step 5 To create a shortcut for the IDM, click Yes. The Cisco IDM Launcher dialog box appears.
Note You must have JRE 1.5 (JAVA 5) installed to create shortcuts for the IDM. If you have JRE 1.6 (JAVA 6) installed, the shortcut is created automatically.
Step 6 To authenticate the IDM, enter your username and password, and click OK. The IDM begins to load. If you change panes from Home to Configuration or Monitoring before the IDM has complete initialization, a Status dialog box appears with the following message:
Please wait while IDM is loading the current configuration from the sensor.
The main window of the IDM appears.
Note Both the default username and password are cisco. You were prompted to change the password during sensor initialization.
Note If you created a shortcut, you can launch the IDM by double-clicking the IDM shortcut icon. You can also close the The Cisco IPS Device Manager Version 7.0 window. After you launch the IDM, is it not necessary for this window to remain open.
Licensing the Sensor
This section describes how to obtain a license key and how to license the sensor using the CLI, the IDM, or the IME. It contains the following topics:
•Understanding the License
•Service Programs for IPS Products
•Obtaining and Installing the License Key
Understanding the License
Although the sensor functions without the license key, you must have a license key to obtain signature updates and use the global correlation features. To obtain a license key, you must have the following:
•Cisco Service for IPS service contract
Contact your reseller, Cisco service or product sales to purchase a contract.
•Your IPS device serial number
To find the IPS device serial number in the IDM or the IME, for the IDM choose Configuration > Sensor Management > Licensing, and for the IME choose Configuration > sensor_name > Sensor Management > Licensing, or in the CLI use the show version command.
•Valid Cisco.com username and password
Trial license keys are also available. If you cannot get your sensor licensed because of problems with your contract, you can obtain a 60-day trial license that supports signature updates that require licensing.
You can obtain a license key from the Cisco.com licensing server, which is then delivered to the sensor. Or, you can update the license key from a license key provided in a local file. Go to http://www.cisco.com/go/license and click IPS Signature Subscription Service to apply for a license key.
You can view the status of the license key in these places:
•IDM Home window Licensing section on the Health tab
•IDM Licensing pane (Configuration > Licensing)
•IME Home page in the Device Details section on the Licensing tab
•License Notice at CLI login
Whenever you start the IDM, the IME, or the CLI, you are informed of your license status—whether you have a trial, invalid, or expired license key. With no license key, an invalid license key, or an expired license key, you can continue to use the IDM, the IME, and the CLI, but you cannot download signature updates.
If you already have a valid license on the sensor, you can click Download on the License pane to download a copy of your license key to the computer that the IDM or the IME is running on and save it to a local file. You can then replace a lost or corrupted license, or reinstall your license after you have reimaged the sensor.
Service Programs for IPS Products
You must have a Cisco Services for IPS service contract for any IPS product so that you can download a license key and obtain the latest IPS signature updates. If you have a direct relationship with Cisco Systems, contact your account manager or service account manager to purchase the Cisco Services for IPS service contract. If you do not have a direct relationship with Cisco Systems, you can purchase the service account from a one-tier or two-tier partner.
When you purchase the following IPS products you must also purchase a Cisco Services for IPS service contract:
•IPS 4240
•IPS 4255
•IPS 4260
•IPS 4270-20
•AIM IPS
•IDSM2
•NME IPS
When you purchase an ASA 5500 series adaptive security appliance product that does not contain IPS, you must purchase a SMARTnet contract.
Note SMARTnet provides operating system updates, access to Cisco.com, access to TAC, and hardware replacement NBD on site.
When you purchase an ASA 5500 series adaptive security appliance product that ships with the AIP SSM installed, or if you purchase it to add to your ASA 5500 series adaptive security appliance product, you must purchase the Cisco Services for IPS service contract.
Note Cisco Services for IPS provides IPS signature updates, operating system updates, access to Cisco.com, access to TAC, and hardware replacement NBD on site.
For example, if you purchased an ASA 5510 and then later wanted to add IPS and purchased an ASA-SSM-AIP-10-K9, you must now purchase the Cisco Services for IPS service contract. After you have the Cisco Services for IPS service contract, you must also have your product serial number to apply for the license key.
Caution
If you ever send your product for RMA, the serial number will change. You must then get a new license key for the new serial number.
Obtaining and Installing the License Key
You can install the license key through the CLI, the IDM, or the IME. This section describes how to obtain and install the license key, and contains the following topics:
•Using the IDM or the IME
•Using the CLI
Using the IDM or the IME
Note In addition to a valid Cisco.com username and password, you must also have a Cisco Services for IPS service contract before you can apply for a license key.
To obtain and install the license key, follow these steps:
Step 1 Log in to the IDM or the IME using an account with administrator privileges.
Step 2 For the IDM choose Configuration > Sensor Management > Licensing. For the IME choose Configuration > sensor_name > Sensor Management > Licensing. The Licensing pane displays the status of the current license. If you have already installed your license, you can click Download to save it if needed.
Step 3 Obtain a license key by doing one of the following:
•Click the Cisco.com radio button to obtain the license from Cisco.com. The IDM or the IME contacts the license server on Cisco.com and sends the server the serial number to obtain the license key. This is the default method. Go to Step 4.
•Click the License File radio button to use a license file. To use this option, you must apply for a license key at this URL: www.cisco.com/go/license. The license key is sent to you in e-mail and you save it to a drive that the IDM or the IME can access. This option is useful if your computer cannot access Cisco.com. Go to Step 7.
Step 4 Click Update License, and in the Licensing dialog box, click Yes to continue. The Status dialog box informs you that the sensor is trying to connect to Cisco.com. An Information dialog box confirms that the license key has been updated.
Step 5 Click OK.
Step 6 Go to www.cisco.com/go/license.
Step 7 Fill in the required fields. Your license key will be sent to the e-mail address you specified.
Caution
You must have the correct IPS device serial number because the license key only functions on the device with that number.
Step 8 Save the license key to a hard-disk drive or a network drive that the client running the IDM or the IME can access.
Step 9 Log in to the IDM or the IME.
Step 10 For the IDM choose Configuration > Sensor Management > Licensing. For the IME choose Configuration > sensor_name > Sensor Management > Licensing.
Step 11 Under Update License, click the License File radio button.
Step 12 In the Local File Path field, specify the path to the license file or click Browse Local to browse to the file.
Step 13 Browse to the license file and click Open.
Step 14 Click Update License.
Using the CLI
Note You cannot install an older license key over a newer license key.
Use the copy source-url license_file_name license-key command to copy the license key to your sensor.
The following options apply:
•source-url—The location of the source file to be copied. It can be a URL or keyword.
•destination-url—The location of the destination file to be copied. It can be a URL or a keyword.
•license-key—The subscription license file.
•license_file_name—The name of the license file you receive.
The exact format of the source and destination URLs varies according to the file. Here are the valid types:
•ftp:—Source URL for an FTP network server. The syntax for this prefix is:
ftp://[[username@]location][/relativeDirectory]/filename
ftp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password.
•scp:—Source URL for the SCP network server. The syntax for this prefix is:
scp://[[username@]location][/relativeDirectory]/filename
scp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password. You must add the remote host to the SSH known hosts list.
•http:—Source URL for the web server. The syntax for this prefix is:
http://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file.
•https:—Source URL for the web server. The syntax for this prefix is:
https://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file. The remote host must be a TLS trusted host.
Installing the License Key
To install the license key, follow these steps:
Step 1 Apply for the license key at this URL: www.cisco.com/go/license.
Note In addition to a valid Cisco.com username and password, you must also have a Cisco Services for IPS service contract before you can apply for a license key.
Step 2 Fill in the required fields. Your Cisco IPS Signature Subscription Service license key will be sent by e-mail to the e-mail address you specified.
Note You must have the correct IPS device serial number because the license key only functions on the device with that number.
Step 3 Save the license key to a system that has a web server, FTP server, or SCP server.
Step 4 Log in to the CLI using an account with administrator privileges.
Step 5 Copy the license key to the sensor.
sensor# copy scp://user@10.89.147.3://tftpboot/dev.lic license-key
Step 6 Verify the sensor is licensed.
Cisco Intrusion Prevention System, Version 7.0(1)E3
Signature Update S391.0 2008-04-16
Virus Update V1.2 2005-11-24
OS Version: 2.4.30-IDS-smp-bigphys
Serial Number: P300000220
Sensor up-time is 3 days.
Using 1031888896 out of 2093682688 bytes of available memory (49% usage)
system is using 17.8M out of 29.0M bytes of available disk space (61% usage)
application-data is using 52.4M out of 166.6M bytes of available disk space (33% usage)
boot is using 37.8M out of 68.5M bytes of available disk space (58% usage)
MainApp N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500 Running
AnalysisEngine N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500 Running
CLI N-2007_JUN_19_16_45 (Release) 2007-06-19T17:10:20-0500
IPS-K9-7.0-1-E3 15:36:05 UTC Thu Apr 24 2008
Recovery Partition Version 1.1 - 7.0(1)E3
Host Certificate Valid from: 25-Apr-2008 to 26-Apr-2010
Step 7 Copy your license key from a sensor to a server to keep a backup copy of the license.
sensor# copy license-key scp://user@10.89.147.3://tftpboot/dev.lic
Installing or Upgrading Cisco IME and Migrating Data In to the IME
This section describes how to install and upgrade the IME, and how to migrate data from IEV or a previous version of the IME.
Cisco IEV, Cisco IOS IPS, and CSM
If you have a version of Cisco IPS Event Viewer installed, the Install wizard prompts you to remove it before installing the IME.
IME event monitoring is also supported in IOS-IPS versions that support the Cisco IPS 5.x/6.x signature format. We recommend IOS-IPS 12.4(15)T4 if you intend to use the IME to monitor an IOS IPS device. Some of the new IME functionality including health monitoring is not supported.
Caution
Do not install the IME on top of existing installations of CSM. You must uninstall CSM before installing the IME. Do not install CSM on top of existing installations of the IME.
Installation Notes and Caveats
Observe the following when installing or upgrading the IME:
•You can install the IME over all versions of the IME but not over IEV. All alert database and user settings are preserved.
•The IME detects previous versions of IEV and prompts you to manually remove the older version before installing the IME or to install the IME on another system. The installation program then stops.
•Make sure you close any open instances of the IME before upgrading to a new version of the IME.
•Disable any anti-virus or host-based intrusion detection software before beginning the installation, and close any open applications. The installer spawns a command shell application that may trigger your host-based detection software, which causes the installation to fail.
•You must be administrator to install the IME.
•The IME coexists with other instances of the MySQL database. If you have a MySQL database installed on your system, you do NOT have to uninstall it before installing the IME.
Installing or Upgrading the IME
To install the IME, follow these steps:
Step 1 From the Download Software site on Cisco.com, download the IME executable file to your computer, or start the IDM in a browser window, and under Cisco IPS Manager Express, click download to install the IME executable file. IME-7.0.4.exe is an example of what the IME executable file might look like.
Step 2 Double-click the executable file. The Cisco IPS Manager Express - InstallShield Wizard appears. You receive a warning if you have a previous version of Cisco IPS Event Viewer installed. Acknowledge the warning, and exit installation. Remove the older version of IEV, and then continue IME installation.
Step 3 Click Next to start IME installation.
Step 4 Accept the license agreement and click Next.
Step 5 Click Next to choose the destination folder, click Install to install the IME, and then click Finish to exit the wizard. The Cisco IME and Cisco IME Demo icons are now on your desktop.
Note The first time you start the IME, you are prompted to set up a password.
Migrating IEV Data
To migrate IEV 5.x events to the IME, you must exit the installation and manually export the old events by using the IEV 5.x export function to move the data to local files. After installing the IME, you can import these files to the new IME system.
Note The IME does not support import and migration functions for IEV 4.x.
To export event data from IEV 5.x to a local file:
Step 1 From IEV 5.x, choose File > Database Administration > Export Database Tables.
Step 2 Enter the file name and select the table(s).
Step 3 Click OK. The events in the selected table(s) are exported to the specified local file.
Importing IEV Event Data In to the IME
To import event data in to the IME, follow these steps:
Step 1 From the IME, choose File > Import.
Step 2 Select the file exported from IEV 5.x and click Open. The contents of the selected file are imported in to the IME.
For More Information
For more information about Cisco IME, refer to Cisco Intrusion Prevention System Manager Express Configuration Guide for IPS 7.0.
Restrictions and Limitations
The following restrictions and limitations apply to Cisco IPS 7.0(1)E3 software and the products that run it:
•For IPS 5.0 and later, you can no longer remove the cisco account. You can disable it using the no password cisco command, but you cannot remove it. To use the no password cisco command, there must be another administrator account on the sensor. Removing the cisco account through the service account is not supported. If you remove the cisco account through the service account, the sensor most likely will not boot up, so to recover the sensor you must reinstall the sensor system image.
•Anomaly detection does not support IPv6 traffic; only IPv4 traffic is directed to the anomaly detection processor.
•IPv6 does not support the following event actions: Request Block Host, Request Block Connection, or Request Rate Limit.
•The AIM IPS and the NME IPS do not support the IPv6 features, because the router in which they are installed does not send them IPv6 data. IPv6 inspection may work on the IDSM2, but we do not officially support it. There is no support for IPv6 on the management (command and control) interface.
•VACLs on Catalyst switches do not have IPv6 support. The most common method for copying traffic to a sensor configured in Promiscuous mode is to use VACL capture. If you want to have IPv6 support, you can use SPAN ports.
•ICMP signature engines do not support ICMPv6, they are IPv4-specific, for example, the Traffic ICMP signature engine. ICMPv6 is covered by the Atomic IP Advanced signature engine.
•The AIM IPS and the NME IPS do not support virtualization.
•When you reload the router, the AIM IPS and the NME IPS also reload. To ensure that there is no loss of data on the AIM IPS or the NME IPS, make sure you shut down the module using the shutdown command before you use the reload command to reboot the router.
•Do not deploy IOS IPS and the AIM IPS and the NME IPS at the same time.
•When the AIM IPS and the NME IPS are used with an IOS firewall, make sure SYN flood prevention is done by the IOS firewall.
The AIM IPS and the NME IPS and the IOS firewall complement abilities of each other to create security zones in the network and inspect traffic in those zones. Because the AIM IPS and the NME IPS and the IOS firewall operate independently, sometimes they are unaware of the activities of the other. In this situation, the IOS firewall is the best defense against a SYN flood attack.
•Cisco access routers only support one IDS/IPS per router.
•On IPS sensors with multiple processors (for example, the IPS 4260 and IPS 4270-20), packets may be captured out of order in the IP logs and by the packet command. Because the packets are not processed using a single processor, the packets can become out of sync when received from multiple processors.
•An IPS appliance can support both promiscuous and inline monitoring at the same time; however you must configure each physical interface in either promiscuous or inline mode. The sensor must contain at least two physical sensing interfaces to perform both promiscuous and inline monitoring. The exceptions to this ar the e AIP SSM-10, AIP SSM-20, and AIP SSM-40. The AIP SSM can support both promiscuous and inline monitoring on its single physical back plane interface inside the adaptive security appliance. The configuration on the main adaptive security appliance can be used to designate which packets/connections should be monitored by the AIP SSM as either promiscuous or inline.
•When deploying an IPS sensor monitoring two sides of a network device that does TCP sequence number randomization, we recommend using a virtual senor for each side of the device.
•After you upgrade any IPS software on your sensor, you must restart the IDM to see the latest software features.
•The IDM does not support any non-English characters, such as the German umlaut or any other special language characters. If you enter such characters as a part of an object name through the IDM, they are turned into something unrecognizable and you will not be able to delete or edit the resulting object through the IDM or the CLI.
This is true for any string that is used by CLI as an identifier, for example, names of time periods, inspect maps, server and URL lists, and interfaces.
•You can only install eight IDSM2s per switch chassis.
•When SensorApp is reconfigured, there is a short period when SensorApp is unable to respond to any queries. Wait a few minutes after reconfiguration is complete before querying SensorApp for additional information.
•The IDM and the IME launch MySDN from the last browser window you opened, which is the default setting for Windows. To change this default behavior, in Internet Explorer, choose Tools > Internet Options, and then click the Advanced tab. Scroll down and uncheck the Reuse windows for launching shortcuts check box.
For More Information
•For more information on interoperability between modules, refer to Interoperability With Other IPS Modules.
•For more information about IPv6, switches, and lack of VACL capture, see IPv6, Switches, and Lack of VACL Capture.
Recovering the Password
For most IPS platforms, you can now recover the password on the sensor rather than using the service account or reimaging the sensor. This section describes how to recover the password for the various IPS platforms. It contains the following topics:
•Understanding Password Recovery
•Recovering the Appliance Password
•Recovering the IDSM2 Password
•Recovering the AIP SSM Password
•Recovering the AIM IPS Password
•Recovering the NME IPS Password
•Disabling Password Recovery
•Verifying the State of Password Recovery
•Troubleshooting Password Recovery
Understanding Password Recovery
Password recovery implementations vary according to IPS platform requirements. Password recovery is implemented only for the cisco administrative account and is enabled by default. The IPS administrator can then recover user passwords for other accounts using the CLI. The cisco user password reverts to cisco and must be changed after the next login.
Note Administrators may need to disable the password recovery feature for security reasons.
Table 4 lists the password recovery methods according to platform.
Table 4 Password Recovery Methods According to Platform
|
Platform
|
Description
|
Recovery Method
|
4200 series sensors |
Stand-alone IPS appliances |
GRUB prompt or ROMMON |
AIP SSM |
ASA 5500 series adaptive security appliance modules |
ASA CLI command |
IDSM2 |
Switch IPS module |
Password recovery image file |
AIM IPS |
Router IPS modules |
Bootloader command |
For More Information
For more information on when and how to disable password recovery, see Disabling Password Recovery.
Recovering the Appliance Password
This section describes the two ways to recover the password for appliances. It contains the following topics:
•Using the GRUB Menu
•Using ROMMON
Using the GRUB Menu
For 4200 series appliances, the password recovery is found in the GRUB menu, which appears during bootup. When the GRUB menu appears, press any key to pause the boot process.
Note You must have a terminal server or direct serial connection to the appliance to use the GRUB menu to recover the password.
To recover the password on appliances, follow these steps:
Step 1 Reboot the appliance.
The following menu appears:
GNU GRUB version 0.94 (632K lower / 523264K upper memory)
-------------------------------------------
2: Cisco IPS Clear Password (cisco)
-------------------------------------------
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
Commands before booting, or 'c' for a command-line.
Step 2 Press any key to pause the boot process.
Step 3 Choose 2: Cisco IPS Clear Password (cisco). The password is reset to cisco. You can change the password the next time you log into the CLI.
For More Information
For more information on connecting an appliance to a terminal server, refer to Connecting an Appliance to a Terminal Server.
Using ROMMON
For the IPS 4240 and the IPS 4255 you can use the ROMMON to recover the password. To access the ROMMON CLI, reboot the sensor from a terminal server or direct connection and interrupt the boot process.
Note After recovering the password, you must reset the confreg to 0, otherwise, when you try to upgrade the sensor, the upgrade fails because when the sensor reboots, it goes to password recovery (confreg 0x7) rather than to the upgrade option.
To recover the password using the ROMMON CLI, follow these steps:
Step 1 Reboot the appliance.
Step 2 To interrupt the boot process, press ESC or Control-R (terminal server) or send a BREAK command (direct connection).
The boot code either pauses for 10 seconds or displays something similar to one of the following:
•Evaluating boot options
•Use BREAK or ESC to interrupt boot
Step 3 Enter the following commands to reset the password.
Sample ROMMON session:
Booting system, please wait...
Embedded BIOS Version 1.0(11)2 01/25/06 13:21:26.17
Evaluating BIOS Options...
Launch BIOS Extension to setup ROMMON
Cisco Systems ROMMON Version (1.0(11)2) #0: Thu Jan 26 10:43:08 PST 2006
Use BREAK or ESC to interrupt boot.
Use SPACE to begin boot immediately.
MAC Address:000b.fcfa.d155
Update Config Register (0x7) in NVRAM...
Step 4 Enter the following command to reset the confreg value to 0:
Recovering the IDSM2 Password
To recover the password for the IDSM2, you must install a special password recovery image file. This installation only resets the password, all other configuration remains intact. The password recovery image is version-dependent and can be found on the Cisco Download Software site. For IPS 6.x, download WS-SVC-IDSM2-K9-a-6.0-password-recovery.bin.gz. For IPS 7.x, download WS-SVC-IDSM2-K9-a-7.0-password-recovery.bin.gz.
FTP is the only supported protocol for image installations, so make sure you put the password recovery image file on an FTP server that is accessible to the switch. You must have administrative access to the Cisco 6500 series switch to recover the password on the IDSM2.
During the password recovery image installation, the following message appears:
Upgrading will wipe out the contents on the hard disk.
Do you want to proceed installing it [y|n]:
This message is in error. Installing the password recovery image does not remove any configuration, it only resets the login account.
Once you have downloaded the password recovery image file, follow the instructions to install the system image file but substitute the password recovery image file for the system image file. The IDSM2 should reboot into the primary partition after installing the recovery image file. If it does not, enter the following command from the switch:
hw-module module module_number reset hdd:1
Note The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.
For More Information
•For the procedures for reimaging the IDSM2, refer to Installing the IDSM2 System Image.
•For more information on downloading Cisco IPS software, see Obtaining Software on Cisco.com.
Recovering the AIP SSM Password
You can reset the password to the default (cisco) for the AIP SSM using the CLI or the ASDM. Resetting the password causes it to reboot. IPS services are not available during a reboot.
Note To reset the password, you must have ASA 7.2.2 or later.
Use the hw-module module slot_number password-reset command to reset the password to the default cisco. If the module in the specified slot has an IPS version that does not support password recovery, the following error message is displayed:
ERROR: the module in slot <n> does not support password recovery.
Resetting the Password Using the CLI
To reset the password on the AIP SSM, follow these steps:
Step 1 Log into the adaptive security appliance and enter the following command to verify the module slot number:
Mod Card Type Model Serial No.
--- -------------------------------------------- ------------------ -----------
0 ASA 5510 Adaptive Security Appliance ASA5510 JMX1135L097
1 ASA 5500 Series Security Services Module-40 ASA-SSM-40 JAF1214AMRL
Mod MAC Address Range Hw Version Fw Version Sw Version
--- --------------------------------- ------------ ------------ ---------------
0 001b.d5e8.e0c8 to 001b.d5e8.e0cc 2.0 1.0(11)2 8.4(3)
1 001e.f737.205f to 001e.f737.205f 1.0 1.0(14)5 7.0(7)E4
Mod SSM Application Name Status SSM Application Version
--- ------------------------------ ---------------- --------------------------
Mod Status Data Plane Status Compatibility
--- ------------------ --------------------- -------------
Step 2 Reset the password for module 1.
asa# hw-module module 1 password-reset
Reset the password on module in slot 1? [confirm]
Step 3 Press Enter to confirm.
Password-Reset issued for slot 1.
Step 4 Verify the status of the module. Once the status reads Up, you can session to the AIP SSM.
Mod Card Type Model Serial No.
--- -------------------------------------------- ------------------ -----------
1 ASA 5500 Series Security Services Module-40 ASA-SSM-40 JAF1214AMRL
Mod MAC Address Range Hw Version Fw Version Sw Version
--- --------------------------------- ------------ ------------ ---------------
1 001e.f737.205f to 001e.f737.205f 1.0 1.0(14)5 7.0(7)E4
Mod SSM Application Name Status SSM Application Version
--- ------------------------------ ---------------- --------------------------
Mod Status Data Plane Status Compatibility
--- ------------------ --------------------- -------------
Step 5 Session to the AIP SSM.
Opening command session with slot 1.
Connected to slot 1. Escape character sequence is 'CTRL-^X'.
Step 6 Enter the default username (cisco) and password (cisco) at the login prompt.
You are required to change your password immediately (password aged)
Changing password for cisco.
(current) password: cisco
Step 7 Enter your new password twice.
New password: new password
Retype new password: new password
This product contains cryptographic features and is subject to United States and local
country laws governing import, export, transfer and use. Delivery of Cisco cryptographic
products does not imply third-party authority to import, export, distribute or use
encryption. Importers, exporters, distributors and users are responsible for compliance
with U.S. and local country laws. By using this product you agree to comply with
applicable laws and regulations. If you are unable to comply with U.S. and local laws,
return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to export@cisco.com.
There is no license key installed on this IPS platform. The system will continue to
operate with the currently installed signature set. A valid license must be obtained in
order to apply signature updates. Please go to http://www.cisco.com/go/license to obtain a
new license or install a license.
Using the ASDM
To reset the password in the ASDM, follow these steps:
Step 1 From the ASDM menu bar, choose Tools > IPS Password Reset.
Note This option does not appear in the menu if there is no IPS present.
Step 2 In the IPS Password Reset confirmation dialog box, click OK to reset the password to the default (cisco). A dialog box displays the success or failure of the password reset. If the reset fails, make sure you have the correct ASA and IPS software versions.
Step 3 Click Close to close the dialog box. The sensor reboots.
Recovering the AIM IPS Password
To recover the password for the AIM IPS, use the clear password command. You must have console access to the AIM IPS and administrative access to the router.
To recover the password for the AIM IPS, follow these steps:
Step 1 Log in to the router.
Step 2 Enter privileged EXEC mode on the router.
Step 3 Confirm the module slot number in your router.
router# show run | include ids-sensor
Step 4 Session in to the AIM IPS.
router# service-module ids-sensor slot/port session
Example
router# service-module ids-sensor 0/0 session
Step 5 Press Control-shift-6 followed by x to navigate to the router CLI.
Step 6 Reset AIM IPS from the router console.
router# service-module ids-sensor 0/0 reset
Step 7 Press Enter to return to the router console.
Step 8 When prompted for boot options, enter *** quickly. You are now in the bootloader.
Step 9 Clear the password.
ServicesEngine boot-loader# clear password
The AIM IPS reboots. The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.
Recovering the NME IPS Password
To recover the password for the NME IPS, use the clear password command. You must have console access to the NME IPS and administrative access to the router.
To recover the password for the NME IPS, follow these steps:
Step 1 Log in to the router.
Step 2 Enter privileged EXEC mode on the router.
Step 3 Confirm the module slot number in your router.
router# show run | include ids-sensor
Step 4 Session in to the NME IPS.
router# service-module ids-sensor slot/port session
Example
router# service-module ids-sensor 1/0 session
Step 5 Press Control-shift-6 followed by x to navigate to the router CLI.
Step 6 Reset the NME IPS from the router console.
router# service-module ids-sensor 1/0 reset
Step 7 Press Enter to return to the router console.
Step 8 When prompted for boot options, enter *** quickly. You are now in the bootloader.
Step 9 Clear the password.
ServicesEngine boot-loader# clear password
The NME IPS reboots. The password is reset to cisco. Log in to the CLI with username cisco and password cisco. You can then change the password.
Disabling Password Recovery
Caution
If you try to recover the password on a sensor on which password recovery is disabled, the process proceeds with no errors or warnings; however, the password is not reset. If you cannot log in to the sensor because you have forgotten the password, and password recovery is set to disabled, you must reimage your sensor.
Password recovery is enabled by default. You can disable password recovery through the CLI or the IDM.
Disabling Password Recovery Using the CLI
To disable password recovery in the CLI, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Enter global configuration mode.
sensor# configure terminal
Step 3 Enter host mode.
sensor(config)# service host
Step 4 Disable password recovery.
sensor(config-hos)# password-recovery disallowed
Disabling Password Recovery Using the IDM
To disable password recovery in the IDM, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Choose Configuration > Sensor Setup > Network. The Network pane appears.
Step 3 To disable password recovery, uncheck the Allow Password Recovery check box.
For More Information
•If you are not certain about whether password recovery is enabled or disabled, see Verifying the State of Password Recovery.
•For more information on reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.
Verifying the State of Password Recovery
Use the show settings | include password command to verify whether password recovery is enabled. To verify whether password recovery is enabled, follow these steps:
Step 1 Log in to the CLI.
Step 2 Enter service host submode.
sensor# configure terminal
sensor (config)# service host
Step 3 Verify the state of password recovery by using the include keyword to show settings in a filtered output.
sensor(config-hos)# show settings | include password
password-recovery: allowed <defaulted>
Troubleshooting Password Recovery
To troubleshoot password recovery, pay attention to the following:
•You cannot determine whether password recovery has been disabled in the sensor configuration from the ROMMON prompt, GRUB menu, switch CLI, or router CLI. If password recovery is attempted, it always appears to succeed. If it has been disabled, the password is not reset to cisco. The only option is to reimage the sensor.
•You can disable password recovery in the host configuration. For the platforms that use external mechanisms, such as the AIM IPS and the NME IPS bootloader, ROMMON, and the maintenance partition for the IDSM2, although you can run commands to clear the password, if password recovery is disabled in the IPS, the IPS detects that password recovery is not allowed and rejects the external request.
•To check the state of password recovery, use the show settings | include password command.
•When performing password recovery on the IDSM2, you see the following message: Upgrading will wipe out the contents on the storage media. You can ignore this message. Only the password is reset when you use the specified password recovery image.
For More Information
•For more information on reimaging sensors, refer to Upgrading, Downgrading, and Installing System Images.
•For the procedure for disabling password recovery, see Disabling Password Recovery.
•For the procedure for verifying the state of password recovery, see Verifying the State of Password Recovery.
Caveats
This section lists the resolved and known caveats, and contains the following topics:
•Resolved Caveats
•Known Caveats
Resolved Caveats
The following known issues have been resolved in the 7.0(1)E3 release:
•CSCsj40623—4260/4270 quad copper hw bypass has problems linking < 1000Mbps
•CSCsq51372—IPS:6.1.1 Iplogging out of file descriptors warning should be summarized
•CSCsu24412—Cisco.com update leaves open https connection
•CSCsu88701—correct checking for SigEventList NULL error message
•CSCsv49498—ASA loses connectivity with the SSM (IPS)
•CSCsv66660—sensorApp abort during database hashtree expire
•CSCsv75021—event-count and alert-interval does not work correctly
•CSCsv80568—Tuning sig 1610.0 locks up the SSM
•CSCsw14574—smbadvanced abort in processdecodedtcpmessage
•CSCsw25900—IPS has bad health and welfare stats after E3 upgrade
•CSCsx17909—sensor eventStore 10 Meg size too small
•CSCsx35823—Sig 1317 with Jumbo packet may cause sensorApp abort.
•CSCsx47618—4255 unresponsive when running specific stress test
•CSCsx48178—sensorApp abort when reconfiguring signatures.
•CSCsx50254—4260/4270 speed/duplex errors in main log
•CSCsy77167—auto purge (sigEdit/sigUpdate) does not return ununsed memory
•CSCsy88163—implement sensor self-purge for memory protection (off by default)
The following known IDM issues have been resolved in the 7.0(1)E3 release:
•CSCsw35201—IDM is not working with Java 6.0_11 yet
•CSCsu42407—The links inside the Details from IPS gadgets in ASDM do not work
The following known IME issues have been resolved in the 7.0(1)E3 release:
•CSCsu75677—Time stamps in IME e-mail notifications are incorrect
•CSCsv49788—IME shows fiber interfaces as up when you power down 4270
Known Caveats
The following known issues are found in Cisco IPS 7.0(1)E3:
•CSCse40651—Config operation on heavily loaded system may cause unresponsive system
•CSCse54528—Aurora - recover application-partition unfinished
•CSCse58463—Support tunnelled traffic with syn cookies
•CSCsg18379—MainApp unexpected behavior due to XML Parsing Error
•CSCsg26929—Interface errors when enabled in cli and ifconfig up
•CSCsg96871—AnalysisEngine InspectorServiceAICWeb::ToServiceInspect abort
•CSCsh16294—IPSVIRTUALIZATION:Physical Interface info not passed to ASA/SSM Database
•CSCsh45936—Leading Space in the uri-regex in Service-HTTP Works Ambiguously
•CSCsh50760—NAC causes high mainApp usage
•CSCsh89833—Delete event variable referenced by filter or sig from IDM
•CSCsi21029—"GRE tunnels blocked by sensorApp inspection defect"
•CSCsi60530—69xx firing but reporting wrong interface
•CSCsi73502—6.0(2)E1: No warning message when removing sensor used by ASA
•CSCsj00429—Risk Rating as odd values for STring.tcp sigs
•CSCsj35723—Sigs not alarming after default service sig sig0
•CSCsj57474—Frag traffic with dot1q headers misses a few sweep and atomic-ip sigs
•CSCsj70643—Normalizer signatures not modifying-packet-inline
•CSCsj82458—global-block-timeout allows values outside supported range
•CSCsl66235—Setup errors after defaulting sensor config via IDM
•CSCsl69776—AD is not generating an alert for every worm attacker
•CSCsl75224—cli command no mars-category causes sensor connection closed
•CSCsm37654—Signature 1220.0 does not alarm
•CSCsm37826—Signature 1300 does not always alarm on a 4260
•CSCsm37943—Tcp Timeout Sigs do not produce alarms in promic
•CSCsm44644—Signature 1303 false negative
•CSCsm46158—Critical memory condition can cause race condition
•CSCsm47102—Signature 1308 does not function
•CSCso15962—"show interface clear" does not clear Management interface counters
•CSCso60709—Flood net Engine Sigs 69xx are not firing in promiscuous mode
•CSCso74628—AIM and NME underperforming in promiscuous mode
•CSCso98858—config change with bypass off triggers ASA failover
•CSCsq18457—Unauthenticated Ntp settings lost after recover application-partition
•CSCsq53214—IPS reports different sig version in CT and CLI
•CSCsr02826—Missed Packet statistic does not work on AIM/NME
•CSCsr72489—IPSv5 SIG:5588-1 ENGINE:service-smb-advanced S342 Signature Failure
•CSCsu80349—4270 10-gig interface errors in main.log when under stress
•CSCsu86596—Fixed UDP Engine does not properly handle start of packet ("^") in regex
•CSCsv01700—Analysis engine is down when Denied attackers are configured repeatedly
•CSCsv07624—Engine service pack installs on a sensor of equal maj.min(sp) level
•CSCsv26568—IPS SNMP InterfaceGroup OID does not show correct Virtual Sensor
•CSCsv56782—sensorApp terminates while deleting database nodes
•CSCsw31368—SensorApp fails to shutdown during Engine Update
•CSCsw41042—IPS Signature 7428-0 modified to increase fidelity.
•CSCsw53162—Performance drop on 4270 inline with .41 build
•CSCsx20458—Sig 1300.0 firing incorrectly
•CSCsx21487—IPS: Sensor Becomes Unresponsive to Remote Monitoring
•CSCsx38213—EICAR Signature misses packet when sensor is under load
•CSCsx40862—Alert not generated for diff attacker & target addr for filter testcases
•CSCsx54168—TCP SYN Flood Cookie protection not inhibiting flood to victim in IPv6
•CSCsx62373—Cid/E errSystemError - Application "AnalysisEngine "terminated premature
•CSCsx66883—CSM package for 6.1.2 has decripancy in interface typedef
•CSCsx70656—Occasional latency event or disrupted traffic flow on inline sensor.
•CSCsx71481—Add note to analysis engine stats about histogram being cleared
•CSCsy18476—sensor allows creation of custom atomic ipv6 signature
•CSCsy21269—Alerts should not contain reputation fields for unmatched ip addresses
•CSCsy29684—IPS 6.1.2E3: sensorApp terminates unexpectedly in UpdateTime
•CSCsy41498—Health Status for GC always green if GC-inspection off or old DB exist
•CSCsy44884—mainapp aborts while retreiving ntp config in 6.1
•CSCsy46895—IPS 6.0 SensorApp crash
•CSCsy47529—IPS: EnetStub Producer Causes Core in sensorApp
•CSCsy74853—Engine Flood.Host Source Ports Bug
•CSCsy96323—Alarm Context data is not complete in E3
•CSCsz01229—Multistring Engine False Negative
•CSCsz11870—IPS 6.2.1E3 signature 4002 UDP host flood stopped firing
•CSCsz12949—sensorApp stop/restart results in not using reputation data
•CSCsz19556—7280.0 does not reliably alert
•CSCsz19631—Error: execUpgradeSoftware : The current version is a QA version
•CSCsz39460—Improve error messages for global correlation DNS failure
The following known issues are found in Cisco IPS 7.0(1)E3 IDM:
•CSCso96654—Editing EventActionRules removes all like Sig Actions
•CSCsq89977—IDM unable to edit multistring sig regex list entry
•CSCsr82134—IDM is allowing user to delete Risk Category that is in use
•CSCsu08058—Signatures Restore Default makes no changes if modified
•CSCsu21774—Better handling needed for Signature editing
•CSCsu47761—creating advanced atomic sig. results in blank main screen
•CSCsv02875—IDM problems after tuning sig to have atomic-ip-advanced engine
•CSCsv83687—IDM SSM startup wizard does not assign interface to virtual sensor
•CSCsx42999—IDM/Unable to sort Signature by "Action"
•CSCsy52817—IDM index.html has broken image file on IE 7
The following known issues are found in Cisco IPS 7.0(1)E3 IME:
•CSCsq38696—Unable to create Inline Vlan Pair using Startup Wizard
•CSCsq40627—IME ver 6.1.1 the RSS feed fails to display
•CSCsq50814—IME needs a refresh option for unsupported platforms
•CSCsq66078—IME not purging user permissions when device is deleted
•CSCsr02064—E-mail configuration missing from IME Help
•CSCsr18447—IME: During session teardown with sensor, IME improperly sends TCP RST
•CSCsr38568—Filters for Signatures not resetting
•CSCsu78195—Importing event data results in table full
•CSCsu90943—Change name Event Time to Local time for Event Details
•CSCsu90970—E-mail for Events is sending times with local time offset added
•CSCsx01428—EPS not being displayed for SSC-5
•CSCsx01435—Top services not being created for SSC-5
•CSCsx79397—IME allows combination of IPV4 and IPV6 address in deny attacker line
•CSCsy72188—JavaSocketExceptions seen in console for all Help screens
•CSCsz04668—IME fails in PooledExecutor: An error occured loading the configuration
Related Documentation
For more information on Cisco IPS, refer to the following documentation found at this URL:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html
•Documentation Roadmap for Cisco Intrusion Prevention System
•Cisco Intrusion Prevention System Device Manager Configuration Guide
•Cisco Intrusion Prevention System Manager Express Configuration Guide
•Cisco Intrusion Prevention System Command Reference
•Cisco Intrusion Prevention System Sensor CLI Configuration Guide
•Cisco Intrusion Prevention System Appliance and Module Installation Guide
•Installling and Removing Interface Cards in Cisco IPS-4260 and IPS 4270-20
•Regulatory Compliance and Safety Information for the Cisco Intrusion Detection and Prevention System 4200 Series Appliance Sensor
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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. (1110R)
Copyright © 2009-2013 Cisco Systems, Inc. All rights reserved.
Feedback