Foreword |
|
xxiii | |
Introduction |
|
xxv | |
|
Chapter 1 Understanding the Bigger Picture |
|
|
1 | (50) |
|
Evolving Threat Landscape |
|
|
2 | (6) |
|
Identifying Threat Actors |
|
|
2 | (2) |
|
|
4 | (1) |
|
Cyberattack Preparation Framework |
|
|
5 | (1) |
|
Cyberattack Execution Framework |
|
|
6 | (2) |
|
Defining Cyber Breach Response |
|
|
8 | (5) |
|
Events, Alerts, Observations, Incidents, and Breaches |
|
|
9 | (1) |
|
|
9 | (1) |
|
|
9 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
|
11 | (1) |
|
What Is Cyber Breach Response? |
|
|
12 | (1) |
|
Identifying Drivers for Cyber Breach Response |
|
|
13 | (10) |
|
|
13 | (1) |
|
Conducting Risk Management |
|
|
13 | (1) |
|
|
14 | (3) |
|
|
17 | (1) |
|
Cyber Threat Intelligence |
|
|
18 | (1) |
|
What Is Cyber Threat Intelligence? |
|
|
18 | (1) |
|
Importance of Cyber Threat Intelligence |
|
|
19 | (1) |
|
|
20 | (1) |
|
Compliance Considerations |
|
|
20 | (1) |
|
Compliance Requirements for Cyber Breach Response |
|
|
21 | (1) |
|
Changing Business Objectives |
|
|
22 | (1) |
|
Incorporating Cyber Breach Response into a Cybersecurity Program |
|
|
23 | (4) |
|
|
23 | (1) |
|
|
24 | (1) |
|
Implementing Program Components |
|
|
25 | (1) |
|
|
26 | (1) |
|
|
27 | (1) |
|
|
27 | (13) |
|
|
28 | (1) |
|
|
28 | (2) |
|
|
30 | (2) |
|
|
32 | (1) |
|
Vision and Mission Statement |
|
|
32 | (1) |
|
|
33 | (1) |
|
Establishing Requirements |
|
|
33 | (2) |
|
Defining a Target Operating Model |
|
|
35 | (1) |
|
Developing a Business Case and Executive Alignment |
|
|
35 | (2) |
|
|
37 | (1) |
|
Enacting an Incident Response Policy |
|
|
37 | (1) |
|
Assigning an Incident Response Team |
|
|
38 | (1) |
|
Creating an Incident Response Plan |
|
|
38 | (1) |
|
Documenting Legal Requirements |
|
|
38 | (1) |
|
|
39 | (1) |
|
|
40 | (6) |
|
|
40 | (1) |
|
Enterprise Security Policy |
|
|
41 | (1) |
|
|
41 | (1) |
|
Identifying Key Stakeholders |
|
|
42 | (1) |
|
|
42 | (1) |
|
Project Steering Committee |
|
|
42 | (1) |
|
Chief Information Security Officer |
|
|
43 | (1) |
|
Stakeholders with Interest in Cyber Breach Response |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
44 | (1) |
|
Necessity to Determine if the Program Is Effective |
|
|
45 | (1) |
|
Changing Threat Landscape |
|
|
45 | (1) |
|
Changing Business Objectives |
|
|
45 | (1) |
|
|
46 | (1) |
|
|
47 | (4) |
|
Chapter 2 Building a Cybersecurity Incident Response Team |
|
|
51 | (46) |
|
|
51 | (4) |
|
|
52 | (1) |
|
The Role of a CSIRT in the Enterprise |
|
|
52 | (3) |
|
Defining Incident Response Competencies and Functions |
|
|
55 | (6) |
|
|
55 | (1) |
|
Developing and Maintaining Procedures |
|
|
56 | (1) |
|
Conducting Incident Response Exercises |
|
|
56 | (1) |
|
Assisting with Vulnerability Identification |
|
|
57 | (1) |
|
Deploying, Developing, and Tuning Tools |
|
|
58 | (1) |
|
Implementing Lessons Learned |
|
|
59 | (1) |
|
|
59 | (1) |
|
Digital Forensics and Incident Response |
|
|
59 | (1) |
|
Cyber Threat Intelligence |
|
|
60 | (1) |
|
|
60 | (1) |
|
|
61 | (1) |
|
Creating an Incident Response Team |
|
|
61 | (17) |
|
Creating an Incident Response Mission Statement |
|
|
62 | (1) |
|
|
62 | (1) |
|
|
63 | (1) |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
66 | (1) |
|
Organizing an Incident Response Team |
|
|
66 | (1) |
|
|
66 | (2) |
|
|
68 | (1) |
|
Hiring and Training Personnel |
|
|
69 | (1) |
|
|
69 | (2) |
|
|
71 | (1) |
|
Pros and Cons of Security Certifications |
|
|
72 | (1) |
|
Conducting Effective Interviews |
|
|
73 | (1) |
|
Retaining Incident Response Talent |
|
|
74 | (1) |
|
|
75 | (1) |
|
|
75 | (1) |
|
|
76 | (1) |
|
|
76 | (1) |
|
|
76 | (1) |
|
Introducing an Incident Response Team to the Enterprise |
|
|
77 | (1) |
|
|
78 | (4) |
|
Defining a Coordination Model |
|
|
78 | (2) |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
81 | (1) |
|
Assigning Roles and Responsibilities |
|
|
82 | (8) |
|
|
82 | (1) |
|
|
82 | (1) |
|
|
83 | (1) |
|
|
83 | (1) |
|
|
84 | (1) |
|
|
85 | (1) |
|
|
85 | (1) |
|
|
85 | (1) |
|
|
86 | (1) |
|
Information Technology Functions |
|
|
87 | (1) |
|
|
87 | (1) |
|
|
88 | (1) |
|
Outsourcing Partners and Vendors |
|
|
89 | (1) |
|
|
89 | (1) |
|
Working with Outsourcing Partners |
|
|
90 | (4) |
|
Outsourcing Considerations |
|
|
91 | (1) |
|
Proven Track Record of Success |
|
|
91 | (1) |
|
Offered Services and Capabilities |
|
|
91 | (1) |
|
|
92 | (1) |
|
|
92 | (1) |
|
Outsourcing Costs and Pricing Models |
|
|
92 | (1) |
|
Establishing Successful Relationships with Vendors |
|
|
93 | (1) |
|
|
94 | (1) |
|
|
95 | (2) |
|
Chapter 3 Technology Considerations in Cyber Breach Investigations |
|
|
97 | (46) |
|
|
98 | (4) |
|
Comparing Commercial vs. Open Source Tools |
|
|
98 | (1) |
|
|
98 | (1) |
|
|
98 | (1) |
|
|
99 | (1) |
|
Developing In-House Software Tools |
|
|
100 | (1) |
|
|
101 | (1) |
|
|
102 | (11) |
|
|
102 | (1) |
|
|
103 | (1) |
|
|
103 | (2) |
|
System Memory Acquisition |
|
|
105 | (1) |
|
|
106 | (1) |
|
Forensic Acquisition Use Cases |
|
|
107 | (1) |
|
|
108 | (1) |
|
Live Response Considerations |
|
|
109 | (1) |
|
|
109 | (3) |
|
|
112 | (1) |
|
Incident Response Investigations in Virtualized Environments |
|
|
113 | (5) |
|
Traditional Virtualization |
|
|
115 | (1) |
|
|
115 | (1) |
|
|
115 | (2) |
|
Log Management in Cloud Computing Environments |
|
|
117 | (1) |
|
Leveraging Network Data in Investigations |
|
|
118 | (5) |
|
Firewall Logs and Network Flows |
|
|
118 | (2) |
|
Proxy Servers and Web Gateways |
|
|
120 | (1) |
|
|
120 | (3) |
|
Identifying Forensic Evidence in Enterprise Technology Services |
|
|
123 | (7) |
|
|
123 | (2) |
|
Dynamic Host Configuration Protocol |
|
|
125 | (1) |
|
|
125 | (1) |
|
|
126 | (1) |
|
|
127 | (1) |
|
Intrusion Detection and Prevention Systems |
|
|
127 | (1) |
|
Web Application Firewalls |
|
|
127 | (1) |
|
Data Loss Prevention Systems |
|
|
128 | (1) |
|
|
128 | (1) |
|
Endpoint Detection and Response |
|
|
129 | (1) |
|
|
129 | (1) |
|
|
130 | (10) |
|
|
130 | (2) |
|
|
132 | (1) |
|
|
133 | (1) |
|
|
134 | (1) |
|
Agent-Based vs. Agentless Collection |
|
|
134 | (1) |
|
Log Management Architectures |
|
|
135 | (2) |
|
Managing Logs with a SIEM |
|
|
137 | (1) |
|
|
138 | (1) |
|
|
139 | (1) |
|
|
140 | (1) |
|
|
141 | (2) |
|
Chapter 4 Crafting an Incident Response Plan |
|
|
143 | (52) |
|
Incident Response Lifecycle |
|
|
143 | (7) |
|
Preparing for an Incident |
|
|
144 | (1) |
|
Detecting and Analyzing Incidents |
|
|
145 | (1) |
|
|
146 | (1) |
|
|
146 | (1) |
|
Containment, Eradication, and Recovery |
|
|
147 | (1) |
|
|
147 | (1) |
|
Eradicating a Threat Actor |
|
|
148 | (1) |
|
Recovering Business Operations |
|
|
149 | (1) |
|
|
149 | (1) |
|
Understanding Incident Management |
|
|
150 | (10) |
|
Identifying Process Components |
|
|
151 | (1) |
|
|
151 | (2) |
|
|
153 | (2) |
|
|
155 | (1) |
|
|
155 | (3) |
|
Roles and Responsibilities |
|
|
158 | (1) |
|
|
159 | (1) |
|
Incident Management Workflow |
|
|
160 | (11) |
|
Sources of Incident Notifications |
|
|
160 | (2) |
|
Incident Classification and Documentation |
|
|
162 | (1) |
|
|
163 | (1) |
|
|
163 | (4) |
|
Capturing Incident Information |
|
|
167 | (2) |
|
|
169 | (1) |
|
|
169 | (1) |
|
|
169 | (1) |
|
Creating and Managing Tasks |
|
|
169 | (1) |
|
|
170 | (1) |
|
|
171 | (1) |
|
Crafting an Incident Response Playbook |
|
|
171 | (6) |
|
|
171 | (2) |
|
Identifying Workflow Components |
|
|
173 | (1) |
|
|
173 | (1) |
|
|
174 | (2) |
|
Containment and Eradication |
|
|
176 | (1) |
|
|
176 | (1) |
|
Other Workflow Components |
|
|
177 | (1) |
|
|
177 | (7) |
|
|
177 | (1) |
|
|
178 | (1) |
|
Vulnerability Management Lifecycle |
|
|
178 | (2) |
|
Integrating Vulnerability Management and Risk Management |
|
|
180 | (1) |
|
|
180 | (1) |
|
Lessons-Learned Process Components |
|
|
181 | (2) |
|
Conducting a Lessons-Learned Meeting |
|
|
183 | (1) |
|
|
184 | (3) |
|
Continual Improvement Principles |
|
|
184 | (1) |
|
|
184 | (1) |
|
|
185 | (2) |
|
The Seven-Step Improvement Process |
|
|
187 | (5) |
|
Step 1 Define a Vision for Improvement |
|
|
188 | (1) |
|
|
188 | (1) |
|
|
189 | (1) |
|
|
190 | (1) |
|
Step 5 Analyze Information |
|
|
191 | (1) |
|
Step 6 Assess Findings and Create Plan |
|
|
191 | (1) |
|
Step 7 Implement the plan |
|
|
192 | (1) |
|
|
192 | (1) |
|
|
193 | (2) |
|
Chapter 5 Investigating and Remediating Cyber Breaches |
|
|
195 | (48) |
|
|
196 | (6) |
|
|
197 | (1) |
|
Acquire and Preserve Data |
|
|
198 | (2) |
|
|
200 | (2) |
|
|
202 | (1) |
|
|
202 | (21) |
|
|
203 | (1) |
|
Digital Forensics Disciplines |
|
|
203 | (2) |
|
|
205 | (1) |
|
Other Considerations in Digital Forensics |
|
|
206 | (1) |
|
Cyber Threat Intelligence |
|
|
207 | (1) |
|
Cyber Threat Intelligence Lifecycle |
|
|
208 | (1) |
|
Identifying Attacker Activity with Cyber Threat Intelligence |
|
|
209 | (3) |
|
|
212 | (2) |
|
|
214 | (1) |
|
|
214 | (2) |
|
|
216 | (1) |
|
|
217 | (1) |
|
Malware Analysis and Cyber Threat Intelligence |
|
|
217 | (1) |
|
|
218 | (1) |
|
Prerequisites to Threat Hunting |
|
|
218 | (1) |
|
|
219 | (2) |
|
|
221 | (2) |
|
|
223 | (5) |
|
|
223 | (1) |
|
|
223 | (2) |
|
|
225 | (1) |
|
|
226 | (1) |
|
|
227 | (1) |
|
|
228 | (13) |
|
|
229 | (1) |
|
Establishing a Remediation Team |
|
|
230 | (1) |
|
|
231 | (1) |
|
|
232 | (1) |
|
|
233 | (1) |
|
|
233 | (1) |
|
Technology Considerations |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
Consequences of Alerting the Attacker |
|
|
236 | (1) |
|
Developing an Execution Plan |
|
|
237 | (1) |
|
Containment and Eradication |
|
|
238 | (1) |
|
|
238 | (1) |
|
|
239 | (1) |
|
Monitoring for Attacker Activity |
|
|
240 | (1) |
|
|
241 | (1) |
|
|
242 | (1) |
|
Chapter 6 Legal and Regulatory Considerations in Cyber Breach Response |
|
|
243 | (38) |
|
Understanding Breaches from a Legal Perspective |
|
|
244 | (8) |
|
Laws, Regulations, and Standards |
|
|
244 | (1) |
|
|
245 | (1) |
|
|
246 | (1) |
|
|
246 | (1) |
|
Materiality in Financial Disclosure |
|
|
247 | (1) |
|
|
248 | (1) |
|
Motive, Opportunity, Means |
|
|
248 | (1) |
|
Attributing a Cyber Attack |
|
|
249 | (2) |
|
|
251 | (1) |
|
|
252 | (1) |
|
Collecting Digital Evidence |
|
|
252 | (6) |
|
What Is Digital Evidence? |
|
|
253 | (1) |
|
Digital Evidence Lifecycle |
|
|
253 | (1) |
|
|
254 | (1) |
|
|
254 | (1) |
|
|
255 | (1) |
|
|
255 | (1) |
|
|
255 | (1) |
|
|
256 | (1) |
|
|
256 | (1) |
|
|
257 | (1) |
|
|
258 | (1) |
|
Admissibility of Digital Evidence |
|
|
258 | (3) |
|
Federal Rules of Evidence |
|
|
258 | (2) |
|
|
260 | (1) |
|
|
260 | (1) |
|
|
260 | (1) |
|
Admission of Digital Evidence in Court |
|
|
261 | (1) |
|
|
261 | (2) |
|
|
261 | (1) |
|
Business Records Exemption Rule |
|
|
262 | (1) |
|
|
262 | (1) |
|
Working with Legal Counsel |
|
|
263 | (2) |
|
Attorney-Client Privilege |
|
|
263 | (1) |
|
|
264 | (1) |
|
Non-testifying Expert Privilege |
|
|
264 | (1) |
|
|
265 | (1) |
|
Establishing a Chain of Custody |
|
|
265 | (6) |
|
What Is a Chain of Custody? |
|
|
266 | (1) |
|
Establishing a Defensible Protocol |
|
|
266 | (1) |
|
Traditional Forensic Acquisition |
|
|
267 | (1) |
|
Live Response and Logical Acquisition |
|
|
268 | (1) |
|
Documenting a Defensible Protocol |
|
|
269 | (1) |
|
|
269 | (1) |
|
|
270 | (1) |
|
Auditability and Reproducibility |
|
|
270 | (1) |
|
|
270 | (1) |
|
Data Privacy and Cyber Breach Investigations |
|
|
271 | (6) |
|
|
271 | (1) |
|
Handling Personal Data During Investigations |
|
|
272 | (1) |
|
Enacting a Policy to Support Investigations |
|
|
272 | (1) |
|
Cyber Breach Investigations and GDPR |
|
|
273 | (1) |
|
Data Processing and Cyber Breach Investigations |
|
|
274 | (1) |
|
Establishing a Lawful Basis for the Processing of Personal Data |
|
|
275 | (1) |
|
Territorial Transfer of Personal Data |
|
|
276 | (1) |
|
|
277 | (1) |
|
|
278 | (3) |
Index |
|
281 | |