Skip to content

Template · Web pentesting · Infrastructure and AD pentesting

Penetration test report template

Penetration test report template in Markdown: executive summary, scope and methodology, detailed findings and a remediation plan.

By Steven Carrier Published

pentest-report-template.md

Download (2.1 KB)
Preview the file
# Penetration test report: [application or system name]

| | |
|---|---|
| Client | [Organisation] |
| Provider | [Testing company] |
| Document version | 1.0 |
| Date | [YYYY-MM-DD] |
| Classification | Confidential |

## Document history

| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | [YYYY-MM-DD] | [Author] | Initial version |

## 1. Executive summary

### 1.1 Context and objectives

[Two or three sentences: why this test, on what scope, on which dates.]

### 1.2 Overall risk level

[Critical / High / Medium / Low], because [one-sentence justification].

### 1.3 Findings by severity

| Critical | High | Medium | Low | Informational |
|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 0 |

### 1.4 Priority actions

1. [Decision to make, owner, deadline]
2. [Decision to make, owner, deadline]
3. [Decision to make, owner, deadline]

## 2. Scope and methodology

### 2.1 Scope tested

| Asset | Address or URL | Environment |
|---|---|---|
| [Application] | [https://…] | [Staging / Production] |

### 2.2 Exclusions

- [Excluded asset and reason]

### 2.3 Testing conditions

- Test type: [black / grey / white box], [internal / external]
- Period: from [date] to [date]
- Accounts provided: [roles]
- Source IP addresses: [addresses]

### 2.4 Standards

- OWASP Web Security Testing Guide (WSTG)
- CVSS 3.1 for vulnerability scoring

### 2.5 Limitations

[What could not be tested, and why.]

## 3. Detailed findings

### 3.1 [ID-01] [Vulnerability title]

| Severity | CVSS 3.1 vector | Score |
|---|---|---|
| [High] | `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N` | [7.5] |

**Description**

[What is vulnerable, and why.]

**Evidence**

1. [Reproduction step]
2. [Reproduction step]

**Impact**

[Concrete consequence for the organisation.]

**Remediation**

- [Primary fix]
- [Defence-in-depth measure]

**References**

- [CWE, OWASP, vendor documentation]

## 4. Remediation plan

| ID | Finding | Severity | Action | Owner | Deadline |
|---|---|---|---|---|---|
| ID-01 | [Title] | [High] | [Action] | [Team] | [Date] |

## 5. Appendices

- A. Tools used and versions
- B. Testing log: dates, times, source IP addresses
- C. Glossary

A penetration test report has two audiences: decision-makers, who read the summary and decide, and technical teams, who fix issues from the write-ups. This template serves both. Download it, then replace every passage in square brackets.

What the template contains

  • Executive summary: context, overall risk level, findings by severity, priority actions.
  • Scope and methodology: assets tested, exclusions, testing conditions, standards, limitations.
  • Detailed findings: one write-up per vulnerability, scored with CVSS 3.1.
  • Remediation plan: one row per action, with an owner and a deadline.
  • Appendices: tools, testing log, glossary.

Writing tips

  • Write the executive summary last, once every write-up is finished.
  • One vulnerability, one write-up: group occurrences of the same flaw in a single write-up.
  • Describe the test’s limitations: what was not tested matters as much as what was.
  • To save time, the report writing AI skill produces write-ups in this format.

Convert to Word or PDF

The template is in Markdown so it stays easy to version. Pandoc converts it to whatever format your client expects:

pandoc pentest-report-template.md -o report.docx
pandoc pentest-report-template.md -o report.pdf

Sources

Related resources

  • AI prompt · Web pentesting · Infrastructure and AD pentesting

    Critical vulnerability alert prompt

    Prompt that drafts the urgent client notification when a critical vulnerability is found during testing: facts, impact and immediate containment advice.

    Published

  • AI prompt · Infrastructure and AD pentesting · Web pentesting

    CVE summary prompt

    Prompt that summarises a CVE or vendor advisory: affected versions, conditions, impact, applicability questions for the client, fix and limits.

    Published

  • Tool · Web pentesting · Infrastructure and AD pentesting

    CVSS 3.1 calculator

    Compute the CVSS 3.1 base score, severity and vector string of a vulnerability, or paste an existing vector to review it. Runs in your browser.

    Published

BEAROPS

Need a penetration test?

BEAROPS experts test your applications, infrastructure and cloud, black box or grey box, following OWASP, NIST and ANSSI guidance.