This chapter covers the following subjects:
• Configuration choices, basic procedures, and required input parameters: Describes the difference between intrusion detection and intrusion prevention. It also covers the concept of signatures.
• Choosing an IPS sensor platform: Cisco provides many platforms through which you can deploy Cisco IOS intrusion prevention. The company’s hardware and software implementations are covered in this section.
• Deploying Cisco IOS Software IPS signature policies: Covers creating and deploying signature policies.
• Tuning Cisco IOS Software IPS signatures: Covers tuning IPS signatures to fit your network.
• Deploying Cisco IOS Software IPS signature updates: Learn how to update the signatures for your intrusion prevention system in this section.
• Monitoring Cisco IOS Software IPS events: Covers the different methods to monitor events from the intrusion prevention system.
• Troubleshooting Cisco IOS Software IPS sensor: In the event that you have problems with your intrusion prevention deployment, troubleshooting guidelines and procedures are provided in this section.
As the reliance on the Internet becomes more and more crucial to the success of businesses, the ability to secure and protect information assets becomes increasingly critical. Today’s environments must stave off several different types of compromises such as disclosing privacy information, corporate espionage, or denial of service attacks to name a few. Deploying a layered approach to security implementations is the best way to protect a network from attack. Having the ability to proactively monitor traffic as it traverses networks adds an important layer of security. Actively inspecting data that passes through stateful firewalls can detect malicious packets and reduce the risk of exposure for corporations. Intrusion detection and prevention systems are security tools that provide the ability to inspect data as traffic flows through firewalls on permitted ports. Intrusion prevention and detection both analyze traffic based on signature matching. The main difference is that intrusion prevention can proactively take action to prevent malicious traffic from entering your network. Intrusion detection requires manual intervention by network administrators to stop traffic after the intrusion detection system triggers an event.
This chapter covers the Cisco IOS intrusion prevention system (IPS). Upon completing this chapter, you will have an understanding of how to configure intrusion prevention on a Cisco IOS router, which includes enabling Cisco IPS, understanding and updating signatures, and monitoring events with either syslog or Security Device Event Exchange (SDEE).
The “Do I Know This Already?” quiz helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.
The eight-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.
Table 13-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.
Table 13-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.
1. What types of security controls are capable of monitoring traffic to detect problems in the network?
a. Intrusion prevention systems (IPS)
b. Protocol analyzers
c. Intrusion detection systems (IDS)
d. Security policy
2. What security controls are capable of monitoring traffic to detect and prevent problems in the network?
a. Intrusion detection systems (IDS)
b. Wireless sniffers
c. Intrusion prevention systems (IPS)
d. None of these answers are correct.
3. The software-based IPS can support which of the same analysis features as the hardware IPS appliances?
a. Some
b. All
c. None
d. Most
4. It is highly recommended to deploy all selected signatures initially without putting which type of action in place to permit tuning the sensor for a particular environment to minimize false positive and false negative events?
a. Remote
b. Passive
c. Preventative
d. All of these answers are correct.
5. What is an indication of confidence in a signature’s performance given the environment in which it is deployed?
a. Attack Severity Rating (ASR)
b. Signature Fidelity Rating (SFR)
c. Target Value Rating (TVR)
d. Event Risk Rating (ERR)
6. If a license on a router expires, it will no longer be able to do what after the license expiration date?
a. Apply any signatures created
b. Analyze traffic
c. Take preventative action when a signature is matched
d. None of these answers are correct.
7. SDEE uses what kind of communication model for event messages?
a. Pull
b. Push
c. Manual
d. None of these answers are correct.
8. What is one of the common issues found when deploying Cisco IOS Software IPS sensors to accommodate the signature database?
a. Lack of router memory
b. Insufficient router processor speed
c. Insufficient interface throughput
d. None of these answers are correct.
The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:
• 6 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and “Exam Preparation” sections.
• 7 or 8 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 14, “Introduction to Cisco IOS Site-to-Site Security Solutions.”
This chapter discusses the Cisco IOS IPS. Unlike the Cisco IOS IDS, which was tightly integrated with the Cisco IOS Firewall feature set, IPS is an independent component of Cisco IOS Software Release 12.3T and later.
This chapter covers seven main topics that pertain to the Cisco IOS IPS, as covered in the following sections.
This section describes the Cisco IOS features and new enhancements.
Intrusion detection systems (IDS) are types of security controls that are capable of monitoring traffic to detect problems in the network. They are typically network devices called sensors that monitor traffic to or from (or both) a particular network segment and perform analysis to detect misuse of network resources. The analysis can be based on a set of signatures, anomalous traffic as compared to normal traffic, or a user-specified policy.
The following list describes some examples of common attacks, although this is by no means an exhaustive list:
• Network sweeps and scans indicate a possible network reconnaissance attack that can be detected by network IDS components.
• Certain anomalies in traffic patterns can be detected by network IDS. These are often referred to as malformed packets:
• Invalid IP datagrams (for example, a “Christmas Tree” packet). This is a packet for which every single option is set regardless of the protocol.
• Invalid TCP packets (for example, a source or destination port is set to 0).
• Invalid application layer information such as instructions in an HTTP request that do not meet RFC specifications.
• Denial of service (DoS) attacks, such as floods of Internet Control Message Protocol (ICMP) packets or TCP packets can cause performance degradation by rendering normal services unavailable.
• Application layer attacks, such as buffer overflows and command injections.
Upon detection of these and other types of attacks, intrusion detection systems generate alerts. These alerts are either stored locally on the IDS but also can be retrieved by a management system. With IDS, security administrators must monitor alerts and make configuration changes manually to stop and prevent further attack traffic.
Intrusion prevention systems (IPS) are security controls that are capable of monitoring traffic to detect and prevent problems in the network. Cisco IPS is a solution designed to detect, classify, and stop malicious attacks. Action by administrators is typically not required because IPS sensors take immediate, real-time action to protect the network. It is recommended that administrative staff continue to monitor alerts generated by intrusion prevention systems for analysis.
Signatures are rules that are configured in a network IPS device that describe network traffic patterns that match a known type of malicious activity. Extensive research is conducted upon attacks and vulnerabilities to develop signatures to match certain attacks.
A signature-based network IPS uses a local database of known attack signatures against which it analyzes traffic flows. The signature-based network IPS looks inside packet headers and payloads in an attempt to match a possible string of bytes to a known signature. Consider the following examples:
• There are specific types of URLs that can be used to attack a web server. The signature-based network IPS will look inside HTTP packets to try to find these malicious data patterns.
• Buffer overflows inside the Multi-Purpose Internet Mail Extension (MIME) headers of an email message can be used in an attempt to attack an email client. The IPS will look for a particular series of bytes in the MIME part of a message to try to detect these types of attacks.
By definition, a signature-based network IPS can only detect attacks that are included in the signature database by the vendor or that are created by a network security administrator. Attack signatures that are not in the database typically go undetected by signature-based IPS devices. For this reason, signature-based IPS devices must have their signature databases updated frequently to stay current. IPS vendors will usually publish database updates that can be automatically downloaded and applied by the IPS device. However, network security administrators should always stay abreast of new attacks and ensure that their database signatures will match them. In some cases, administrators will need to create custom signatures to match them. Table 13-2 describes some of the advantages and disadvantages of IPS.
Table 13-2. Advantages and Limitations: Signature-Based Intrusion Prevention Systems

