| | |  | Software Engineering | Home » » » Fuzzing for Software Security Testing and Quality Assurance (Artech House Information Security and Privacy) | | | | | | | Description: | | "Fuzzing for Software Security Testing and Quality Assurance" gives software developers a powerful new tool to build secure, high-quality software, and takes a weapon from the malicious hackers' arsenal. This practical resource helps developers think like a software cracker, so they can find and patch flaws in software before harmful viruses, worms, and Trojans can use these vulnerabilities to rampage systems. Traditional software programmers and testers learn how to make fuzzing a standard practice that integrates seamlessly with all development activities. The book progresses 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 covers those cases where commercial tools fall short and developers need to build their own custom fuzzing tools. | | | Product Details: | | | Author:
| Ari Takanen | | Hardcover:
| 287 pages | | Publisher:
| Artech House Print on Demand | | Publication Date:
| June 30, 2008 | | Language:
| English | | ISBN:
| 1596932147 | | Product Length:
| 10.3 inches | | Product Width:
| 7.16 inches | | Product Height:
| 0.88 inches | | Product Weight:
| 1.55 pounds | | Package Length:
| 10.2 inches | | Package Width:
| 7.2 inches | | Package Height:
| 0.8 inches | | Package Weight:
| 1.55 pounds | | Average Customer Rating:
|  based on 2 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
 ( 2 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
5 of 5 found the following review helpful:
 Disappointing and a messJun 17, 2009
By User 1138
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.
2 of 4 found the following review helpful:
 One of the Best Resources on Fuzzing by Highly Skilled ex-NSA EmployeesAug 08, 2008
By Robert
"Linux User, Attorney, Hacker"
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.
| | |
|
