To compare penetration testing quotes, line them up against the same fourteen lines: scope, test types, tester-days, timing, test basis, who tests, method, compliance and reporting needs, report contents, retest, exclusions, scope changes, contact during testing, and your preparation. Ask each provider to fill any blank line before you compare prices.
Quotes rarely disagree about price as much as they seem to. They disagree about what’s being bought, and the disagreement hides in the lines one proposal includes and another leaves out. A total at the bottom of the page tells you nothing until the lines above it match.
This post is the worksheet for the moment the proposals have arrived. If you haven’t asked for quotes yet, start with our guide to penetration testing cost, which covers what drives the price and how to brief providers so their quotes come back comparable. If you’re still deciding what kind of test you need, our penetration testing page sets out the types we run.
What Should a Penetration Testing Quote Include?
A penetration testing quote should say what will be tested, how, by whom, for how many days, and what you’ll receive at the end. Everything else is detail on those five.
That isn’t our invention. The National Cyber Security Centre’s guidance on commissioning a test says the scoping exercise should produce a document stating, among other things, “the technical boundaries of the test”, “the types of test expected”, and the timeframe and effort, which it notes is “usually given in terms of resource days” (opens in a new tab) (NCSC, Penetration testing, last reviewed 10 January 2022). A quote is that document with a price on it. If the document is thin, the price is a guess.
The CREST guidance on its Defensible Penetration Test (opens in a new tab) (CREST, June 2023), which it addresses to organisations buying penetration testing as well as those delivering it, goes further on the output. It expects the report to include “A statement of totality against the defined scope”, which is a plain statement of how much of what you paid for was actually covered. Few buyers ask for that. Every buyer should.
Fourteen lines follow from those two sources and from what goes wrong in practice.
The Penetration Testing Quote Comparison Worksheet
Copy the table, put each provider in its own column, and fill in what each quote actually says. A blank cell is a question to send back, not a point in anyone’s favour.
| # | Line | What a comparable quote states | If it’s missing, ask |
|---|---|---|---|
| 1 | Scope | Named systems: IP ranges, hosts, applications, APIs, user roles | “Which of our systems does this price cover, by name?” |
| 2 | Test types | External, internal, web application, API, cloud, wireless, as separate lines | “Which types of test are included, and which aren’t?” |
| 3 | Tester-days | A number of days, per test type where there’s more than one | “How many tester-days does this price buy?” |
| 4 | Timing | Testing window, report date, any out-of-hours work | “When would testing start and when would we have the report?” |
| 5 | Test basis | What you’ll provide: asset lists, credentials, architecture diagrams, or nothing | “Is this priced as closed box or with our information?” |
| 6 | People | Who scopes, who tests and who signs off, with their qualifications | “Who will do the work, and what do they hold?” |
| 7 | Method | The methodology the test follows, named | “Which methodology will you test against?” |
| 8 | Compliance and reporting needs | PCI DSS, a contract or an insurer; CVSS or other severity scale | “Does this meet our [driver] requirement, and in what format?” |
| 9 | Report contents | Findings, risk to your organisation, how to fix each, a statement of coverage | “Can we see a sanitised sample report?” |
| 10 | Retest | Included or not, what it covers, how long after the test | “Is a retest included, and on what terms?” |
| 11 | Exclusions and assumptions | What’s out of scope, and what the price assumes you’ll provide | “What does this quote assume, and what does it exclude?” |
| 12 | Scope changes | What happens when the tester finds something outside scope | “If you find something outside scope that affects what’s in it, what happens to cost and time?” |
| 13 | Contact during testing | Who the testers call about a critical finding or a problem | “Who do your testers contact, and how fast?” |
| 14 | Your preparation | Accounts, access, whitelisting and anything else you must have ready | “What do you need from us before day one?” |
A downloadable version of the worksheet is available. The substance is all in the table above, so nobody needs to download anything to use it.
Where the Worksheet’s Lines Come From
Two free documents underpin most of the worksheet, and both are worth reading in full before you sign.
The NCSC’s Penetration testing guidance is the UK baseline for commissioning a test. It covers lines 1 to 5, 8, 9 and 12 to 14 directly: who should be in the scoping conversation, what the scoping document should contain, what the report should include, and what happens during testing. It’s short, and it’s written for the person buying, not the person testing. Read the NCSC guidance (opens in a new tab).
CREST’s Defensible Penetration Test guidance covers lines 6, 9 and 11 in more detail than the NCSC does. It requires that its Defensible Penetration Tests be “scoped, delivered and signed off by a suitably qualified individual”, and its reporting framework asks for the scope with “any exclusions or restrictions that applied to the assessment and the coverage gained” (opens in a new tab). It’s written around CREST’s own assurance product, so treat it as a benchmark for what good looks like, not a rule every provider must meet.
Line 10, the retest, isn’t covered by either document. It comes from practice, and it’s the line most often left out of a quote.
For the questions to ask about the company itself (accreditation, insurance, subcontracting), our checklist on how to choose a penetration testing company covers them. This worksheet is about the document in front of you.
How to Fill In the Worksheet for Your Own Quotes
Fill the worksheet in five steps, in this order, and leave the prices until last.
Step 1: Write Your Own Scope in the First Column
Put your scope in the first column before you read any quote closely. This is the yardstick. Each provider’s column is compared with it, not with each other.
Use the scope you sent out, if you sent one. If you didn’t, write down now what you meant: which systems, which kinds of test, and what question you want answered. The NCSC’s advice that “During scoping, you should outline any issues which might impact on testing” applies here too, so note any fragile systems or blackout dates.
The mistake this prevents: judging quotes against the most detailed one, which just rewards the provider who wrote the most.
Step 2: Convert Every Quote to Tester-Days
Write the number of tester-days against each quote in line 3. If a quote doesn’t state days, that’s the first question back.
Days are the unit that makes quotes comparable, because they’re what the scope decides. A quote with twice the price and twice the days isn’t more expensive. It’s more testing. A quote with the same price and half the days is the one to question.
The mistake this prevents: comparing a price per engagement with a price per day and thinking they’re the same thing.
Step 3: Mark Every Line a Quote Leaves Blank
Go down lines 4 to 14 for each provider and mark every blank. Don’t fill blanks with assumptions, however reasonable.
Blank lines are where the price differences live. A quote that says nothing about a retest hasn’t included one until it says so. A quote that says nothing about exclusions has some; you just don’t know which. The CREST guidance expects constraints that stop the full scope being tested to be “formally documented and included as part of the report write up and sign-off processes”. It’s far better to know about them before the test.
The mistake this prevents: assuming the cheapest quote includes everything the most expensive one lists.
Step 4: Send One Follow-Up List to Every Provider
Send each provider its blank lines as questions, using the last column of the worksheet, and give them all the same deadline.
It takes an afternoon. It’s also the most useful test of the provider you’ll get before the actual test: a firm that answers precisely and quickly in writing is showing you how it communicates. If an answer changes the scope, ask for a revised quote rather than a note in an email.
The mistake this prevents: one provider answering on the phone, another in a revised quote, and a third not at all, which puts you back where you started.
Step 5: Compare the Totals Last
Once every line is filled for every provider, compare the prices. Only now do they mean something.
Look at price per tester-day, then at total days against your scope, then at what’s in lines 9 to 11. The NCSC’s list of what a report should contain is a good tiebreaker: the security issues found, an assessment of the risk each one poses to your organisation, how to resolve each one, and advice on your own vulnerability assessment. A quote that delivers all of that for a few more days is usually worth it.
The mistake this prevents: deciding on price, then discovering what the price left out.
How to Tell Your Penetration Testing Quotes Are Now Comparable
Your quotes are comparable when every cell in every column is filled, every quote states its days, and every quote tests the scope in your first column.
A quick check before you decide:
- No blanks. Every line has an answer, even if the answer is “not included”.
- Same scope. Line 1 matches your first column for every provider, or the differences are written down and priced.
- Days stated. You can divide each price by its days.
- Retest known. You know whether each price includes a retest, and what it covers.
- Exclusions listed. You can say what each provider won’t test.
If any of those fail, you’re comparing a quote with a guess.
A Worked Example With Three Penetration Testing Quotes
The example below is illustrative. It isn’t a real engagement, and the numbers are chosen to show how the worksheet works, not what a test should cost.
An organisation wants an external test of its internet-facing infrastructure and an authenticated test of its customer portal, which has two user roles. Three quotes arrive.
| Line | Quote A | Quote B | Quote C |
|---|---|---|---|
| Scope | “Your external estate and web application” | Named IP range; portal, both roles | Named IP range; portal, one role |
| Test types | Not stated | External; authenticated web application | External; web application |
| Tester-days | Not stated | 2 external + 5 web application | 6 in total, not split |
| Retest | Not stated | Included, high and critical findings, within 60 days | Quoted separately |
| Report | “Comprehensive report” | Sample provided | Sample provided |
| Exclusions | Not stated | Denial of service; third-party hosted payment page | Not stated |
| Blank lines after follow-up | 6 | 0 | 2 |
Quote A was the lowest. It also answered the fewest lines, and after the follow-up it turned out to be an automated scan with a brief manual review, which is a different product. Our post on vulnerability scans and penetration tests explains why that matters.
Quote C looked close to Quote B, until the worksheet showed it tested one user role, not two, and priced the retest separately. On a portal with two roles, the second role is often where the interesting findings are.
Quote B was the most expensive and the only one that matched the scope. On a per-day basis it may not have been the most expensive at all. The worksheet is what showed it.
It’s rather like comparing car insurance. The cheapest premium is only cheaper if the excess and the cover are the same, and nobody sensible compares premiums without reading those two lines first.
What to Do Once the Penetration Testing Quotes Line Up
Once the worksheet is full, the decision is usually obvious, and the price is the last thing that makes it. Choose the quote that tests your scope with the most clearly stated days, report and retest, then check the provider itself before you sign.
If you’d like a second pair of eyes on the quotes you’ve got, including where one of them is ours, do get in touch.
Comparing penetration testing quotes isn’t about finding the lowest number. It’s about finding the missing ones.