Free tool

Pentest attestation letter generator

Create a professional penetration test attestation letter in minutes: scope, methodology, findings by severity and retest results. Free, no sign-up, and nothing you type leaves your browser.

Everything stays in your browser. Nothing you type is sent to us or stored on a server.

Your firm
The engagement
Methodology
Findings in the report
Remediation retest

Still open after the retest

Report and signature
In the print dialog, choose “Save as PDF”.

[Your firm]

Date:
21 November 2026
Reference:
ATT-2026-001

Penetration Test Attestation Letter

To whom it may concern,

At the request of [Client], [Your firm] performed a [type of assessment] between [start date] and [end date].

The scope of the assessment was:

  • [Systems in scope, one per line]

Testing followed OWASP WSTG and PTES, and combined automated tools with manual testing.

The assessment did not identify any vulnerabilities within the scope tested.

The testing performed is documented in the full assessment report, which is confidential to [Client].

This letter summarizes a point-in-time assessment of the scope listed above. It does not guarantee that the systems are free of vulnerabilities, and it does not cover assets, changes or threats outside that scope and testing period.

Sincerely,

[Name]

Letter template by Closeout · getcloseout.tech

What is a pentest attestation letter?

A pentest attestation letter (also called a letter of attestation or a penetration test summary letter) is a short, signed document in which the testing firm confirms that a penetration test took place: who performed it, when, against which scope, following which methodology, and with what overall result.

Unlike the full report, it contains no technical details of the vulnerabilities. That is the point: the client can hand it to auditors, customers and insurers without exposing how to attack their systems.

Who asks for one

  • SOC 2 and ISO 27001 auditors, as evidence that independent security testing is performed.
  • Enterprise customers, in vendor security questionnaires. They want proof that you test, not your report.
  • PCI DSS assessments: requirement 11.4 calls for internal and external penetration testing at least once every 12 months and after significant changes.
  • Cyber insurance underwriters, when pricing or renewing a policy.
  • Investors and acquirers, during technical due diligence.

What to include in an attestation letter

  1. The testing firm, on its letterhead, and the client the test was performed for.
  2. The type of assessment and the testing window (start and end dates).
  3. The scope: the domains, applications and IP ranges that were tested, and nothing else.
  4. The methodology, for example OWASP WSTG, PTES or NIST SP 800-115.
  5. A summary of findings by severity: counts only, never technical details.
  6. The remediation status after the retest, with the retest date.
  7. A reference to the full report (title, version, date) and a note that it is confidential.
  8. A limitations paragraph: the test was a point-in-time assessment of a defined scope.
  9. The name, title and signature of the person responsible.

The generator above writes every one of these paragraphs for you; fill in the fields and the letter updates as you type.

Attestation letter vs. full pentest report

Attestation letterFull pentest report
AudienceThird parties: auditors, customers, insurersThe client's security and engineering teams
LengthOne pageOften 30 to 200 pages
Vulnerability detailsNoneEvidence, impact, steps to reproduce, fixes
Can be sharedYes, by designOnly under NDA
PurposeProve the test happened, and its outcomeGet the issues fixed

Should the letter mention open findings?

Yes, honestly. A letter that hides open critical findings exposes the testing firm if something goes wrong later. The common practice is to give counts by severity and state the remediation status as of the retest date. If the client wants a letter with nothing open, issue it after a retest has verified the fixes, and never attest to a fix nobody verified.

Issue it before or after the retest?

Both are common. A letter right after testing says what was found; a letter after the retest says what was fixed, which is what auditors and enterprise customers usually want to see. Our guide to pentest retesting explains how to verify fixes so the letter holds up, and the one on remediation timelines covers how long clients usually get.

In Closeout, the attestation comes from the retests themselves: a finding counts as fixed only after an automated retest and a person on your team confirm it, and the letter cites the delivered report by its SHA-256 hash, so an auditor can match the two.

Frequently asked questions

Is this attestation letter generator free?

Yes. There's no account, no limit on letters and no watermark: just an optional one-line credit at the bottom that you can switch off.

Is my client's data safe?

The generator runs entirely in your browser. What you type is kept only in your browser's local storage, so you don't lose a draft, and is never sent to Closeout or stored on a server.

Can I add my logo and brand color?

Yes. Upload a PNG, JPG or SVG logo and pick an accent color; both appear on the letterhead of the PDF.

Is a pentest attestation letter legally binding?

It's a statement of fact from the testing firm, not a certification or a guarantee. That's why it should include a limitations paragraph and only state what was actually tested and verified.

How long is a pentest attestation letter valid?

There's no fixed expiry, but most auditors and enterprise customers expect a test from the last 12 months. PCI DSS, for example, requires penetration testing at least once a year and after significant changes.

What's the difference between an attestation letter and a pentest certificate?

A “certificate” suggests a pass or fail against a standard, and no such standard exists for penetration testing. An attestation letter states what was tested, how, and what was found and fixed, which is what auditors actually ask for.