About the Author |
|
xxiii | |
About the Technical Reviewer |
|
xxv | |
Acknowledgments |
|
xxvii | |
Introduction |
|
xxix | |
|
Part I Getting a Handle on Things |
|
|
1 | (66) |
|
|
3 | (10) |
|
|
3 | (4) |
|
|
3 | (1) |
|
Regulated Industries That Require Audits |
|
|
4 | (1) |
|
Regulated Industries Without Explicit Audits |
|
|
4 | (1) |
|
Business Transactions Can Loop You into an Audit |
|
|
5 | (1) |
|
A Lawsuit May Drag You into Something Worse Than an Audit |
|
|
6 | (1) |
|
Business-to-Business Audits |
|
|
6 | (1) |
|
Will/Should You Audit Your IT Security Controls? |
|
|
6 | (1) |
|
|
7 | (1) |
|
The Burden of Audit Is on You |
|
|
7 | (1) |
|
Aim Higher Than Compliance |
|
|
7 | (1) |
|
|
7 | (2) |
|
Audits Make You Look Good |
|
|
8 | (1) |
|
The Audit as a Forcing Function |
|
|
8 | (1) |
|
|
9 | (2) |
|
|
9 | (1) |
|
|
9 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
What Is the Right Audit for You? |
|
|
11 | (2) |
|
|
13 | (10) |
|
The Lesson of Fort Pulaski |
|
|
13 | (3) |
|
|
13 | (2) |
|
|
15 | (1) |
|
New Exploit Technology Is Introduced |
|
|
15 | (1) |
|
The Complexity of IT Systems |
|
|
16 | (3) |
|
|
17 | (1) |
|
Complexity and Vulnerability |
|
|
18 | (1) |
|
Technical Vulnerabilities |
|
|
19 | (1) |
|
|
19 | (1) |
|
The Assume Breach Mindset |
|
|
20 | (3) |
|
Living in Assume Breach World |
|
|
20 | (3) |
|
Chapter 3 Risk Analysis: Assets and Impacts |
|
|
23 | (16) |
|
|
23 | (1) |
|
Risk Is Context Sensitive |
|
|
24 | (1) |
|
|
24 | (2) |
|
|
25 | (1) |
|
|
26 | (4) |
|
|
27 | (1) |
|
|
27 | (1) |
|
|
28 | (1) |
|
|
29 | (1) |
|
|
30 | (1) |
|
Qualitative vs. Quantitative |
|
|
30 | (6) |
|
|
30 | (1) |
|
Clarifying Your Qualitative |
|
|
30 | (4) |
|
|
34 | (2) |
|
Annualized Loss Expectancy |
|
|
36 | (1) |
|
Formalizing Your Risk Process |
|
|
36 | (3) |
|
Chapter 4 Risk Analysis: Natural Threats |
|
|
39 | (12) |
|
|
39 | (1) |
|
|
40 | (1) |
|
|
41 | (2) |
|
Modeling Impact with Failure Mode Effects Analysis |
|
|
43 | (4) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
Determining Failure Effects |
|
|
46 | (1) |
|
|
47 | (3) |
|
|
50 | (1) |
|
Chapter 5 Risk Analysis: Adversarial Risk |
|
|
51 | (16) |
|
|
51 | (1) |
|
|
52 | (1) |
|
Overview of Attacker Types |
|
|
52 | (1) |
|
Understanding Attacker Capability |
|
|
53 | (3) |
|
|
53 | (1) |
|
|
54 | (1) |
|
|
55 | (1) |
|
|
55 | (1) |
|
Understanding Attacker Incentives |
|
|
56 | (4) |
|
|
57 | (1) |
|
|
58 | (1) |
|
|
59 | (1) |
|
|
60 | (2) |
|
|
60 | (1) |
|
|
61 | (1) |
|
|
62 | (1) |
|
Building the Adversarial Risk Model |
|
|
62 | (5) |
|
|
62 | (2) |
|
|
64 | (3) |
|
Part II Wrangling the Organization |
|
|
67 | (64) |
|
|
69 | (12) |
|
|
69 | (2) |
|
Compliance Requirement Gathering |
|
|
71 | (3) |
|
|
71 | (2) |
|
|
73 | (1) |
|
|
73 | (1) |
|
Supporting Non-IT Departments |
|
|
73 | (1) |
|
|
73 | (1) |
|
|
74 | (1) |
|
|
74 | (1) |
|
Control Effectiveness and Efficiency |
|
|
75 | (1) |
|
|
75 | (1) |
|
|
76 | (3) |
|
|
77 | (1) |
|
|
78 | (1) |
|
|
78 | (1) |
|
|
79 | (2) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
79 | (2) |
|
|
81 | (18) |
|
|
82 | (1) |
|
|
82 | (1) |
|
|
83 | (7) |
|
The ISMS Steering Committee |
|
|
83 | (2) |
|
Duties of the ISMS Committee |
|
|
85 | (1) |
|
|
86 | (2) |
|
|
88 | (2) |
|
Obtain Executive Sponsorship |
|
|
90 | (1) |
|
Plan: Implement and Operate a Security Program |
|
|
90 | (1) |
|
Decide upon and Publish the Goals |
|
|
90 | (1) |
|
|
91 | (6) |
|
|
93 | (4) |
|
Check: Monitor and Review Security Program |
|
|
97 | (1) |
|
Act: Maintain and Improve Security Program |
|
|
98 | (1) |
|
Chapter 8 Talking to the Suits |
|
|
99 | (14) |
|
When Security Appears to be Anti-Business |
|
|
99 | (1) |
|
|
100 | (1) |
|
Understanding the Organization |
|
|
100 | (3) |
|
|
101 | (1) |
|
|
101 | (1) |
|
|
101 | (2) |
|
|
103 | (1) |
|
|
103 | (2) |
|
|
103 | (1) |
|
Don't Wander Outside Your Area of Expertise |
|
|
104 | (1) |
|
|
104 | (1) |
|
|
105 | (8) |
|
Proposing a Course of Action |
|
|
107 | (6) |
|
Chapter 9 Talking to the Techs |
|
|
113 | (10) |
|
|
114 | (1) |
|
|
115 | (3) |
|
The Infinitely Long IT Work Queue |
|
|
115 | (1) |
|
|
116 | (1) |
|
|
117 | (1) |
|
|
117 | (1) |
|
Working with Other Security Pros |
|
|
118 | (5) |
|
|
118 | (1) |
|
|
119 | (4) |
|
Chapter 10 Talking to the Users |
|
|
123 | (8) |
|
Specific Challenges for the Users |
|
|
123 | (2) |
|
|
124 | (1) |
|
Different Paradigm, Different Goals |
|
|
124 | (1) |
|
|
125 | (1) |
|
|
125 | (4) |
|
|
125 | (1) |
|
Let the Work Flow Smoothly |
|
|
126 | (1) |
|
|
127 | (1) |
|
|
128 | (1) |
|
Security Awareness Training |
|
|
129 | (2) |
|
Part III Managing Risk with Controls |
|
|
131 | (128) |
|
|
133 | (12) |
|
|
133 | (1) |
|
|
134 | (1) |
|
|
134 | (2) |
|
|
135 | (1) |
|
|
135 | (1) |
|
Policies Don't Have to Be Perfect |
|
|
135 | (1) |
|
Key Policy: Security Policy |
|
|
136 | (2) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
Expectations for User Behavior |
|
|
137 | (1) |
|
|
137 | (1) |
|
Key Policy: Acceptable Usage Policy |
|
|
138 | (5) |
|
|
139 | (1) |
|
|
139 | (1) |
|
|
139 | (1) |
|
|
139 | (1) |
|
|
139 | (1) |
|
|
140 | (1) |
|
|
140 | (1) |
|
Security Responsibilities |
|
|
140 | (1) |
|
|
140 | (1) |
|
Sample Acceptable Usage Policy |
|
|
141 | (2) |
|
|
143 | (2) |
|
Chapter 12 Control Design |
|
|
145 | (8) |
|
A Control Not Used Is a Control Wasted |
|
|
145 | (1) |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
146 | (1) |
|
Standardized and Measured |
|
|
147 | (1) |
|
|
147 | (1) |
|
|
147 | (1) |
|
|
148 | (2) |
|
|
148 | (1) |
|
|
149 | (1) |
|
Control Functions and Failures |
|
|
149 | (1) |
|
|
150 | (3) |
|
Reducing the Cost of Controls |
|
|
151 | (2) |
|
Chapter 13 Administrative Controls |
|
|
153 | (12) |
|
|
153 | (2) |
|
Capability Maturity Model |
|
|
154 | (1) |
|
The Power of Good Admin Controls |
|
|
155 | (1) |
|
|
155 | (1) |
|
Critical Admin Control: Asset Management |
|
|
156 | (1) |
|
Sample Asset Management Policy |
|
|
156 | (1) |
|
Sample Asset Management Standard |
|
|
156 | (1) |
|
Critical Admin Control: Change Control |
|
|
157 | (3) |
|
Sample Change Control Policy |
|
|
158 | (1) |
|
|
159 | (1) |
|
|
159 | (1) |
|
Critical Admin Control: Application Security |
|
|
160 | (2) |
|
Sample Application Security Policy |
|
|
160 | (1) |
|
Application Security Standards |
|
|
161 | (1) |
|
|
161 | (1) |
|
Critical Manual Control: Record and Media Management |
|
|
162 | (3) |
|
Sample Record and Media Management Policy |
|
|
162 | (3) |
|
Chapter 14 Vulnerability Management |
|
|
165 | (10) |
|
Organizing Vulnerability Management |
|
|
166 | (1) |
|
Sample Vulnerability Management Policy |
|
|
166 | (1) |
|
Vulnerability Management Breakdown of Responsibilities |
|
|
166 | (1) |
|
|
167 | (2) |
|
Sample Hardening and Vulnerability Management Standard |
|
|
167 | (1) |
|
How to Fill in the Hardening Standards? |
|
|
168 | (1) |
|
|
169 | (4) |
|
Vulnerability Notification |
|
|
169 | (1) |
|
|
169 | (2) |
|
|
171 | (1) |
|
|
172 | (1) |
|
Dynamic Application Testing |
|
|
172 | (1) |
|
Prioritization and Risk Scoring |
|
|
173 | (1) |
|
|
173 | (1) |
|
|
173 | (1) |
|
|
174 | (1) |
|
|
174 | (1) |
|
|
174 | (1) |
|
Chapter 15 People Controls |
|
|
175 | (12) |
|
|
175 | (1) |
|
Sample Human Resource Security Policy |
|
|
175 | (1) |
|
|
176 | (1) |
|
|
177 | (3) |
|
|
178 | (1) |
|
|
178 | (1) |
|
|
179 | (1) |
|
What to Do When There's a Problem |
|
|
180 | (1) |
|
|
180 | (1) |
|
|
181 | (1) |
|
Sanctions for Policy Violations |
|
|
181 | (1) |
|
Managing the Insider Threat |
|
|
182 | (2) |
|
|
182 | (1) |
|
|
183 | (1) |
|
|
183 | (1) |
|
|
183 | (1) |
|
|
184 | (1) |
|
|
184 | (1) |
|
Processes, Not Individuals |
|
|
184 | (3) |
|
Chapter 16 Logical Access Control |
|
|
187 | (10) |
|
|
187 | (1) |
|
Sample Logical Access Control Policy |
|
|
187 | (1) |
|
|
188 | (4) |
|
|
188 | (1) |
|
|
189 | (1) |
|
|
190 | (1) |
|
Multifactor Authentication |
|
|
190 | (1) |
|
|
190 | (2) |
|
|
192 | (2) |
|
Role-based Access Control |
|
|
192 | (2) |
|
|
194 | (1) |
|
Sample Authorization Standards |
|
|
194 | (1) |
|
|
194 | (1) |
|
|
195 | (2) |
|
Chapter 17 Network Security |
|
|
197 | (22) |
|
Understand Networking Technology |
|
|
197 | (1) |
|
|
198 | (8) |
|
|
199 | (1) |
|
|
200 | (1) |
|
Drive-by-Download Attacks |
|
|
200 | (1) |
|
Network Denial of Service |
|
|
201 | (1) |
|
|
202 | (2) |
|
|
204 | (1) |
|
|
204 | (1) |
|
|
205 | (1) |
|
|
206 | (13) |
|
Sample Network Security Policy |
|
|
206 | (2) |
|
Network Security Standards |
|
|
208 | (1) |
|
Network Security Procedures |
|
|
208 | (1) |
|
|
209 | (2) |
|
|
211 | (1) |
|
|
212 | (7) |
|
Chapter 18 More Technical Controls |
|
|
219 | (12) |
|
Internet Services Security |
|
|
219 | (5) |
|
|
219 | (2) |
|
|
221 | (2) |
|
|
223 | (1) |
|
|
224 | (3) |
|
Why Is Encryption Hard to Do? |
|
|
225 | (1) |
|
Storage Crypto Policy and Standards |
|
|
226 | (1) |
|
|
226 | (1) |
|
|
227 | (1) |
|
Anti-Malware Policy and Standards |
|
|
227 | (1) |
|
|
227 | (1) |
|
|
228 | (3) |
|
Chapter 19 Physical Security Controls |
|
|
231 | (8) |
|
Getting a Handle on Physical Security |
|
|
231 | (1) |
|
Physical Risk Assessments |
|
|
232 | (1) |
|
|
232 | (2) |
|
Sample Physical Security Policy |
|
|
233 | (1) |
|
|
234 | (1) |
|
|
234 | (1) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
|
236 | (1) |
|
Secured Facilities Controls |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
237 | (1) |
|
|
237 | (1) |
|
Media and Portable Media Controls |
|
|
237 | (1) |
|
|
237 | (1) |
|
|
238 | (1) |
|
Convergence of IT and Physical Security Controls |
|
|
238 | (1) |
|
Chapter 20 Response Controls |
|
|
239 | (20) |
|
|
239 | (5) |
|
|
240 | (1) |
|
|
240 | (1) |
|
|
241 | (2) |
|
|
243 | (1) |
|
|
244 | (1) |
|
Keep Backups Offsite and Safe |
|
|
244 | (1) |
|
|
244 | (1) |
|
|
245 | (1) |
|
|
245 | (1) |
|
Business Continuity Planning |
|
|
245 | (3) |
|
Sample Business Continuity Policy |
|
|
246 | (1) |
|
Expectations for Recovery |
|
|
246 | (1) |
|
Disaster Recovery Planning |
|
|
247 | (1) |
|
Incident Response Planning |
|
|
248 | (1) |
|
|
248 | (1) |
|
|
249 | (6) |
|
|
249 | (2) |
|
|
251 | (1) |
|
Procedures for Common Scenarios |
|
|
251 | (1) |
|
|
252 | (1) |
|
|
253 | (1) |
|
Legal Reporting Requirements |
|
|
253 | (1) |
|
Working with Law Enforcement |
|
|
254 | (1) |
|
Human Side of Incident Response |
|
|
254 | (1) |
|
|
255 | (4) |
|
|
255 | (1) |
|
|
256 | (1) |
|
|
256 | (3) |
|
|
259 | (42) |
|
Chapter 21 Starting the Audit |
|
|
261 | (14) |
|
|
261 | (2) |
|
|
263 | (1) |
|
We're All on the Same Side |
|
|
264 | (1) |
|
What Happens During Audit |
|
|
264 | (4) |
|
|
265 | (1) |
|
|
265 | (1) |
|
|
266 | (1) |
|
|
267 | (1) |
|
|
268 | (5) |
|
|
269 | (2) |
|
|
271 | (1) |
|
|
272 | (1) |
|
Disagreeing with Auditors |
|
|
273 | (2) |
|
Chapter 22 Internal Audit |
|
|
275 | (8) |
|
The Role of Internal Audit |
|
|
275 | (2) |
|
Internal Auditor Independence |
|
|
275 | (1) |
|
Internal Auditor Competence |
|
|
276 | (1) |
|
How Small Can the Role Go? |
|
|
277 | (1) |
|
|
277 | (1) |
|
Check Before the Auditors Check |
|
|
277 | (1) |
|
The Internal Audit Process |
|
|
278 | (5) |
|
|
278 | (3) |
|
|
281 | (1) |
|
|
281 | (2) |
|
Chapter 23 Third-Party Security |
|
|
283 | (10) |
|
Which Third Parties Are Relevant? |
|
|
283 | (1) |
|
Analysis of Third Parties |
|
|
284 | (3) |
|
|
284 | (1) |
|
Control Gap Analysis Approach |
|
|
285 | (1) |
|
|
286 | (1) |
|
Reading Their Audit Reports |
|
|
286 | (1) |
|
|
287 | (1) |
|
Controlling Third-Party Risk |
|
|
287 | (5) |
|
Sample Policy for Third-Party Management |
|
|
288 | (1) |
|
|
288 | (1) |
|
Security Service Agreements |
|
|
289 | (2) |
|
|
291 | (1) |
|
|
292 | (1) |
|
Chapter 24 Post Audit Improvement |
|
|
293 | (8) |
|
|
293 | (3) |
|
|
293 | (2) |
|
Reviewing What Didn't Work |
|
|
295 | (1) |
|
|
296 | (2) |
|
Looking for Systematic Issues |
|
|
297 | (1) |
|
Look for Things that Aren't Broken yet, but Will Be |
|
|
297 | (1) |
|
|
298 | (2) |
|
|
298 | (1) |
|
|
298 | (1) |
|
|
299 | (1) |
|
Rolling out a Change Plan |
|
|
299 | (1) |
|
We Can Never Stop Trying to Improve |
|
|
300 | (1) |
Index |
|
301 | |