Product Description
“A fascinating look at the new direction fuzzing technology is taking — useful for both QA engineers and bug hunters alike!”
–Dave Aitel, CTO, Immunity Inc.
Learn the code cracker’s malicious mindset, so you can find worn-size holes in the software you are designing, testing, and building. Fuzzing for Software Security Testing and Quality Assurance takes a weapon from the black-hat arsenal to give you a powerful new tool to build secure, high-quality software. This practical resource helps you add extra protection without adding expense or time to already tight schedules and budgets. The book shows you how to make fuzzing a standard practice that integrates seamlessly with all development activities.
This comprehensive reference goes through each phase of software development and points out where testing and auditing can tighten security. It surveys all popular commercial fuzzing tools and explains how to select the right one for a software development project. The book also identifies those cases where commercial tools fall short and when there is a need for building your own fuzzing tools.
#1 by Robert Hudock on February 11, 2010 - 3:04 pm
Quote
Fuzzing generally involves testing the parameters of an application using random or specifically formatted randomized input to evaluate whether a given application crashes and/ or can be exploited. At least two of the authors have worked at the National Security Agency. Dr. Charlie Miller is well known for publishing an interesting article on the economics of the black market trading of security vulnerabilities (avaliable at weis2007.econinfosec.org/papers/29.pdf). Dr. Miller demonstrated the utility of the procedures discussed in this book at BlackHat 2008. This book provides insight into an area of research that is not usually publicly avaliable. The book details a number of open-source and commercially avaliable fuzzers and their relative reliability in finding bugs. Fuzzers are one of the most reliable methods for finding vulnerabilities in closed source programs. The book is conceptually accessible to an individual with some knowledge of secure programming and vulnerabilities.
Rating: 5 / 5
#2 by User 1138 on February 11, 2010 - 4:18 pm
Quote
The introduction to this book mentions its broken up history, being picked up and abandoned a couple times. It definitely shows in the writing, which is unfocused, choppy, and repetitive. Most of the first half is taken up with repetitive descriptions of the general software testing process. The second half contains a summary of one author’s thesis on using evolutionary algorithms for fuzzing and the final author’s use of various fuzzing tools to try to find hand-inserted vulnerabilities. While the latter half is better than the first, each topic is worthy of a single blog post. Given this book’s price and the authors’ reputations, I expected more.
At the same time, I read “Gray Hat Python” and it was enjoyable. Even though it had a much broader focus on other topics, it contained more hands-on info on fuzzing tools. I’m also interested in “Fuzzing: Brute Force Vulnerability Discovery”, although I have not read it yet.
Don’t waste your time on this book. Download the Sulley manual, read the slides from a few Blackhat talks, and you’ll be at the state of the art for current fuzzing knowledge.
Rating: 1 / 5