Tip

Architectural Risk Analysis -- Chapter 5, Software Security: Building Security In


Software Security: Building Security In
By McGraw, Gary
Published by AWP
Series: Addison-Wesley Software Security Series
ISBN: 0321356705; Published: 1/29/2006; Copyright 2006; Pages: 448; Edition: 1
Click here for more information or to buy the book

    Requires Free Membership to View




As a registered member of SearchAppSecurity.com, you're entitled to a complimentary copy of Chapter 5 of Software Security: Building Security In written by Gary McGraw and published by Addison Wesley Professional. "Architectural Risk Analysis" helps you identify risk, thereby creating a good general-purpose measure of software security, especially if you track risk over time.



Book description:
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 touch points, 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 bugs and architectural flaws), designing for security, and subjecting all software artifacts to thorough, objective risk analyses and testing.

Software Security is about putting the touch points to work for you. Because you can apply these touch points 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 the following:

  • Risk management frameworks and processes
  • Code review using static analysis tools
  • Architectural risk analysis
  • Penetration testing
  • Security testing
  • Abuse case development

In addition to the touch points, Software Security covers knowledge management, training and awareness, and enterprise-level software security programs.

>> Read Chapter 5: Architectural Risk Analysis now.

>> Buy the book





This was first published in February 2006

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.