Part $3$: Prepare a Penetration Test Report

Note: In this part of the lab, you will use the information gathered using Nmap and OpenVAS to develop a penetration test report. In its simplest form, a penetration test report documents $(1)$ the goal of the test, $(2)$ who did it$,(3)$ what the tester did, and $(4)$ what the tester found. It is also important to clearly document the target$($s$)$ of the test, the purpose of the test $($why are you being asked to do this$),$ and the scope of the test. The scope of a penetration test is similar to rules of engagement. Within a report, the Scope section should state what the penetration tester is allowed to do$,$ such as whether potentially destructive scans are allowed. While the Target$($s$)$ section defines what will be tested, the Scope section defines how the tester plans to reach the target $($for example, clearing obstacles in the way$)$ and how aggressive the tester can be$.$ Because there is no separate section for tests carried out, the Scope section should include planned$/$executed tests.

Depending on the purpose of a penetration test, there may be multiple findings. In some cases, a single successful compromise means the test is over. In other cases, the tester continues carrying out all of the tests listed in the Scope section and reports the results of each test. In this case, you will limit your scope to a simple vulnerability scan of the

drisst.com web server and limit your findings to the three high$-$severity vulnerabilities identified by OpenVAS.

Within a penetration test report, the Summary of Findings section should focus on any activities that resulted in a compromised system. If a penetration tester could succeed, so could a malicious attacker. Since you will not actually be exploiting your target, your Summary of Findings section will be limited to the vulnerabilities you identified. Finally, the Conclusion section should simply state what the