Release Notes for Cisco Intrusion Prevention System 7.2(2)E4
Available Languages
Table of Contents
Release Notes for Cisco Intrusion Prevention System 7.2(2)E4
IPS Management and Event Viewers
AC Power Supply in the IPS 4300 Series V01 and V02 Chassis
Applying IPS 7.2(2)E4 to Sensors Using CSM
Installing the IPS 4300 Series System Image
Installing the IPS 4500 Series System Image
Installing the ASA 5500-X IPS SSP Series System Image
Installing the ASA 5585-X IPS SSP Series System Image
Licensing the ASA 5500-X IPS SSP
Advanced Setup for the IPS Appliance
Advanced Setup for the ASA 5500-X IPS SSP
Advanced Setup for the ASA 5585-X IPS SSP
Installing or Upgrading the IME
Cisco Security Intelligence Operations
Obtaining Documentation, Using the Cisco Bug Search Tool, and Submitting a Service Request
Release Notes for Cisco Intrusion Prevention System 7.2(2)E4
Contents
- IPS File List
- Supported Platforms
- Supported Servers
- ROMMON and TFTP
- IPS Management and Event Viewers
- New and Changed Information
- AC Power Supply in the IPS 4300 Series V01 and V02 Chassis
- Obtaining Software
- Upgrading to IPS 7.2(2)E4
- Applying IPS 7.2(2)E4 to Sensors Using CSM
- Reimaging the Sensor
- Licensing the Sensor
- Initializing the Sensor
- Logging In to the IDM
- Installing or Upgrading the IME
- Cisco Security Intelligence Operations
- Restrictions and Limitations
- Caveats
IPS File List
Note Use the 4520 files to update the IPS 4520-XL.
The following files are part of Cisco IPS 7.2(2)E4:
–
IPS-SSP_5512-K9-7.2-2-E4.pkg
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
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.
IPS Management and Event Viewers
Use the following tools for configuring Cisco IPS 7.2(2)E4 sensors:
IDM 7.2.2 is included within the IPS 7.2(2)E4 files.
IDM 7.2.2 is included within IME 7.2.6.
IDM 7.2.2 requires JRE 1.6 or later.
You can use IDM 7.2.2 to configure IPS 7.2(2) sensors.
You can use IME 7.2.6 to configure IPS 6.1, 6.2, 7.0, 7.1, 7.2, and 7.3 sensors.
Use the following tools for monitoring Cisco IPS 7.2(2)E4 sensors:
You can use CSM 4.5 SP1 to manage the following IPS sensors:
Note You may need to configure viewers that are already configured to monitor the earlier version sensors to accept a new SSL certificate for the Cisco IPS 7.2 sensors.
For the procedure to apply IPS 7.2(2)E4 to sensors using CSM 4.5 SP1 or later, see Applying IPS 7.2(2)E4 to Sensors Using CSM.
New and Changed Information
Cisco IPS 7.2(2)E4 contains the following new and changed information:
Note We recommend that you configure SNMPv3 users with security levels that require authentication, such as authPriv and authNoPriv, with authPriv being the most highly recommended. Configuring SNMPv3 users with the noAuthNoPriv security level is NOT recommended.
- Slashes are NOT valid for hostnames, for example, firewall5/ips.
- Improved management for SDEE subscriptions
- Serviceability enhancements related to core files
- During password recovery, the password/privilege level of the default account is set back to the default values of cisco/administrator.
- Continuing support for the IPS 4300 series, IPS 4500 series, ASA 5585-X IPS SSP series, and ASA 5500-X IPS SSP series sensors
- For detailed information about SNMPv3 and how to configure it, for the IDM and IME, refer to Configuring SNMP , and for the CLI refer to Configuring SNMP .
- For information about SDEE subscription, for the IDM and IME refer to Displaying SDEE Subscriptions and for the CLI refer to Displaying SDEE Subscriptions .
AC Power Supply in the IPS 4300 Series V01 and V02 Chassis
The Cisco IPS 4300 series sensors with the AC power supply can restore the previous power state of the system if AC power is lost. Earlier IPS 4300s (V01) require you to turn on the power with the power switch. Newer IPS 4300s (V02) automatically turn on when you plug in the power cable.
To determine your version, do one of the following:
• At the CLI, enter the show inventory command and look for V01 or V02 in the output.
The V01 chassis has the following limitations (these limitations do not apply to the V02 chassis):
- The sensor requires 50 seconds from the time that AC power is applied before the power state can be updated and stored. This means that any changes to the power state within the first 50 seconds of applying AC power will not be observed if AC power is removed within that time.
- The sensor requires 10 seconds from the time it is placed into standby mode before the power state can be updated and stored. This means any changes to the power state within the first 10 seconds of entering standby mode (including the standby mode itself) will not be observed if AC power is removed within that time.
For information on the AC power supplies in the IPS 4300 series sensors, refer to Installing the IPS 4300 Series Sensors .
Obtaining Software
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 in a release train format, a new release every three months. Major and minor updates are also posted periodically. Check Cisco.com regularly for the latest IPS software.
You must have an account with cryptographic access before you can download software. You set this account up the first time you download IPS software from the Download Software site.
Note You must be logged in to Cisco.com to download software. You must have an active IPS maintenance contract and a Cisco.com password to download software. You must have a sensor license to apply signature updates.
Downloading Cisco IPS Software
To download software on Cisco.com, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note You must have an IPS subscription service license to download software.
Step 7
Step 8
Step 9
Step 10
a.
b.
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.
Step 11
Step 12
Upgrading to IPS 7.2(2)E4
This section describes how to upgrade the IPS 4300 series, IPS 4500 series, ASA 5500-X IPS SSP series, and ASA 5585-X IPS SSP series sensors, and contains the following topics:
Upgrade Notes and Caveats
Pay attention to the following upgrade notes and caveats when upgrading to IPS 7.2(2)E4:
–
–
If you have SNMPv3 configured in 7.2(2)E4 and you try to upgrade to 7.3(1)E4, which does not support SNMPv3, you receive the following error message and does not allow you to enter service notification configuration mode:
–
- If the client does not support SSHv2 or if SSHv2 is disabled, the management connectivity will be lost after upgrading to IPS 7.2(2)E4 because SSHv1 is disabled by default in IPS 7.2(2)E4.
- If the management application does not support TLS1.0 or higher, the management connectivity will be lost after upgrading to IPS 7.2(1) because IPS 7.2(1) does not support TLS versions before TLS1.0.
• You cannot upgrade to 7.2(2)E4 if the sensor license was generated for 6.0.x versions and earlier. The upgrade fails and the following message is displayed:
Error: execUpgradeSoftware : This license is a IPS version 6.0 or earlier license which is not compatible with platforms running 7.1.X IPS Versions. Please install a IPS version 6.1 or later license type. Refer to 7.2.X IPS version README or IPS documents for the details of generating a new license.
Note For IPS 7.2(1)E4, while executing an immediate upgrade, you cannot use the IDM, IME, or CLI, or start any new sessions until the upgrade is complete. For IPS 7.2(2)E4 and later, you can use the IDM, IME, and CLI immediately after you begin an automatic update because the automatic update is now executed as background process.
- The default value of the Cisco server IP address has been changed to www.cisco.com in the Auto Update URL configuration. If you have automatic update configured on your sensor, you may need to update firewall rules to allow the sensor to connect to this new address.
- Anomaly detection has been disabled by default. If you did not configure the operation mode manually before the upgrade, it defaults to inactive after you upgrade to IPS 7.2(2)E4. If you configured the operation mode to detect, learn, or inactive, the tuned value is preserved after the upgrade.
- You must have a valid maintenance contract per sensor to download software upgrades from Cisco.com.
- You must be running the following versions to upgrade the following platforms to IPS 7.2(2)E4:
–
–
–
- This service pack automatically reboots the sensor to apply the changes. During reboot, inline network traffic is disrupted.
- You cannot uninstall 7.2(2)E4. To revert to a previous version, you must reimage the sensor using the appropriate system image file
• For the procedure to download software from Cisco.com, see Obtaining Software.
- For the procedure for using the upgrade command to upgrade the sensor, see Upgrading the Sensor.
- For the procedure for installing the IPS 4300 series system images, see Installing the IPS 4300 Series System Image.
- For the procedure installing the IPS 4500 series system images, see Installing the IPS 4500 Series System Image.
- For the procedure for installing the ASA 5500-X IPS SSP series system image, see Installing the ASA 5500-X IPS SSP Series System Image.
- For the procedure for installing the ASA 5585-X IPS SSP series system image, see Installing the ASA 5585-X IPS SSP Series System Image.
Upgrading the Sensor
Use the upgrade source-url command to apply service pack, signature update, engine update, minor version, major version, or recovery partition file upgrades.
• source-url —Specifies the location of the source file to be copied:
–
ftp://[[username@]location][/relativeDirectory]/filename
ftp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password.
–
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://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file.
–
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.
To upgrade the sensor, follow these steps:
Step 1
Step 2
Step 3
The URL points to where the update file is located, for example, to retrieve the update using FTP, enter the following:
Step 5
Step 6
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.
Step 7
For a list of the specific IPS upgrade filenames, see IPS File List.
Applying IPS 7.2(2)E4 to Sensors Using CSM
Pay attention to the following when updating sensors using CSM:
- You can manage IPS 7.2(2)E4 sensors using CSM 4.4 SP2 and CSM 4.5 in backward-compatibility mode.
- We recommend that you upgrade to CSM 4.5 SP1 to manage sensors running IPS 7.2(2)E4.
- You must use CSM 4.5 to automatically or manually update to IPS 7.2(2)E4.
- Full support of IPS 7.2(2)E4 including SNMPv3 configuration management is available in CSM 4.6.
To apply 7.2(2)E4 to sensors using CSM, follow these steps:
Step 1
Step 2
Step 3
Step 5
Step 6
Step 7
Reimaging the Sensor
This section describes how to reimage the sensor using the system image, and contains the following topics:
- Installing the IPS 4300 Series System Image
- Installing the IPS 4500 Series System Image
- Installing the ASA 5500-X IPS SSP Series System Image
- Installing the ASA 5585-X IPS SSP Series System Image
Installing the IPS 4300 Series System Image
You can install the IPS 4345 and IPS 4360 system image by using the ROMMON on the appliance to TFTP the system image on to the compact flash device.
Note This procedure is for IPS 4345, but is also applicable to IPS 4360. The system image for IPS 4360 has “4360” in the filename.
To install the IPS 4345 and IPS 4360 system image, follow these steps:
Step 1
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your IPS 4345.
Step 3
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The
rommon>prompt appears.Step 4
The variables have the following definitions:
- Address—Local IP address of the IPS 4345.
- Server—TFTP server IP address where the application image is stored.
- Gateway—Gateway IP address used by the IPS 4345.
- Port—Ethernet interface used for the IPS 4345 management.
- VLAN—VLAN ID number (leave as untagged).
- Image—System image file/path name.
- Config—Unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5
Note The default interface used for TFTP downloads is Management 0/0, which corresponds to the MGMT interface of the IPS 4345.
Step 6
Note Use the same IP address that is assigned to the IPS 4345.
Step 7
Step 8
Step 9
Step 10
Caution Make sure that you enter the IMAGE command in all uppercase. You can enter the other ROMMON commands in either lower case or upper case, but the IMAGE command specifically must be all uppercase.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 11
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 12
Caution To avoid corrupting the system image, do not remove power from the IPS 4345 while the system image is being installed.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4345. Be sure to use the IPS 4345 image.
- For the procedure for locating software, see Obtaining Software.
- For a list of supported TFTP servers, see Supported Servers.
• For a list of the specific IPS software files, see IPS File List.
- For the procedure for initializing the sensor with the setup command, see Initializing the Sensor.
Installing the IPS 4500 Series System Image
You can install the IPS 4510, IPS 4520, and 4250-XL system image by using the ROMMON on the appliance to TFTP the system image onto the compact flash device.
Note The following procedure references the IPS 4510 but it also refers to the IPS 4520 and IPS 4520-XL. Use the 4520 files to upgrade the IPS 4520-XL.
To install the IPS 4510 system image, follow these steps:
Step 1
Note Make sure you can access the TFTP server location from the network connected to the Management port of your IPS 4510.
Step 3
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The
rommon>prompt appears.Step 4
The variables have the following definitions:
- Address—Specifies the local IP address of the IPS 4510.
- Server—Specifies the TFTP server IP address where the application image is stored.
- Gateway—Specifies the gateway IP address used by the IPS 4510.
- Port—Specifies the Ethernet interface used for IPS 4510 management.
- VLAN—Specifies the VLAN ID number (leave as untagged).
- Image—Specifies the system image file/path name.
- Config—Unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5
Note Use the same IP address that is assigned to the IPS 4510.
Step 6
Step 7
Step 8
Step 9
Note The path is relative to the UNIX TFTP server default tftpboot directory. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 10
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 11
Caution To avoid corrupting the system image, do not remove power from the IPS 4510 while the system image is being installed.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4510. Be sure to use the IPS 4510 image.
- For the procedure for locating software, see Obtaining Software.
- For a list of supported TFTP servers, see Supported Servers.
- For a list of the specific IPS software files, see IPS File List.
- For the procedure for initializing the sensor with the setup command, see Initializing the Sensor.
Installing the ASA 5500-X IPS SSP Series System Image
Note Be sure the TFTP server that you specify can transfer files up to 60 MB in size.
To install the system image on the ASA 5500-X IPS SSP, follow these steps:
Step 1
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of the adaptive security appliance.
Step 2
Step 4
Step 5
Step 6
Step 7
Note The Status field in the output indicates the operational status of the ASA 5500-X IPS SSP. An ASA 5500-X IPS SSP operating normally shows a status of “Up.” While the adaptive security appliance transfers an application image to the ASA 5500-X IPS SSP, the Status field in the output reads “Recover.” When the adaptive security appliance completes the image transfer and restarts the ASA 5500-X IPS SSP, the newly transferred image is running.
Note To debug any errors that may happen in the recovery process, use the debug module-boot command to enable debugging of the system reimaging process.
Step 8
- For the procedure for locating software, see Obtaining Software.
- For a list of supported TFTP servers, see Supported Servers.
- For a list of the specific IPS software files, see IPS File List.
- For the procedure for initializing the sensor with the setup command, see Initializing the Sensor.
Installing the ASA 5585-X IPS SSP Series System Image
This section describes how to install the ASA 5585-X IPS SSP series system image using the hw-module command or ROMMON, and contains the following topics:
Using the hw-module Command
To install the system image, transfer the software image from a TFTP server to the ASA 5585-X IPS SSP using the adaptive security appliance CLI. The adaptive security appliance can communicate with the ROMMON application of the ASA 5585-X IPS SSP to transfer the image.
Note Be sure the TFTP server that you specify can transfer files up to 60 MB in size.
Note This process can take approximately 15 minutes to complete, depending on your network and the size of the image.
To install the ASA 5585-X IPS SSP software image, follow these steps:
Step 1
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your adaptive security appliance.
Step 2
Step 4
Note If you make an error in the recovery configuration, use the hw-module module 1 recover stop command to stop the system reimaging and then you can correct the configuration.
Step 5
Step 6
Note The port IP address is the management IP address of the ASA 5585-X IPS SSP.
Step 7
Step 8
Step 9
Step 10
Note The status reads
Recoveryduring recovery and readsUpwhen installation is complete.
Note The Status field in the output indicates the operational status of the ASA 5585-X IPS SSP. An ASA 5585-X IPS SSP operating normally shows a status of “Up.” While the adaptive security appliance transfers the software image to the ASA 5585-X IPS SSP, the Status field in the output reads “Recover.” When the adaptive security appliance completes the software image transfer and restarts the ASA 5585-X IPS SSP, the newly transferred image is running.
Note To debug any errors that may happen during this process, use the debug module-boot command to enable debugging of the software installation process.
Step 11
Step 12
Step 13
- For the procedure for locating software, see Obtaining Software.
- For a list of supported TFTP servers, see Supported Servers.
• For a list of the specific IPS software files, see IPS File List.
- For the procedure for initializing the sensor with the setup command, see Initializing the Sensor.
Using ROMMON
You can install the ASA 5585-X IPS SSP system image by using the ROMMON on the adaptive security appliance to TFTP the system image onto the ASA 5585-X IPS SSP.
To install the ASA 5585-X IPS SSP system image, follow these steps:
Step 1
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your adaptive security appliance.
Step 2
Com KbdBuf SMM UsbHid Msg0 Prompt Pmrt Cache1 LowM ExtM HugeM Cache2 Flg Siz0 Amrt PMM PnpDsp Smbios Lpt0 Npx1 Apm Lp1 Acpi Typ Dbg Enb Mp MemReduce MemSync1 CallRoms MemSync2 DriveInitStep 3
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The
rommon>prompt appears.Step 4
The variables have the following definitions:
- Address—Specifies the local IP address of the ASA 5585-X IPS SSP.
- Server—Specifies the TFTP server IP address where the application image is stored.
- Gateway—Specifies the gateway IP address used by the ASA 5585-X IPS SSP.
- Port—Specifies the Ethernet interface used for the ASA 5585-X IPS SSP management.
- VLAN—Specifies the VLAN ID number (leave as untagged).
- Image—Specifies the system image file/path name.
- Config—Specifies the unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5
Note The default interface used for TFTP downloads is Management 0/0, which corresponds to the management interface of the ASA 5585-X IPS SSP.
Step 6
Note Use the same IP address that is assigned to the ASA 5585-X IPS SSP.
Step 7
Step 8
Step 9
Step 10
Caution Make sure that you enter the IMAGE command in all uppercase. You can enter the other ROMMON commands in either lower case or upper case, but the IMAGE command specifically must be all uppercase.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 11
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 12
Note If the network settings are correct, the system downloads and boots the specified image on the ASA 5585-X IPS SSP. Be sure to use the ASA 5585-X IPS SSP image.
Caution To avoid corrupting the system image, do not remove power from the ASA 5585-X IPS SSP while the system image is being installed.
- For the procedure for locating software, see Obtaining Software.
- For a list of supported TFTP servers, see Supported Servers.
• For a list of the specific IPS software files, see IPS File List.
- For the procedure for initializing the sensor with the setup command, see Initializing the Sensor.
Licensing the Sensor
You can install the license key through the CLI, IDM, or IME. This section describes how to obtain and install the license key, and contains the following topics:
Using the IDM or 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
Step 2
Step 3
Step 4
- 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 5.
- 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 5
Step 7
Step 8
Step 9
Caution You must have the correct IPS device serial number and product identifier (PID) because the license key only functions on the device with that number.
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
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.
• 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://[[username@]location][/relativeDirectory]/filename
ftp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password.
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://[[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.
To install the license key, follow these steps:
Step 1
Step 2
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 3
Note You must have the correct IPS device serial number and product identifier (PID) because the license key only functions on the device with that number.
Step 4
Step 5
Step 6
Step 7
Licensing the ASA 5500-X IPS SSP
For the ASA 5500-X series adaptive security appliances with the IPS SSP, the ASA requires the IPS Module license. To view your current ASA licenses, in ASDM choose Home > Device Dashboard > Device Information > Device License . For more information about ASA licenses, refer to the licensing chapter in the configuration guide. After you obtain the ASA IPS Module license, you can obtain and install the IPS license key.
- For more information about getting started using the ASA 5500-X IPS SSP, refer to the Cisco IPS Module on the ASA Quick Start Guide .
- For the procedures for obtaining and installing the IPS License key, see Licensing the Sensor.
Initializing the Sensor
This section describes how to initialize the sensor using the setup command, and contains the following sections:
- Understanding Initialization
- Simplified Setup Mode
- System Configuration Dialog
- Basic Sensor Setup
- Advanced Setup for the IPS Appliance
- Advanced Setup for the ASA 5500-X IPS SSP
- Advanced Setup for the ASA 5585-X IPS SSP
- Verifying Initialization
Understanding Initialization
Note You must be administrator to use the setup command.
After you install the sensor on your network, you must use the setup command to initialize it so that you can communicate with it over the network. You cannot use the IDM or the IME to configure the sensor until you initialize the sensor using the setup command.
With the setup command, you configure basic sensor settings, including the hostname, IP interfaces, access control lists, global correlation servers, and time settings. You can continue using advanced setup in the CLI to enable Telnet, configure the web server, and assign and enable virtual sensors and interfaces, or you can use the Startup Wizard in the IDM or the IME. After you configure the sensor with the setup command, you can change the network settings in the IDM or the IME.
Caution You must have a valid sensor license for global correlation features to function. You can still configure and display statistics for the global correlation features, but the global correlation databases are cleared and no updates are attempted. Once you install a valid license, the global correlation features are reactivated.
Simplified Setup Mode
The sensor automatically calls the setup command when you connect to the sensor using a console cable and the sensor basic network settings have not yet been configured. The sensor does not call automatic setup under the following conditions:
- When initialization has already been successfully completed.
- If you have recovered or downgraded the sensor.
- If you have set the host configuration to default after successfully configuring the sensor using automatic setup.
When you enter the setup command, an interactive dialog called the System Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you through the configuration process. The values shown in brackets next to each prompt are the default values last set.
System Configuration Dialog
When you enter the setup command, an interactive dialog called the System Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you through the configuration process. The values shown in brackets next to each prompt are the current values.
You must go through the entire System Configuration Dialog until you come to the option that you want to change. To accept default settings for items that you do not want to change, press Enter .
To return to the EXEC prompt without making changes and without going through the entire System Configuration Dialog, press Ctrl-C . The System Configuration Dialog also provides help text for each prompt. To access the help text, enter ? at a prompt.
When you complete your changes, the System Configuration Dialog shows you the configuration that you created during the setup session. It also asks you if you want to use this configuration. If you enter yes , the configuration is saved. If you enter no , the configuration is not saved and the process begins again. There is no default for this prompt; you must enter either yes or no .
You can configure daylight savings time either in recurring mode or date mode. If you choose recurring mode, the start and end days are based on week, day, month, and time. If you choose date mode, the start and end days are based on month, day, year, and time. Choosing disable turns off daylight savings time.
Note You only need to set the date and time in the System Configuration Dialog if the system is an appliance and is NOT using NTP.
Note The System Configuration Dialog is an interactive dialog. The default settings are displayed.
Example 1 Sample Configuration Dialog
Example 1 shows a sample System Configuration Dialog.
Participation in the SensorBase Network allows Cisco to collect aggregated statistics about traffic sent to your IPS.If you agree to participate in the SensorBase Network, Cisco will collect aggregated statistics about traffic sent to your IPS.This includes summary data on the Cisco IPS network traffic properties and how this traffic was handled by the Cisco appliances. We do not collect the data content of traffic or other sensitive business or personal information. All data is aggregated and sent via secure HTTP to the Cisco SensorBase Network servers in periodic intervals. All data shared with Cisco will be anonymous and treated as strictly confidential.Basic Sensor Setup
To perform basic sensor setup using the setup command, follow these steps:
Step 1
Note Both the default username and password are cisco.
Step 2
Step 3
Step 4
Step 5
Step 6
a.
b.
Note For example, 10.0.0.0/8 permits all IP addresses on the 10.0.0.0 network (10.0.0.0-10.255.255.255) and 10.1.1.0/24 permits only the IP addresses on the 10.1.1.0 subnet (10.1.1.0-10.1.1.255). If you want to permit access to a single IP address than the entire network, use a 32-bit netmask. For example, 10.1.1.1/32 permits just the 10.1.1.1 address.
c.
Step 7
a.
b.
Caution You must have a valid sensor license for global correlation features to function. You can still configure and display statistics for the global correlation features, but the global correlation databases are cleared and no updates are attempted. Once you install a valid license, the global correlation features are reactivated.
Step 8
a.
Note Summertime is also known as DST. If your location does not use Summertime, go to Step m.
b.
c.
d.
e.
f.
Note The default recurring summertime parameters are correct for time zones in the United States. The default values specify a start time of 2:00 a.m. on the second Sunday in March, and a stop time of 2:00 a.m. on the first Sunday in November. The default summertime offset is 60 minutes.
g.
h.
i.
j.
k.
l.
m.
n.
o.
p.
Step 9
- Off—No data is contributed to the SensorBase Network.
- Partial—Data is contributed to the SensorBase Network, but data considered potentially sensitive is filtered out and never sent.
- Full—All data is contributed to the SensorBase Network except the attacker/victim IP addresses that you exclude.
The SensorBase Network Participation disclaimer appears. It explains what is involved in participating in the SensorBase Network.
Step 10
Step 11
Step 12
Advanced Setup for the IPS Appliance
Note The currently supported Cisco IPS appliances are the IPS 4300 series and the IPS 4500 series.
Note Adding new subinterfaces is a two-step process. You first organize the interfaces when you edit the virtual sensor configuration. You then choose which interfaces and subinterfaces are assigned to which virtual sensors.
To continue with advanced setup for the appliance, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note If 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 following format:
https://appliance_ip_address:port(for example,https://10.1.9.201:1040).
Note The web server is configured to use TLS/SSL encryption by default. Setting the port to 80 does not disable the encryption.
Step 7
Step 8
Note The following options let you create and delete interfaces. You assign the interfaces to virtual sensors in the virtual sensor configuration. If you are using promiscuous mode for your interfaces and are not subdividing them by VLAN, no additional configuration is necessary.
Step 9
Step 10
Step 11
Step 12
Step 13
Note Entering a carriage return at a prompt without a value returns you to the previous menu.
Note At this point, you can configure another interface, for example, GigabitEthernet 0/1, for inline VLAN pair.
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Step 25
Note The sensor comes with a built-in override to add the deny packet event action to high risk rating alerts. If you do not want this protection, disable automatic threat prevention.
Virtual sensor newVs is configured to prevent high risk threats in inline mode. (Risk Rating 90-100)Step 26
Step 27
Step 28
Step 30
Step 31
Advanced Setup for the ASA 5500-X IPS SSP
To continue with advanced setup for the ASA 5500-X IPS SSP, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note If you change the web server port, you must specify the port in the URL address of your browser when you connect to the IDM. Use the following format:
https://ips_ssp_ip_address:port(for example,https://10.1.9.201:1040).
Note The web server is configured to use TLS/SSL encryption by default. Setting the port to 80 does not disable the encryption.
Step 7
Step 8
Note You do not need to configure interfaces on the ASA 5500-X IPS SSP. You should ignore the modify interface default VLAN setting. The separation of traffic across virtual sensors is configured differently for the ASA 5500-X IPS SSP than for other sensors.
Step 9
Step 10
Step 11
Step 12
Note Multiple virtual sensors are supported. The adaptive security appliance can direct packets to specific virtual sensors or can send packets to be monitored by a default virtual sensor. The default virtual sensor is the virtual sensor to which you assign PortChannel 0/0. We recommend that you assign PortChannel 0/0 to vs0, but you can assign it to another virtual sensor if you want to.
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Note If PortChannel 0/0 has not been assigned to vs0, you are prompted to assign it to the new virtual sensor.
Step 20
Step 21
Note The sensor comes with a built-in override to add the deny packet event action to high risk rating alerts. If you do not want this protection, disable automatic threat prevention.
Virtual sensor newVs is configured to prevent high risk threats in inline mode. (Risk Rating 90-100)Step 22
Step 23
Step 24
Step 25
Step 26
Step 27
Step 28
Advanced Setup for the ASA 5585-X IPS SSP
To continue with advanced setup for the ASA 5585-X IPS SSP, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note If you change the web server port, you must specify the port in the URL address of your browser when you connect to IDM. Use the following format:
https://ips_ssp_ip_address:port(for example,https://10.1.9.201:1040).
Note The web server is configured to use TLS/SSL encryption by default. Setting the port to 80 does not disable the encryption.
Step 7
Step 8
Note You do not need to configure interfaces on the ASA 5585-X IPS SSP. You should ignore the modify interface default VLAN setting. The separation of traffic across virtual sensors is configured differently for the ASA 5585-X IPS SSP than for other sensors.
Step 9
Step 10
Step 11
Step 12
Note Multiple virtual sensors are supported. The adaptive security appliance can direct packets to specific virtual sensors or can send packets to be monitored by a default virtual sensor. The default virtual sensor is the virtual sensor to which you assign PortChannel 0/0. We recommend that you assign PortChannel 0/0 to vs0, but you can assign it to another virtual sensor if you want to.
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Note If PortChannel 0/0 has not been assigned to vs0, you are prompted to assign it to the new virtual sensor.
Step 20
Step 21
Note The sensor comes with a built-in override to add the deny packet event action to high risk rating alerts. If you do not want this protection, disable automatic threat prevention.
Virtual sensor newVs is configured to prevent high risk threats in inline mode. (Risk Rating 90-100)Step 22
Step 23
Step 24
Step 25
Step 26
Step 27
Step 28
Verifying Initialization
Note The following show configuration output is an example of what your configuration may look like. It will not match exactly because of the optional setup choices.
To verify that you initialized your sensor, follow these steps:
Step 1
Step 2
Note You can also use the more current-config command to view your configuration.
Step 3
Step 4
Logging In to the IDM
The IDM is a web-based, Java Web Start application that enables you to configure and manage your sensor. The web server for the IDM resides on the sensor. You can access it through Internet Explorer or Firefox web browsers.
Note The IDM is already installed on the sensor.
To log in to the IDM, follow these steps:
Step 1
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://192.0.2.1:1040).
Step 2
Step 3
Step 4
Step 5
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
The main window of the IDM appears.
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 window. After you launch the IDM, it is not necessary for this window to remain open.
Installing or Upgrading the IME
This section describes how to install and upgrade the IME, and how to migrate data from IEV or a previous version of 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.
The 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.
Installation Notes and Caveats
Note If you are using Windows 7 or Windows Server 2008, and an IME version earlier than 7.1.1, uninstall IME before upgrading it. Otherwise, just upgrade from your current IME version.
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
Step 2
Step 3
Step 4
Step 5
Note The first time you start the IME, you are prompted to set up a password.
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
Step 2
Step 3
Importing IEV Event Data In to IME
To import event data in to the IME, follow these steps:
Step 1
Step 2
For more information about the IME, refer to Cisco Intrusion Prevention System Manager Express Installation Guide for IPS 7.2 .
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:
Restrictions and Limitations
The following restrictions and limitations apply to Cisco IPS 7.2(2)E4 software and the products that run it:
• IME 7.2.6 is the only supported IME release for IPS 7.2(2)E4.
• After upgrading to 7.2(2)E4, you cannot automatically update the sensor to IPS 7.3(1) E4 using the CLI, IDM, or IME, because SNMPv3 support is not available in IPS 7.3(1)E4. You can however, manually update to 7.3(1)E4 using the CLI, which warns you that the SNMP configuration will be removed from the sensor.
- For IPS 7.2(1)E4, while executing an immediate upgrade, you cannot use the IDM, IME, or CLI, or start any new sessions until the upgrade is complete. For IPS 7.2(2)E4 and later, you can use the IDM, IME, and CLI immediately after you begin an automatic update because the automatic update is now executed as background process.
- If a client connecting to a sensor that is using SSH does not support SSHv2, or if SSHv2 is disabled, the management connectivity is lost after upgrading to IPS 7.2(2)E4 from any 7.1(x) version because SSHv1 is disabled by default in IPS 7.2(2)E4.
- IPS 7.2(2)E4 supports TLS 1.0 and later. If the peer uses an older SSL version, the connection cannot be established.
- To support the immediate automatic update feature, a default update schedule with a start time of 00:00:00 and interval of 24 hours has been set. You must enable the automatic update settings before issuing an immediate automatic update. Disable the automatic update schedule if you do not want to use the default scheduled update.
- The dual module configuration is available only for the IPS 4520. You can install another IPS 4520 module in an existing 4520 or you can order the IPS 4520-XL, which has the two-module configuration.
- The ASA 5512-X IPS SSP and the ASA 5515-X IPS SSP do not support the Regex accelerator card and the String XL engines.
- Applying any signature template erases any existing tunings associated with the targeted signature definition file. The ASA 5512-X IPS SSP and ASA 5515-X IPS SSP do not support signature templates (signature threat profiles).
- The ASA 5512-X IPS SSP and ASA 5515-X IPS SSP do not support HTTP advanced decoding.
- Enabling HTTP advanced decoding can have a significantly negative performance and memory impact on the sensor.
- Use the show statistics virtual-sensor | include load command (CLI) or look at the statistics for the virtual sensor at Configuration > Sensor Monitoring > Support Information > Statistics (IDM/IME) to determine the load value over a longer period of time. The show statistics analysis-engine command (CLI) and the statistics for the Analysis Engine show values over a shorter period of time. If you compare the output, the values will appear to be inconsistent due to the different time periods. To get an accurate comparison between them, compare the processing load percentage from the statistics for the virtual sensor and the one-minute averaged value from the statistics for the Analysis Engine.
- TACACS+ authentication is not supported in IPS 7.2(2)E4.
- The CLI timeout feature is applicable only for sessions established through SSH, Telnet, and the console. Service account logins are not affected.
- 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.
- Global correlation does not support IPv6.
- There is no support for IPv6 on the management (command and control) interface.
- 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.
- CSM does not support IPv6.
- 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.
- 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.
- 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 IDM, they are turned into something unrecognizable and you will not be able to delete or edit the resulting object through IDM or the CLI. This is true for any string that is used by the CLI as an identifier, for example, names of time periods, inspect maps, server and URL lists, and interfaces.
• When the SensorApp is reconfigured, there is a short period when the SensorApp is unable to respond to any queries. Wait a few minutes after reconfiguration is complete before querying the SensorApp for additional information.
- The IDM and 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.
Caveats
This section lists the resolved and unresolved caveats, and contains the following topics:
Resolved Caveats
The following known issues are resolved in IPS 7.2(2)E4:
- CSCul58230 ASA 5512-5555 Fails to Get IPS Module Unique Device Identifier
- CSCuh49784 4510 cannot be re-imaged if 'erase' command is run from rommon
- CSCuj02243 local scp update timeout will cause mainApp failure
- CSCuf82384 Data corruption in pipe during authentication request CT hangs mainApp
- CSCui25688 IPS crashes while generating TLS certificate with many HTTPS connections
- CSCui91266 Large fragmented packet causes verbose-alert action failure
- CSCug87980 HTTP-advanced-decoding causes sensorApp to fail for gzip encoding
- CSCub75688 sig update sensorApp abort in libhoard dlmalloc
- CSCuh36529 SSP-IPS drops packets on particular queues, possible ixgbe buffer leak
- CSCud20579 packet logging can trigger mainApp failure when monitored by MARS
- CSCud32612 IPS drops IPv6 packets with flowlabel set due to sig 1250/0
- CSCue39065 IPS Signature 31939/1 false positives
- CSCtq32936 IPS crashes if signature auto-update is enabled without the license
- CSCum12974 Invalid host-name characters including slash are allowed
- CSCtx17567 SNMP related port are open by default
- CSCty68417 Orphaned User Sessions When Adding Authorized Key With RADIUS Enabled
- CSCub77629 nac fails to handle the pager correctly for long login banners
- CSCue54325 cli-inactivity-timeout does not proactively end the cli session
- CSCuf47278 radius authentication fails if first byte of IP addr is greater than 127
- CSCug32267 Configuration Import Fails if Some Auto-Upgrade Information is Missing
- CSCug41013 IPS: RegexDepth Token Does Not Limit Hardware-accelerated Inspection
- CSCug54770 some sessions in Closing state have not set closing timeout
- CSCuh42051 IPS: \"http error response: 400\" - Default Auto/Cisco.com cisco-url Value
- CSCuh66943 if attemptLimit is reached, there is no way to reset the account
- CSCui05041 AutoUpdate Proxy Not Working
- CSCui54193 summary-key Axxb in sweep engine does not work
Related Documentation
Refer to the following URLs for related documentation:
- For a complete list of Cisco IPS 7.2 documentation and where to find it, refer to the documentation roadmap found at this URL:
http://www.cisco.com/en/US/docs/security/ips/7.2/roadmap/roadmap7_2.html
• For all IPS documentation, refer to this URL:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html
- For a complete list of the Cisco ASA 5500 series documentation and where to find it, refer to the documentation roadmap found at this URL:
http://www.cisco.com/en/US/docs/security/asa/roadmap/asaroadmap.html
Obtaining Documentation, Using the Cisco Bug Search Tool, 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)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)