- Paperback: 448 pages
- Publisher: Addison-Wesley Professional; 1 edition (February 2, 2006)
- Language: English
- ISBN-10: 0321356705
- ISBN-13: 978-0321356703
- Product Dimensions: 7 x 1.5 x 9.2 inches
- Shipping Weight: 1.9 pounds (View shipping rates and policies)
- Average Customer Review: 38 customer reviews
- Amazon Best Sellers Rank: #578,311 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Security: Building Security In 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Frequently bought together
Customers who bought this item also bought
"Overall, I rekon this was the best new security book I've seen this year. It certainly made me think more than any other security book I've read recently. I'd consider it a must-buy for the serious practitioner."--Ross Anderson, Professor of Security Engineering, University of Cambridge Computer Laboratory
From the Back Cover
This is the Mobipocket version of the print book. ""When it comes to software security, the devil is in the details. This book tackles the details." "
--Bruce Schneier, CTO and founder, Counterpane, and author of "Beyond Fear" and "Secrets and Lies" ""McGraw's book shows you how to make the 'culture of security' part of your development lifecycle.""
--Howard A. Schmidt, Former White House Cyber Security Advisor ""McGraw is leading the charge in software security. His advice is as straightforward as it is actionable. If your business relies on software (and whose doesn't), buy this book and post it up on the lunchroom wall.""
--Avi Rubin, Director of the NSF ACCURATE Center; Professor, Johns Hopkins University; and coauthor of "Firewalls and Internet Security" Beginning where the best-selling book "Building Secure Software" left off, "Software Security" teaches you how to put software security into practice.The software security best practices, or touchpoints, described in this book have their basis in good software engineering and involve explicitly pondering security throughout the software development lifecycle. This means knowing and understanding common risks (including implementation bugsand architectural flaws), designing for security, and subjecting all software artifacts to thorough, objective risk analyses and testing. "Software Security" is about putting the touchpoints to work for you. Because you can apply these touchpoints to the software artifacts you already produce as you develop software, you can adopt this book's methods without radically changing the way you work. Inside you'll find detailed explanations of
- Risk management frameworks and processes
- Code review using static analysis tools
- Architectural risk analysis
- Penetration testing
- Security testing
- Abuse case development
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The one space I see need for change is that this book addresses the traditional software development scenario. As more of the world moves to Agile and DevOps, this model will need to be adapted to fit into ever shrinking and more focused development cycles - I look forward to an update from Dr. McGraw on security for the DevOps world.
As it turns out Gary McGraw offered fortify as a freeware, and without properly identifying the impact on this product( the book), he sold the software to HP. This is another case of lack of thorough due diligence prior to closing mergers and acquisitions. Unfortunately as always is the case customers ( in this case the students) were the losers.
Of course, part of missed due diligence was our faculty that had not vetted if everything worked before conducting the course.
Good book if only updated with relevant tools.