Biography |
|
xix | |
|
|
1 | (22) |
|
1.1 The Role of the Information Security Manager |
|
|
1 | (2) |
|
1.1.1 Audit as a Driver for Security Initiatives |
|
|
2 | (1) |
|
1.1.2 Technology as a Driver for Security Initiatives |
|
|
2 | (1) |
|
1.1.3 Compliance as a Driver for Security Initiatives |
|
|
2 | (1) |
|
1.1.4 Security Risk as a Driver for Security Initiatives |
|
|
2 | (1) |
|
1.2 Ensuring a Quality Information Security Risk Assessment |
|
|
3 | (1) |
|
1.3 Security Risk Assessment |
|
|
3 | (8) |
|
1.3.1 The Role of the Security Risk Assessment |
|
|
4 | (1) |
|
1.3.2 Definition of a Security Risk Assessment |
|
|
5 | (2) |
|
1.3.3 The Need for a Security Risk Assessment |
|
|
7 | (1) |
|
1.3.3.1 Checks and Balances |
|
|
7 | (1) |
|
|
7 | (1) |
|
1.3.3.3 Risk-Based Spending |
|
|
8 | (2) |
|
|
10 | (1) |
|
1.3.4 Security Risk Assessment Secondary Benefits |
|
|
10 | (1) |
|
|
11 | (5) |
|
|
11 | (2) |
|
|
13 | (1) |
|
|
14 | (1) |
|
1.4.4 Vulnerability Scanning |
|
|
14 | (1) |
|
1.4.5 Penetration Testing |
|
|
15 | (1) |
|
|
15 | (1) |
|
|
15 | (1) |
|
|
15 | (1) |
|
1.5 The Need for This Book |
|
|
16 | (2) |
|
1.6 Who Is This Book For? |
|
|
18 | (5) |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
21 | (1) |
|
|
21 | (2) |
|
2 Information Security Risk Assessment Basics |
|
|
23 | (16) |
|
2.1 Phase 1: Project Definition |
|
|
23 | (2) |
|
2.2 Phase 2: Project Preparation |
|
|
25 | (1) |
|
2.3 Phase 3: Data Gathering |
|
|
25 | (1) |
|
2.4 Phase 4: Risk Analysis |
|
|
25 | (6) |
|
|
26 | (1) |
|
2.4.2 Threat Agents and Threats |
|
|
27 | (1) |
|
|
27 | (1) |
|
|
28 | (1) |
|
|
29 | (1) |
|
|
30 | (1) |
|
2.5 Phase 5: Risk Mitigation |
|
|
31 | (2) |
|
|
31 | (2) |
|
2.5.2 Residual Security Risk |
|
|
33 | (1) |
|
2.6 Phased: Risk Reporting and Resolution |
|
|
33 | (6) |
|
|
34 | (1) |
|
|
35 | (1) |
|
|
36 | (1) |
|
|
37 | (2) |
|
|
39 | (34) |
|
3.1 Ensuring Project Success |
|
|
39 | (23) |
|
|
40 | (1) |
|
3.1.1.1 Customer Satisfaction |
|
|
40 | (4) |
|
|
44 | (5) |
|
3.1.1.3 Completion within Budget |
|
|
49 | (1) |
|
|
50 | (1) |
|
3.1.3 Determining the Objective |
|
|
51 | (1) |
|
|
52 | (1) |
|
|
52 | (1) |
|
|
53 | (1) |
|
3.1.4.3 Security Controls |
|
|
54 | (1) |
|
|
55 | (1) |
|
3.1.4.5 Reasonableness in Limiting the Scope |
|
|
56 | (1) |
|
3.1.5 Identifying System Boundaries |
|
|
56 | (1) |
|
3.1.5.1 Physical Boundary |
|
|
57 | (1) |
|
3.1.5.2 Logical Boundaries |
|
|
58 | (2) |
|
3.1.6 Specifying the Rigor |
|
|
60 | (1) |
|
3.1.7 Sample Scope Statements |
|
|
60 | (2) |
|
|
62 | (11) |
|
|
62 | (1) |
|
|
63 | (1) |
|
3.2.2.1 Specifying the Service Description |
|
|
63 | (1) |
|
3.2.2.2 Scope of Security Controls |
|
|
63 | (1) |
|
3.2.2.3 Specifying Deliverables |
|
|
64 | (2) |
|
|
66 | (1) |
|
|
67 | (3) |
|
|
70 | (1) |
|
|
71 | (1) |
|
|
72 | (1) |
|
4 Security Risk Assessment Preparation |
|
|
73 | (38) |
|
|
73 | (5) |
|
4.1.1 Introductory Letter |
|
|
74 | (1) |
|
4.1.2 Pre-Assessment Briefing |
|
|
74 | (1) |
|
4.1.3 Obtain Proper Permission |
|
|
75 | (1) |
|
4.1.3.1 Policies Required |
|
|
76 | (1) |
|
4.1.3.2 Permission Required |
|
|
76 | (1) |
|
4.1.3.3 Scope of Permission |
|
|
77 | (1) |
|
4.1.3.4 Accounts Required |
|
|
78 | (1) |
|
4.2 Review Business Mission |
|
|
78 | (3) |
|
4.2.1 What Is a Business Mission? |
|
|
79 | (1) |
|
4.2.2 Obtaining Business Mission Information |
|
|
80 | (1) |
|
4.3 Identify Critical Systems |
|
|
81 | (4) |
|
4.3.1 Determining Criticality |
|
|
81 | (2) |
|
4.3.1.1 Approach 1: Find the Information Elsewhere |
|
|
83 | (1) |
|
4.3.1.2 Approach 2: Create the Information on a High Level |
|
|
83 | (1) |
|
4.3.1.3 Approach 3: Classify Critical Systems |
|
|
83 | (2) |
|
|
85 | (10) |
|
4.4.1 Checklists and Judgment |
|
|
86 | (1) |
|
4.4.2 Asset Sensitivity/Criticality Classification |
|
|
86 | (1) |
|
4.4.2.1 Approach 1: Find Asset Classification Information Elsewhere |
|
|
86 | (1) |
|
4.4.2.2 Approach 2: Create Asset Classification Information |
|
|
86 | (3) |
|
4.4.2.3 Approach 3: Determine Asset Criticality |
|
|
89 | (2) |
|
|
91 | (1) |
|
4.4.3.1 Approach 1: Binary Asset Valuation |
|
|
91 | (1) |
|
4.4.3.2 Approach 2: Classification-Based Asset Valuation |
|
|
91 | (1) |
|
4.4.3.3 Approach 3: Rank-Based Asset Valuation |
|
|
92 | (1) |
|
4.4.3.4 Approach 4: Consensus Asset Valuation |
|
|
93 | (1) |
|
4.4.3.5 Approaches 5-7: Accounting Valuation Approaches |
|
|
93 | (2) |
|
|
95 | (9) |
|
|
96 | (1) |
|
|
96 | (1) |
|
4.5.1.2 Undesirable Events |
|
|
96 | (1) |
|
4.5.2 Listing Possible Threats |
|
|
96 | (3) |
|
4.5.2.1 Checklists and Judgment |
|
|
99 | (1) |
|
4.5.2.2 Threat Agent and Undesirable Event Pairing |
|
|
99 | (2) |
|
|
101 | (1) |
|
4.5.4 Validating Threat Statements |
|
|
102 | (1) |
|
4.5.4.1 Factors Affecting Threat Statement Validity |
|
|
102 | (2) |
|
4.6 Determine Expected Controls |
|
|
104 | (7) |
|
|
108 | (1) |
|
|
108 | (2) |
|
|
110 | (1) |
|
|
110 | (1) |
|
|
111 | (34) |
|
|
112 | (5) |
|
5.1.1 Sampling Objectives |
|
|
114 | (1) |
|
|
115 | (1) |
|
5.1.3 Use of Sampling in Security Testing |
|
|
116 | (1) |
|
5.1.3.1 Approach 1: Representative Testing |
|
|
116 | (1) |
|
5.1.3.2 Approach 2: Selected Sampling |
|
|
116 | (1) |
|
5.1.3.3 Approach 3: Random Sampling |
|
|
117 | (1) |
|
5.2 The RIIOT Method of Data Gathering |
|
|
117 | (28) |
|
5.2.1 RIIOT Method Benefits |
|
|
118 | (1) |
|
5.2.2 RIIOT Method Approaches |
|
|
118 | (1) |
|
5.2.2.1 Review Documents or Designs |
|
|
119 | (6) |
|
5.2.2.2 Interview Key Personnel |
|
|
125 | (7) |
|
5.2.2.3 Inspect Security Controls |
|
|
132 | (2) |
|
5.2.2.4 Observe Personnel Behavior |
|
|
134 | (2) |
|
5.2.2.5 Test Security Controls |
|
|
136 | (4) |
|
5.2.3 Using the RIIOT Method |
|
|
140 | (1) |
|
|
141 | (1) |
|
|
141 | (2) |
|
|
143 | (2) |
|
6 Administrative Data Gathering |
|
|
145 | (70) |
|
6.1 Threats and Safeguards |
|
|
145 | (22) |
|
|
146 | (1) |
|
|
146 | (5) |
|
|
151 | (3) |
|
|
154 | (1) |
|
6.1.2 Organizational Structure |
|
|
154 | (1) |
|
6.1.2.1 Senior Management |
|
|
155 | (1) |
|
|
156 | (1) |
|
6.1.2.3 Security Operations |
|
|
156 | (1) |
|
|
157 | (1) |
|
6.1.3 Information Control |
|
|
158 | (1) |
|
|
158 | (1) |
|
|
159 | (1) |
|
|
160 | (1) |
|
6.1.3.4 Sensitive Information |
|
|
160 | (1) |
|
6.1.4 Business Continuity |
|
|
161 | (1) |
|
6.1.4.1 Contingency Planning |
|
|
162 | (1) |
|
6.1.4.2 Incident Response Program |
|
|
163 | (1) |
|
|
163 | (1) |
|
|
163 | (2) |
|
6.1.5.2 Application Security |
|
|
165 | (1) |
|
6.1.5.3 Configuration Management |
|
|
166 | (1) |
|
6.1.5.4 Third-Party Access |
|
|
166 | (1) |
|
6.2 The RIIOT Method: Administrative Data Gathering |
|
|
167 | (48) |
|
6.2.1 Review Administrative Documents |
|
|
173 | (1) |
|
6.2.1.1 Documents to Request |
|
|
173 | (1) |
|
6.2.1.2 Review Documents for Clarity, Consistency, and Completeness |
|
|
173 | (4) |
|
6.2.1.3 Reviewing Documents Other than Policies |
|
|
177 | (9) |
|
6.2.2 Interview Administrative Personnel |
|
|
186 | (1) |
|
6.2.2.1 Administrative Interview Topics |
|
|
186 | (1) |
|
6.2.2.2 Administrative Interview Subjects |
|
|
187 | (1) |
|
6.2.2.3 Administrative Interview Questions |
|
|
188 | (4) |
|
6.2.3 Inspect Administrative Security Controls |
|
|
192 | (1) |
|
6.2.3.1 Listing Administrative Security Controls |
|
|
192 | (1) |
|
6.2.3.2 Verify Information Gathered |
|
|
192 | (2) |
|
6.2.3.3 Determine Vulnerabilities |
|
|
194 | (1) |
|
6.2.3.4 Document and Review Findings |
|
|
194 | (1) |
|
6.2.3.5 Inspect the Security Organization |
|
|
194 | (5) |
|
6.2.4 Observe Administrative Behavior |
|
|
199 | (1) |
|
6.2.5 Test Administrative Security Controls |
|
|
200 | (1) |
|
6.2.5.1 Information Labeling Testing |
|
|
200 | (1) |
|
6.2.5.2 Media Destruction Testing |
|
|
200 | (7) |
|
6.2.5.3 Account and Access Control Procedures Testing |
|
|
207 | (2) |
|
6.2.5.4 Outsourcing and Information Exchange |
|
|
209 | (2) |
|
|
211 | (1) |
|
|
212 | (2) |
|
|
214 | (1) |
|
|
214 | (1) |
|
7 Technical Data Gathering |
|
|
215 | (72) |
|
7.1 Technical Threats and Safeguards |
|
|
215 | (16) |
|
7.1.1 Information Control |
|
|
215 | (1) |
|
|
215 | (4) |
|
7.1.1.2 Sensitive and Critical Information |
|
|
219 | (1) |
|
|
219 | (1) |
|
7.1.2 Business Continuity |
|
|
220 | (1) |
|
7.1.2.1 Contingency Planning |
|
|
221 | (1) |
|
|
221 | (1) |
|
|
221 | (1) |
|
7.1.3.2 Application Security |
|
|
222 | (1) |
|
7.1.3.3 Change Management |
|
|
223 | (1) |
|
7.1.4 Secure Architecture |
|
|
223 | (1) |
|
|
224 | (1) |
|
|
225 | (1) |
|
7.1.4.3 Perimeter Network |
|
|
226 | (1) |
|
|
227 | (1) |
|
|
227 | (1) |
|
7.1.5.2 Intrusion Detection |
|
|
228 | (1) |
|
|
229 | (1) |
|
|
229 | (1) |
|
|
230 | (1) |
|
|
230 | (1) |
|
|
230 | (1) |
|
7.2 The RIIOT Method: Technical Data Gathering |
|
|
231 | (56) |
|
7.2.1 Review Technical Documents |
|
|
231 | (1) |
|
7.2.1.1 Technical Documents to Request |
|
|
231 | (1) |
|
7.2.1.2 Review Technical Documents for Information |
|
|
231 | (5) |
|
7.2.1.3 Review Technical Security Designs |
|
|
236 | (12) |
|
7.2.2 Interview Technical Personnel |
|
|
248 | (1) |
|
7.2.2.1 Technical Interview Topics |
|
|
248 | (1) |
|
7.2.2.2 Technical Interview Subjects |
|
|
248 | (1) |
|
7.2.2.3 Technical Interview Questions |
|
|
248 | (1) |
|
7.2.3 Inspect Technical Security Controls |
|
|
249 | (2) |
|
7.2.3.1 List Technical Security Controls |
|
|
251 | (4) |
|
7.2.3.2 Verify Information Gathered |
|
|
255 | (7) |
|
7.2.3.3 Determine Vulnerabilities |
|
|
262 | (1) |
|
7.2.3.4 Document and Review Findings |
|
|
262 | (1) |
|
7.2.4 Observe Technical Personnel Behavior |
|
|
262 | (3) |
|
7.2.5 Test Technical Security Controls |
|
|
265 | (1) |
|
7.2.5.1 Monitoring Technology |
|
|
265 | (1) |
|
|
266 | (1) |
|
7.2.5.3 Anti-Virus Systems |
|
|
266 | (1) |
|
7.2.5.4 Automated Password Policies |
|
|
267 | (1) |
|
7.2.5.5 Virtual Private Network |
|
|
267 | (1) |
|
7.2.5.6 Firewalls, IDS, and System Hardening |
|
|
268 | (1) |
|
7.2.5.7 Vulnerability Scanning |
|
|
268 | (11) |
|
7.2.5.8 Penetration Testing |
|
|
279 | (1) |
|
7.2.5.9 Testing Specific Technology |
|
|
280 | (3) |
|
|
283 | (1) |
|
|
283 | (2) |
|
|
285 | (1) |
|
|
285 | (2) |
|
8 Physical Data Gathering |
|
|
287 | (78) |
|
8.1 Physical Threats and Safeguards |
|
|
288 | (37) |
|
8.1.1 Utilities and Interior Climate |
|
|
288 | (1) |
|
|
288 | (4) |
|
|
292 | (1) |
|
|
293 | (1) |
|
|
293 | (2) |
|
8.1.2.1 Fire Impact and Likelihood |
|
|
295 | (1) |
|
|
295 | (1) |
|
8.1.2.3 Fire Alarm Systems |
|
|
296 | (5) |
|
8.1.2.4 Fire Alarm Installation Types |
|
|
301 | (2) |
|
|
303 | (2) |
|
|
305 | (1) |
|
8.1.3 Flood and Water Damage |
|
|
306 | (2) |
|
|
308 | (1) |
|
|
309 | (1) |
|
|
310 | (1) |
|
|
310 | (1) |
|
|
310 | (2) |
|
|
312 | (1) |
|
8.1.10 Natural Hazards Summary |
|
|
312 | (1) |
|
8.1.11 Human Threats to Physical Security |
|
|
312 | (2) |
|
8.1.11.1 Personnel Screening |
|
|
314 | (1) |
|
|
315 | (1) |
|
|
316 | (1) |
|
8.1.11.4 Intrusion Detection |
|
|
317 | (4) |
|
8.1.11.5 Physical Access Control |
|
|
321 | (1) |
|
8.1.11.6 Preventing Unauthorized Entry |
|
|
321 | (4) |
|
8.1.11.7 Preventing Unauthorized Removal |
|
|
325 | (1) |
|
8.2 The RIIOT Method: Physical Data Gathering |
|
|
325 | (40) |
|
8.2.1 Review Physical Documents |
|
|
325 | (3) |
|
8.2.1.1 Physical Documents to Request |
|
|
328 | (1) |
|
8.2.1.2 Review Physical Documents for Information |
|
|
328 | (9) |
|
8.2.2 Interview Physical Personnel |
|
|
337 | (1) |
|
8.2.2.1 Physical Security Interview Topics |
|
|
337 | (1) |
|
8.2.2.2 Physical Security Interview Subjects |
|
|
337 | (1) |
|
8.2.2.3 Physical Security Interview Questions |
|
|
338 | (1) |
|
8.2.3 Inspect Physical Security Controls |
|
|
338 | (1) |
|
8.2.3.1 Listing Physical Security Controls |
|
|
338 | (3) |
|
8.2.3.2 Verify Information Gathered |
|
|
341 | (7) |
|
8.2.3.3 Determine Physical Vulnerabilities |
|
|
348 | (1) |
|
8.2.3.4 Document and Review Physical Findings |
|
|
348 | (1) |
|
8.2.4 Observe Physical Personnel Behavior |
|
|
348 | (4) |
|
8.2.5 Test Physical Security Safeguards |
|
|
352 | (1) |
|
|
352 | (1) |
|
8.2.5.2 Intrusion Detection |
|
|
352 | (1) |
|
|
352 | (10) |
|
|
362 | (1) |
|
|
363 | (2) |
|
|
365 | (16) |
|
9.1 Determining Security Risk |
|
|
365 | (9) |
|
9.1.1 Uncertainty and Reducing Uncertainty |
|
|
366 | (3) |
|
9.1.1.1 Review Available Data |
|
|
369 | (1) |
|
9.1.1.2 Examine Historical Data |
|
|
369 | (1) |
|
|
369 | (2) |
|
|
371 | (1) |
|
9.1.1.5 Use Conditional Probabilities |
|
|
371 | (3) |
|
9.2 Creating Security Risk Statements |
|
|
374 | (1) |
|
9.3 Team Review of Security Risk Statements |
|
|
375 | (6) |
|
9.3.1 Obtaining Consensus |
|
|
375 | (3) |
|
9.3.2 Deriving Overall Security Risk |
|
|
378 | (1) |
|
|
378 | (1) |
|
|
378 | (1) |
|
|
379 | (2) |
|
10 Security Risk Mitigation |
|
|
381 | (14) |
|
10.1 Selecting Safeguards |
|
|
381 | (2) |
|
10.1.1 Method 1: Missing Control Leads to Implementing Safeguard |
|
|
382 | (1) |
|
10.1.2 Method 2: People, Process, Technology |
|
|
382 | (1) |
|
10.1.3 Method 3: Administrative, Physical, Technical |
|
|
382 | (1) |
|
10.1.4 Method 4: Preventive, Detective, Corrective |
|
|
382 | (1) |
|
10.1.5 Method 5: Available Technology |
|
|
383 | (1) |
|
10.2 Safeguard Solution Sets |
|
|
383 | (6) |
|
10.2.1 Safeguard Cost Calculations |
|
|
385 | (1) |
|
10.2.2 Justifying Safeguard Selections |
|
|
386 | (1) |
|
10.2.2.1 Justification through Judgment |
|
|
386 | (1) |
|
10.2.2.2 Cost-Benefit Analysis |
|
|
387 | (2) |
|
10.3 Establishing Security Risk Parameters |
|
|
389 | (6) |
|
|
392 | (1) |
|
|
392 | (1) |
|
|
393 | (2) |
|
11 Security Risk Assessment Reporting |
|
|
395 | (14) |
|
11.1 Cautions in Reporting |
|
|
395 | (2) |
|
11.2 Pointers in Reporting |
|
|
397 | (1) |
|
|
397 | (3) |
|
11.3.1 Executive-Level Report |
|
|
398 | (1) |
|
|
398 | (1) |
|
11.3.3 Appendices and Exhibits |
|
|
399 | (1) |
|
11.4 Document Review Methodology: Create the Report Using a Top-Down Approach |
|
|
400 | (5) |
|
11.4.1 Document Specification |
|
|
401 | (3) |
|
|
404 | (1) |
|
|
405 | (1) |
|
|
405 | (1) |
|
|
406 | (3) |
|
|
406 | (1) |
|
|
407 | (1) |
|
|
407 | (1) |
|
|
407 | (2) |
|
12 Security Risk Assessment Project Management |
|
|
409 | (26) |
|
|
409 | (15) |
|
12.1.1 Project Definition |
|
|
409 | (1) |
|
12.1.2 Project Planning Details |
|
|
410 | (1) |
|
12.1.2.1 Project Phases and Activities |
|
|
410 | (1) |
|
12.1.2.2 Phases and Activities Scheduling |
|
|
411 | (1) |
|
12.1.2.3 Allocating Hours to Activities |
|
|
412 | (1) |
|
|
413 | (1) |
|
12.1.3.1 Objectivity vs. Independence |
|
|
413 | (2) |
|
12.1.3.2 Internal vs. External Team Members |
|
|
415 | (1) |
|
|
416 | (1) |
|
|
416 | (1) |
|
12.1.3.5 Team Member Skills |
|
|
416 | (8) |
|
|
424 | (4) |
|
|
424 | (1) |
|
12.2.2 Calendar Time Tracking |
|
|
424 | (3) |
|
12.2.3 Project Progress Tracking |
|
|
427 | (1) |
|
12.3 Taking Corrective Measures |
|
|
428 | (2) |
|
12.3.1 Obtaining More Resources |
|
|
428 | (1) |
|
12.3.2 Using Management Reserve |
|
|
428 | (2) |
|
12.4 Project Status Reporting |
|
|
430 | (1) |
|
|
430 | (1) |
|
|
430 | (1) |
|
12.4.3 Status Report Content |
|
|
431 | (1) |
|
12.5 Project Conclusion and Wrap-Up |
|
|
431 | (4) |
|
12.5.1 Eliminating "Scope Creep" |
|
|
431 | (1) |
|
12.5.2 Eliminating Project Run-On |
|
|
432 | (1) |
|
|
432 | (1) |
|
|
433 | (1) |
|
|
433 | (2) |
|
13 Security Risk Assessment Approaches |
|
|
435 | (20) |
|
13.1 Quantitative vs. Qualitative Analysis |
|
|
436 | (10) |
|
13.1.1 Quantitative Analysis |
|
|
436 | (1) |
|
|
437 | (1) |
|
13.1.1.2 Single Loss Expectancy |
|
|
437 | (1) |
|
13.1.1.3 Annualized Loss Expectancy |
|
|
438 | (1) |
|
|
438 | (1) |
|
13.1.1.5 Quantitative Analysis Advantages |
|
|
439 | (2) |
|
13.1.1.6 Quantitative Analysis Disadvantages |
|
|
441 | (2) |
|
13.1.2 Qualitative Analysis |
|
|
443 | (1) |
|
13.1.2.1 Qualitative Analysis Advantages |
|
|
444 | (2) |
|
13.1.2.2 Qualitative Analysis Disadvantages |
|
|
446 | (1) |
|
|
446 | (1) |
|
|
447 | (1) |
|
|
447 | (1) |
|
13.3 Security Risk Assessment Methods |
|
|
447 | (8) |
|
13.3.1 FAA Security Risk Management Process |
|
|
448 | (1) |
|
|
448 | (1) |
|
|
448 | (3) |
|
|
451 | (1) |
|
|
451 | (1) |
|
|
451 | (1) |
|
|
452 | (1) |
|
|
452 | (3) |
Index |
|
455 | |