Skip to content

AI prompt · Web pentesting · Infrastructure and AD pentesting

Prompt: executive summary of a technical report

Prompt that produces a one-page executive summary from a technical report: business risk, top priorities phrased as decisions, and no jargon.

By Steven Carrier Published

Works with: Claude, other chat assistants

You are a cybersecurity consultant writing for non-technical executives. Write the one-page summary of the audit report below.

Technical report: {{report}}
Business sector: {{sector}}
Target audience: {{audience}}

The summary fits on one page and follows this structure:
1. situation in three sentences: what was tested, the overall risk level, the main reason;
2. business risks: at most three, each phrased as a business consequence (business interruption, customer data leak, regulatory penalty, reputational damage), with no vulnerability name or technical acronym;
3. priorities: at most five, phrased as decisions to take (who decides, what, by when), with the estimated effort as an order of magnitude;
4. positive points observed, if any;
5. proposed next step.

Rules: no unexplained jargon, no raw technical score (CVSS); add no information that is absent from the report; neither downplay nor exaggerate severity; if the report does not allow you to qualify a business consequence, say so rather than assume.

Replace the highlighted variables before use.

An audit report is written first for technical teams. This prompt helps extract the page that management will read: what risk for the business, which decisions to take, in what order. It complements the writing described in the pentest report skill, which covers the full report.

Fill in the variables

Variable Example
{{report}} the findings summary of the report (titles, severity, impact, recommendations), without credentials or exploitation details
{{sector}} private clinic, health data processing, dependence on an online appointment booking platform
{{audience}} managing director and chief financial officer, no technical background, quarterly budget decisions

The sector guides the translation into business consequences; the audience sets the level of language and the kind of decisions available. Clear scoping upfront, as in the penetration test scoping checklist, makes this easier.

Review the output

  • Compare every risk and every priority with the report: the summary must contain nothing that is not in it.
  • Check the severity: an alarmist or reassuring wording that departs from the actual criticality puts your credibility at stake.
  • Check that each priority is really a decision (an owner, a deadline), not general advice.
  • Reread it as a non-technical reader would: any term that needs explaining must be explained or removed.
  • Treat effort estimates as orders of magnitude to validate with the teams concerned.
  • Give the model only what your engagement agreement allows you to share with an AI service; summarise and anonymise the report rather than pasting it whole.

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.