Customer Security Reviews
Penetration testing for customer security reviews
What Buyers Ask
Common questions in a security review, and what to send
Has the product had an independent penetration test in the last 12 months?
Who carried it out, and are they accredited?
What did the test cover?
Can we see the report?
Were the critical and high findings fixed?
Sharing Your Report
What to send a buyer, in this order
The attestation letter
The main penetration testing report
The vulnerability report
How It Works
From first contact to final report
Tell us what you need
Receive a written, fixed-price proposal
Testing, with direct access to your consultant
Report delivery and debrief
Typical Scope and Price
A worked example from our published prices
| What the buyer is reviewing | Testing | Indicative price |
|---|---|---|
| Web application with multi-tenancy and user roles | Web application penetration testing | £6,000 to £8,400 |
| Standard API, 20 to 50 endpoints | API penetration testing | £2,950 to £5,050 |
What You Receive
Included in every engagement
Reports and attestation letter
An executive summary for the buyer's procurement team, a technical report with every finding, evidence, CVSS scoring and remediation guidance, and an attestation letter confirming the test was carried out to the agreed scope and methodology.Debrief session
A video call or presentation to walk through findings and remediation priorities with your technical and security teams.Retesting and platform access
Retesting where included for the service, with finding statuses updated so you can show what was fixed, and the attestation PDF available to download from the Exploitr platform at no extra cost.
Common Questions
Penetration testing for security reviews: frequently asked questions
You can, but we suggest sending the attestation letter first. It confirms the test was carried out to the agreed scope and methodology without listing findings, which answers most questionnaire questions. If the buyer wants to know what was found, send the executive summary, which is written for non-technical readers.
The full technical report contains the detail needed to reproduce each finding, so share it only when the buyer needs it, under an NDA, and once the critical and high findings have been retested. Our reports are written with the expectation that they may be shared with third parties, but what you share is your decision.
We reply to every enquiry within one business day to confirm the scope, then send a written, fixed-price proposal. Our standard lead time from agreement to testing is 2 to 3 weeks, testing a typical SaaS product takes around 4 to 7 days, and the report follows within 2 business days of testing finishing. The attestation letter is available to download from the platform once the assessment is complete.
If a deal is waiting on the evidence, include the deadline in your quote request and we'll work to your timeline where possible. The earlier you ask, the more options we have.
There's no universal rule. Many questionnaires ask for a test within the last 12 months, and some buyers also ask about testing after major releases, so check your buyer's wording. NHS DTAC, for example, asks for a penetration test from the previous 12 months (see our healthcare penetration testing page).
If your product has changed significantly since your last test, say so when you reply and consider commissioning a new one.
Having findings in a report is normal. What buyers usually want to know is whether the critical and high ones were fixed. Fix what you can, request a retest and share the updated statuses: retested findings are marked as fixed or still open in the report and the Exploitr platform. Be straightforward about anything that remains, with your plan and timeline for fixing it.
Retesting is included for remotely delivered web application, API, website and external network testing, and is agreed at scoping for internal testing.