A signature engine is a component of the sensors’ analysis engine. The signature engine will inspect a specific type of traffic and support a specific category of signatures. Each signature within a Cisco IPS component is created and controlled by a signature engine that is designed for a particular type of traffic. An example would be the STRING.TCP engine, which is designed to analyze TCP connections and look for particular string patterns. An example of a signature supported by the STRING.TCP engine is provided next.
• Signature 3118, rwhoisd format-string, triggers when the engine detects an soa command being sent to an rwhois server with an abnormally large argument.
• Signature 3138 fires when a match to the C variant of the Bagle C virus email attachment is detected in an email attachment.
Each engine is made up of a parser and an inspector. There are a legal set of parameters with prescribed ranges or sets of values. These configurable engine parameters provide the ability to tune the signatures to match the current environment.
In Cisco IOS Software Release 12.4(11)T and later T-Train releases, IOS IPS signature provisioning is accomplished by selecting one of two signature categories: Basic or Advanced. Starting with IOS Release 15.0(1)M, a new category called “IOS IPS Default” will be also supported and released within IPS signature packages. At that time, the IOS Advanced category will be changed to contain exactly the same signatures as in the IOS Default category, allowing both category names to be used interchangeably for backward compatibility. Users can also add or remove individual signatures and/or can tune signature parameters through Cisco Configuration Professional (CCP) or Cisco Security Manager (CSM) management or through the command-line interface (CLI), which allows easy scripting to manage signature configuration for a large number of routers.
IOS Basic and Advanced/Default signature categories are preselected signature sets intended to serve as a good starting set for most users of IOS IPS. They contain the latest high-fidelity (low-false-positive) worm, virus, IM, or peer-to-peer blocking signatures for detecting security threats, allowing easier deployment and signature management. Cisco IOS IPS also allows the selection and tuning of signatures outside those two categories. Table 13-3 lists signature engines and their descriptions.

Because of the complexity of today’s network environments, security controls, such as IDS or IPS, can sometimes produce incorrect results that are due to either misconfigurations or something in the environment. All events should be vigorously investigated before assuming that an alert is incorrect.
There are four classifications into which the decisions made by IPS and IDS can fall:

• True positives: The IPS or IDS sensor triggered because of legitimate malicious activity. This is normal, desired operation.
• False positives: The IPS or IDS sensor triggered because of nonmalicious activity. This is usually because of errors caused by signatures that are configured to be too relaxed or broad in scope. In other words, the sensor mistook normal traffic patterns to be malicious.
• True negatives: The IPS or IDS sensor failed to trigger when there was no malicious activity. This is normal, desired operation.
• False negatives: The IPS or IDS sensor failed to trigger when there was malicious activity. This is usually because of errors caused by signatures that are configured to be too specific.
Care must be taken when tuning signatures. Adjusting signatures to be less restrictive to reduce the number of false positives can move your sensor closer to the possibility of missing legitimate attacks (false negatives).
Proper knowledge, research, and expertise in a specific environment are required to adjust signatures to a state where they successfully trigger on legitimate malicious activity, yet do not trigger on legitimate nonmalicious activity and block legitimate traffic.
The Cisco IOS Sensor functionality can be deployed in two different platforms. One platform is software based and uses the router’s main CPU for processing, and the other is hardware based and takes advantage of special-purpose hardware processors.

Cisco Integrated Services Routers (ISR) can implement the Cisco IPS sensor functionality by using the router’s main CPU to analyze packets. Software-based IPS only works in inline mode, meaning that packets are examined as they are forwarded by the router. The software-based IPS can support most of the same analysis features as the hardware IPS appliances. One of the benefits of it being inline is that it can drop traffic, block attacks, send alarms, and reset connections. This allows the router to respond immediately to detected security attacks.
The IOS Software–based IPS is limited by the router’s CPU and memory performance, which are shared with other processes running on the router. Additionally, the Cisco IOS Software IPS requires a license to enable signatures after a certain date. The IPS signature update license is part of the IOS license configuration and is configured as any other Cisco IOS Software licensed feature.
This study guide covers the Cisco IOS Software IPS sensor that is available in all Cisco ISR routers.
There are two other options for deploying the intrusion prevention system on the Cisco ISR that offer a more granular, high-performance IPS solution. The Cisco IPS Advanced Integration Module and the Cisco IPS Network Module Enhanced are two other methods for implementing the intrusion prevention system on the Cisco ISR.
The Cisco IPS Advanced Integration Module and the Cisco IPS Network Module Enhanced are dedicated hardware IPS coprocessors for the Cisco ISR. The Advanced Integration Module (AIM) is typically geared toward the small- to medium-sized businesses as well as for branch office implementations. The Network Module Enhanced (NME) is typically appropriate for small enterprises to large branch office deployments. Both modules run the same software as the IPS appliance and provide the full intrusion prevention feature set.
AIM-IPS and NME-IPS can both be implemented in both inline and promiscuous inspection modes. The modules are able to monitor and analyze traffic from any router interface as well as generic routing encapsulation (GRE) and IPsec traffic that is decrypted by the router; however, neither module supports policy virtualization.
Table 13-4 summarizes the characteristics of and supported models for the hardware-based sensors.

Table 13-4. Cisco IPS Hardware Modules

The Cisco NME-IPS module has one external Gigabit Ethernet port that is used as a command and control interface for out-of-band management. The AIM-IPS module does not have any external interfaces. These modules run the full Cisco IPS software and therefore are outside the scope of this chapter.
There are several deployment tasks you must do to deploy the IPS on Cisco IOS Software devices. The following list summarizes what you must do for a successful implementation:
Step 1: Configure a Cisco IOS Software IPS Signature policy, which means enabling a particular set of signatures on a specific router interface or interfaces.
Step 2: Tune Cisco IOS Software IPS Signature policies to balance between and manage false positives and false negatives.
Step 3: Deploy the Cisco IOS Software IPS Signature update feature, which configures the router to independently load new signatures as they become available.
Step 4: Select a monitoring tool and use it to monitor intrusion events generated by the Cisco IOS Software IPS sensor.
The following guidelines should be considered when deploying Cisco IOS Software IPS:

