A customer asks for a pentest report. Now what?

The deal is almost closed. Then the customer's procurement or security team comes back with one question: can you provide a recent pentest report? If you have one, the question is what you do and don't share. If you don't, the deal hangs on a document you don't have. Both are solvable. The customer isn't asking for perfection, but for proof that an independent party has looked and that you have fixed the problems it found.

The short answer

If you have a recent report, share the executive summary and the retest statement, and the full technical report only under NDA. If you don't, be honest about it, name a date and schedule the test on the product the customer is going to use. A concrete schedule keeps a deal warm more often than a vague "we're working on it".

Why the customer asks

In almost every case the customer has to demonstrate something themselves, to a regulator, an auditor or their own board. You are a link in their story.

What drives the customerWhat the customer has to demonstrate
NIS2That they assess the security of their suppliers. That requirement travels to you through the supplier questionnaire.
ISO 27001That information security in supplier relationships is safeguarded (Annex A 5.19 to 5.22).
SOC 2That they assess and manage the risks of their vendors (CC9.2). Their auditor asks how they did that.
GDPRThat their processors take appropriate technical measures. Article 32 explicitly mentions regularly testing and evaluating those measures.
DORA (banks, insurers)That ICT risks at third-party providers are managed and contractually secured.

That means a customer can't simply accept "we take security seriously". They need something they can put in their own file. The NIS2 supply-chain requirement is covered in NIS2 and your supply chain.

What the customer wants to see in the report

Not every report convinces. Security teams look at a handful of fixed points.

  • Recent. In practice most customers apply a twelve-month window. If your product has changed significantly since then, even a six-month-old report carries less weight.
  • Independent. Carried out by an external party. Nobody is convinced by people assessing their own work.
  • About the right product. The scope has to cover the service the customer buys. A report on your marketing website says nothing about your customer portal.
  • Manual, not a scan. An export from a vulnerability scanner is not a pentest report. A security team sees the difference at a glance.
  • With resolved findings. They want to see that critical and high findings have been fixed, preferably confirmed by a retest. Having findings is normal.
  • Genuine. A PDF can be altered in a few minutes. That is why every Resync report is digitally signed, so your customer can check for themselves that it is authentic and unaltered. Is a penetration test report genuine? explains how that works.

What you do and don't share if you already have a report

A complete pentest report describes step by step how an attacker could have got in. Even when everything has been fixed, that remains sensitive information about your architecture, your integrations and the places where things went wrong before. So you don't just send it as an attachment.

DocumentWho do you share it with?
Executive summaryThe customer who asks for it. It describes scope, approach, the number of findings per severity and the conclusion, without technical details.
Retest statementThe customer who asks for it. It shows that the findings have been resolved.
Full technical reportOnly under NDA, and preferably for review rather than as an attachment. Ask the customer what they need it for. Often the summary turns out to be enough.

If your report is more than a year old, or does not cover the product the customer is buying, say so honestly and say when the next report will be ready. Presenting an old report as current will come out sooner or later, and then it costs you more trust than the gap itself.

If a customer is waiting for a pentest report, in a free intake we work out what scope the customer needs and when you can have the report. Reply within one working day.

Request a free intake →

How to keep the deal warm without a report

Not having a report doesn't have to cost you the deal, as long as you have an answer. Five steps that work in practice:

  1. Be honest. "We haven't had an external pentest done yet" is a better answer than a vague story. Security teams ask follow-up questions, and an evasive answer will come out anyway.
  2. Name a date. Schedule the test and let the customer know when it takes place and when you expect the report. For many procurement teams, a confirmed schedule with an independent party is enough to continue the process.
  3. Choose the scope that matters to this customer. Test the product this customer is going to use, including the APIs and the roles their staff will get. The rest can come later.
  4. Plan time for remediation before the deadline. The report you want to share is the report with resolved findings. So work backwards: test, fix, retest. From intake to report, a multi-day pentest typically takes one to three weeks. The retest follows as soon as you have patched.
  5. Meanwhile, fill in the rest of the questionnaire. Policies, access management with multi-factor authentication, the incident process and backups are things you can answer right now. The pentest report then fills the section on technical evidence.

If the deadline is short and the application is straightforward, Resync Zero, a one-day manual pentest of the highest-risk parts, can be an interim answer. Do say that it is a short test. Whether a customer accepts that varies from customer to customer. How to prepare the test so that no day is lost is covered in preparing for a pentest.

What does not work

Presenting a vulnerability scanner export as a pentest report. A report that is two years old, or about a different product. Or pointing to your hosting provider's ISO certificate. That last one only says something about the data centre. Security teams see the difference, and afterwards trust the rest of your answers less too.

Turn it into a selling point

If you expect the question, you gain time. In a procurement process, the supplier that stands out is the one that answers the security question in a single email, with the summary and the retest statement attached.

  • Say it up front. State in your sales material or on your website that an independent pentest takes place every year, and that the summary is available on request.
  • Test before the rush. Schedule the pentest before an important sales period or a big tender.
  • Keep the rhythm. At least once a year and after every significant change. Where that rule of thumb comes from is covered in how often you should run a penetration test.
  • Don't let the questionnaires pile up. If security questions from customers come in regularly and nobody owns them, a security advisor on retainer can answer them with you.

Conclusion

A customer who asks for a pentest report is asking for proof they can show someone themselves. If you have a recent report, share the summary and the retest statement, and the full report only under NDA. If you don't, be honest, name a date and test the product the customer is going to use, with time for remediation before the deadline. That way the question that seemed to be slowing the deal down becomes a moment where you show that you take security seriously, with proof instead of words.

Frequently asked questions

Can I share a pentest report with a customer?

Yes. The report was made for you, and you decide who you share it with. Preferably share the executive summary and the retest statement. The full technical report contains details an attacker could use to speed up their work, so you only share it under NDA and preferably for review only.

How old can a pentest report be?

Most customers apply a twelve-month window. If your application has changed significantly since then, for example through a new login method, a migration or major new functionality, a customer will expect a more recent test.

Is a vulnerability scan enough as proof for a customer?

Usually not. A scan finds known vulnerabilities, but not logic and authorisation flaws, and security teams recognise scanner output immediately. A scan is a useful addition, but it doesn't replace a manual pentest.

How quickly can I have a pentest report?

After an intake and sign-off on the quote, the test usually starts within one to two weeks. From intake to report, a multi-day pentest typically takes one to three weeks, depending on scope. If the deadline is short, a one-day manual pentest (Resync Zero) can be an interim solution.

The report your customer wants to see.

A manual pentest of the product your customer buys, with an executive summary for the customer, a retest statement as proof of remediation and a digitally signed report your customer can verify themselves. Fixed price, retest included.

Request a free intake →