Cybersecurity & Information Security

Writing a Penetration Test Report That Leads to Remediation

6 min readPublished: August 5, 2026

Professional visual illustration of writing a Penetration Test report in the field of Penetration Testing

Quick answer

Writing a Penetration Test report must only be done within an approved Scope and Rules of Engagement. The process includes information gathering, controlled verification, Evidence, risk assessment, remediation, and Retest.

Professional penetration testing is an authorized and defined process, not just a collection of commands. Scope, Rules of Engagement, evidence, risk assessment, remediation, and Retest are an integral part of the work. This article focuses on writing a Penetration Test report and is intended for Junior Pentesters and security managers. The goal is to provide a work methodology that can be applied in practice, during professional interviews, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always partial. Executive summary, scope, methodology can indicate a direction, but their meaning depends on time, asset, user, and expected activity. Therefore, we will build the test around an investigative question, required evidence, and a clear criterion for completion.

The practical scenario in the article is: rewriting a weak Finding into a professional finding. All examples are lab data or process descriptions. When it comes to Penetration Testing, Web, or Cloud, work only with explicit authorization, a defined Scope, and the ability to stop the test.

Report Structure

The important fields are not necessarily those displayed at the top of the screen. When writing a Penetration Test report, stable identifiers, time, source, destination, result, and context must be identified. Useful examples are executive summary, scope, methodology, finding, evidence, risk. The goal is to enable Correlation between records and not just reading a single Event.

It is recommended to create a small Data dictionary: field name, meaning, format, source, expected Null values, and whether it is reliable for linking. This way, a distinction can be made between a display field and an investigative identifier, and it can be identified when a Connector or version has changed the Schema.

Executive summary

The topic 'Executive summary' is a central part of writing a Penetration Test report. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

In practice, write down the executive summary, scope, methodology, finding, evidence, compare it to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Technical finding

The topic 'Technical finding' is a central part of writing a Penetration Test report. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

Risk rating and Evidence

The topic 'Risk rating and Evidence' is a central part of writing a Penetration Test report. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

Remediation, Retest and Appendices

A professional test for writing a Penetration Test report begins with success and failure conditions. A positive Case, negative Case, boundary Case, and similar legitimate activity are defined. This way, both False Negative and False Positive can be identified.

In an authorized environment, a minimal action is used that proves the claim without causing damage. Input, Output, time, and version are saved, and after remediation, a Retest is performed in the same scenario, also checking for Regression on nearby functions.

Unique Test Foci

In this topic, it is recommended to build a focused evidence map in advance. The main test foci are: executive summary, scope, methodology, finding, evidence, risk, remediation, retest. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

executive summary: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.
scope: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.
methodology: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.
finding: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.
evidence: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.
risk: Define the expected value, what will be considered abnormal, and what additional source will verify the finding.

When one of the foci is unavailable, the gap must be documented and an alternative chosen. For example, if a Process identifier is unstable, time, Host, User, and Parent can be used; if a Payload is encrypted, Metadata, volume, frequency, and TLS/DNS context are used.

Recommended Workflow

Define Scope and one working question regarding writing a Penetration Test report.
List the data sources and required evidence: executive summary, scope, methodology, finding.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a lab environment and save time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Perform a Pivot to an additional source to confirm or refute the initial explanation.
Summarize a decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is rewriting a weak Finding into a professional finding. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting, dummy data, a time window, and an expected outcome are defined.

At the end of the exercise, a deliverable that another analyst or tester can review should be submitted: a screenshot or Export of the evidence, a short Timeline, initial assumption, confirming evidence, limitation, and recommendation. When there is insufficient evidence, the correct conclusion is that the scenario has not been proven.

Step	What is performed	Deliverable
Preparation	Define Scope, time, and target. Note which fields or evidence from executive summary, scope, methodology are expected to appear.	Short test plan
Data creation	Perform a safe and simulated action related to writing a Penetration Test report, without real information or impact on a production system.	Controlled Event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Ensure Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what is the possible legitimate explanation.	Intermediate conclusion
Completion	Choose closure, escalation, Finding, or Tuning; add a recommendation and Retest.	Documented deliverable

Practical Checklist

Check and document: Scope and ROE.
Check and document: Test time and source.
Check and document: Request/Response or tool output.
Check and document: Proven impact in the lab.
Check and document: Risk rating.
Check and document: Remediation and Retest.
Specify Time zone, tool version, and collection time.
Save raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and next action with a deadline.

Common Mistakes

Starting a test without a signed Scope.
Using an aggressive Exploit by default.
Not saving Evidence.
Reporting only on CVSS without context.
Not proposing a feasible remediation.
Not performing a Retest.

Summary and CTA

Writing a Penetration Test report that leads to remediation is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and re-tested.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Is it permissible to test writing a Penetration Test report on a public website?

Not without explicit permission from the system owner. Even a seemingly simple test can change data, trigger defense mechanisms, or be considered unauthorized access.

What to do when some data is missing?

Document the missing data, check for an alternative source, and reduce the level of certainty. Do not complete fields based on assumption or present Unknown as valid.

How long should evidence be retained?

The time depends on policy, regulation, cost, and the type of event. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without endangering a real system?

Use virtual machines, dummy data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.