• Consider using the Cisco IOS Software Release 15.0(1)M or later, because it supports lightweight signature engines, which allows the use of more active signatures with the same CPU and memory configuration as compared to older Cisco IOS Software releases.
• Deploy Cisco IOS Software IPS at the edge of the network to have the security control running where malicious software is most likely to enter the environment.
• If there will be a large number of Cisco IOS Software IPS sensors deployed in the environment, consider using a centralized Security Information Manager (SIM) application to effectively manage the event information.
• If there will be a large number of Cisco IOS Software IPS sensors deployed in the environment, consider using a tool that will centralize deployment and configuration of the sensors. The Cisco Security Manager supports provisioning Cisco IOS Software IPS sensor configurations in large, complex environments.
The first deployment task you must complete is to deploy IPS signature policies. The configuration tasks that you must complete are listed next.
The first deployment task for the Cisco IOS Software IPS sensor is to enable the IPS functionality globally on the router, designate the interfaces on which the router will inspect traffic, and select a signature set that will be tuned in a later task. The following configuration tasks cover this first deployment task:
Task 1: Import the RSA public key that the router will use to verify authenticity and integrity of all signature packages and updates to the router.
Task 2: Create the IPS ruleset that will be applied to interfaces.
Task 3: Apply the configured IPS ruleset to the router interfaces.
Task 4: From Cisco.com, download the basic signature package onto the router.
Task 5: Choose the initial signature set by specifying the signature categories that will be enabled by default and the category-based actions that will be assigned to these signatures.
Prior to installing and configuring Cisco IOS IPS, you need to consider a few factors, as discussed in the following sections. Figure 13-1 shows the scenario used for the configuration tasks in this chapter.
Figure 13-1. Configuration Scenario

The configuration tasks will enable the IPS function on the router to inspect traffic on the interface nearest the attacker. An initial signature set that will drop all packets containing malicious traffic will also be configured on the router.
The configuration steps in the chapter will assume that the Cisco ISR is already configured with a complete configuration to provide full connectivity between all involved networks.
The first configuration task in this sequence is to import a known RSA public key whose private key is used by Cisco IPS engineering to digitally sign all signature packages and updates for Cisco IPS sensors. This public key will be used by the Cisco ISR to validate the digital signature of signature packages and updates as authentic. This is important because it is designed to prevent rogue updates from being deployed onto Cisco IPS sensors. This is not associated with the Cisco IPS licensing framework.
To install the known RSA public key, create an RSA public key chain on the router, using the crypto key pubkey-chain rsa command, and inside it, create a new named signature key with the name realm-cisco.pub using the named-key command. Then, enter the key-string command and paste the text from the realm-cisco.pub.key.txt file, which is found at Cisco.com. The commands are shown in Example 13-1.
Example 13-1. Import RSA Key to Cisco ISR
Router# configure terminal
Router(config)# crypto key pubkey-chain rsa
Router(config-pubkey-chain)# named-key realm-cisco.pub signature
Translating "realm-cisco.pub"
Router(config-pubkey-key)# key-string
Enter a public key as a hexadecimal number ....
! Note: The $ to the left of the hex characters represent there are more
numbers present than would fit on one line.
Router(config-pubkey)# $2A864886 F70D0101 01050003 82010F00 3082010A 02820101
Router(config-pubkey)# $D6CC7A24 5097A975 206BE3A2 06FBA13F 6F12CB5B 4E441F16
Router(config-pubkey)# $912BE27F 37FDD9C8 11FC7AF7 DCDD81D9 43CDABC3 6007D128
Router(config-pubkey)# $085FADC1 359C189E F30AF10A C0EFB624 7E0764BF 3E53053E
Router(config-pubkey)# $0298AF03 DED7A5B8 9479039D 20F30663 9AC64B93 C0112A35
Router(config-pubkey)# $994AE74C FA9E481D F65875D6 85EAF974 6D9CC8E3 F0B08B85
Router(config-pubkey)# $5E4189FF CC189CB9 69C46F9C A84DFBA5 7A0AF99E AD768C36
Router(config-pubkey)# $A3B3FB1F 9FB7B3CB 5539E1D1 9693CCBB 551F78D2 892356AE
Router(config-pubkey)# $80CA4F4D 87BFCA3B BFF668E9 689782A5 CF31CB6E B4B094D3
Router(config-pubkey)# F3020301 0001
Router(config-pubkey)# quit
Router(config-pubkey-key)# end
The second and third tasks involve creating and applying a named IPS ruleset. A default location for the IPS sensor configuration files in the router’s local file system must be specified.
The majority of the Cisco IOS Software IPS sensor’s configuration is not stored in the router’s running configuration. It stores the signature definitions and other auxiliary files as XML files in the designated location in the file system. When a signature is updated or the signature policy is changed, these XML files are changed by the CLI or Cisco Configuration Professional configuration tasks that are executed.
Create the new directory on the router’s local file system with the mkdir command. Then, enter configuration mode and specify the location of the new folder with the ip ips config location command.
Next, create a basic named IPS ruleset using the ip ips name command. Note that the only parameters to configure inside the named ruleset would be to specify an optional access list if there is a requirement to inspect only a portion of the traffic seen by the IPS function. To inspect all traffic, simply create the ruleset and apply it to all the interfaces that require inspection by IPS. The CLI commands are shown in Example 13-2.
Example 13-2. Import RSA Key to Cisco ISR
Router# configure terminal
Router(config)# ip ips config location flash:/ipsroot
Router(config)# ip ips name MY-IPS
Router(config)# interface GigabitEthernet0/0
Router(config-if)# ip ips MY-IPS in
Router(config-if)# ip ips MY-IPS out
Router(config-pubkey)# end
Router# copy running-config startup-config
Task 4 loads a basic IPS signature package onto the router, which then compiles and creates the local signature database.
First, the signature package must be downloaded from Cisco.com. Go to the download section of Cisco.com and navigate to Products > Security > Integrated Router/Switch Security > Integrated Threat Control > Cisco IOS Intrusion Prevention System Feature Software > IOS IPS Signature Data File. Download the latest package, which should have a filename in the format IOS-Sxxx-CLI.pkg. Put the file on the server from which you will transfer it to the router. Use the copy command to transfer the file to the router’s idconf alias. This causes the router to download and unpack the contents of the file (XML files) into the folder that was specified in Task 2 of this section. The router compiles the files into the required internal format and displays any errors that occur.
The last task of this sequence involves choosing signatures that will be included in the initial signature set. The most efficient way to choose signatures would be to choose them by category. Cisco IOS Software IPS provides categories for the IPS signatures based on attack type, operating system relevance, network protocol, and so on. Also, select the default action to be taken by the sensor for any entire category of signatures.
When a signature is matched by a packet in a session, the Cisco IOS IPS sensor will take any of the following configurable actions:
• Send an alarm
• Drop the offending packet
• Reset the connection
• Deny traffic for a particular source address
• Deny traffic for a particular connection (session)
For each category and for each individual signature in the signature database, two different states can be specified:
• Some signatures can be disabled. This signature is present in the router’s memory but is not being used for traffic inspection. It can be enabled without the router needing to recompile the signature database.
• Some signatures can be retired. This signature is not present in the router’s memory. Unretiring a retired signature requires that the router recompile the signature database. This can temporarily affect performance and take a long time with a large signature database.
This configuration task is completed by entering the signature category configuration mode using the ip ips signature-category command. See Example 13-3 for the relevant configuration. First, retire and disable all signatures because only the desired signatures will be enabled. This is achieved using the category all command. Then, use the retired true and enabled false commands to disable and retire all signatures by default. Next, enable all signatures that are designed to prevent attacks against Cisco IOS Software devices and assign a preventative action to them. Enter the category that comprises these signatures using the category os ios command and enable them by using the retired false and enabled true commands. Use the event-action produce-alert deny-packet-inline command to enable these signatures to generate an alert and drop the offending packets when they trigger.
Example 13-3. Configure a Signature Set and Default Category Actions on the Cisco ISR
Router# configure terminal
Router(config)# ip ips signature-category
Router(config-ips-category)# category all
Router(config-ips-category-action)# enabled false
Router(config-ips-category-action)# retired true
Router(config-ips-category-action)# exit
Router(config-ips-category)# category os ios
Router(config-ips-category-action)# retired false
Router(config-ipss-category-action)# exit
Router(config)# exit
Do you want to accept these changes?[confirm] yes
Verifying the signature policy configuration can be accomplished through the use of the show ip ips configuration command, as demonstrated in Example 13-4. This will show the database location, the signature database load times, and the signature categories that have been configured to create the initial signature set. Use the show ip ips interfaces command to view the interfaces on which the IPS functionality has been applied. You can use the show ip ips statistics command to view information such the number of packets audited and the number of interfaces configured for auditing.
Example 13-4. Verifying a Signature Set and Default Category Actions on the Cisco ISR
Router# show ip ips configuration
Event notification through syslog is enabled
Event notification through Net Director is enabled
Default action(s) for info signatures is alarm
Default action(s) for attack signatures is alarm
Default threshold of recipients for spam signature is 25
PostOffice:HostID:5 OrgID:100 Addr:10.2.7.3 Msg dropped:0
HID:1000 OID:100 S:218 A:3 H:14092 HA:7118 DA:0 R:0
CID:1 IP:172.21.160.20 P:45000 S:ESTAB (Curr Conn)
Audit Rule Configuration
Audit name AUDIT.1
info actions alarm
show ip ips interface Command
Interface Configuration
Interface Ethernet0
Inbound IPS audit rule is AUDIT.1
info actions alarm
Outgoing IPS audit rule is not set
Interface Ethernet1
Inbound IPS audit rule is AUDIT.1
info actions alarm
Outgoing IPS audit rule is AUDIT.1
info actions alarm
show ip ips statistics
Signature audit statistics [process switch:fast switch]
signature 2000 packets audited: [0:2]
signature 2001 packets audited: [9:9]
signature 2004 packets audited: [0:2]
signature 3151 packets audited: [0:12]
Interfaces configured for audit 2
Session creations since subsystem startup or last reset 11
Current session counts (estab/half-open/terminating) [0:0:0]
Maxever session counts (estab/half-open/terminating) [2:1:0]
Last session created 19:18:27
Last statistic reset never
HID:1000 OID:100 S:218 A:3 H:14085 HA:7114 DA:0 R:0
Consider the following guidelines when deploying the initial Cisco IOS Software IPS sensor policies:
• Rather than deploying a large number of signatures initially, it is recommended to configure a selection of critical signatures first and then add more signatures later if it is determined that the router’s resources can handle them.
• It is highly recommended to deploy all selected signatures initially without a preventative action (drop packet, reset connection, deny connection) to permit tuning the sensor for a particular environment to minimize false positive and false negative events.
In most cases, to manage the number of false positives and false negatives being received from the Cisco IOS Software IPS sensor, administrators need to tune the active signatures after they have been exposed to live network traffic. Individual signatures can be tuned using the CLI or the Cisco Configuration Professional. Signature parameters that can be tuned include
• Tuning trigger conditions
• Tuning response actions
Advanced tuning requires the Cisco IOS Software Signature Event Action Processor (SEAP) function. Advanced tuning is only possible using SEAP.
Manage false positives by creating address-based filters that selectively disable signatures for specific hosts whose legitimate traffic triggers signatures. This is similar to creating an exception based upon a host’s address.
Create global actions for all signatures based on the risk level (covered later in this topic).
The Cisco IOS Software IPS sensor uses a concept called event risk rating (ERR) to calculate and provide to administrators the severity of an event in a given network environment. The event risk rating is an integer with a value between 0 and 100. Values over 100 are capped at 100. The value is dynamically configured after the firing of a signature. The higher the value, the greater the security risk of the event.
The ERR calculation, as shown in the formula in Figure 13-2, uses several components from an intrusion event. Some of these components must be manually configured, some of them are preconfigured and can be tuned, and some are collected automatically from the environment.
Figure 13-2. Formula for Event Risk Rating Calculation

