Platform OverviewOne evidence trail, from intake to Jira.See how it fits together
See it on your documentsA 30-minute call. Bring a vendor you are reviewing now.Book a demo
Assurance reports and vendor evidencePublished Updated

Penetration test report

Also called: Pen test report, Pentest summary

Definition

A penetration test report is the written result of an authorised simulated attack on a system, documenting the scope, method, findings with severity and recommendations. Vendors usually share a summary or a letter from the tester rather than the full report.

What Penetration test report means

NIST SP 800-115 describes penetration testing as security testing in which assessors mimic real-world attacks to find ways around a system's security features. PCI DSS Requirement 11.4 requires internal and external penetration testing at least once every 12 months and after significant changes. Under DORA Articles 26 and 27, certain financial entities carry out threat-led penetration testing at least every three years.

The full report contains exploitable detail, so most vendors share an executive summary, a letter from the testing firm, or a findings table without technical specifics. That can still be enough if it shows scope, dates, the tester's independence and the status of each finding.

What matters for a review is coverage and follow-through. A clean test of a marketing website says nothing about the application you use, and a list of high-severity findings with no retest date is a remediation question, not a pass.

What to check in vendor documents

  • The scope, and whether it covers the application, APIs and environment you use.
  • The test dates, and whether the testing firm is independent of the vendor.
  • The number of findings by severity and their remediation status.
  • Retest evidence for critical and high-severity findings.
  • The method used, such as authenticated testing of the application.

Related terms

Sources

  1. NIST SP 800-115, Technical Guide to Information Security Testing and Assessmentcsrc.nist.gov/pubs/sp/800/115/final
  2. Regulation (EU) 2022/2554 (DORA)eur-lex.europa.eu/eli/reg/2022/2554/oj
  3. PCI Security Standards Council, document library (PCI DSS v4.0.1 and AOC templates)www.pcisecuritystandards.org/document_library

Summarised for practitioners, not legal advice. Check the source text for your own obligations.

Penetration test report: questions

Short, direct answers.

Not necessarily. A summary from the testing firm that shows scope, dates and the status of each finding is often enough. For critical vendors, ask to review the full report under NDA or on screen.

See it on your own vendor documents.

Open a demo workspace with a sample vendor, its documents and its findings. Or bring your own vendor to a 30-minute call.

Procurement, compliance, security and auditOne workspace, one record of every decision