Skip to content

Template · Web pentesting · Infrastructure and AD pentesting

Retest report template

Retest report template in Markdown: reference to the initial report, retest scope, status per finding, evidence and residual risk.

By Steven Carrier Published

retest-report-template.md

Download (3.1 KB)
Preview the file
# Retest report: [application or system name]

| | |
|---|---|
| Client | [Organisation] |
| Provider | [Assessment company] |
| Document version | 1.0 |
| Report date | [YYYY-MM-DD] |
| Classification | Confidential |

## Document history

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

## 1. Reference to the initial report

| | |
|---|---|
| Initial report title | [Title] |
| Version and date | [1.0, YYYY-MM-DD] |
| Initial test period | [date] to [date] |
| Number of initial findings | [N] |

This document supplements the initial report and reuses its finding identifiers.

## 2. Retest scope

### 2.1 Findings covered

| ID | Title | Initial severity | Included in the retest |
|---|---|---|---|
| [ID-01] | [Title] | [High] | [Yes / No, reason] |

### 2.2 Conditions

- Period: [date] to [date]
- Environment tested: [Staging / Production], [deployed version or build]
- Accounts provided: [roles]
- Source IP addresses: [addresses]
- Known changes since the initial test: [new features, migration, architecture change]

### 2.3 Limitations

[What was not rechecked, and why. The retest does not look for new vulnerabilities: it verifies that the listed findings have been fixed.]

## 3. Summary of results

| Fixed | Partially fixed | Not fixed | Not retested |
|---|---|---|---|
| [0] | [0] | [0] | [0] |

Overall assessment: [one or two sentences on how the risk level has changed since the initial report.]

| Risk level | Initial report | After retest |
|---|---|---|
| Overall | [High] | [Medium] |

## 4. Result per finding

Status definitions:

- **Fixed**: the original scenario and its reasonable variants no longer work.
- **Partially fixed**: the original scenario is blocked, but a variant or a residual effect remains.
- **Not fixed**: the finding can still be reproduced.
- **Not retested**: the finding could not be verified, with the reason.

### 4.1 [ID-01] [Finding title]

| Initial severity | Status | Residual severity | Retest date |
|---|---|---|---|
| [High] | [Fixed / Partially fixed / Not fixed / Not retested] | [None / Low / …] | [YYYY-MM-DD] |

**Fix announced by the client**

[Description of the declared fix, with the ticket or version reference.]

**Verification performed**

1. [Verification step: original scenario replayed]
2. [Verification step: variants tested]

**Evidence**

```text
[Request or command replayed and observed result]
```

**Residual risk**

[What remains exposed, under which conditions, with what impact. State "None" if the finding is fixed.]

**Recommendation**

- [Complementary action, or "No action"]

## 5. Remaining action plan

| ID | Finding | Status | Residual risk | Action | Owner | Deadline |
|---|---|---|---|---|---|---|
| [ID-02] | [Title] | [Not fixed] | [Medium] | [Action] | [Team] | [Date] |

## 6. Findings not retested and accepted risks

| ID | Finding | Reason | Decision |
|---|---|---|---|
| [ID-05] | [Title] | [Environment unavailable / Risk accepted by management] | [New retest on YYYY-MM-DD / None] |

## 7. Appendices

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

A retest verifies that the fixes announced by the client really remove the vulnerabilities in the initial report. It does not look for new flaws: it answers, finding by finding, the question "is it fixed?". This template reuses the identifiers from the penetration test report template and extends its follow-up.

What the template contains

  • Reference to the initial report: title, version, date, number of findings.
  • Retest scope: findings selected, conditions, known changes, limitations.
  • Summary of results: count by status and change in risk level.
  • Result per finding: status (fixed, partially fixed, not fixed, not retested), verification, evidence, residual risk.
  • Remaining action plan: what is still to be handled, with owner and deadline.
  • Findings not retested and accepted risks: the reason and the associated decision.

Writing tips

  • Replay the original scenario first, then try a few reasonable variants: a fix that only blocks the exact request in the report is "partially fixed".
  • Keep the identifiers from the initial report and from the matching vulnerability write-up.
  • State the version or build tested: a finding fixed in staging is not necessarily fixed in production.
  • Do not mark a finding "fixed" if you could not recheck it: use "not retested" and give the reason.
  • Reassess the residual severity in CVSS 3.1, starting from the initial report’s vector and changing only the metrics that the fix has affected.
  • Update the executive summary with the new risk level.

Convert to Word or PDF

pandoc retest-report-template.md -o retest.docx
pandoc retest-report-template.md -o retest.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.