The Attack Severity Rating (ASR) is assigned to each signature by the Cisco IPS sensor. The ASR is determined by the severity configured for each signature. The severity level can be informational, low, medium, or high. Each of these severity levels has a numeric value that is associated with it that is used in the ERR calculation:
• Informational (25)
• Low (50)
• Medium (75)
• High (100)
The Target Value Rating (TVR) is assigned to each asset and is used to assign value to a particular asset. To the Cisco IPS sensor, each unique asset is identified by its IP address. Assets in the environment that are more important or mission critical would receive a higher value than those assets that are not as important. The target value rating level can be set to zero, low, medium, high, or mission critical. Each target level has a numeric value that is associated with it that is used in the ERR calculation:
• Zero (50)
• Low (75)
• Medium (100)
• High (150)
By default, the Cisco IPS sensors consider all assets as having a Medium TVR.
The Signature Fidelity Rating (SFR) is assigned to each asset and is used to assign value. The SFR is an indication of confidence in a signature’s performance given the environment in which it is deployed. The SFR has a value between 0 and 100.
Figure 13-3 shows the calculation of event risk rating for a signature with the following properties:
• Attack Severity Rating = 50 (Low)
• Signature Fidelity Rating = 90
• The target has a default TVR of 100.
Figure 13-3. Event Risk Rating Calculation

