Run fping against the subnet and output to a targets file. Then edit out the hosts in the targets file.
Christopher B. Karr, CISSP President ÜberGuard Information Security Consulting, LLC 91 Clinton St. Avon, NY 14414 Direct: (585) 226-2635 Mobile: (585) 703-9774 Fax: (585) 226-9329 [EMAIL PROTECTED] www.uberguard.com/ We protect your business to keep you in business Confidentiality Notice: The information contained in this e-mail and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josh Zlatin-Amishav Sent: Tuesday, November 22, 2005 4:35 AM To: Martin, Jared Cc: [email protected] Subject: Re: Exceptions in my targets file On Mon, 21 Nov 2005, Martin, Jared wrote: > I'm running batch scans weekly of my "10.0.10.255" subnet and I'd like > it to not scan a single IP ie:10.0.10.5. > Is there a way that I can specify that it not be scanned in my targets > file? I think the only way you can do this in the targets file is to specify each host separately and leave out 10.0.10.5. A better solution might be to setup a rule in the user's nessus account that does not allow them the scan 10.0.10.5. Something like: deny 10.0.10.5/32 default accept -- - Josh _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
