Core Software Security: Security at the Source
Format: PDF / Kindle (mobi) / ePub
"... an engaging book that will empower readers in both large and small software development and engineering organizations to build security into their products. ... Readers are armed with firm solutions for the fight against cyber threats."
―Dr. Dena Haritos Tsamitis. Carnegie Mellon University
"... a must read for security specialists, software developers and software engineers. ... should be part of every security professional’s library."
―Dr. Larry Ponemon, Ponemon Institute
"... the definitive how-to guide for software security professionals. Dr. Ransome, Anmol Misra, and Brook Schoenfield deftly outline the procedures and policies needed to integrate real security into the software development process. ...A must-have for anyone on the front lines of the Cyber War ..."
―Cedric Leighton, Colonel, USAF (Ret.), Cedric Leighton Associates
"Dr. Ransome, Anmol Misra, and Brook Schoenfield give you a magic formula in this book - the methodology and process to build security into the entire software development life cycle so that the software is secured at the source! "
―Eric S. Yuan, Zoom Video Communications
There is much publicity regarding network security, but the real cyber Achilles’ heel is insecure software. Millions of software vulnerabilities create a cyber house of cards, in which we conduct our digital lives. In response, security people build ever more elaborate cyber fortresses to protect this vulnerable software. Despite their efforts, cyber fortifications consistently fail to protect our digital treasures. Why? The security industry has failed to engage fully with the creative, innovative people who write software.
Core Software Security expounds developer-centric software security, a holistic process to engage creativity for security. As long as software is developed by humans, it requires the human element to fix it. Developer-centric security is not only feasible but also cost effective and operationally relevant. The methodology builds security into software development, which lies at the heart of our cyber infrastructure. Whatever development method is employed, software must be secured at the source.
- Supplies a practitioner's view of the SDL
- Considers Agile as a security enabler
- Covers the privacy elements in an SDL
- Outlines a holistic business-savvy SDL framework that includes people, process, and technology
- Highlights the key success factors, deliverables, and metrics for each phase of the SDL
- Examines cost efficiencies, optimized performance, and organizational structure of a developer-centric software security program and PSIRT
- Includes a chapter by noted security architect Brook Schoenfield who shares his insights and experiences in applying the book’s SDL framework
View the authors' website at http://www.androidinsecurity.com/
References xi 8.6 Chapter 9 9.0 9.1 Applying the SDL Framework to the Real World Introduction Build Software Securely 9.1.1 Produce Secure Code 9.1.2 Manual Code Review 9.1.3 Static Analysis 9.2 Determining the Right Activities for Each Project 9.2.1 The Seven Determining Questions 9.3 Architecture and Design 9.4 Testing 9.4.1 Functional Testing 9.4.2 Dynamic Testing 9.4.3 Attack and Penetration Testing 9.4.4 Independent Testing 9.5 Agile: Sprints 9.6 Key Success Factors and Metrics 9.6.1
Waterfall method, you are more likely to face an Agile approach to software development Plan Build Test Review Deploy Plan Build Test Review Deploy Figure 2.12 Iterative Waterfall software development methodology. The Secure Development Lifecycle 53 rather than either a standard or an iterative Waterfall methodology in today’s environment. 2.10.2 Agile Development The Agile approach is based on both iterative and incremental development methods. Requirements and solutions evolve
the most experience and expertise of any of the tasks within the SDL. Fortunately, tools are currently available and in the process of being developed that can assist this phase, and help leverage and scale a skill set that is typically a limited resource in a software security group. Additional security training that may be needed for key developers to understand the current threats and potential exploitations of their products, as well as training for secure design and coding techniques
SOFTWARE SECURITY SECURITY AT THE SOURCE K15922_FM.indd 1 11/5/13 11:22 AM K15922_FM.indd 2 11/5/13 11:22 AM CORE SOFTWARE SECURITY SECURITY AT THE SOURCE JAMES RANSOME ANMOL MISRA CONTRIBUTING AUTHOR (CHAPTER 9): BROOK SCHOENFIELD FOREWORD BY HOWARD SCHMIDT K15922_FM.indd 3 11/5/13 11:22 AM CRC Press Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 © 2014 by Taylor & Francis Group, LLC CRC Press is an imprint of Taylor & Francis Group, an
reviewed, because the goal is to maximize security as a default for a software product Architecture (A2): SDL Activities and Best Practices 129 that is being developed. Threat modeling uses a structured approach at a component-by-component level, identifying the assets that the software must manage and the interfaces by which those assets can be accessed. The likelihood of harm being done to any of the assets identified during threat modeling is estimated as a measure of risk. Countermeasures