Based on the data and the rating formula, the event risk for this particular occurrence is 45.
The SEAP signature event action overrides (SEAO) are a Cisco IOS Software IPS configuration tool that allows one or more actions to be added to all active signatures based on the calculated risk rating of each event.
Event action overrides provide a way to add actions globally without having to configure each signature or signature category. Each event action override is associated with an event risk rating range. If a signature event occurs and the event risk rating for the event falls within the configured range for the event action override, the action will be added to the event. For example, if you set the risk rating range for the “deny packet inline” action to 85–100, for every signature event that has an event risk rating calculation that falls within this range, the “drop packet inline” action will be added to the event.
The SEAP signature event action filters are a Cisco IOS Software IPS configuration tool that allows one or more actions to be removed from all active signatures based on the attacker and/or target (source and destination) address and event risk rating criteria.
Signature event action filters are typically used to remove one, several, or all actions from a particular signature when certain circumstances are met, such as when triggered by a specific source IP address.
The second deployment task for the Cisco IOS Software IPS sensor is to tune the IPS sensor’s signature policies to adapt them to the installed environment. This involves the four following configuration tasks:
Task 1: Optionally, tune individual signatures.
Task 2: Configure Target Value Ratings for your environment.
Task 3: Configure SEAP signature event action overrides to globally add actions to signatures.
Task 4: Configure SEAP signature event action filters to remove actions from events to address false positive events.
The scenario in which the configuration tasks will be implemented will include the following information:
• Tune the “IOS FTPd Successful Login” signature (signature ID 5860, subsignature ID 1) to only produce alerts. Additionally, set its Signature Fidelity Rating to 40 and its severity to Low.
• Using SEAP, filter the “Malformed MGCP Packet” signature (signature ID 6179, subsignature ID 0) to not trigger if traffic is sourced from 10.1.1.10.
• Assign a Mission Critical Target Value Rating (TVR) for hosts in the 10.10.10.0/25 subnet.
• For configured signatures of any category, add the “Deny attacker inline” action if the event risk rating exceeds 90. This causes the attacker to be temporarily blocked by the IPS-enabled router.
The configuration steps in the chapter will assume that the Cisco ISR is already configured with a complete configuration to provide full connectivity among all involved networks.
The first task involves tuning an individual signature to change its event actions and signature parameter. First, enter signature configuration mode using the ip ips signature-definition command. Specify the signature that needs to be configured using the signature command by specifying its signature and subsignature ID (“IOS FTPd Successful Login,” signature 5860, subsignature ID 0).
Example 13-5 shows the commands used to produce an alert as the event action and set the fidelity rating to 40.
Example 13-5. Tune Individual Signatures Using the CLI
Router# configure terminal
Router(config)# ip ips signature-definition
Router(config-sigdef-sig)# signature 5860 1
Router(config-sigdef-action)# engine
Router(config-sigdef-action-engine)# event-action produce-alert
Router(config-sigdef-action)# alert-severity low
Router(config-sigdef-action)# fidelity-rating 40
Router(config-if)# ^Z
Do you want to accept these chagnes:[confirm] y
Inside the signature configuration mode, enter the signature engine configuration mode by entering the engine command and only specify the produce-alert action for this signature. Exit from the signature engine configuration mode by using the exit command. Back in signature configuration mode, alter the default ASR and SFR values for this signature by using the alert-severity and fidelity-rating commands. Refer to the “References” section, later in this chapter, for links to Cisco IOS command references.
Cisco Configuration Professional (CCP) can also be used to edit the parameters of individual signatures. Refer to Figure 13-4 and complete the following steps in CCP:
Step 1: Navigate to Configure > Security > Advanced Security > Intrusion Prevention > Edit IPS > Signatures.
Step 2: Under Signatures, select the All Categories > OS > Windows > IOS category to display all enabled signatures for this category.
Step 3: Find the signature to be configured (“IOS FTPd Successful Login,” signature ID 5860, subsignature ID 1), select it, and click the Edit button.
Step 4: In the Edit Signature window, change the Alert Severity, Sig Fidelity Rating, and Event Action values in their corresponding fields.
Step 5: Click OK and then click Apply Changes to confirm the changes to the signature.
Figure 13-4. Tune Signature in Cisco Configuration Professional

Task 2 allows the optional configuration of the Target Value Ratings for the hosts (assets) in the network. Note, by default, that all hosts are assigned a Target Value Rating of 100.
You can adjust the Target Value Rating for a host or an address range by entering the SEAP configuration mode using the ip ips event-action-rules command. Inside the SEAP configuration mode, use the target-value command to set the TVR for a host or a network. Example 13-6 shows the configuration using Cisco IOS CLI commands, and the following steps detail the process in Cisco Configuration Professional:
Step 1: Navigate to Configure > Security > Advanced Security > Intrusion Prevention > Edit IPS > SEAP Configuration > Target Value Rating.
Step 2: Click Add to add a new TVR rule.
Step 3: In the Add Target Value Rating window, select the Target Value Rating and specify the address or address range for this Target Value Rating.
Step 4: Click OK and then click Apply Changes to confirm the Target Value Rating rule.
Example 13-6. Tune Individual Signatures Using the CLI
Router# configure terminal
Router(config)# ip ips event-action-rules
Router(config)# target-value mission-critical target-address 10.10.10.0/24
Router(config-pubkey)# end
Router# copy running-config startup-config
Task 3 illustrates how to create SEAP event action overrides to add actions to signatures that trigger based on the event risk rating. The example includes adding a “Deny attacker inline” action if the ERR exceeds 90. Interactively creating SEAP event action overrides can only be accomplished using Cisco Configuration Professional.
The following steps detail the process in Cisco Configuration Professional:
Step 1: Navigate to Configure > Security > Advanced Security > Intrusion Prevention > Edit IPS > SEAP Configuration > Event Action Overrides.
Step 2: Select the Use Event Action Override check box.
Step 3: Click Add to create a new event action override. The Add Event Action Override window opens, as shown in Figure 13-5. It is possible to create multiple event action overrides to add multiple actions.
Step 4: Select the event action to be added to a signature event from the Event Action list.
Step 5: To enable the event action, select the Yes radio button in the Enabled field.
Step 6: In the Risk Rating field, assign a risk rating range to the action override.
Step 7: Click the OK button. The new event action override now appears in the list on the Event Action Overrides tab (not shown).
Step 8: Click OK and then click Apply Changes to confirm the event action override rule.
Figure 13-5. Configure Event Action Override

Task 4 illustrates how to create SEAP event action filters to remove actions from signatures that trigger based on the source and/or destination IP address and the event risk rating. Interactively creating SEAP event action filters can only be accomplished using Cisco Configuration Professional.
The following steps detail the process in Cisco Configuration Professional:
Event action filters are processed as an ordered list, and filters can be moved up and down the list. A filter that removes all actions from an event effectively disables the signature in the defined context.
Step 1: Navigate to Configure > Security > Advanced Security > Intrusion Prevention > Edit IPS > SEAP Configuration > Event Action Filters.
Step 2: Select the Use Event Action Filters check box.
Step 3: Click Add, and the Add Event Action Filter window opens, as shown in Figure 13-6.
Step 4: In the Name field, enter a name for the event action filter. A default name is always supplied, but it can be changed to have a more meaningful name.
Step 5: To enable the event action filter, select the Yes radio button in the Enabled field.
Step 6: In the Signature ID field, enter the signature IDs of all signatures to which this filter should be applied.
Step 7: In the Subsignature field, enter the subsignature IDs of the subsignatures to which this filter should be applied.
Step 8: In the Attacker Address field, enter the IP address of the source host. This can be entered as a specific host IP address or as a range of IP addresses, such as 0.0.0.0-255.255.255.255.
Step 9: In the Attacker Port field, enter the port number used by the attacker to send the offending packet. The default value is all ports.
Step 10: In the Victim Address field, enter the IP address of the destination host. This can be a specific host or a range of IP addresses such as 0.0.0.0-255.255.255.255.
Step 11: In the Victim Port field, enter the port number used by the victim host to receive the offending packet. The default value is all ports.
Step 12: In the Risk Rating field, specify a risk rating range for this filter.
Step 13: In the Actions to Subtract field, select the actions to remove from the signature event.
Step 14: In the Stop on Match field, select one of the following radio buttons:
• Yes: Choose this option to have the event action filters stop processing after actions that meet this filter’s parameters have been removed. Any remaining filters will not be processed, and no additional actions can be removed from this event.
• No: Choose this option to continue processing additional filters.
Step 15: In the Comments field, provide any comments that need to be stored with this filter, such as the purpose of the filter or why it is configured in a particular way.
Step 16: Click OK. The new event action filter now appears in the list on the Event Action Filters tab.
Step 17: Click Apply Changes to apply the new configuration to the router.
Figure 13-6. Configure Event Action Filter

