Software Security Engineering

Foreword xi Preface xiii About the Authors xxiii Chapter 1: Why Is Security a Software Issue? 1 1.1 Introduction 1 1.2 The Problem 2 1.3 Software Assurance and Software Security 6 1.4 Threats to Software Security 9 1.5 Sources of Software Insecurity 11 1.6 The Benefits of Detecting Software Security Defects Early 13 1.7 Managing Secure Software Development 18 1.8 Summary 23 Chapter 2: What Makes Software Secure? 25 2.1 Introduction 25 2.2 Defining Properties of Secure Software 26 2.3 How to Influence the Security Properties of Software 36 2.4 How to Assert and Specify Desired Security Properties 61 2.5 Summary 71 Chapter 3: Requirements Engineering for Secure Software 73 3.1 Introduction 73 3.2 Misuse and Abuse Cases 78 3.3 The SQUARE Process Model 84 3.4 SQUARE Sample Outputs 91 3.5 Requirements Elicitation 99 3.6 Requirements Prioritization 106 3.7 Summary 112 Chapter 4: Secure Software Architecture and Design 115 4.1 Introduction 115 4.2 Software Security Practices for Architecture and Design: Architectural Risk Analysis 119 4.3 Software Security Knowledge for Architecture and Design: Security Principles, Security Guidelines, and Attack Patterns 137 4.4 Summary 148 Chapter 5: Considerations for Secure Coding and Testing 151 5.1 Introduction 151 5.2 Code Analysis 152 5.3 Coding Practices 160 5.4 Software Security Testing 163 5.5 Security Testing Considerations Throughout the SDLC 173 5.6 Summary 180 Chapter 6: Security and Complexity: System Assembly Challenges 183 6.1 Introduction 183 6.2 Security Failures 186 6.3 Functional and Attacker Perspectives for Security Analysis: Two Examples 189 6.4 System Complexity Drivers and Security 203 6.5 Deep Technical Problem Complexity 215 6.6 Summary 217 Chapter 7: Governance, and Managing for More Secure Software 221 7.1 Introduction 221 7.2 Governance and Security 223 7.3 Adopting an Enterprise Software Security Framework 226 7.4 How Much Security Is Enough? 236 7.5 Security and Project Management 244 7.6 Maturity of

Julia H. Allen is a senior member of the technical staff within the CERTProgram at the Software Engineering Institute (SEI), a unit of Carnegie Mellon University in Pittsburgh, PA. In addition to her work in software security and assurance, Allen is engaged in developing and transitioning executive outreach programs in enterprise security and governance. She is the author of The CERT Guide to System and Network Security Practices (Addison-Wesley, 2001), Governing for Enterprise Security (CMU/SEI, 2005), and the CERT Podcast Series: Security for Business Leaders (2006/2007). Sean Barnum is a Principal Consultant at Cigital and is technical lead for their federal services practice. He has more than twenty years of experience in the software industry in the areas of development, software quality assurance, quality management, process architecture and improvement, knowledge management, and security. He is a frequent contributor and speaker for regional and national software security and software quality publications, conferences, and events. He is very active in the software assurance community and is involved in numerous knowledge standards-defining efforts, including the Common Weakness Enumeration (CWE), the Common Attack Pattern Enumeration and Classification (CAPEC), and other elements of the Software Assurance Programs of the Department of Homeland Security and the Department of Defense. He is also the lead technical subject matter expert for the Air Force Application Software Assurance Center of Excellence. Robert J. Ellison, Ph.D., is a member of the Survivable Systems Engineering Team within the CERTProgram at the Software Engineering Institute and, in that capacity, has served in a number of technical and management roles. He was a project leader for the evaluation of software engineering development environments and associated software development tools. He was also a member of the Carnegie Mellon University team that wrote the proposal for the SEI; he