Acknowledgments |
|
xvii | |
Introduction |
|
xix | |
Domain 1 Planning and Scoping |
|
1 | (36) |
|
Objective 1.1 Explain the importance of planning for an engagement |
|
|
2 | (14) |
|
Understanding the Target Audience |
|
|
2 | (2) |
|
|
4 | (1) |
|
|
5 | (1) |
|
Resources and Requirements |
|
|
6 | (1) |
|
Confidentiality of Findings |
|
|
6 | (1) |
|
|
7 | (1) |
|
|
7 | (1) |
|
Impact Analysis and Remediation Timelines |
|
|
8 | (1) |
|
|
8 | (1) |
|
|
9 | (1) |
|
|
9 | (4) |
|
|
13 | (1) |
|
|
13 | (2) |
|
|
15 | (1) |
|
Objective 1.2 Explain key legal concepts |
|
|
16 | (4) |
|
|
16 | (1) |
|
Environmental Differences |
|
|
17 | (1) |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
20 | (1) |
|
Objective 1.3 Explain the importance of scoping an engagement properly |
|
|
20 | (13) |
|
Types of Penetration Testing |
|
|
21 | (2) |
|
Goals-Based/Objectives-Based Penetration Testing |
|
|
21 | (1) |
|
Compliance-Based Penetration Testing |
|
|
22 | (1) |
|
|
22 | (1) |
|
Special Scoping Considerations |
|
|
23 | (1) |
|
|
23 | (3) |
|
|
23 | (2) |
|
|
25 | (1) |
|
|
26 | (1) |
|
|
27 | (1) |
|
|
28 | (1) |
|
|
28 | (1) |
|
|
28 | (1) |
|
|
28 | (2) |
|
|
30 | (1) |
|
|
30 | (1) |
|
|
31 | (1) |
|
|
32 | (1) |
|
Objective 1.4 Explain the key aspects of compliance-based assessments |
|
|
33 | (4) |
|
Compliance-Based Assessments, Limitations, and Caveats |
|
|
33 | (1) |
|
Rules to Complete Assessment |
|
|
34 | (1) |
|
Password Policies and Key Management |
|
|
34 | (1) |
|
|
34 | (1) |
|
|
35 | (1) |
|
Clearly Defined Objectives Based on Regulations |
|
|
35 | (1) |
|
|
35 | (1) |
|
|
35 | (1) |
|
|
36 | (1) |
Domain 2.0 Information Gathering and Vulnerability Identification |
|
37 | (54) |
|
Objective 2.1 Given a scenario, conduct information gathering using appropriate techniques |
|
|
38 | (18) |
|
|
41 | (2) |
|
|
43 | (5) |
|
|
43 | (1) |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
Services and Applications |
|
|
46 | (1) |
|
|
47 | (1) |
|
Social Network Enumeration |
|
|
47 | (1) |
|
|
48 | (1) |
|
|
48 | (1) |
|
|
48 | (1) |
|
|
49 | (1) |
|
|
50 | (1) |
|
|
50 | (2) |
|
RF Communication Monitoring |
|
|
51 | (1) |
|
|
52 | (1) |
|
|
52 | (1) |
|
|
53 | (1) |
|
Open-Source Intelligence Gathering |
|
|
53 | (1) |
|
|
54 | (1) |
|
|
55 | (1) |
|
|
56 | (1) |
|
Objective 2.2 Given a scenario, perform a vulnerability scan |
|
|
56 | (11) |
|
Credentialed vs. Noncredentialed |
|
|
57 | (1) |
|
|
57 | (1) |
|
|
58 | (1) |
|
|
58 | (2) |
|
|
60 | (1) |
|
|
61 | (1) |
|
|
61 | (1) |
|
|
62 | (1) |
|
Considerations of Vulnerability Scanning |
|
|
62 | (3) |
|
|
62 | (1) |
|
|
63 | (1) |
|
Network Topology and Bandwidth Limitations |
|
|
64 | (1) |
|
Fragile Systems/Nontraditional Assets |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
65 | (1) |
|
|
66 | (1) |
|
Objective 2.3 Given a scenario, analyze vulnerability scan results |
|
|
67 | (7) |
|
|
68 | (2) |
|
|
70 | (1) |
|
Prioritization of Vulnerabilities |
|
|
71 | (1) |
|
|
72 | (1) |
|
|
72 | (1) |
|
|
73 | (1) |
|
|
73 | (1) |
|
Objective 2.4 Explain the process of leveraging information to prepare for exploitation |
|
|
74 | (9) |
|
Map Vulnerabilities to Potential Exploits |
|
|
74 | (3) |
|
Prioritize Activities in Preparation for a Penetration Test |
|
|
77 | (1) |
|
Describe Common Techniques to Complete an Attack |
|
|
77 | (5) |
|
|
78 | (1) |
|
|
79 | (1) |
|
|
79 | (1) |
|
Proof-of-Concept Development (Exploit Development) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
81 | (1) |
|
|
82 | (1) |
|
|
82 | (1) |
|
|
83 | (1) |
|
Objective 2.5 Explain weaknesses related to specialized systems |
|
|
83 | (8) |
|
|
83 | (2) |
|
|
85 | (1) |
|
|
85 | (1) |
|
|
86 | (1) |
|
|
86 | (1) |
|
|
86 | (1) |
|
|
87 | (1) |
|
|
87 | (1) |
|
|
88 | (1) |
|
|
89 | (2) |
Domain 3.0 Attacks and Exploits |
|
91 | (186) |
|
Objective 3.1 Compare and contrast social engineering attacks |
|
|
92 | (14) |
|
|
93 | (4) |
|
|
93 | (1) |
|
|
94 | (2) |
|
|
96 | (1) |
|
|
96 | (1) |
|
|
97 | (2) |
|
|
97 | (1) |
|
Example Tactics for Elicitation |
|
|
98 | (1) |
|
|
99 | (1) |
|
|
99 | (1) |
|
|
100 | (1) |
|
|
100 | (1) |
|
|
101 | (1) |
|
|
102 | (2) |
|
|
104 | (2) |
|
|
106 | (1) |
|
Objective 3.2 Given a scenario, exploit network-based vulnerabilities |
|
|
106 | (38) |
|
|
107 | (8) |
|
|
107 | (6) |
|
NetBIOS and LLMNR Name Services |
|
|
113 | (2) |
|
|
115 | (2) |
|
|
117 | (2) |
|
|
119 | (2) |
|
|
121 | (2) |
|
|
123 | (2) |
|
|
125 | (8) |
|
|
125 | (4) |
|
|
129 | (1) |
|
|
130 | (1) |
|
|
131 | (2) |
|
|
133 | (1) |
|
|
133 | (2) |
|
|
135 | (1) |
|
|
136 | (1) |
|
|
137 | (1) |
|
|
138 | (5) |
|
|
143 | (1) |
|
Objective 3.3 Given a scenario, exploit wireless and RF-based vulnerabilities |
|
|
144 | (21) |
|
|
144 | (5) |
|
|
145 | (1) |
|
|
145 | (1) |
|
|
146 | (3) |
|
|
149 | (9) |
|
|
149 | (2) |
|
|
151 | (1) |
|
|
151 | (1) |
|
|
152 | (2) |
|
|
154 | (1) |
|
WPS Implementation Weakness |
|
|
154 | (4) |
|
|
158 | (5) |
|
|
158 | (3) |
|
|
161 | (1) |
|
|
162 | (1) |
|
|
163 | (1) |
|
|
163 | (1) |
|
|
164 | (1) |
|
Objective 3.4 Given a scenario, exploit application-based vulnerabilities. |
|
|
165 | (34) |
|
|
165 | (14) |
|
|
166 | (5) |
|
HTML Injection and Cross-Site Scripting |
|
|
171 | (3) |
|
Code Injection and Command Injection |
|
|
174 | (5) |
|
Security Misconfiguration |
|
|
179 | (3) |
|
|
179 | (1) |
|
|
180 | (1) |
|
|
181 | (1) |
|
|
182 | (4) |
|
|
182 | (1) |
|
|
183 | (1) |
|
|
184 | (1) |
|
Default and Weak Credentials |
|
|
185 | (1) |
|
|
186 | (2) |
|
|
186 | (1) |
|
Insecure Direct Object Reference |
|
|
187 | (1) |
|
|
188 | (6) |
|
|
188 | (1) |
|
|
189 | (1) |
|
|
189 | (1) |
|
|
190 | (1) |
|
Unauthorized Use of Functions/Unprotected APIs |
|
|
191 | (1) |
|
|
192 | (1) |
|
|
193 | (1) |
|
|
194 | (2) |
|
Cross-Site Request Forgery |
|
|
194 | (1) |
|
|
195 | (1) |
|
|
196 | (1) |
|
|
196 | (2) |
|
|
198 | (1) |
|
Objective 3.5 Given a scenario, exploit local host vulnerabilities |
|
|
199 | (50) |
|
Windows Host-Based Vulnerabilities |
|
|
199 | (16) |
|
|
199 | (9) |
|
Windows OS Vulnerabilities |
|
|
208 | (2) |
|
Windows Configuration Weaknesses |
|
|
210 | (2) |
|
|
212 | (3) |
|
Linux Host-Based Vulnerabilities |
|
|
215 | (15) |
|
|
216 | (5) |
|
|
221 | (2) |
|
Linux Default Configurations |
|
|
223 | (1) |
|
|
224 | (3) |
|
|
227 | (3) |
|
Apple Device Host-Based Vulnerabilities |
|
|
230 | (5) |
|
|
230 | (2) |
|
|
232 | (3) |
|
Sandbox Escape and Controls Evasion |
|
|
235 | (5) |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
237 | (1) |
|
|
238 | (1) |
|
AV and Antimalware Evasion |
|
|
239 | (1) |
|
|
240 | (5) |
|
Exploitation of Memory Vulnerabilities |
|
|
240 | (2) |
|
|
242 | (1) |
|
|
242 | (3) |
|
|
245 | (1) |
|
|
246 | (2) |
|
|
248 | (1) |
|
Objective 3.6 Summarize physical security attacks related to facilities |
|
|
249 | (5) |
|
|
249 | (1) |
|
|
250 | (1) |
|
|
250 | (1) |
|
|
251 | (1) |
|
|
251 | (1) |
|
|
251 | (1) |
|
Bypassing Other Surveillance |
|
|
252 | (1) |
|
|
253 | (1) |
|
|
253 | (1) |
|
|
254 | (1) |
|
Objective 3.7 Given a scenario, perform post-exploitation techniques |
|
|
254 | (23) |
|
|
255 | (10) |
|
|
255 | (1) |
|
|
256 | (1) |
|
|
257 | (1) |
|
|
258 | (1) |
|
|
258 | (1) |
|
|
259 | (1) |
|
|
260 | (1) |
|
|
261 | (1) |
|
|
261 | (1) |
|
|
262 | (1) |
|
|
263 | (1) |
|
|
264 | (1) |
|
|
265 | (7) |
|
|
266 | (3) |
|
|
269 | (1) |
|
|
269 | (2) |
|
|
271 | (1) |
|
|
272 | (1) |
|
|
272 | (1) |
|
|
273 | (1) |
|
|
274 | (3) |
Domain 4.0 Penetration Testing Tools |
|
277 | (108) |
|
Objective 4.1 Given a scenario, use Nmap to conduct information gathering exercises |
|
|
278 | (11) |
|
|
278 | (6) |
|
|
278 | (1) |
|
|
279 | (1) |
|
|
279 | (1) |
|
|
280 | (1) |
|
|
280 | (2) |
|
|
282 | (1) |
|
|
282 | (1) |
|
|
283 | (1) |
|
|
283 | (1) |
|
|
284 | (3) |
|
|
284 | (1) |
|
|
284 | (1) |
|
|
284 | (2) |
|
|
286 | (1) |
|
|
286 | (1) |
|
|
287 | (1) |
|
|
287 | (1) |
|
|
288 | (1) |
|
Objective 4.2 Compare and contrast various use cases of tools |
|
|
289 | (1) |
|
Objective 4.3 Given a scenario, analyze tool output or data related to a penetration test |
|
|
289 | (81) |
|
|
289 | (70) |
|
|
289 | (2) |
|
|
291 | (1) |
|
|
292 | (1) |
|
|
293 | (1) |
|
|
294 | (1) |
|
|
294 | (1) |
|
|
295 | (1) |
|
|
296 | (4) |
|
|
300 | (1) |
|
|
301 | (1) |
|
|
302 | (1) |
|
|
303 | (1) |
|
|
304 | (1) |
|
|
305 | (2) |
|
|
307 | (1) |
|
Findbugs/Findsecbugs/SpotBugs |
|
|
308 | (2) |
|
|
310 | (1) |
|
|
311 | (2) |
|
|
313 | (1) |
|
|
313 | (2) |
|
|
315 | (1) |
|
|
315 | (1) |
|
|
316 | (2) |
|
|
318 | (1) |
|
|
319 | (1) |
|
|
320 | (1) |
|
|
321 | (1) |
|
|
322 | (1) |
|
|
323 | (2) |
|
|
325 | (2) |
|
|
327 | (1) |
|
|
328 | (1) |
|
|
329 | (1) |
|
|
330 | (1) |
|
|
330 | (1) |
|
|
331 | (1) |
|
|
332 | (2) |
|
|
334 | (2) |
|
|
336 | (1) |
|
|
336 | (1) |
|
|
337 | (1) |
|
|
338 | (1) |
|
|
339 | (1) |
|
|
339 | (1) |
|
|
340 | (2) |
|
|
342 | (2) |
|
|
344 | (1) |
|
|
345 | (1) |
|
|
346 | (2) |
|
|
348 | (1) |
|
|
348 | (1) |
|
|
349 | (1) |
|
|
350 | (1) |
|
|
350 | (2) |
|
|
352 | (1) |
|
|
353 | (1) |
|
|
354 | (1) |
|
|
355 | (1) |
|
|
356 | (1) |
|
|
357 | (2) |
|
|
359 | (3) |
|
|
359 | (1) |
|
|
360 | (1) |
|
|
361 | (1) |
|
|
362 | (2) |
|
|
362 | (1) |
|
|
362 | (1) |
|
|
363 | (1) |
|
|
364 | (1) |
|
Tomcat Compromise with Metasploit |
|
|
364 | (1) |
|
|
365 | (1) |
|
|
366 | (3) |
|
|
369 | (1) |
|
Objective 4.4 Given a scenario, analyze a basic script |
|
|
370 | (15) |
|
|
370 | (1) |
|
|
371 | (1) |
|
|
371 | (3) |
|
|
374 | (1) |
|
|
374 | (1) |
|
|
375 | (2) |
|
|
375 | (1) |
|
|
376 | (1) |
|
|
376 | (1) |
|
|
377 | (3) |
|
|
380 | (1) |
|
|
381 | (1) |
|
|
382 | (1) |
|
|
382 | (2) |
|
|
384 | (1) |
Domain 5.0 Reporting and Communication |
|
385 | (30) |
|
Objective 5.1 Given a scenario, use report writing and handling best practices |
|
|
386 | (7) |
|
|
386 | (1) |
|
Written Report of Findings and Remediation |
|
|
387 | (3) |
|
|
388 | (1) |
|
|
388 | (1) |
|
|
389 | (1) |
|
|
389 | (1) |
|
|
390 | (1) |
|
|
390 | (1) |
|
Secure Handling and Disposition of Reports |
|
|
391 | (1) |
|
|
391 | (1) |
|
|
392 | (1) |
|
|
393 | (1) |
|
Objective 5.2 Explain post-report delivery activities |
|
|
393 | (5) |
|
|
394 | (1) |
|
Client Acceptance and Attestation of Findings |
|
|
394 | (1) |
|
|
395 | (1) |
|
|
396 | (1) |
|
|
396 | (1) |
|
|
396 | (2) |
|
|
398 | (1) |
|
Objective 5.3 Given a scenario, recommend mitigation strategies for discovered vulnerabilities |
|
|
398 | (10) |
|
|
398 | (2) |
|
|
400 | (6) |
|
Shared Local Administrator Credentials |
|
|
400 | (1) |
|
|
401 | (1) |
|
|
402 | (1) |
|
No Multifactor Authentication |
|
|
403 | (1) |
|
|
404 | (1) |
|
Unnecessary Open Services |
|
|
405 | (1) |
|
|
406 | (1) |
|
|
407 | (1) |
|
|
408 | (1) |
|
Objective 5.4 Explain the importance of communication during the penetration testing process |
|
|
408 | (7) |
|
|
408 | (1) |
|
|
409 | (1) |
|
|
409 | (1) |
|
|
409 | (1) |
|
Indicators of Prior Compromise |
|
|
410 | (1) |
|
Reasons for Communication |
|
|
410 | (1) |
|
|
410 | (1) |
|
|
411 | (1) |
|
|
411 | (1) |
|
|
411 | (1) |
|
|
412 | (1) |
|
|
412 | (1) |
|
|
413 | (2) |
A About the Online Content |
|
415 | (4) |
|
|
415 | (1) |
|
Your Total Seminars Training Hub Account |
|
|
415 | (1) |
|
|
415 | (1) |
|
Single User License Terms and Conditions |
|
|
415 | (2) |
|
|
417 | (1) |
|
Performance-Based Questions |
|
|
417 | (1) |
|
|
418 | (1) |
Glossary |
|
419 | (10) |
Index |
|
429 | |