Software Security Engineering: A Guide for Project Managers
Buy SSE on informIT

Software Security series
Buy the box set now!

Software Security series
The Software Security series

Software Security Engineering: A Guide for Project Managers
Buy the book!


August 20, 2008: Gary McGraw and Julia Allen discuss How to Start a Secure Software Development Program

July 8, 2008: Hear Julia Allen and Nancy Mead discuss the book on Identifying Software Security Requirements Early, Not After the Fact

May 11, 2008: Software Security Engineering is available - order it now!

Software Security Engineering

A Guide for Project Managers

Software that is developed from the beginning with security in mind will resist, tolerate, and recover from attacks more effectively than would otherwise be possible. While there may be no silver bullet for security, there are practices that project managers will find beneficial. With this management guide, you can select from a number of sound practices likely to increase the security and dependability of your software, both during its development and subsequently in its operation.

Software Security Engineering draws extensively on the systematic approach developed for the Build Security In (BSI) Web site. Sponsored by the Department of Homeland Security Software Assurance Program, the BSI site offers a host of tools, guidelines, rules, principles, and other resources to help project managers address security issues in every phase of the software development life cycle (SDLC). The book’s expert authors, themselves frequent contributors to the BSI site, represent two well-known resources in the security world: the CERT Program at the Software Engineering Institute (SEI) and Cigital, Inc., a consulting firm specializing in software security.

This book will help you understand why

  • Software security is about more than just eliminating vulnerabilities and conducting penetration tests
  • Network security mechanisms and IT infrastructure security services do not sufficiently protect application software from security risks
  • Software security initiatives should follow a risk-management approach to identify priorities and what is "good enough"—understanding that software security risks will change throughout the SDLC
  • Project managers and software engineers need to learn to think like an attacker in order to address the range of functions that software should not do, and how software can better resist, tolerate, and recover when under attack

Whether you are a project manager, lead requirements analyst, software architect, or systems integrator, you will learn how to manage the development of secure, software-intensive systems. You’ll also come away with the tools you need to identify and compare potential new practices that can be adapted to augment your current practices.