Skip to main content
Legia

Cybersecurity

Can a Penetration Testing Report Be Used for a Tender?

A penetration testing report can be used as evidence of security testing in a tender, as long as its scope, date, and remediation status meet the requirements. Here is how to prepare it without exposing the details of the flaws.

SEO and Content Specialist

2 min read Reviewed by Legia Cybersecurity Team

A glowing laptop keyboard in a dark room

Short answer: yes, as evidence that your system has been tested, as long as its scope covers the system being offered, its test date is within the requested period, and important findings have been closed, as shown by a retest. Usually what is submitted is not the full technical report but a summary and a statement that the flaws have been closed. The exact requirements always follow the tender documents or the client’s request.

Requests for evidence of security testing are increasingly common in tenders and system procurement contracts. The question for a bidding company: is the existing pentest report enough for the tender, and which parts are safe to hand to an outside party.

What is checked in a pentest report for a tender?

There is no single format, but reviewers generally want to confirm these six things:

What is checkedThe question behind it
TesterWho did the testing, and whether they are outside the development team
ScopeWhether the system being offered was actually included in the test
Date and periodWhen the test was done, and whether it still represents the current system
Method and referenceBlack box, grey box, or white box, and references such as OWASP
Summary of findingsHow many findings at each severity level
Remediation statusWhether critical and high findings have been closed

If the tender documents require more detail, such as tester qualifications or a specific standard, confirm the fit before testing starts, not after the report is done.

Illustration: security testing

Full report or summary?

A technical report contains the attack path and reproduction steps, so its content is a map of the gaps in your system. PTES separates the executive summary for decision-makers from the technical report for the team doing the fixes. For a tender, submit the executive summary plus the statement that flaws have been closed. If the client still asks for the full report, propose handing it over under a confidentiality agreement and through a restricted channel, not as an attachment to the bid file read by many people. How to read the report’s contents is covered in the article How to Read a Penetration Testing Report.

Date, validity, and retesting

A penetration testing report has no official validity period. The report describes the system at the time it was tested, so every major release makes it less representative. Audit requirements generally call for testing once a year, but the accepted period still follows the tender documents.

Retesting is often the most convincing part. A report with critical findings still open can actually hurt a bid, while a retest report shows the flaws have been fixed and checked again by the tester. So schedule testing far enough ahead of the tender deadline for fixes and the retest to be completed.

How Legia prepares it

Legia’s Penetration Testing report contains a summary for management, the attack path, reproduction steps, CVSS-based severity, and retest results with a statement that the flaws have been closed. Retesting is included in the package. The report is delivered through an encrypted channel only to the recipients you designate, under a confidentiality agreement. Each client’s requirements differ, so share your tender requirements during the consultation session. The factors that affect its scope and cost are in the article What Determines the Cost of Penetration Testing.

Sources

Category Cybersecurity

Keep reading

Related articles

All Articles