Guide

How to deliver a pentest report securely

A pentest report is a step-by-step guide to attacking your client. Here's how to get it to the right people without it ending up in the wrong inbox, and how to prove it arrived.

Updated 28 October 2026 · By the Closeout team

Why the report needs protecting

A good report contains everything an attacker would want: vulnerable endpoints, working proofs of concept, internal hostnames, sometimes credentials or session tokens captured during testing. Until the findings are fixed, it is the most sensitive document the client has about their own systems.

Email is where it usually leaks. Messages get forwarded, synced to personal phones, kept on mail servers for years, and exposed when a mailbox is compromised. Once sent, an attachment can't be recalled, and you never know who opened it.

Delivery methods compared

MethodEncrypted at restAccess controlProof of deliveryVersions
Email attachmentNoNone once sentNoNo
Password-protected ZIP or PDFDepends on the cipher and passwordAnyone with the passwordNoNo
File-sharing link (Drive, SharePoint, Box)By the providerDepends on link settingsPartial (access logs)Partial
PGP or S/MIME emailYesRecipient's keyNoNo
Client portalYesNamed accounts, with MFAYesYes

No method is perfect, but the gap between an attachment and a portal with named accounts and a download record is large, and it's the difference auditors and security-conscious clients notice.

A secure delivery checklist

  1. Agree the recipients before testing starts: named people, not a shared mailbox.
  2. Deliver to individual accounts protected by multi-factor authentication.
  3. Encrypt the report at rest, ideally with a key specific to the engagement.
  4. Never send a password through the same channel as the file it protects.
  5. Record who downloaded which version, and when.
  6. Issue updates as new versions (v2, v3) rather than overwriting the original.
  7. Publish the SHA-256 hash of the final report, so anyone can later check a copy is the genuine one.
  8. Revoke access when the engagement ends, and delete the report when the agreed retention period is over.

If you must use a password-protected file

  • Use AES-256 encryption. Legacy ZIP encryption (ZipCrypto) is broken and can be cracked quickly; tools like 7-Zip offer AES-256.
  • Use a long random password, not the client's name and the year.
  • Share the password through a different channel: a phone call, SMS or a messenger the client uses.
  • Remember that anyone with the password can open every copy, forever. There is no way to revoke it.

Proof of delivery and versions

“We never got the report” and “which PDF is the final one?” are both avoidable. A delivery record with the version, the person and the time settles the first; locked, numbered versions settle the second. After a retest, re-issue the report as a new version and keep the old one, so the history of what was found and what was fixed stays intact. Our guide to pentest retesting covers what the new version should contain.

The SHA-256 hash ties it together: an attestation letter that cites the report's hash lets an auditor confirm the letter refers to exactly the document the client received.

After delivery: retention and deletion

Keep the report for as long as your contract and legal obligations require, and no longer. Write the retention period into the statement of work, delete your copies when it ends, and tell the client when you have. Old reports on a forgotten file share are a liability for both sides.

Closeout delivers the report inside the client's remediation portal: each PDF, up to 200 MB, is encrypted with its engagement's own key, every download is recorded with the person and the version, delivered versions are locked, and the attestation cites the report by its SHA-256 hash.

Frequently asked questions

Is it OK to send a pentest report by email?

It's common, but it's the weakest option: the attachment can be forwarded, synced and kept indefinitely, and you can't revoke it or know who opened it. If you use email, at least encrypt the file and send the password separately.

Should I password-protect the PDF?

It's better than nothing if you use AES-256 and a strong password sent by another channel. But anyone with the password can open every copy forever, and you still have no record of who did.

How long should a pentest firm keep client reports?

As long as the contract and legal obligations require, and no longer. Agree the period in the statement of work and delete your copies when it ends.

What is the SHA-256 hash of a report for?

It's a fingerprint of the exact file. Anyone can recompute it to confirm a copy hasn't been altered, and an attestation letter can cite it so the letter and the report can be matched.

Who should receive the report?

Named people agreed before testing, usually the security lead and the owners of the affected systems. Avoid shared mailboxes and distribution lists.