Nessus Network Auditing
Learn about this open-source vulnerability scanner, how to get the most out of the tool, recognize its limitations and how to deal with them, and what makes it flexible to perform a wide range of network-based operations.
TABLE OF CONTENTS Nessus Network Auditing
Frequently Asked Questions
The following Frequently Asked Questions, answered by the authors of this book, are designed to both measure your understanding of the concepts presented in this chapter and to assist you with real-life implementation of these concepts. To have your questions about this chapter answered by the author, browse to www.syngress.com/solutions and click on the Ask the Author form. You will also gain access to thousands of other FAQs at ITFAQnet.com.
| 1. | Is it feasible to scan my entire enterprise network periodically? |
|
| 2. | How often should those scans run? You discuss daily/weekly scans, but we can hardly cope with our current rate of quarterly network audits! |
|
| 3. | When dealing with other departments, I have difficulties explaining why a certain vulnerability needs to be addressed. This is especially true when dealing with knowledgeable technical people such as system administrators and programmers. How can I convince them that the problem is indeed serious and should be dealt with promptly? |
|
| 4. | How scalable are the solutions presented in this chapter? Will they work in my complicated network? |
|
Answers
| 1. | The question is not whether you should scan your entire network, it is whether you can afford not to scan it. Not knowing what vulnerabilities you have in your network is certainly not going to help you secure the organization. This chapter should give you some ideas on how to manage this obviously challenging task. |
| 2. | As noted earlier, the Sasser worm started spreading in just over three weeks... |
Copyright Syngress Publishing, Inc. 2004 under license agreement with Books24x7
