Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 38 ยท Reporting and Remediation

Writing the Penetration Test Report

Learn the structure of a professional penetration test report, how to write an executive summary and clear findings, and how to generate a consistent report from data.

The report is the product of a penetration test. The client cannot see your skill during the test; they only see what you deliver. A report that is accurate, readable and actionable justifies the engagement and gets problems fixed. A confusing report, however clever the testing, leaves the client no better off.

A good report serves two audiences at once: executives who need to understand the business risk in a few minutes, and engineers who need exact steps to reproduce and fix each issue. The structure below separates them so each reader can stop when they have what they need.

The usual structure

  1. Title page and document control: client, dates, version, author, classification ("Confidential"), distribution list.
  2. Executive summary (one or two pages, no jargon): what was tested, the overall result, the top risks in business terms, and the most important actions.
  3. Scope and methodology: what was in and out of scope, the dates and testing positions (external, internal, assumed breach), the standards followed (for example PTES, OWASP WSTG, NIST SP 800-115), limitations and assumptions.
  4. Summary of findings: counts by severity, a table of all findings with IDs, an attack-path diagram if relevant.
  5. Detailed findings: one section per finding in a fixed template.
  6. Positive observations: controls that worked well.
  7. Remediation roadmap: prioritized actions (quick wins, short, long term).
  8. Appendices: tools used, raw scan summaries, test accounts, evidence manifest, glossary.

One report, two readers

Leaders Risk in plain words
Engineers Steps to reproduce and fix
Auditors Scope, method, evidence

Layer the document so each reader finds their part fast.

1 / 2

The executive summary

Write it last, but put it first. A strong summary answers: Are we safe? What are the worst problems? What should we do first? Use business language:

  • Weak: "We identified SQL injection (CWE-89) in the id parameter."
  • Strong: "An unauthenticated visitor could read the customer database through the public web portal. We recommend fixing this immediately, before anything else."

Include the overall impression honestly: a few well-managed controls and several serious gaps, with the number of findings by severity and the biggest theme (for example "credentials management and network segmentation"). Do not scare, do not flatter, and do not use the executive page to show off tools.

The finding template

Every finding uses the same fields so readers know where to look:

Field Content
ID and title F-003 Insecure direct object reference in order API
Rating Severity, likelihood, impact, CVSS vector and score
Affected assets Exact URLs, hosts, accounts
Description What the flaw is, in two or three sentences
Steps to reproduce Numbered, exact, with sanitized requests
Evidence Redacted screenshots or captures
Impact What an attacker gains, in business terms
Recommendation Specific, prioritized fix; short-term mitigation and long-term fix
References CWE, OWASP, vendor advisory

Write recommendations the client can act on: "Check on the server that the order belongs to the logged-in user before returning it; add an automated test for it" beats "improve access control".

Write each finding so it can be read alone. It will be pasted into tickets, emailed to the team that owns the system and read months later by someone who never saw the rest of the report.

Generating a consistent report

Many teams keep findings as structured data and generate the document from a template. That keeps formatting and wording consistent across testers and makes statistics automatic. The stand-in below builds a Markdown report from a findings list: it sorts by severity, counts them, fills the template, and writes the executive paragraph from the numbers.

Python Generate a report from findings data

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Because the content is data, a style change (adding a "retest status" column, for instance) happens in one place, and every finding follows the same pattern automatically. Reading the generated document also shows if any finding is missing its steps or its fix.

Writing style tips

  • Plain, active sentences. "The server accepts any order ID" is clearer than "improper authorization was observed."
  • Consistent terms: choose one word for each concept and use it every time.
  • Show, do not claim: every rating needs evidence next to it.
  • Be fair: describe the facts and the risk without blaming people or teams.
  • State limitations: what you did not test, time constraints, systems that were unavailable.
  • Proofread and have a colleague review: wrong IPs and mixed-up client names destroy trust.

Delivery and confidentiality

The report contains a map of the client's weaknesses, so protect it like a loaded tool. Send it through an encrypted channel or a secure portal, mark it with the classification and version, limit the distribution list, and follow the contract's retention rules. Deliver urgent critical findings before the final report, in a short verbal or written alert.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Who is the executive summary written for?

    Executives need the overall result, the main risks and the priorities without technical detail.
  2. 2. Which recommendation is best?

    Specific, actionable advice lets the team fix the problem without guessing.
  3. 3. Why generate reports from structured finding data?

    A template with data produces consistent sections and easy summaries.
  4. 4. When should urgent critical findings be communicated?

    A critical exposure should not wait weeks for a document.

Summary

  • A report serves executives, engineers and auditors; layer it with an executive summary, scope and method, findings and appendices.
  • Write the executive summary in business terms and be honest about results.
  • Use a fixed finding template with rating, assets, steps, evidence, impact and a specific recommendation.
  • Generate reports from structured data for consistency; proofread and review.
  • Protect the report in transit and storage, and deliver critical issues immediately.

Next: Remediation and retesting