Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security ISSForum
[Top] [All Lists]

[ISSForum] Alert on sensor "Not Responding"

Subject: [ISSForum] Alert on sensor "Not Responding"
Date: Tue, 24 May 2005 09:46:09 +0100
How can I setup ISS SP2.0 to alert whenever a sensor is seen as "Not
Responding" in the console view?

We have a number of NIDS that occassionally fail, but the issDaemon and
issCSF et al. serives are still running on the NIDS, but the events are
not being sent back to the console.   It would be of benefit if we could
be alerted to this fact via SNMP.

Or are we looking at a shell script to capture the heartbeat/stats events
and to determine whether one has been seen in the last 10mins or so?  We
have all the alerting turned on, in the event collector prefences at the
moment.

How does everyone else do this on the list?

best regards,

Nick.

yes, i didnt email from my work account  ;-)  I am that paraniod
_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security Systems, 
6303 Barfield Road, Atlanta, Georgia, USA 30328.

<Prev in Thread] Current Thread [Next in Thread>