Acknowledgments |
|
xxi | |
Introduction |
|
xxiii | |
|
1.0 Threat and Vulnerability Management |
|
|
1 | (126) |
|
Objective 1.1 Explain the importance of threat data and intelligence |
|
|
2 | (25) |
|
|
4 | (1) |
|
|
4 | (2) |
|
Proprietary and Closed-Source Intelligence |
|
|
6 | (1) |
|
|
7 | (1) |
|
|
7 | (1) |
|
|
8 | (1) |
|
|
8 | (1) |
|
|
9 | (1) |
|
Structured Threat Information expression (STIX) |
|
|
10 | (1) |
|
Trusted Automated exchange of Indicator Intelligence (TAXII) |
|
|
11 | (2) |
|
|
13 | (1) |
|
|
13 | (1) |
|
Known Threats vs. Unknown Threats |
|
|
14 | (1) |
|
|
15 | (1) |
|
Advanced Persistent Threats |
|
|
15 | (1) |
|
|
16 | (1) |
|
|
16 | (1) |
|
|
16 | (1) |
|
|
17 | (1) |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
20 | (1) |
|
|
20 | (1) |
|
|
20 | (1) |
|
Information Sharing and Analysis Communities |
|
|
21 | (1) |
|
|
22 | (1) |
|
|
23 | (1) |
|
|
23 | (1) |
|
|
23 | (1) |
|
|
24 | (1) |
|
|
24 | (1) |
|
|
25 | (1) |
|
|
26 | (1) |
|
Objective 1.2 Given a scenario, utilize threat intelligence to support organizational security |
|
|
27 | (19) |
|
|
27 | (1) |
|
|
27 | (2) |
|
The Diamond Model of Intrusion Analysis |
|
|
29 | (1) |
|
|
30 | (1) |
|
|
31 | (1) |
|
|
31 | (1) |
|
|
32 | (1) |
|
Indicators of Compromise (IOCs) |
|
|
33 | (1) |
|
Common Vulnerability Scoring System (CVSS) |
|
|
33 | (2) |
|
Threat Modeling Methodologies |
|
|
35 | (1) |
|
Common Threat Modeling Methodologies |
|
|
36 | (1) |
|
|
36 | (1) |
|
|
37 | (1) |
|
|
37 | (1) |
|
|
38 | (1) |
|
|
39 | (1) |
|
Threat Intelligence Sharing with Supported Functions |
|
|
40 | (1) |
|
|
41 | (1) |
|
|
41 | (1) |
|
|
42 | (1) |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
Objective 1.3 Given a scenario, perform vulnerability management activities |
|
|
46 | (23) |
|
Vulnerability Identification |
|
|
46 | (2) |
|
|
48 | (1) |
|
Active vs. Passive Scanning |
|
|
48 | (1) |
|
|
49 | (1) |
|
|
50 | (1) |
|
|
50 | (1) |
|
|
51 | (1) |
|
|
51 | (1) |
|
|
51 | (1) |
|
|
52 | (1) |
|
|
52 | (1) |
|
|
53 | (1) |
|
|
54 | (1) |
|
|
55 | (1) |
|
|
55 | (1) |
|
Verification of Mitigation |
|
|
56 | (1) |
|
Scanning Parameters and Criteria |
|
|
56 | (1) |
|
Risks Associated with Scanning Activities |
|
|
56 | (1) |
|
|
57 | (1) |
|
|
57 | (1) |
|
Credentialed vs. Non-Credentialed |
|
|
58 | (1) |
|
Server-Based vs. Agent-Based |
|
|
58 | (1) |
|
|
59 | (1) |
|
|
60 | (3) |
|
Inhibitors to Remediation |
|
|
63 | (1) |
|
Memorandum of Understanding (MOU) |
|
|
64 | (1) |
|
Service Level Agreement (SLA) |
|
|
64 | (1) |
|
Organizational Governance |
|
|
64 | (1) |
|
Business Process Interruption |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
65 | (1) |
|
|
65 | (1) |
|
|
66 | (1) |
|
|
67 | (1) |
|
|
68 | (1) |
|
Objective 1.4 Given a scenario, analyze the output from common vulnerability assessment tools |
|
|
69 | (16) |
|
Vulnerability Assessment Tools |
|
|
69 | (1) |
|
|
70 | (1) |
|
|
70 | (2) |
|
Software Assessment Tools and Techniques |
|
|
72 | (2) |
|
|
74 | (1) |
|
|
74 | (3) |
|
Network Vulnerability Scanners |
|
|
77 | (2) |
|
|
79 | (2) |
|
Cloud Infrastructure Assessment |
|
|
81 | (2) |
|
|
83 | (1) |
|
|
83 | (1) |
|
|
84 | (1) |
|
Objective 1.5 Explain the threats and vulnerabilities associated with specialized technology |
|
|
85 | (13) |
|
|
85 | (1) |
|
Mobile Device Threats and Vulnerabilities |
|
|
85 | (1) |
|
Corporate Device Considerations |
|
|
86 | (1) |
|
Mobile Device Protections |
|
|
87 | (1) |
|
|
87 | (1) |
|
|
88 | (2) |
|
|
90 | (1) |
|
Building Automation Systems |
|
|
91 | (1) |
|
|
92 | (2) |
|
Industrial Control Systems |
|
|
94 | (1) |
|
Workflow and Process Automation Systems |
|
|
94 | (1) |
|
Supervisory Control and Data Acquisition (SCADA) |
|
|
94 | (1) |
|
|
95 | (1) |
|
|
96 | (1) |
|
|
97 | (1) |
|
Objective 1.6 Explain the threats and vulnerabilities associated with operating in the cloud |
|
|
98 | (11) |
|
|
98 | (1) |
|
Software as a Service (SaaS) |
|
|
99 | (1) |
|
Platform as a Service (PaaS) |
|
|
100 | (1) |
|
Infrastructure as a Service (IaaS) |
|
|
101 | (1) |
|
Serverless Architecture and Function as a Service (FaaS) |
|
|
101 | (1) |
|
Infrastructure as Code (IaC) |
|
|
102 | (1) |
|
|
102 | (1) |
|
|
102 | (1) |
|
|
103 | (1) |
|
|
103 | (1) |
|
|
103 | (1) |
|
|
104 | (1) |
|
Insecure Application Programming Interface (API) |
|
|
104 | (1) |
|
|
105 | (1) |
|
|
105 | (1) |
|
Insufficient Logging and Monitoring |
|
|
106 | (1) |
|
|
106 | (1) |
|
|
107 | (1) |
|
|
107 | (1) |
|
|
108 | (1) |
|
Objective 1.7 Given a scenario, implement controls to mitigate attacks and software vulnerabilities |
|
|
109 | (18) |
|
|
109 | (1) |
|
|
110 | (1) |
|
|
110 | (1) |
|
Insecure Object Reference |
|
|
111 | (1) |
|
|
111 | (1) |
|
|
112 | (1) |
|
|
113 | (1) |
|
|
113 | (1) |
|
Insufficient Logging and Monitoring |
|
|
113 | (1) |
|
Weak or Default Configurations |
|
|
114 | (1) |
|
Use of Insecure Functions |
|
|
114 | (1) |
|
|
115 | (1) |
|
|
115 | (3) |
|
|
118 | (3) |
|
|
121 | (2) |
|
|
123 | (1) |
|
|
124 | (1) |
|
|
125 | (2) |
|
2.0 Software and Systems Security |
|
|
127 | (64) |
|
Objective 2.1 Given a scenario, apply security solutions for infrastructure management |
|
|
128 | (34) |
|
Infrastructure Management |
|
|
128 | (1) |
|
|
128 | (1) |
|
|
129 | (1) |
|
|
130 | (3) |
|
|
133 | (3) |
|
|
136 | (1) |
|
|
137 | (2) |
|
|
139 | (1) |
|
Identity and Access Management |
|
|
140 | (1) |
|
|
140 | (3) |
|
|
143 | (3) |
|
Cloud Access Security Broker (CASB) |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
147 | (2) |
|
|
149 | (6) |
|
|
155 | (2) |
|
|
157 | (1) |
|
|
158 | (2) |
|
|
160 | (2) |
|
|
162 | (1) |
|
Objective 2.2 Explain software assurance best practices |
|
|
162 | (16) |
|
|
162 | (1) |
|
|
163 | (1) |
|
|
163 | (1) |
|
|
164 | (1) |
|
|
164 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
Service-Oriented Architecture |
|
|
165 | (1) |
|
Security Assertions Markup Language (SAML) |
|
|
166 | (1) |
|
Simple Object Access Protocol (SOAP) |
|
|
167 | (1) |
|
Representational State Transfer (REST) |
|
|
167 | (1) |
|
|
167 | (1) |
|
Software Development Lifecycle (SDLC) Integration |
|
|
168 | (1) |
|
|
168 | (1) |
|
Secure Coding Best Practices |
|
|
169 | (1) |
|
|
169 | (1) |
|
|
170 | (1) |
|
|
170 | (1) |
|
|
170 | (1) |
|
|
171 | (1) |
|
|
172 | (1) |
|
Software Assessment Methods |
|
|
172 | (1) |
|
|
172 | (1) |
|
|
173 | (1) |
|
Security Regression Testing |
|
|
173 | (1) |
|
|
173 | (1) |
|
|
174 | (1) |
|
|
174 | (1) |
|
Formal Methods for Verification of Critical Software |
|
|
175 | (1) |
|
|
175 | (1) |
|
|
176 | (1) |
|
|
177 | (1) |
|
Objective 2.3 Explain hardware assurance best practices |
|
|
178 | (13) |
|
|
178 | (1) |
|
Trusted Platform Module (TPM) |
|
|
179 | (1) |
|
Hardware Security Module (HSM) |
|
|
179 | (1) |
|
|
180 | (1) |
|
Unified Extensible Firmware Interface (UEFI) |
|
|
180 | (1) |
|
|
181 | (1) |
|
|
182 | (1) |
|
Trusted Execution and Secure Enclave |
|
|
182 | (1) |
|
Processor Security Extensions |
|
|
183 | (1) |
|
|
183 | (1) |
|
|
184 | (1) |
|
|
184 | (1) |
|
Self-Encrypting Drive (SED) |
|
|
185 | (1) |
|
|
185 | (1) |
|
Measured Boot and Attestation |
|
|
186 | (1) |
|
|
186 | (2) |
|
|
188 | (1) |
|
|
189 | (2) |
|
3.0 Security Operations and Monitoring |
|
|
191 | (68) |
|
Objective 3.1 Given a scenario, analyze data as part of security monitoring activities |
|
|
192 | (23) |
|
|
192 | (1) |
|
|
193 | (1) |
|
|
193 | (1) |
|
Known-Good vs. Anomalous Behavior Analysis |
|
|
194 | (1) |
|
Malware Analysis and Reverse Engineering |
|
|
195 | (1) |
|
|
195 | (1) |
|
|
196 | (1) |
|
System and Application Behavior |
|
|
196 | (1) |
|
User and Entity Behavior Analytics (UEBA) |
|
|
196 | (1) |
|
Analysis of Endpoint Exploitation Techniques |
|
|
197 | (1) |
|
|
198 | (1) |
|
Uniform Resource Locator (URL) and Domain Name System (DNS) Analysis |
|
|
198 | (1) |
|
Domain Generation Algorithm |
|
|
199 | (1) |
|
|
199 | (1) |
|
Packet and Protocol Analysis |
|
|
199 | (1) |
|
Network-Based Malware Analysis |
|
|
200 | (1) |
|
|
201 | (1) |
|
|
201 | (1) |
|
|
202 | (1) |
|
|
202 | (1) |
|
Web Application Firewall (WAF) |
|
|
202 | (1) |
|
|
203 | (1) |
|
Intrusion Detection System (IDS)/Intrusion Prevention System (IPS) |
|
|
203 | (1) |
|
|
203 | (1) |
|
Organization Impact vs. Localized Impact |
|
|
204 | (1) |
|
|
204 | (1) |
|
Security Information and Event Management (SIEM) Review |
|
|
205 | (1) |
|
|
205 | (1) |
|
|
206 | (1) |
|
|
207 | (1) |
|
|
207 | (1) |
|
|
207 | (1) |
|
|
208 | (1) |
|
|
208 | (1) |
|
|
208 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
210 | (1) |
|
|
210 | (1) |
|
Domain Keys Identified Mail (DKIM) |
|
|
210 | (1) |
|
Sender Policy Framework (SPF) |
|
|
211 | (1) |
|
Domain-Based Message Authentication, Reporting, and Conformance (DMARC) |
|
|
211 | (1) |
|
|
211 | (2) |
|
|
213 | (1) |
|
|
214 | (1) |
|
Objective 3.2 Given a scenario, implement configuration changes to existing controls to improve security |
|
|
215 | (24) |
|
Review of Control Concepts |
|
|
215 | (1) |
|
Control Categories and Functions |
|
|
215 | (2) |
|
Control Implementation and Risk |
|
|
217 | (1) |
|
|
218 | (1) |
|
|
219 | (2) |
|
|
221 | (2) |
|
|
223 | (1) |
|
|
224 | (1) |
|
|
224 | (2) |
|
|
226 | (1) |
|
Packet-Filtering Firewalls |
|
|
226 | (1) |
|
|
227 | (1) |
|
Stateful Inspection Firewalls |
|
|
227 | (1) |
|
Application-Level Gateways |
|
|
227 | (1) |
|
Web Application Firewalls (WAFs) |
|
|
228 | (1) |
|
Next-Generation Firewalls |
|
|
228 | (1) |
|
|
228 | (1) |
|
Intrusion Prevention System (IPS) Rules |
|
|
229 | (1) |
|
Data Loss Prevention (DLP) |
|
|
230 | (1) |
|
Endpoint Detection and Response (EDR) |
|
|
230 | (1) |
|
Network Access Control (NAC) |
|
|
231 | (2) |
|
|
233 | (1) |
|
|
233 | (1) |
|
|
234 | (1) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (2) |
|
|
237 | (1) |
|
|
238 | (1) |
|
Objective 3.3 Explain the importance of proactive threat hunting |
|
|
239 | (9) |
|
Establishing a Hypothesis |
|
|
239 | (1) |
|
Profiling Threat Actors and Activities |
|
|
240 | (1) |
|
|
241 | (1) |
|
Executable Process Analysis |
|
|
241 | (1) |
|
Reducing the Attack Surface Area |
|
|
241 | (1) |
|
|
241 | (1) |
|
|
242 | (1) |
|
|
242 | (1) |
|
|
243 | (1) |
|
|
244 | (1) |
|
|
244 | (1) |
|
|
245 | (1) |
|
Improving Detection Capabilities |
|
|
245 | (1) |
|
|
246 | (1) |
|
|
246 | (1) |
|
|
247 | (1) |
|
Objective 3.4 Compare and contrast automation concepts and technologies |
|
|
248 | (11) |
|
|
248 | (1) |
|
|
248 | (1) |
|
Security Orchestration, Automation, and Response (SOAR) |
|
|
249 | (1) |
|
|
250 | (1) |
|
Application Programming Interface (API) Integration |
|
|
250 | (1) |
|
Automated Malware Signature Creation |
|
|
251 | (1) |
|
|
251 | (1) |
|
|
252 | (1) |
|
|
252 | (1) |
|
Use of Automation Protocols and Standards |
|
|
253 | (2) |
|
Automating Software Integration, Delivery, and Deployment |
|
|
255 | (1) |
|
|
256 | (1) |
|
|
257 | (1) |
|
|
258 | (1) |
|
|
259 | (68) |
|
Objective 4.1 Explain the importance of the incident response process |
|
|
260 | (13) |
|
Critical Incident Response Processes |
|
|
260 | (1) |
|
|
260 | (3) |
|
Response Coordination with Relevant Entities |
|
|
263 | (4) |
|
Factors Contributing to Data Criticality |
|
|
267 | (3) |
|
|
270 | (1) |
|
|
271 | (2) |
|
|
273 | (1) |
|
Objective 4.2 Given a scenario, apply the appropriate incident response procedure |
|
|
273 | (19) |
|
Incident Response Procedures |
|
|
273 | (1) |
|
|
274 | (2) |
|
|
276 | (4) |
|
|
280 | (1) |
|
|
281 | (4) |
|
|
285 | (4) |
|
|
289 | (1) |
|
|
290 | (1) |
|
|
291 | (1) |
|
Objective 4.3 Given an incident, analyze potential indicators of compromise |
|
|
292 | (17) |
|
Analyzing Indicators of Compromise |
|
|
292 | (1) |
|
|
293 | (4) |
|
|
297 | (7) |
|
|
304 | (3) |
|
|
307 | (1) |
|
|
307 | (1) |
|
|
308 | (1) |
|
Objective 4.4 Given a scenario, utilize basic digital forensics techniques |
|
|
309 | (18) |
|
|
309 | (1) |
|
|
310 | (3) |
|
|
313 | (2) |
|
Endpoint Forensics Considerations |
|
|
315 | (2) |
|
|
317 | (1) |
|
|
318 | (1) |
|
|
319 | (1) |
|
|
320 | (4) |
|
|
324 | (1) |
|
|
325 | (1) |
|
|
326 | (1) |
|
5.0 Compliance and Assessment |
|
|
327 | (52) |
|
Objective 5.1 Understand the importance of data privacy and protection |
|
|
328 | (12) |
|
|
328 | (1) |
|
|
329 | (5) |
|
|
334 | (4) |
|
|
338 | (1) |
|
|
339 | (1) |
|
|
340 | (1) |
|
Objective 5.2 Given a scenario, apply security concepts in support of organizational risk mitigation |
|
|
340 | (20) |
|
Organizational Risk Mitigation |
|
|
340 | (1) |
|
Business Impact Analysis (BIA) |
|
|
341 | (3) |
|
Risk Identification Process |
|
|
344 | (1) |
|
|
345 | (1) |
|
Communication of Risk Factors |
|
|
346 | (2) |
|
|
348 | (3) |
|
|
351 | (2) |
|
Documented Compensating Controls |
|
|
353 | (1) |
|
|
354 | (2) |
|
|
356 | (2) |
|
|
358 | (1) |
|
|
359 | (1) |
|
|
360 | (1) |
|
Objective 5.3 Explain the importance of frameworks, policies, procedures, and controls |
|
|
360 | (19) |
|
Organizational Governance Flow |
|
|
360 | (1) |
|
|
361 | (1) |
|
|
362 | (7) |
|
|
369 | (1) |
|
|
370 | (3) |
|
|
373 | (2) |
|
|
375 | (1) |
|
|
376 | (1) |
|
|
377 | (2) |
|
A About the Online Content |
|
|
379 | (4) |
|
|
379 | (1) |
|
Your Total Seminars Training Hub Account |
|
|
379 | (1) |
|
|
379 | (1) |
|
Single User License Terms and Conditions |
|
|
379 | (2) |
|
|
381 | (1) |
|
Performance-Based Questions |
|
|
381 | (1) |
|
|
382 | (1) |
Glossary |
|
383 | (20) |
Index |
|
403 | |