Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Penetration test reporting turns an engagement into a document that two audiences can act on: an executive summary for decision-makers and reproducible technical findings for engineers.

What Is Penetration Test Reporting?
The report is the deliverable. Everything a tester finds during an engagement exists only in their notes until it is written down in a form that an engineer can reproduce and a director can fund. A weak report wastes a good test, and clients have no way of telling the two apart except by what lands in their inbox at the end.
A professional report answers four questions for every issue: what is wrong, how do we know, what could an attacker do with it, and what exactly should we change. Anything that does not serve one of those four purposes is padding.
Reports are read by at least two audiences who want different things, so the document is layered.
Each finding needs a plain-language title, a severity rating, the affected systems, a description, evidence, impact, and remediation advice. Severity normally comes from CVSS, but a bare CVSS base score is not enough on its own: a critical flaw on an isolated test server matters less than a medium one on an internet-facing payroll system, and the report should say so.
Evidence has to be reproducible. Screenshots with the request and response visible, the exact URL or host, the parameter involved, and the steps in order. Redact anything that would turn the report itself into an attack manual or expose real personal data. Where a tester chained several issues together to reach a crown-jewel system, draw the chain out explicitly, because that narrative is usually what persuades a board to release budget.
Remediation advice should be specific to the client’s technology. “Implement input validation” helps nobody. “Replace the dynamic SQL in OrderLookup.cs with a parameterised query, and remove the db_owner role from the application account” is something a developer can act on this week.
Several schemes set expectations for what a report must contain. CREST member companies work to a defined methodology and reporting standard. Under the NCSC CHECK scheme, tests of government and public sector systems must be led by qualified team leaders and reported in the prescribed format. For financial services, the Bank of England’s CBEST framework requires a detailed threat intelligence-led report plus a joint remediation plan agreed with the regulator.
PCI DSS expects a documented methodology covering the full cardholder data environment, with findings tracked to resolution and testing repeated to confirm the fix. Organisations in scope of the NIS Regulations or working towards ISO 27001 use reports as evidence that technical controls are tested, so the scope statement and dates have to be precise.
A readout call is worth more than another ten pages. Walking the technical team through the top findings, demonstrating one or two live, and agreeing who owns what converts a document into a work plan. Findings then go into the normal vulnerability management process with owners and dates, not into a shared drive.
A retest closes the loop. Without one, nobody can say whether the fixes worked, and the next report will repeat half the same findings.
Ask for a redacted sample before you buy. Warning signs are easy to spot: findings copied verbatim from scanner output, generic remediation text, no evidence, every issue rated high, or an executive summary that is really a technical chapter with shorter paragraphs. Good signs are a clear risk narrative, findings specific to your systems, honest acknowledgement of what could not be tested, and advice that reflects your constraints.
Our Penetration Test Services include a technical report, a board-level summary, a walkthrough session, and a retest of remediated findings.
Length follows findings, not page targets. A focused web application test might produce twenty to forty pages, while a large infrastructure engagement can run past a hundred with appendices. What matters is that the executive summary stays short enough to be read in full, and that every finding carries evidence a developer can reproduce without contacting the tester.
Treat it as highly confidential: it is a map of exactly how to break into your systems. Distribution usually covers the security team, the technical owners of affected systems, and a senior sponsor. Share it over an encrypted channel, not email attachments, record who has a copy, and agree retention periods with your supplier in the contract.
CVSS gives a consistent, defensible starting point and is expected by most auditors. It should not be the final word. A mature report adjusts for business context, saying plainly when an internet-facing medium matters more than an internal critical, and explains the reasoning. Report both the raw score and the contextual rating so readers can see how you got there.
It is a chronological account of how the tester moved from no access to a significant compromise, linking individual findings into one story. A weak password policy plus an unpatched file server plus excessive service account rights may each look moderate alone, but the narrative shows they combined into domain compromise. This section usually drives remediation decisions more than any single rating.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.