Welcome to the Cisco Networking Professionals Ask the Expert conversation. This is an opportunity to get an update on Intrusion Prevention System with Scott Fringer. Scott Fringer is a Technical Assistance Center engineer on the intrusion detection system team in Research Triangle Park, North Carolina. His team supports Cisco's various intrusion detection/prevention sensors, the Cisco IOS IPS feature set, Cisco Security MARS, Cisco Security Manager, Cisco Security Agent, and the Cisco Anomaly Detector/Guard products. Fringer has represented the Technical Assistance Center at previous Networkers conferences and currently holds CCSP certification.
Remember to use the rating system to let Scott know if you have received an adequate response.
Scott might not be able to answer each question due to the volume expected during this event. Our moderators will post many of the unanswered questions in other discussion forums shortly after the event. This event lasts through September 24, 2010. Visit this forum often to view responses to your questions and the questions of other community members.
My IPS sensor is configured for automatically updating its signatures. Recently the updates stopped occurring, after working successfully. How can I correct this?
There are multiple causes for automatic IPS signature updates to stop functioning. Two quick CLI commands can help narrow the troubleshooting process. From the CLI of your sensor, issue the following command:
This command will allow you to check that the IPS sensor has a valid IPS services license. Specifically, you will note output similar to the following:
Cisco Intrusion Prevention System, Version 7.0(2)E3
Realm Keys key1.0
Signature Update S478.0 2010-05-20
OS Version: 2.4.30-IDS-smp-bigphysPlatform: IPS-4240-K9
Serial Number: JMX00000NS
Licensed, expired: 24-May-2010 UTC
If the license is expired (red text), you will need to work with your Cisco account team or partner to renew the IPS signature support for the IPS sensor. This will allow you to receive a new license key, which should restore signature update functionality.
One other culprit that can be verified from this output is that you are running the most recent analysis engine software for the IPS sensor (green text). Cisco's signature development team writes signatures to the current version of analysis engine. These signatures will not be compatible with older analysis engine releases. If you are not at the most recent analysis engine release, you can upgrade the IPS software to correct this issue.
If the license is not expired and you are running the current analysis engine release, the next command will help determine if there is a credential issue or potential connectivity issue:
show statistics host
At the very end of the output of this command is a section titled,"Auto Update Statistics", you will be able to see the results of the most recent automatic signature update attempt. This output may clearly indicate the credentials are invalid, there was a communication issue or there was not currently an update available (confusingly the output is "Success: No installable auto update package found on server"). Corrective action will need to be tailored to this output.
may I ask you:
1) if the IPS appliances (as other IPS solutions MCAFEE / TIPPING POINT/ ISS )...can drop and/or block the intruders IP without using "external cisco features products" (VLAN maps / ACLs/ shun /...) ?
2) when does tha IPS module for the ASA5505 will support the version 7.x ?
3) when does the IOS IPS will support the IPv6 IPS feature ?
Thanks in advance
To answer your questions:
1) Yes, Cisco's IPS appliances (and modules) can perform traffic denial actions directly on the sensor when configured for inline operation. These actions can deny a single packet, just the attacker, the attacker/victim pair, or the connection.
2) Current plans are in place for the AIP-SSC-5 to be supported in the 7.0(5) release of IPS software.
3) I am not currently aware of a time-frame to bring IPv6 support to the IOS IPS feature set.
Cisco just recently added AAA authentication support for the IPS. While this is a good start, it's limited to the CLI and IDM, and only supports RADIUS.
Thanks for all your help here on the forums, Scott!
Apologies, it appears my earlier reply via email did not post as expected.
At this time, I do no have any insight into the planning for implementation of either feature you mention.
I cannot provide insight into the decisions made from a product
development standpoint. My role is that of product support.
Thanks for doing this. My question is related to Global Correlation feature in IPS ver 7.x.
1. Is there a way to tell how many packets/sessions were actually dropped by this feature in say for example last 24 hrs?
2. Identify the related events generated so I can for example find out which internal machine tried to contact a botnet internet IP?
3. Any other reporting function which would actually indicate global correlation is playing a role in dropping malicious traffic?
The only place I see global correlation info is in the actual event generated but I am looking to see if there is a more generic reporting feature.
Global correlation brings two methods for responding to potential malicious activity:
When GC inspection is utilized, the IPS sensor will adjust the risk rating of a firing signature event based on the reputation score of the attacker IP address. When this action is taken, the details are included in the signature event details. So, you should be able to discern from the signature event both the GC inspection changes and actions taken by the sensor. This will be reported on a per-signature event basis.
When reputation filtering is utilized, there is no corresponding signature event fired when an attacker is denied; the sensor simply
denies the traffic. You can track the outcome of this activity from the sensor CLI by issuing:
show statistics analysis-engine
The last section of the analysis engine statistics covers global correlation activity. It is titled,"GlobalCorrelationStats" and will provide event counts and hosts that were determined as potentially malicious.
Within the IPS Device Manager GUI (IDM) you can add a gadget to the dashboard which provides a graph/table of the percentage of packets denied due to global correlation. It will present a segment for "Traditional IPS Detection", "Global Correlation Inspection" and "Reputation Filtering".
I have a 3750 series switch. WS-C3750-48TS-E
Wanted to know, does it support routing. Could you please explain the way we can differntiate the different 3750 series switches to support routing.
Could you please provide me the URL to know much about 3750 series switches.
Unfortunately, the Catalyst 3750 is not my area of expertise. You can find out all about the Catalyst 3750 series switches at the following link:
From the initial details on that page, it does appear the Catalyst 3750 supports various IP routing options.
I need Ip cache flow source and destination. What command would get an output like this on a switch or router: Source. Destination. Packets. Bytes 10..x.x.x 10..x.x.x 2 76 Thank you in advance Jay
Posted from my mobile device.
This is not a topic related to Cisco's IPS devices (my area of focus), and is not a question for which I can provide an answer.