Verify the configuration of SEAP parameters using the CLI with the show ip ips event-rules target-value-rating command to see configured TVRs for IP address ranges in the network. Use the show ip ips event-action-rules overrides command to display all configured SEAP event action overrides and verify that they comply with the corporate policy. Additionally, use the show ip ips event-action-rules filters command to display the configured SEAP event action filter information. Example 13-7 shows these verification commands in use.
Example 13-7. Verify SEAP Parameters Using the CLI
Router# show ip ips event-action-rules filters
Filters
Global Filters Status: Enabled
Consider the following implementation guidelines when tuning the Cisco IOS Software IPS sensor:
• Use event action filters to tune false positives from specific traffic flows.
• Consider using event action filters to subtract a specific action from all signatures. For example, after initial deployment and when the IPS sensor signatures are still being tuned, use an event action filter to subtract configured blocking actions for all signatures.
Signatures packs on Cisco IOS Software IPS-enabled routers can be updated either manually, as shown in the second task in this topic, or can be updated automatically by configuring the router to download updates from repositories.
Cisco distributes signature updates as digitally signed files, which can be securely transferred over untrusted networks to ensure their authenticity and integrity. Note that the signature update process is bound to the license on the router. If a license on a router expires, it will no longer be able to apply any signatures created after the license expiration date, but it will continue to analyze traffic using the existing, preexpiration IPS signatures.
The router can be configured to update itself from Cisco.com, if the router has Internet connectivity or if a local staging server can be used. The local staging server must have the signature packs downloaded manually by an administrator for them to be available for the router to retrieve.
Two tasks must be completed to configure automatic signature updates.
The following tasks detail the process in Cisco Configuration Professional:
Task 1: Install and verify the signature update license on the router.
Task 2: Configure the router to automatically update its signature database from Cisco.com or a local server.
The scenario used for the following two tasks includes uploading a license file to the router and then enabling automatic updates from Cisco.com (at https://www.cisco.com/cgi-bin/front.x/ids/locator/locator.pl) or a local server at 10.1.1.1. The configuration steps in the following sections assume that the Cisco ISR is already configured for basic IPS functionality and full IP connectivity among the necessary networks.
The first task that must be completed is to install the appropriate signature update license on the router. The license is a file that can be obtained by providing the appropriate Product Authorization Key (PAK) to the Cisco licensing web application.
The Cisco Product License Registration application can be found at www.cisco.com/go/license.
Use the license install command to download and install the license file to the router. Use the show ip ips license command to display license information, especially its validity and expiration date. Example 13-8 shows the usage of these two commands.
Example 13-8. Install and Display Signature Update License Information
Router# license install http://10.1.1.1/Router-sig-license-2010.lic
Router# show ip ips license
IPS License Status valid
Expiration Date: 2010-12-31
Signatures Loaded: Not Available S0.0
Signature Package: Not Available S0.0
The second task illustrates how to configure the router to attempt to retrieve automatic signature updates from Cisco.com or a local server.
To do this, first configure the update URL using the ida-client server url command. Use the https://www.cisco.com/cgi-bin/front.x/ids/locator/locator.pl URL. Next, create an auto-update profile using the ip ips auto-update command. Use the cisco command inside the profile to designate obtaining updates from Cisco.com. To control when the update attempts occur, use the occur-at command. Example 13-9 illustrates the setup of the configuration to retrieve automatic updates from the Cisco.com repository as well as to provide the Cisco.com credentials that will be used for authentication through using the username command. Example 13-10 illustrates the setup of the configuration to retrieve automatic updates from a local staging server.
The following specifics are used in the example:
• Days of the week: 0-6 (Sunday–Saturday)
• Minutes: Minutes from the top of the hour (0)
• Hour: Hour of the day (3:00 a.m.)
Example 13-9. Configure Automatic Signature Updates from Cisco.com
Router(config)# ida-client server url https://www.cisco.com/cgi-bin/
front.x/ids/locator/locator.pl
Router(config)# ip ips auto-update cisco
Router(cnofig-ips-auto-update)# occur-at weekly 0-6 0 3
Router(config-ips-auto-update)# username CCOUSERNAME password CCOPASSWORD
Router(config-ips-auto-update)# exit
Router(config)# password encryption aes
Router(config)# key config-key password-encryption
Example 13-10. Configure Automatic Signature Updates from a Local Server
Router(config)# ip ips auto-update
Router(config-ips-auto-update)# occur-at weekly 0-6 0 3
Router(config-ips-auto-update)# url https://10.1.1.1/sigupdate/ios-sig-update.pkg
To verify automatic signature update operation, use the show ip ips license command. The output will show the current signature set release loaded and the dates of its release and application. Example 13-11 shows the command usage and output.
Example 13-11. Verification of Signature Updates
Router# show ip ips license
IPS License Status valid
Expiration Date: 2010-12-31
Signatures Loaded: 2010-03-24.S479
Signature Package: 2009-03-19.S479
A successful intrusion prevention system must include a review of the generated events. Although intrusion prevention by nature can be configured to automatically react to traffic patterns that match signatures, you must analyze log information as well.
Monitoring and managing IPS events fall into one of two categories:
• Real-time event monitoring and management
• Performing analysis on archived log information
Cisco IPS sensors produce several types of events, such as intrusion alerts and status events, that are communicated to client applications such as event management applications using the proprietary SDEE protocol. The Cisco IPS sensors can also be configured to forward intrusion events to its local syslog facility.
SDEE is a standardized IPS communication protocol developed by Cisco for the IDS Consortium at the International Computer Security Association (ICSA). Cisco IPS sensors use SDEE to provide an application programming interface (API) to the IPS that can integrate with third-party management and monitoring solutions. This gives users a choice of third-party solutions to use for monitoring and managing events generated by the Cisco IPS sensor.
SDEE uses a pull communication model for event messages. This allows management consoles to pull alerts from the Cisco IPS sensors over an HTTPS connection.
On a Cisco IOS Software IPS-enabled router, SDEE is always running, but it does not receive and process IPS events unless SDEE notification is specifically enabled. Characteristics of the SDEE protocol are as follows:
• When Cisco SDEE notification is enabled, by default, 200 events can be stored in the local event store. This number can be increased to hold a maximum of 1000. All stored events are lost if SDEE notifications are disabled, and a new local event store is allocated when the notification feature is enabled again.
• The local HTTP or HTTPS server must be enabled on the router when enabling SDEE. It is highly recommended to use HTTPS to secure the data as it travels across the network.
• The Cisco IOS IPS router can send IPS alerts through syslog and can have the SDEE notification feature enabled at the same time.
Cisco IPS Manager Express (IME) is an IPS management application designed to meet the requirements of small- and medium-sized businesses. Cisco IME provides a comprehensive set of application functions but is very intuitive and easy to navigate. There is a high-level information display that integrates the functions of the application that enables quick assessment of network activity and decreases threat response times. There are many functions that can be customized to align with a particular environment, which allows users to adapt the application to their needs and preferences.
Cisco IME can manage both the dedicated Cisco IPS sensor appliances and modules as well as the Cisco IOS Software IPS sensors. The following features are provided for managing the Cisco IOS Software IPS sensors:
• Monitor events: IME provides the ability to monitor the IPS events generated by the sensor.
• Generate reports: Cisco IME comes with built-in reporting capabilities that allow reports to be generated quickly using predefined templates. The reports are based on current events and/or historical event data stored in the IME event database.
The Cisco IPS Manager Express supports up to ten simultaneous Cisco IPS sensors and has a limit of 100 events per second. The application is available free of charge and can be downloaded from Cisco.com.
Installing Cisco IPS Manager Express (IME) is a simple task. However, ensure that the system upon which Cisco IME will be installed meets the minimum installation requirements. IME has the following system requirements:
• IBM PC–compatible system with a 2-GHz or faster processor
• Color monitor with at least 1024 x 768 resolution and a video card capable of 16-bit colors
• 100 GB of hard drive space
• 2 GB of RAM
• Java Runtime Environment 1.5.0_07 or higher
• Operating systems:
• Microsoft Windows Vista Business and Ultimate (32-bit only)
• Microsoft Windows XP Professional (32-bit only)
• Microsoft Windows 2003 server
IME supports only the 32-bit U.S. English and Japanese versions of Windows. IME does not support Windows OS virtualization.
Two tasks must be completed to integrate a Cisco IOS Software IPS router with the Cisco IME:
Task 1: Configure the SDEE event feed on the router.
Task 2: Add each Cisco IOS Software IPS router as a sensor to the Cisco IME device list.
The scenario used for the following two tasks includes adding a Cisco IOS Software IPS sensor with an IP address of 10.1.1.1 into a preinstalled Cisco IME system. Additionally, adding the configuration to the router to enable the HTTPS server and the SDEE event store will be completed. For the Cisco IME to connect to the SDEE server on the router, appropriate credentials (username/password combination) must be generated on the router as well.
The steps in this configuration sequence assume that the Cisco ISR is already configured with basic IPS functionality and that full IP connectivity for required connectivity already exists.
In the first task, the router is configured as the SDEE event server and also has the HTTPS server enabled. A username and password combination is also created with which the Cisco IME will authenticate to the router when retrieving Cisco IPS events from the SDEE event store.
First, enable authentication, authorization, and accounting (AAA) using the aaa new-model command and configure default login authentication and exec authorization methods that use the local database. The is accomplished using the aaa authentication login default local and the aaa authorization exec default local commands. This AAA functionality is needed to allow Cisco IME subscriptions to the local SDEE server using the router’s HTTPS server.
When configuring AAA methods, be careful to ensure that the configuration does not impact other access methods or adversely affect traffic flowing to and through the router.
The next step is to enable the router’s HTTP server using the ip http server command, enable HTTPS with the ip http secure-server command, and configure AAA for HTTP connections by using the ip http authentication aaa command.
A self-signed certificate will be generated when HTTPS is enabled. This certificate authenticates the HTTPS server to clients. Depending on your environment, it may be necessary to provision a PKI-based certificate for this authentication purpose.
After the HTTPS server is enabled, create a local user account that the Cisco IME will use by entering the username command. It is recommended that a long, random password be used because it will be stored in the Cisco IME device database.
Finally, enable SDEE on the router using the ip ips notify sdee command. This will create the local SDEE event store and allow authenticated remote systems to pull events from the event store.
Example 13-12 demonstrates putting the commands together to enable SDEE and HTTPS on the router.
Example 13-12. Configure SDEE and HTTPS Server on the Cisco ISR
Router# configure terminal
Router(config)# aaa new-model
Router(config)# aaa authentication default local
Router(config)# aaa authorization exec default local
Router(config)# ip http server
Router(config)# ip http secure-server
Router(config)# ip http authentication aaa
Router(config)# username viewer secret ghjWqwkAD2342525daa
Router(config)# ip ips notify sdee
Router(config)# end
Router # copy running-config startup-config
In the second task, the Cisco IOS Software IPS sensor is added to the Cisco IME device database by completing the following steps. Open Cisco IME and perform the following steps:
Step 1: Navigate to Home > Device List and click Add, as shown in Figure 13-7.
Figure 13-7. Add Device to Cisco IPS Manager Express

Step 2: Enter the information in the required fields in the Add Device dialog box:
a. Enter the name and IP address of the router being added.
b. Enter the username and password configured for Cisco IME on the router.
c. Select the preferred communication protocol (HTTPS or HTTP).
d. Select the event start time by either selecting the Most Recent Alerts check box or by entering a start date and time in the Start Date and Start Time fields. To receive a continuous event feed from this moment on, choose the Most Recent Alerts option.
e. Under Exclude Alerts of the Following Severity Level(s), optionally select the check boxes of any levels that you want to exclude. The default is to have all levels configured. It is more appropriate to receive all event levels and then use event action filters to exclude specific events.
f. Click OK to add the sensor to the IMS system.
Step 3: If you are connecting to the router of a trusted network, when asked to accept the certificate, click Yes. The IME will store the authorized router certificate locally for subsequent connections.
If you click No to reject the certificate, Cisco IME will not be able to connect to the router.
Verification of the event feed can be achieved by executing the show ip sdee subscriptions command on the router. On Cisco IME, examine the Event Status field in the device list. The field should display the feed as Connected. The CLI output is shown in Example 13-13.
Example 13-13. Verify SDEE Operation
Router# show ip sdee subscriptions
Configured concurrent subscriptions: 1
SDEE open subscriptions: 1
Subscription ID Router_23452_45384
Client address 10.2.1.101 port 55044
Subscription opened at 19:03:08 CDT Nov. 15, 2010
Subscription lat accessed at 13:24:32 CDT Nov. 17, 2010
Total GET requests: 1345
Max number of events: 184
Timeout: 5
Verification of an event feed can also be obtained by generating traffic that is known to trigger specific IPS signatures on the router and observing the syslog messages and SDEE events. Routers will always generate syslog messages for every signature that is triggered. The show ip sdee alerts command can be used to view the events that are written to the local SDEE event store. Example 13-14 shows sample output from this command.
Example 13-14. show ip sdee alerts Command Output
Router# show ip sdee alerts
Event storage:1000 events using 656000 bytes of memory
SDEE Alerts
SigID SrcIP DstIP SrcPort DstPort Sev Event ID SigName
1:100 2004 10.0.0.2 10.0.0.1 8 0 2 10211478597901 ICMP
Echo Req
2:100 2004 10.0.0.2 10.0.0.1 8 0 2 10211478887902 ICMP
Echo Req
3:100 2004 10.0.0.2 10.0.0.1 8 0 2 10211479247903 ICMP
Echo Req
4:100 2004 10.0.0.2 10.0.0.1 8 0 2 10211479457904 ICMP
Echo Req
5:100 2004 10.0.0.2 10.0.0.1 8 0 2 10211479487905 ICMP
Echo Req
In the Cisco IME, events pulled from the router’s SDEE event store are displayed in the Event Monitoring pane. Double-click an individual event to examine event details for each signature event that triggered.
Several Cisco IOS CLI commands can be used to troubleshoot IPS sensor issues. It is recommended to generate traffic that is known to cause one of the configured signatures to trigger and then use the following commands to troubleshoot:
• show ip ips license
• show logging / show ip sdee events
• show ip ips signatures
• show ip ips event-action-rules filters
• debug ip ips engine
• debug ip ips auto-update
The following steps represent the recommended process flow for troubleshooting signature triggering on a Cisco IOS Software IPS sensor-enabled router. This process is to troubleshoot a situation in which malicious traffic does not trigger IPS signatures:
Step 1: Verify that signatures do not actually fire because of triggering events. Use the show logging and show ip sdee events commands. Events on the router, but not on the event-monitoring software, indicate an SDEE communication issue rather than a signature-triggering issue.
Step 2: Check that the desired IPS functionality is enabled on all required interfaces. The show ip ips interfaces command will display all interfaces on which IPS is enabled.
Step 3: Check to see whether the signatures that are expected to trigger are actually loaded on the router. Use the show logging command to determine whether there were any signature compilation errors. Verify that the IPS license is valid with the show ip ips license command. Use the show ip ips signatures command to find the signature with the problem and verify that it is enabled and not retired.
Step 4: Ensure that the signature is not being filtered by SEAP event action filters by using the show ip ips event-action-rules filters command.
Example 13-15 shows sample output from some of these commands.
Example 13-15. Troubleshooting Commands
Router# show ip ips license
IPS License Status Valid
Expiration Date: 2009-12-31
Signatures Loaded: 2009-06-25 S375
Signature Package: 2009-06-25 S375
Router# show ip ips signature count
Cisco SDF release version S310.0 ß signature package release version
Trend SDF release version V0.0
Signature Micro-Engine: multi-string: Total Signatures 8
multi-string enabled signatures: 8
multi-string retired signatures: 8
|
Router# show ip ips event-action-rules filters
Filters
Global Filters Status: Enabled
Router# show ip ips auto-update
IPS Auto Update Configuration
URL : tftp://192.168.0.2/jdoe/ips-auto-update/IOS_reqSeq-dw.xml
Username : not configured
Password : not configured
Auto Update Intervals
minutes (0-59) : 0
hours (0-23) : 0-23
days of month (1-31) : 1-31
days of week: (0-6) : 1-5
One of the common issues found when deploying Cisco IOS Software IPS sensors is the lack of router memory to accommodate the signature database. Use the show logging command to search the logs for %SYS-3-MALLOCFAIL error messages, as demonstrated in Example 13-16. Another Cisco IOS IPS message to search for that would indicate that the compilation of the signature package failed is the %IPS-3-ENGINE_BUILD_FAILED error message.
Example 13-16. show logging Command Output
Router# show logging
000167: Jun 27 20:50:10.019 NewYork: %SYS-2-MALLOCFAIL: Memory allocation of 8
bytes failed from 0x619282D8, alignment 0
Pool: Processor Free: 111022040 Cause: Interrupt level allocation
Alternate Pool: None Free: 0 Cause: Interrupt level allocation
-Process= "<interrupt level>", ipl= 1 -Traceback= 0x6299A28Cz 0x6377C2C0z
0x6191F720z 0x6034453Cz 0x60345290z
The debug ip ips auto-update command will debug the automatic update process. If all the previous troubleshooting steps have not solved the problem, the debug ip ips engine-name command can be used to debug the traffic inspection process used by a particular signature engine. This command should only be used in a test environment because its output is very verbose. Example 13-17 demonstrates output from the debug ip ips auto-update command.
Example 13-17. debug ip ips auto-update Output
Router# debug ip ips auto-update
Fail to connect to cisco.com
Nov 20 01:52:53.114: IPS Auto Update: ida_connect() failed.
Nov 20 01:52:53.114: IPS Auto-update: Request for download failed!
Nov 20 01:52:53.114: %IPS-4-IPS_AUTO_UPDATE_LOAD_FAILED: IPS Auto Update unable
to load IPS signature file from cisco
Nov 20 01:52:53.114: Timezone and summer-time offset in seconds = 3600
Nov 20 01:52:53.114: IPS Auto Update: setting update timer for next update: 1 hr
s 0 min
As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix C, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”
Review the most important topics in the chapter, noted with the Key Topics icon in the margin of the page. Table 13-5 lists a reference of these key topics and the page numbers on which each is found.

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work.
Define the following key terms from this chapter, and check your answers in the Glossary:
intrusion detection system (IDS)
intrusion prevention system (IPS)
Security Device Event Exchange (SDEE)
For additional information, refer to these resources:
Cisco Systems, Inc. Cisco Intrusion Prevention System: Introduction, www.cisco.com/go/ips.
Cisco Systems, Inc. Cisco IOS Security Command Reference, Release 15.0M, www.cisco.com/en/US/partner/docs/ios/security/command/reference/sec_book.html.
Cisco Systems, Inc. Cisco Intrusion Detection System Event Viewer 3DES Cryptographic Software Download, www.cisco.com/cgi-bin/tablebuild.pl/ids-ev.
Cisco Systems, Inc. Cisco IOS Security Configuration Guide, Release 12.4: Configuring Cisco IOS Intrusion Prevention System (IPS), www.cisco.com/en/US/docs/ios/security/configuration/guide/12_4/sec_12_4_book.html.
Wikipedia, Christmas Tree Packet, http://en.wikipedia.org/wiki/Christmas_tree_packet.