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 | AScans can return false positives, so items in the report must be checked and verified by a person before being treated as real. | |
| 2Scan result: "Possible SQL injection" - tester confirms it is not exploitable | BA scan only lists possible known weaknesses. It does not exploit them, so it cannot prove real data theft. Proving impact needs a penetration test. | |
| 3A vulnerability scan is automated and produces a list of known weaknesses without exploiting them | CAn automated scan that probes a host and lists open ports and service versions, which can then be checked against known vulnerabilities | |
| 4A penetration test is manual: a tester tries to exploit a weakness to show the real impact | Dscan_report = run_scanner(target) # lists issues only | |
| 5"Our vulnerability scan proved attackers could steal customer data." | EA false positive: the scan flagged a weakness that does not really exist, so a person must verify it | |
| 6"Every item in the scan report is a confirmed, real vulnerability." | Fexploit(target, "weak_admin_login") # tester gains access |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
vulnerability scan vs penetration test — A vulnerability scan is an automated check that lists known weaknesses, some false positives. A penetration test is manual: testers try to exploit them to prove the real impact.Vulnerability scan: automated check
Output: list of known weaknessesPenetration test: manual work by testers
Goal: exploit weaknesses to show impactA scan reports a weakness that is not real:
This is called a false positive.Scan finds a weakness.
Tester tries to exploit it to prove impact.A penetration test proves real impact.
A scan only lists known weaknesses.