Skip to content

Template · Web pentesting · Infrastructure and AD pentesting

Executive summary template

One-page executive summary template: context, overall risk, findings by severity, priority actions as decisions with owners and deadlines.

By Steven Carrier Published

executive-summary-template.md

Download (1.8 KB)
Preview the file
# Executive summary: [application or system name]

| | |
|---|---|
| Client | [Organisation] |
| Provider | [Assessment company] |
| Recipients | [Executive board, CIO, CISO…] |
| Date | [YYYY-MM-DD] |
| Classification | Confidential |

This document fits on one page. Technical details are in the reference report: [report title, version and date].

## Context and objectives

[Two or three sentences: why this test, on which scope, between which dates, from which starting point (external access, user account, internal access).]

## Overall risk level

**[Critical / High / Medium / Low]**, because [one-sentence justification, in terms of business impact].

[One sentence on what works well: strengths observed, to keep the picture balanced.]

## Findings by severity

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

Most important findings:

1. [Finding in one sentence, no jargon, with its possible effect on the organisation]
2. [Finding in one sentence]
3. [Finding in one sentence]

## Priority actions: decisions required

| No. | Decision to take | Findings covered | Owner | Deadline |
|---|---|---|---|---|
| 1 | [Decision, for example "Fix and redeploy…"] | [ID-01, ID-02] | [Name or role] | [YYYY-MM-DD] |
| 2 | [Decision] | [ID-03] | [Name or role] | [YYYY-MM-DD] |
| 3 | [Decision] | [ID-04] | [Name or role] | [YYYY-MM-DD] |

Resources or trade-offs to provide: [budget, person-days, maintenance window, accepted risk to formalise].

## Next steps

- [YYYY-MM-DD]: [debrief with the technical teams]
- [YYYY-MM-DD]: [progress review on the fixes]
- [YYYY-MM-DD]: [retest of the fixed findings]

## Limitations of the test

[One or two sentences: what was not tested, limited duration, accounts available. A penetration test is a snapshot in time, not a guarantee that no vulnerability remains.]

Executives read one page, sometimes less. They are not looking for the list of vulnerabilities: they want to know whether the risk is acceptable, what must be decided and who will do it. This template fits on one page and reuses the summary from the penetration test report template, so it can be delivered separately from the technical report.

What the template contains

  • Context and objectives: why this test, on which scope, on which dates.
  • Overall risk level: one level, a one-sentence justification, and what works well.
  • Findings by severity: a count table and the three findings that matter most.
  • Priority actions: decisions to take, each with an owner and a deadline.
  • Next steps: debrief, fix tracking, retest.
  • Limitations of the test: what was not covered.

Writing tips

  • Write it last, once all the vulnerability write-ups are finished.
  • Phrase decisions, not technical tasks: "Fund the redesign of authentication" rather than "Enable MFA".
  • Translate each finding into its effect on the business, with no jargon or CVSS vector.
  • Name an owner and a date for every action. An action without an owner will not be done.
  • Keep one sentence on strengths: a purely negative summary loses credibility.
  • Stay on one page. What does not fit goes in the technical report.
  • To set scope and expectations upfront, the penetration test scoping checklist is a good starting point.

Convert to Word or PDF

pandoc executive-summary-template.md -o summary.docx
pandoc executive-summary-template.md -o summary.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.