Foreword |
|
xix | |
Preface |
|
xxi | |
Chapter 1 Cyber Security Engineering: Lifecycle Assurance of Systems and Software |
|
1 | (16) |
|
|
1 | (2) |
|
1.2 What Do We Mean by Lifecycle Assurance? |
|
|
3 | (3) |
|
1.3 Introducing Principles for Software Assurance |
|
|
6 | (4) |
|
1.4 Addressing Lifecycle Assurance |
|
|
10 | (3) |
|
1.5 Case Studies Used in This Book |
|
|
13 | (4) |
|
1.5.1 Wireless Emergency Alerts Case Study |
|
|
13 | (1) |
|
1.5.2 Fly-By-Night Airlines Case Study |
|
|
14 | (1) |
|
1.5.3 GoFast Automotive Corporation Case Study |
|
|
15 | (2) |
Chapter 2 Risk Analysis-Identifying and Prioritizing Needs |
|
17 | (22) |
|
2.1 Risk Management Concepts |
|
|
18 | (5) |
|
|
23 | (1) |
|
2.3 Mission Risk Analysis |
|
|
23 | (4) |
|
2.3.1 Task 1: Identify the Mission and Objective(s) |
|
|
24 | (1) |
|
2.3.2 Task 2: Identify Drivers |
|
|
25 | (1) |
|
2.3.3 Task 3: Analyze Drivers |
|
|
25 | (2) |
|
|
27 | (4) |
|
2.5 Security Risk Analysis |
|
|
31 | (7) |
|
2.6 Operational Risk Analysis-Comparing Planned to Actual |
|
|
38 | (1) |
|
|
38 | (1) |
Chapter 3 Secure Software Development Management and Organizational Models |
|
39 | (36) |
|
3.1 The Management Dilemma |
|
|
39 | (3) |
|
3.1.1 Background on Assured Systems |
|
|
40 | (2) |
|
3.2 Process Models for Software Development and Acquisition |
|
|
42 | (6) |
|
3.2.1 CMMI Models in General |
|
|
43 | (1) |
|
3.2.2 CMMI for Development (CMMI-DEV) |
|
|
44 | (1) |
|
3.2.3 CMMI for Acquisition (CMMI-ACQ) |
|
|
45 | (2) |
|
3.2.4 CMMI for Services (CMMI-SVC) |
|
|
47 | (1) |
|
3.2.5 CMMI Process Model Uses |
|
|
48 | (1) |
|
3.3 Software Security Frameworks, Models, and Roadmaps |
|
|
48 | (24) |
|
3.3.1 Building Security In Maturity Model (BSIMM) |
|
|
49 | (1) |
|
3.3.2 CMMI Assurance Process Reference Model |
|
|
50 | (3) |
|
3.3.3 Open Web Application Security Project (OWASP) Software Assurance Maturity Model (SAMM) |
|
|
53 | (2) |
|
3.3.4 DHS SwA Measurement Work |
|
|
55 | (3) |
|
3.3.5 Microsoft Security Development Lifecycle (SDL) |
|
|
58 | (2) |
|
3.3.6 SEI Framework for Building Assured Systems |
|
|
60 | (2) |
|
3.3.7 SEI Research in Relation to the Microsoft SDL |
|
|
62 | (1) |
|
3.3.8 CERT Resilience Management Model Resilient Technical Solution Engineering Process Area |
|
|
63 | (4) |
|
3.3.9 International Process Research Consortium (IPRC) Roadmap |
|
|
67 | (1) |
|
3.3.10 NIST Cyber Security Framework |
|
|
67 | (5) |
|
3.3.11 Uses of Software Security Frameworks, Models, and Roadmaps |
|
|
72 | (1) |
|
|
72 | (3) |
Chapter 4 Engineering Competencies |
|
75 | (22) |
|
4.1 Security Competency and the Software Engineering Profession |
|
|
75 | (2) |
|
4.2 Software Assurance Competency Models |
|
|
77 | (1) |
|
4.3 The DHS Competency Model |
|
|
78 | (3) |
|
|
78 | (1) |
|
4.3.2 Organization of Competency Areas |
|
|
79 | (1) |
|
4.3.3 SwA Competency Levels |
|
|
79 | (1) |
|
4.3.4 Behavioral Indicators |
|
|
80 | (1) |
|
4.3.5 National Initiative for Cybersecurity Education (NICE) |
|
|
80 | (1) |
|
4.4 The SEI Software Assurance Competency Model |
|
|
81 | (15) |
|
|
82 | (2) |
|
4.4.2 SwA Knowledge, Skills, and Effectiveness |
|
|
84 | (4) |
|
4.4.3 Competency Designations |
|
|
88 | (3) |
|
4.4.4 A Path to Increased Capability and Advancement |
|
|
91 | (1) |
|
4.4.5 Examples of the Model in Practice |
|
|
91 | (3) |
|
4.4.6 Highlights of the SEI Software Assurance Competency Model |
|
|
94 | (2) |
|
|
96 | (1) |
Chapter 5 Performing Gap Analysis |
|
97 | (18) |
|
|
97 | (1) |
|
5.2 Using the SEI's SwA Competency Model |
|
|
98 | (8) |
|
|
106 | (8) |
|
|
106 | (2) |
|
5.3.2 BSIMM Sample Report |
|
|
108 | (6) |
|
|
114 | (1) |
Chapter 6 Metrics |
|
115 | (20) |
|
6.1 How to Define and Structure Metrics to Manage Cyber Security Engineering |
|
|
115 | (8) |
|
6.1.1 What Constitutes a Good Metric? |
|
|
116 | (1) |
|
6.1.2 Metrics for Cyber Security Engineering |
|
|
117 | (4) |
|
6.1.3 Models for Measurement |
|
|
121 | (2) |
|
6.2 Ways to Gather Evidence for Cyber Security Evaluation |
|
|
123 | (12) |
|
|
123 | (4) |
|
6.2.2 Evidence from Standards |
|
|
127 | (5) |
|
6.2.3 Measurement Management |
|
|
132 | (3) |
Chapter 7 Special Topics in Cyber Security Engineering |
|
135 | (46) |
|
|
135 | (1) |
|
7.2 Security: Not Just a Technical Issue |
|
|
136 | (8) |
|
|
136 | (6) |
|
7.2.2 Two Examples of Security Governance |
|
|
142 | (1) |
|
|
143 | (1) |
|
7.3 Cyber Security Standards |
|
|
144 | (6) |
|
7.3.1 The Need for More Cyber Security Standards |
|
|
144 | (5) |
|
7.3.2 A More Optimistic View of Cyber Security Standards |
|
|
149 | (1) |
|
7.4 Security Requirements Engineering for Acquisition |
|
|
150 | (9) |
|
7.4.1 SQUARE for New Development |
|
|
151 | (1) |
|
7.4.2 SQUARE for Acquisition |
|
|
151 | (8) |
|
|
159 | (1) |
|
7.5 Operational Competencies (DevOps) |
|
|
159 | (12) |
|
|
159 | (2) |
|
7.5.2 DevOps Practices That Contribute to Improving Software Assurance |
|
|
161 | (7) |
|
7.5.3 DevOpsSec Competencies |
|
|
168 | (3) |
|
7.6 Using Malware Analysis |
|
|
171 | (9) |
|
7.6.1 Code and Design Flaw Vulnerabilities |
|
|
173 | (3) |
|
7.6.2 Malware-Analysis-Driven Use Cases |
|
|
176 | (3) |
|
7.6.3 Current Status and Future Research |
|
|
179 | (1) |
|
|
180 | (1) |
Chapter 8 Summary and Plan for Improvements in Cyber Security Engineering Performance |
|
181 | (8) |
|
|
181 | (2) |
|
8.2 Getting Started on an Improvement Plan |
|
|
183 | (4) |
|
|
187 | (2) |
References |
|
189 | (22) |
Bibliography |
|
211 | (2) |
Appendix A: WEA Case Study: Evaluating Security Risks Using Mission Threads |
|
213 | (14) |
Appendix B: The MSwA Body of Knowledge with Maturity Levels Added |
|
227 | (8) |
Appendix C: The Software Assurance Curriculum Project |
|
235 | (4) |
Appendix D: The Software Assurance Competency Model Designations |
|
239 | (10) |
Appendix E: Proposed SwA Competency Mappings |
|
249 | (30) |
Appendix F: BSIMM Assessment Final Report |
|
279 | (46) |
Appendix G: Measures from Lifecycle Activities, Security Resources, and Software Assurance Principles |
|
325 | (8) |
Index |
|
333 | |