The short answer
The report is the full record: what was tested, every finding, the proof and how to fix it. The attestation letter is a short, signed summary you can share with customers and auditors without handing over the full report.
What is in the report
- 1A summary for leadersWhat was tested, the big risks and what to do first, in plain English.
- 2Scope and methodExactly what was tested, when, and how.
- 3FindingsEach problem, how serious it is, proof that it is real, how to repeat it and how to fix it.
- 4Retest resultsWhich problems were fixed and checked again.
Findings are ranked, so your team fixes the most serious problems first.
What is in the attestation letter
The letter is short and signed by the testing firm. It usually says:
- Who did the test, and when
- What was in scope
- A short summary of the results
- Whether the findings were retested and fixed
It does not list the details of each problem. That is the point: you can share it freely.
Who gets which
- Your team gets the full report, to fix things.
- Your auditor gets the report and the retest results, as evidence.
- Customers and prospects get the letter. Share the full report only under an NDA, if at all.
Using them in Vanta, Drata or Secureframe
Each of these tools has a place for pentest evidence. Upload the report and the letter there. If the tool asks for proof that findings were fixed, add the retest results too.
Keep the files somewhere safe. The report shows how someone could attack you, so treat it like any other secret.
What makes a good report
- Someone outside security can follow it.
- Every finding has proof, not just a tool's guess.
- The fix steps fit your setup, not a generic checklist.
- It says what was not tested, so there are no surprises later.