??? ??? Penetration Test Report one target element per target 0 means 'computed automatically from service breakdown' so leave at 0 unless there is a clear reason not to start and end dates, in ISO format: YYYY-MM-DD client_info.xml FirstName LastName Melanie Rieback Melanie Rieback is a former Asst. Prof. of Computer Science from the VU, who is also the co-founder/CEO of Radically Open Security. FirstName LastName Info Confidential needed for date on frontpage and in signature boxes; it is possible to add a new <version> after each review; in that case, make sure to update the date/time T10:00:00 actual date-time here; you can leave the number attribute alone ROS Writer name of the author here; for internal use only Initial draft for internal use only snippets/company_info.xml
Executive Summary
Introduction

Between and , carried out a penetration test for

This report contains our findings as well as detailed explanations of exactly how performed the penetration test.

Scope of work

The scope of the penetration test was limited to the following target(s):

The scoped services are broken down as follows:

Project objectives

will perform a penetration test with of the . The test is intended to gain insight into the security of . To do so, will access this . and will guide in attempting to find vulnerabilities, and gain further access and elevated privileges by exploiting any vulnerabilities found.

Timeline

The Security Audit took place between and .

resultsinanutshell.xml
Summary of Findings generated from Findings section
Findings by Threat Level
Findings by Type
Summary of Recommendations generated from Findings section
snippets/report/methodology.xml
Reconnaissance and Fingerprinting

We were able to gain information about the software and infrastructure through the following automated scans. Any relevant scan output will be referred to in the findings.

Findings

We have identified the following issues:

Listing of Findings (written by pentesters) Extreme High Elevated Moderate Low
Non-Findings

In this section we list some of the things that were tried but turned out to be dead ends.

Listing of Non-Findings (written by pentesters)
futurework.xml conclusion.xml Testing team