Other think you could do would be to isolate what exactly made it crash, document it, send it to Tivoli and after a (grace period of your choice) publish your findings.
After you find out what did it, don't run that test ;) maybe use a scanner plugin to identify the service and mark hostsos 'dead' so no other scans will happen. Many new vulnerabilities are discovered by security researchers against poorly designed services. One thing to let the client understand, is that nessus in 'safe mode' doesn't do much more than any user (or hacker) could do with nmap, telnet and a web browser. Whatever made those services crash is not nessus, but the Tivoli service not doing something right. Do a write up, help Tivoli clients avoid a DOS attack in the future. -- Michael Scheidell, CTO 561-999-5000, ext 1131 SECNAP Network Security Corporation Keep up to date with latest information on IT security: Real time security alerts: http://www.secnap.com/news _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
