Cybersecurity credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The checklist
What a penetration testing RFP must specify before bids open
Each row is a clause your RFP should carry. A vague clause invites a vague bid, and the vaguest bids come from the firms with the least to show.
Scope, named asset by asset
List the applications, APIs, network ranges and environments in scope, and state explicitly what is out. "Our web presence" is not a scope; a URL list with environments is.
What a good bid shows: An effort estimate tied to your asset list, not a flat price per "site".
Environments and testing windows
Say whether testing hits production or staging, in which hours, with what change freeze, and who is on call on your side while it runs.
What a good bid shows: A testing plan that respects your operation instead of discovering it mid-test.
Methodology expectations
Require manual testing beyond automated scanning, name the standards you expect the work to follow, and ask each bidder to describe how manual effort is evidenced.
What a good bid shows: A described method with evidence of hands-on work, not a tool name.
Reporting requirements
Specify what every finding must carry — reproduction steps, evidence, business impact, a severity rationale and a recommended fix — and ask for a redacted sample report with the bid.
What a good bid shows: A sample report you can judge before signing, not after delivery.
Retest terms
State whether retesting fixed findings is included, within what period, and at what cost. A test that ends at the report leaves you unable to prove anything was actually closed.
What a good bid shows: A written retest commitment with a window and a price.
The filter
How an RFP filters scanner resellers out before the pitch
The cheapest bids for a penetration test are usually not tests. A firm runs an automated vulnerability scanner, exports its findings into a branded template and prices the work at a fraction of a manual engagement — which is honest work when it is sold as a vulnerability scan, and a problem when it is sold as a penetration test. The two answer different questions: a scan lists known weaknesses software can detect; a test tells you what a capable person can actually do with them, chained together, against your specific systems.
A precise RFP makes the difference impossible to hide. Requiring evidence of manual technique, a redacted sample report and the names and experience of the people who will test forces each bidder to show what they actually sell. The reseller cannot produce a sample report with reproduction steps a scanner did not generate, and will not name testers, because the testers are a licence. You learn this from the bid documents, at no cost, instead of from the report, after payment.
The interview
Five questions to put to every penetration testing bidder
Ask these in the clarification round. The answers separate bids faster than the price column does.
1 · Who exactly will test, and what have they tested like this before?
Named people with relevant experience, not a bench description. If the tester assigned depends on availability at kickoff, you are buying availability. Names and backgrounds you can hold the firm to at kickoff.
2 · Show us a redacted report from a comparable engagement
The report is the deliverable. Judge its reproduction steps, evidence quality and severity reasoning now, while you can still choose someone else. Direct evidence of the quality you would receive.
3 · How do you verify a finding is exploitable, and how far do you go?
A real team explains safe exploitation, chaining and the boundaries they stop at. A reseller describes severity scores a tool assigned. A method for proving impact, stated before it is applied to you.
4 · What happens if you find something critical mid-test?
There should be an immediate-notification path with a named contact on both sides, agreed before testing starts — not a surprise in the final report three weeks later. An escalation protocol in writing.
5 · What does the retest cover, and what does it cost?
Fixes need verification by the people who found the flaws. A bidder who treats retesting as a fresh engagement at full price is telling you how the relationship will run. Retest scope and price fixed before award, not negotiated after.
Our role
Where we sit when your pentest RFP goes out
- 01
A bidder that meets the bar
We test manually, name our testers, share redacted sample reporting and contract the retest — because every clause in this checklist is one we would rather compete under than around.
- 02
Help before the RFP, without obligation
If your scope is unclear — which assets matter, whether production or staging should be tested — we will talk it through even if the eventual work goes elsewhere, because a well-scoped test serves the whole market we work in.
- 03
Honesty about scan versus test
Where a vulnerability scan genuinely fits your need and budget, we say so and price it as one. Selling a scan at test prices is the practice this page exists to end.
The award decision is yours, made against your criteria; our interest is that the criteria are sharp enough to reward whoever actually tests.
Common questions
What buyers ask
How detailed should the scope section of a pentest RFP be?+
Detailed enough that two bidders reading it independently would estimate roughly the same effort. That means named applications and APIs with their environments, network ranges by address block, user roles to be tested, and an explicit out-of-scope list. Where you cannot share detail before an NDA, say what exists at the category level and provide specifics to shortlisted bidders. Scope vagueness does not protect you commercially; it transfers the pricing risk into assumptions each bidder makes differently, which makes the bids incomparable.
Should a pentest RFP fix the price or the effort?+
Ask for both, stated separately: the days of testing effort by role, and the price. A fixed price with no effort statement lets a bidder win by silently shrinking the testing days, and the buyer cannot see it happen. When bids show effort explicitly, a price that undercuts the field becomes explainable — fewer days, more junior testers, or more automation — and you can decide whether that trade is acceptable rather than discovering it in a thin report. Comparing effort also exposes the opposite failure: a heavily padded estimate against a scope that does not justify it.
Can we reuse the same RFP for every annual penetration test?+
The structure, yes; the scope, no. The clauses on methodology, reporting, escalation and retest carry over well from year to year. The scope section has to be rebuilt each cycle, because the systems changed: new applications shipped, integrations were added, an environment moved to a different cloud region. An annual test run against last year's asset list quietly excludes exactly the newest systems — which are the ones least tested and most likely to carry the findings that matter. Treat the scope refresh as part of the procurement, not an administrative copy-paste.
In this cluster
A short scoping conversation on your RFP draft — what to tighten before it goes out, whoever you end up sending it to.
Talk through your RFP scope