ESSENTIAL GUIDANCE · BUYER GUIDE · 5 min read

Part of Validate insights →

Penetration Testing Report Example: Scope and Findings

Explore this penetration testing report example from Pentesys. It shows how a sample web application penetration test report covers scope, executive findings, technical evidence, recommendations and retesting.

Need an acronym translated? Open the cyber glossary →

Download our web application penetration testing report example

This is Pentesys's branded Example Ltd web application penetration test report. It is approved for public release. Download the full 24-page PDF to see how scope, executive findings, technical results and next steps are shown.

Download the example penetration test report PDF ↓

Use it as a guide to penetration testing report structure and detail. It is not evidence about your systems. It is not a promise that every engagement produces the same findings, coverage or outputs. Agree those details in your quote.

Start with scope, access and exclusions

The example describes authenticated web application testing in a pre-production environment. It uses a Standard User account and an Administrator account. It records the testing window, the target environment, exclusions and caveats.

Read these boundaries before you interpret the findings. A report should make clear which application, environment, identities and activities were tested, and which were left out.

Read the executive summary with the technical findings

The executive summary brings together key findings and positive observations. The technical results explain the test method and risk rating. They then list each finding with supporting evidence and remediation advice.

Leaders need a clear view of the main risks. Engineers need enough context and evidence to understand the issue and plan the fix. Both views should describe the same assessment and its limits.

Look for evidence and practical recommendations

The example includes findings about access control, login, input handling and security configuration. Each finding should be read with its context, severity and evidence, not as a claim about a different application.

When you commission testing, agree the evidence and report detail your team needs, how critical findings will be escalated, and who will own remediation actions.

Confirm remediation and retest arrangements

The report includes a Retesting & Next Steps section. It covers fix timelines, a retest offer and continued checks. These are the arrangements stated in this example. Confirm the scope, timing, conditions and cost of follow-up in your own quote.

A reported fix and a separately verified fix are different states. A retest should show what was checked again and the result within that scope. It does not prove that every part of a system is secure.

Use the report to discuss your own needs

Compare the sample with the decision your assessment must support. Agree the target systems, starting access, testing method, reporting, debrief and retesting before work begins. AI-led, combined and human-led work can use different test scopes and outputs.

Use the related guidance below to compare delivery models, report inclusions and the evidence you may need to share with customers.

Compare penetration-testing models, review scope and preparation, or explore Pentesys Validate.

Q&A

What does this penetration testing report example show?

It shows Pentesys's branded Example Ltd web application report, including scope, exclusions, executive findings, technical results, recommendations and retesting arrangements. Pentesys has approved this copy for public release.

Does every test produce this exact report?

No. The systems tested, testing method, investigation scope and agreed outputs determine the report. If you are looking for a penetration testing report template, use this completed sample to discuss the structure, evidence and detail you need.

Does downloading this report provide assurance about our systems?

No. The example does not test your systems. Assurance must come from an authorised assessment of your agreed scope, with its dates, evidence and limits.

Is retesting always included on the terms shown in the example?

Confirm the retest scope, timing, conditions and charges in your own quote. The arrangements described in an example report do not automatically apply to a new engagement.

Why is the report's scope so important when reviewing the findings?

Scope defines what was actually tested, including the application, environment, accounts, testing window, exclusions and caveats. Without that context, findings can be misunderstood or applied to systems, users or actions that were not part of the assessment.

Who should read the executive summary and who should read the technical findings?

Leaders should use the executive summary to understand the main risks and positive observations at a decision-making level. Engineering and remediation teams should review the technical findings because they provide the test method, rating, evidence and advice needed to plan corrective work. For a penetration testing executive summary example, read Section 2, Executive Summary, in the downloadable PDF.

What should be agreed before commissioning a penetration test?

You should agree the target systems, starting access, testing method, report detail, evidence requirements, escalation route for critical findings, debrief arrangements, remediation ownership and retesting terms before work begins.

Why does the example report not provide assurance for another organisation's systems?

The example concerns Example Ltd and its stated scope only. Assurance for your organisation requires an authorised assessment of your own agreed systems, access, dates, evidence and limits.

What is the difference between fix work and retesting?

Fix work is the work undertaken to resolve reported issues. Retesting is a separate follow-up check that confirms what was checked again and whether the fix worked within the agreed retest scope.

About this guide

Published by the Pentesys Editorial Team. Technical review lead: James Hinton, Offensive Security Lead. Meet James and explore his experience and qualifications on our Company page.

TALK TO PENTESYS

Apply this guidance to your environment.

Tell us what you need to understand, test or prove. We'll help you choose a proportionate next step—without forcing the conversation into a predefined package.

Discuss your testing scope →Explore Validate

Keep reading

Pentesys trust and assurance

Recognised credentials. Responsible AI. Experienced people.

Clear evidence of our company standards, testing services and access to AI programmes.

Independent company assurance

CREST member company for Penetration Testing in EMEA

CREST member company

Penetration Testing in EMEA. Company standards independently assessed by CREST.

Valid until 1st November 2027View company certificate
CREST Security Testing accreditation for penetration testing

CREST-accredited human-led penetration testing

Independent assurance for Pentesys’s human-led penetration-testing service.

Human-led testingView CREST listing

AI-enabled testing assurance

CREST accreditation for AI-enabled penetration testing

CREST-accredited AI-enabled penetration testing

Pentesys is one of the first ten companies worldwide accredited by CREST for AI-enabled penetration testing. The accreditation assesses the responsible, secure and appropriate use of AI in penetration-testing services.

AI-enabled penetration testingView CREST announcement

Responsible-AI commitment

CREST AI Charter signatory

CREST AI Charter signatory

A separate commitment to responsible, transparent and accountable use of AI in cybersecurity.

Responsible-AI commitmentAbout the CREST AI Charter

Secure organisational baseline

Cyber Essentials certified

Cyber Essentials certified

Pentesys is certified across the whole organisation against the Cyber Essentials baseline controls.

Recertification due 12 August 2027View Cyber Essentials certificate

Controlled AI programme access

Pentesys participates in Anthropic’s Cyber Verification Program (CVP) for Claude and has approved access to OpenAI Daybreak Blue.

Anthropic CVP for Claude

Participation in Anthropic’s Cyber Verification Program.

Programme participationAbout Anthropic CVP

OpenAI Daybreak Blue

Approved access for defensive cybersecurity work.

Approved programme accessAbout Daybreak Blue

CREST accreditation applies to Pentesys’s service delivery, not to an AI model, the Portal or an appliance.

Meet the expertise behind our testing