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
- Remediation planA remediation plan is an agreed set of actions, owners and deadlines for closing the gaps found in a vendor assessment, such as missing controls, contract terms or evidence, tracked until each item is closed or formally accepted.
- PCI DSS Attestation of Compliance (AOC)A PCI DSS Attestation of Compliance (AOC) is the PCI Security Standards Council form that declares an entity's compliance status with the Payment Card Industry Data Security Standard, following either a Report on Compliance or a self-assessment questionnaire.
- Security ratingsSecurity ratings are scores produced by external providers from internet-observable data about an organisation, such as exposed services, certificate and email configuration and malware signals, without the organisation's participation.
- Cyber Resilience Act (CRA)The Cyber Resilience Act (CRA) is Regulation (EU) 2024/2847, which sets cybersecurity requirements for hardware and software products with digital elements sold in the EU. Manufacturers have had to report actively exploited vulnerabilities since 11 September 2026.
Sources
- NIST SP 800-115, Technical Guide to Information Security Testing and Assessmentcsrc.nist.gov/pubs/sp/800/115/final
- Regulation (EU) 2022/2554 (DORA)eur-lex.europa.eu/eli/reg/2022/2554/oj
- 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.