Acknowledgments |
|
xxi | |
Introduction |
|
xxiii | |
Exam Objective Map |
|
xxv | |
|
Part I Secure Software Concepts |
|
|
|
|
3 | (28) |
|
|
3 | (1) |
|
Implementing Confidentiality |
|
|
4 | (1) |
|
|
4 | (2) |
|
|
5 | (1) |
|
|
6 | (1) |
|
|
7 | (11) |
|
Multifactor Authentication |
|
|
9 | (1) |
|
|
9 | (2) |
|
|
11 | (1) |
|
|
11 | (1) |
|
|
11 | (1) |
|
|
11 | (1) |
|
|
12 | (1) |
|
|
12 | (1) |
|
Implementing Authentication |
|
|
12 | (3) |
|
|
15 | (3) |
|
|
18 | (1) |
|
Access Control Mechanisms |
|
|
19 | (1) |
|
Accountability (Auditing and Logging) |
|
|
19 | (3) |
|
|
21 | (1) |
|
|
22 | (1) |
|
|
22 | (1) |
|
Secure Development Lifecycle |
|
|
22 | (1) |
|
|
22 | (1) |
|
Security Features != Secure Software |
|
|
23 | (1) |
|
Secure Development Lifecycle Components |
|
|
23 | (3) |
|
Software Team Awareness and Education |
|
|
24 | (1) |
|
Gates and Security Requirements |
|
|
24 | (1) |
|
|
24 | (1) |
|
|
25 | (1) |
|
|
25 | (1) |
|
|
25 | (1) |
|
|
25 | (1) |
|
|
26 | (5) |
|
|
27 | (1) |
|
|
27 | (2) |
|
|
29 | (2) |
|
Chapter 2 Security Design Principles |
|
|
31 | (24) |
|
|
31 | (2) |
|
|
31 | (1) |
|
|
32 | (1) |
|
|
32 | (1) |
|
|
33 | (4) |
|
|
33 | (1) |
|
|
33 | (1) |
|
|
33 | (1) |
|
|
34 | (1) |
|
|
35 | (1) |
|
|
35 | (1) |
|
|
36 | (1) |
|
|
36 | (1) |
|
|
36 | (1) |
|
Psychological Acceptability |
|
|
36 | (1) |
|
|
37 | (1) |
|
Leverage Existing Components |
|
|
37 | (1) |
|
|
37 | (1) |
|
|
37 | (8) |
|
|
38 | (3) |
|
Multilevel Security Model |
|
|
41 | (1) |
|
|
42 | (1) |
|
|
43 | (2) |
|
|
45 | (4) |
|
|
45 | (1) |
|
|
46 | (2) |
|
|
48 | (1) |
|
|
49 | (6) |
|
|
50 | (1) |
|
|
50 | (2) |
|
|
52 | (3) |
|
Part II Secure Software Requirements |
|
|
|
Chapter 3 Define Software Security Requirements |
|
|
55 | (10) |
|
|
55 | (4) |
|
Role and User Definitions |
|
|
56 | (1) |
|
|
56 | (1) |
|
|
56 | (1) |
|
Subject-Object-Activity Matrix |
|
|
56 | (1) |
|
|
56 | (2) |
|
|
58 | (1) |
|
|
59 | (1) |
|
Operational and Deployment Requirements |
|
|
59 | (1) |
|
|
60 | (1) |
|
|
61 | (4) |
|
|
61 | (1) |
|
|
62 | (2) |
|
|
64 | (1) |
|
Chapter 4 Identify and Analyze Compliance Requirements |
|
|
65 | (28) |
|
Regulations and Compliance |
|
|
65 | (12) |
|
|
66 | (1) |
|
|
66 | (4) |
|
|
70 | (2) |
|
|
72 | (1) |
|
|
73 | (1) |
|
|
73 | (1) |
|
|
73 | (1) |
|
Payment Card Industry Data Security Standard |
|
|
73 | (1) |
|
|
74 | (1) |
|
|
74 | (1) |
|
|
74 | (3) |
|
|
77 | (4) |
|
|
77 | (1) |
|
|
78 | (1) |
|
|
78 | (1) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
81 | (1) |
|
|
81 | (8) |
|
|
82 | (1) |
|
Personally Identifiable Information |
|
|
83 | (1) |
|
Personal Health Information |
|
|
83 | (1) |
|
|
84 | (1) |
|
General Data Protection Regulation |
|
|
84 | (3) |
|
California Consumer Privacy Act 2018 (AB 375) |
|
|
87 | (1) |
|
Privacy-Enhancing Technologies |
|
|
87 | (1) |
|
|
88 | (1) |
|
|
88 | (1) |
|
|
88 | (1) |
|
|
89 | (1) |
|
|
89 | (1) |
|
|
89 | (4) |
|
|
90 | (1) |
|
|
90 | (2) |
|
|
92 | (1) |
|
Chapter 5 Misuse and Abuse Cases |
|
|
93 | (12) |
|
|
93 | (2) |
|
Requirements Traceability Matrix |
|
|
95 | (1) |
|
|
96 | (2) |
|
Definitions and Terminology |
|
|
96 | (1) |
|
|
96 | (1) |
|
|
96 | (1) |
|
Contractual Terms and Service Level Agreements |
|
|
97 | (1) |
|
Requirements Flow Down to Suppliers/Providers |
|
|
97 | (1) |
|
|
98 | (7) |
|
|
98 | (1) |
|
|
99 | (1) |
|
|
100 | (5) |
|
Part III Secure Software Architecture and Design |
|
|
|
Chapter 6 Secure Software Architecture |
|
|
105 | (28) |
|
|
105 | (8) |
|
|
105 | (5) |
|
Attack Surface Evaluation |
|
|
110 | (1) |
|
Attack Surface Measurement |
|
|
110 | (1) |
|
Attack Surface Minimization |
|
|
111 | (1) |
|
|
112 | (1) |
|
|
113 | (1) |
|
Define the Security Architecture |
|
|
113 | (16) |
|
Security Control Identification and Prioritization |
|
|
113 | (3) |
|
|
116 | (1) |
|
Service-Oriented Architecture |
|
|
117 | (2) |
|
|
119 | (1) |
|
Rich Internet Applications |
|
|
120 | (1) |
|
Pervasive/Ubiquitous Computing |
|
|
121 | (2) |
|
|
123 | (1) |
|
|
124 | (3) |
|
|
127 | (1) |
|
Hardware Platform Concerns |
|
|
127 | (1) |
|
|
128 | (1) |
|
|
129 | (1) |
|
|
129 | (4) |
|
|
129 | (1) |
|
|
130 | (2) |
|
|
132 | (1) |
|
Chapter 7 Secure Software Design |
|
|
133 | (24) |
|
Performing Secure Interface Design |
|
|
133 | (2) |
|
|
134 | (1) |
|
|
135 | (1) |
|
Performing Architectural Risk Assessment |
|
|
135 | (1) |
|
Model (Nonfunctional) Security Properties and Constraints |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
137 | (1) |
|
Evaluate and Select Reusable Secure Design |
|
|
137 | (13) |
|
Creating a Practical Reuse Plan |
|
|
137 | (1) |
|
|
138 | (3) |
|
|
141 | (1) |
|
|
142 | (1) |
|
|
143 | (1) |
|
|
143 | (2) |
|
|
145 | (2) |
|
Programming Language Environment |
|
|
147 | (2) |
|
Operating System Controls and Services |
|
|
149 | (1) |
|
Secure Backup and Restoration Planning |
|
|
149 | (1) |
|
Secure Data Retention, Retrieval, and Destruction |
|
|
150 | (1) |
|
Perform Security Architecture and Design Review |
|
|
150 | (1) |
|
Define Secure Operational Architecture |
|
|
151 | (1) |
|
Use Secure Architecture and Design Principles, Patterns, and Tools |
|
|
151 | (1) |
|
|
152 | (5) |
|
|
152 | (1) |
|
|
152 | (2) |
|
|
154 | (3) |
|
Part IV Secure Software Implementation |
|
|
|
Chapter 8 Secure Coding Practices |
|
|
157 | (24) |
|
Declarative vs. Imperative Security |
|
|
157 | (2) |
|
|
158 | (1) |
|
|
158 | (1) |
|
Handling Configuration Parameters |
|
|
159 | (1) |
|
|
159 | (1) |
|
|
160 | (1) |
|
|
160 | (1) |
|
|
160 | (1) |
|
|
161 | (1) |
|
|
161 | (1) |
|
Learning from Past Mistakes |
|
|
162 | (1) |
|
|
162 | (5) |
|
|
162 | (1) |
|
|
163 | (1) |
|
|
163 | (1) |
|
|
164 | (1) |
|
|
164 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
Psychological Acceptability |
|
|
166 | (1) |
|
|
166 | (1) |
|
Leverage Existing Components |
|
|
166 | (1) |
|
|
167 | (1) |
|
|
167 | (2) |
|
|
167 | (1) |
|
|
168 | (1) |
|
|
168 | (1) |
|
|
169 | (2) |
|
|
169 | (1) |
|
Missing Encryption of Sensitive Data |
|
|
169 | (1) |
|
Use of a Broken or Risky Cryptographic Algorithm |
|
|
170 | (1) |
|
Download of Code Without Integrity Check |
|
|
171 | (1) |
|
Use of a One-Way Hash Without a Salt |
|
|
171 | (1) |
|
Input Validation Failures |
|
|
171 | (4) |
|
|
172 | (1) |
|
|
173 | (1) |
|
Missing Defense Functions |
|
|
174 | (1) |
|
Output Validation Failures |
|
|
174 | (1) |
|
General Programming Failures |
|
|
175 | (1) |
|
|
175 | (1) |
|
|
176 | (1) |
|
|
177 | (4) |
|
|
177 | (1) |
|
|
178 | (2) |
|
|
180 | (1) |
|
Chapter 9 Analyze Code for Security Risks |
|
|
181 | (18) |
|
Code Analysis (Static and Dynamic) |
|
|
181 | (4) |
|
Static Application Security Testing |
|
|
182 | (1) |
|
Dynamic Application Security Testing |
|
|
183 | (1) |
|
Interactive Application Security Testing |
|
|
184 | (1) |
|
Runtime Application Self-Protection |
|
|
184 | (1) |
|
|
185 | (1) |
|
|
186 | (1) |
|
Additional Sources of Vulnerability Information |
|
|
186 | (1) |
|
CWE/SANS Top 25 Vulnerability Categories |
|
|
187 | (1) |
|
OWASP Vulnerability Categories |
|
|
188 | (1) |
|
Common Vulnerabilities and Countermeasures |
|
|
189 | (5) |
|
|
189 | (5) |
|
|
194 | (5) |
|
|
194 | (1) |
|
|
195 | (1) |
|
|
196 | (3) |
|
Chapter 10 Implement Security Controls |
|
|
199 | (18) |
|
|
199 | (1) |
|
Implement Security Controls |
|
|
200 | (1) |
|
Applying Security via the Build Environment |
|
|
201 | (1) |
|
Integrated Development Environment |
|
|
201 | (1) |
|
Anti-tampering Techniques |
|
|
202 | (2) |
|
|
202 | (1) |
|
Configuration Management: Source Code and Versioning |
|
|
203 | (1) |
|
|
204 | (1) |
|
Defensive Coding Techniques |
|
|
204 | (4) |
|
Declarative vs. Programmatic Security |
|
|
204 | (1) |
|
|
205 | (1) |
|
|
205 | (1) |
|
Handling Configuration Parameters |
|
|
206 | (1) |
|
|
206 | (1) |
|
|
207 | (1) |
|
|
208 | (1) |
|
Secure Integration of Components |
|
|
208 | (2) |
|
Secure Reuse of Third-Party Code or Libraries |
|
|
209 | (1) |
|
System-of-Systems Integration |
|
|
209 | (1) |
|
|
210 | (7) |
|
|
210 | (1) |
|
|
211 | (2) |
|
|
213 | (4) |
|
Part V Secure Software Testing |
|
|
|
Chapter 11 Security Test Cases |
|
|
217 | (12) |
|
|
217 | (1) |
|
Attack Surface Evaluation |
|
|
218 | (1) |
|
|
219 | (1) |
|
|
220 | (5) |
|
|
220 | (1) |
|
|
221 | (1) |
|
|
221 | (1) |
|
|
222 | (1) |
|
|
222 | (2) |
|
|
224 | (1) |
|
|
225 | (1) |
|
|
225 | (1) |
|
|
225 | (4) |
|
|
226 | (1) |
|
|
226 | (2) |
|
|
228 | (1) |
|
Chapter 12 Security Testing Strategy and Plan |
|
|
229 | (12) |
|
Develop a Security Testing Strategy and a Plan |
|
|
229 | (2) |
|
Functional Security Testing |
|
|
231 | (1) |
|
|
231 | (1) |
|
Nonfunctional Security Testing |
|
|
231 | (1) |
|
|
232 | (1) |
|
|
232 | (1) |
|
|
232 | (1) |
|
|
233 | (1) |
|
|
233 | (1) |
|
|
233 | (1) |
|
|
234 | (2) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
|
236 | (1) |
|
|
236 | (5) |
|
|
236 | (1) |
|
|
237 | (1) |
|
|
238 | (3) |
|
Chapter 13 Software Testing and Acceptance |
|
|
241 | (18) |
|
Perform Verification and Validation Testing |
|
|
242 | (5) |
|
Software Qualification Testing |
|
|
245 | (1) |
|
Qualification Testing Hierarchy |
|
|
246 | (1) |
|
Identify Undocumented Functionality |
|
|
247 | (1) |
|
Analyze Security Implications of Test Results |
|
|
247 | (1) |
|
Classify and Track Security Errors |
|
|
248 | (3) |
|
|
248 | (1) |
|
|
249 | (1) |
|
|
249 | (1) |
|
|
250 | (1) |
|
|
250 | (1) |
|
|
251 | (1) |
|
|
252 | (1) |
|
|
252 | (1) |
|
|
252 | (7) |
|
|
252 | (1) |
|
|
253 | (2) |
|
|
255 | (4) |
|
Part VI Secure Software Lifecycle Management |
|
|
|
Chapter 14 Secure Configuration and Version Control |
|
|
259 | (14) |
|
Secure Configuration and Version Control |
|
|
259 | (1) |
|
Define Strategy and Roadmap |
|
|
260 | (1) |
|
Manage Security Within a Software Development Methodology |
|
|
261 | (2) |
|
Security in Adaptive Methodologies |
|
|
261 | (1) |
|
Security in Predictive Methodologies |
|
|
262 | (1) |
|
Identify Security Standards and Frameworks |
|
|
263 | (1) |
|
Define and Develop Security Documentation |
|
|
264 | (1) |
|
|
264 | (1) |
|
|
265 | (2) |
|
|
266 | (1) |
|
|
267 | (1) |
|
|
267 | (1) |
|
|
268 | (5) |
|
|
268 | (1) |
|
|
269 | (2) |
|
|
271 | (2) |
|
Chapter 15 Software Risk Management |
|
|
273 | (12) |
|
Incorporate Integrated Risk Management |
|
|
273 | (4) |
|
Regulations and Compliance |
|
|
273 | (1) |
|
|
274 | (1) |
|
|
274 | (1) |
|
|
275 | (1) |
|
|
276 | (1) |
|
Technical Risk vs. Business Risk |
|
|
277 | (1) |
|
Promote Security Culture in Software Development |
|
|
277 | (1) |
|
|
278 | (1) |
|
Security Education and Guidance |
|
|
278 | (1) |
|
Implement Continuous Improvement |
|
|
278 | (1) |
|
|
279 | (6) |
|
|
279 | (1) |
|
|
280 | (2) |
|
|
282 | (3) |
|
Part VII Secure Software Deployment, Operations, Maintenance |
|
|
|
Chapter 16 Secure Software Deployment |
|
|
285 | (16) |
|
Perform Operational Risk Analysis |
|
|
285 | (4) |
|
|
287 | (1) |
|
|
288 | (1) |
|
|
288 | (1) |
|
|
289 | (1) |
|
Release Software Securely |
|
|
289 | (3) |
|
Secure Continuous Integration and Continuous Delivery Pipeline |
|
|
290 | (1) |
|
Secure Software Tool Chain |
|
|
291 | (1) |
|
Build Artifact Verification |
|
|
291 | (1) |
|
Securely Store and Manage Security Data |
|
|
292 | (1) |
|
|
292 | (1) |
|
|
293 | (1) |
|
|
293 | (1) |
|
|
293 | (1) |
|
Ensure Secure Installation |
|
|
293 | (3) |
|
|
294 | (1) |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
295 | (1) |
|
Security Policy Implementation |
|
|
296 | (1) |
|
|
296 | (1) |
|
Perform Post-Deployment Security Testing |
|
|
296 | (1) |
|
|
297 | (4) |
|
|
297 | (1) |
|
|
298 | (2) |
|
|
300 | (1) |
|
Chapter 17 Secure Software Operations and Maintenance |
|
|
301 | (16) |
|
Obtain Security Approval to Operate |
|
|
301 | (1) |
|
Perform Information Security Continuous Monitoring |
|
|
302 | (1) |
|
Collect and Analyze Security Observable Data |
|
|
302 | (1) |
|
|
302 | (1) |
|
Intrusion Detection/Response |
|
|
302 | (1) |
|
|
303 | (1) |
|
|
303 | (1) |
|
Support Incident Response |
|
|
303 | (3) |
|
|
304 | (1) |
|
|
305 | (1) |
|
|
305 | (1) |
|
|
306 | (1) |
|
Perform Vulnerability Management |
|
|
306 | (1) |
|
|
307 | (1) |
|
Support Continuity of Operations |
|
|
307 | (2) |
|
Backup, Archiving, Retention |
|
|
308 | (1) |
|
|
308 | (1) |
|
|
309 | (1) |
|
Integrate Service Level Objectives and Service Level Agreements |
|
|
309 | (1) |
|
|
310 | (7) |
|
|
311 | (1) |
|
|
312 | (1) |
|
|
313 | (4) |
|
Part VIII Secure Software Supply Chain |
|
|
|
Chapter 18 Software Supply Chain Risk Management |
|
|
317 | (10) |
|
Implement Software Supply Chain Risk Management |
|
|
317 | (1) |
|
Analyze Security of Third-Party Software |
|
|
318 | (1) |
|
Verify Pedigree and Provenance |
|
|
319 | (3) |
|
|
320 | (1) |
|
System Sharing/Interconnections |
|
|
320 | (1) |
|
|
321 | (1) |
|
Build Environment Security |
|
|
321 | (1) |
|
Cryptographically Hashed, Digitally Signed Components |
|
|
321 | (1) |
|
|
322 | (1) |
|
|
322 | (5) |
|
|
322 | (1) |
|
|
323 | (1) |
|
|
324 | (3) |
|
Chapter 19 Supplier Security Requirements |
|
|
327 | (18) |
|
Ensure Supplier Security Requirements in the Acquisition Process |
|
|
327 | (8) |
|
|
328 | (4) |
|
|
332 | (1) |
|
Audit of Security Policy Compliance |
|
|
333 | (1) |
|
Vulnerability/Incident Notification, Response, Coordination, and Reporting |
|
|
334 | (1) |
|
Maintenance and Support Structure |
|
|
334 | (1) |
|
|
334 | (1) |
|
Support Contractual Requirements |
|
|
335 | (3) |
|
|
335 | (3) |
|
|
338 | (1) |
|
|
338 | (7) |
|
|
338 | (1) |
|
|
339 | (2) |
|
|
341 | (4) |
|
Part IX Appendix and Glossary |
|
|
|
Appendix About the Online Content |
|
|
345 | (4) |
|
|
345 | (1) |
|
Your Total Seminars Training Hub Account |
|
|
345 | (1) |
|
|
345 | (1) |
|
Single User License Terms and Conditions |
|
|
345 | (2) |
|
|
347 | (1) |
|
|
347 | (2) |
Glossary |
|
349 | (20) |
Index |
|
369 | |