Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1nmap -sV 192.168.1.10 | AThe exploit is run before planning. Scope and written permission must be agreed in the planning phase, before any testing starts. | |
| 2whois example.com.au | BScanning phase: probes a target to find open ports and the services running on them | |
| 3Gaining access: the tester exploits a weakness found during scanning to get into the system | CReconnaissance phase: gathers public information about the target, such as who owns the domain | |
| 4Cleaning up: the tester removes test accounts and files and reverses changes made during the test | Dexploit(target, vulnerability) | |
| 5phases = [scanning, planning, reconnaissance, gaining access, reporting] | Edelete_account("test_user") | |
| 6run_exploit(target) write_scope_and_permission() | FThe phases are out of order and maintaining access is missing. Planning must come first, then reconnaissance, then scanning. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
penetration test phases — The ordered stages of a penetration test: planning, reconnaissance, scanning, gaining access, maintaining access, then reporting, with clean-up of any changes made.1. planning
2. reconnaissance
3. scanning2. reconnaissance
3. scanning - find open ports
4. gaining access4. gaining access - exploit a vulnerability4. gaining access
5. maintaining access - stay in
6. reporting5. maintaining access
6. reporting - findings and fixes
clean up any changes made during the test