Request a quote
Emergency SectorsCareers About us Blog Get in touch
Close-up of two monitors showing log lines and coloured terminal output

Pen test cost, and why two quotes rarely test the same thing

Ask about pen test cost and the answer is nearly always “it depends”. That is not evasion: a penetration test is a person’s time, and how much time it takes follows from what is in scope, how much the tester is told up front and what the report must contain. This is what drives that time, and how to request quotes you can actually lay side by side.

7 min read Written by the ITproposal team
Short answer

A pen test is priced in testing days, and the number of days follows from the scope: how many addresses, applications, roles and environments are in the engagement.

What the tester is given up front changes what you get back for the same days. Without accounts, part of the time goes on getting in; with an account per role, it goes on what lies behind the login.

Quotes only become comparable when you state the scope in numbers and ask every provider for testing days, who tests, what the report contains and whether a retest is included.

Pen test cost: why nobody publishes a price list

A penetration test is work rather than a product: a tester tries to get in within an agreed scope, chains the weaknesses they find and records how far they got. The price is therefore almost always the number of testing days times who fills them, plus preparation and reporting.

That explains why answers on pen test cost vary so widely. Two providers quoting very different figures usually have a different engagement in mind: one prices an automated scan with a short manual check, the other a week of hands-on work on the same application. The gap lies in what gets tested, not in who is cheaper.

So the first question is not “how much” but “what needs testing, and why now”. A new customer portal, a requirement from a large client, a standard that asks for it, or an acquisition where you want to know what you are taking on: each leads to a different scope.

Scope: what is in the engagement

Scope is the biggest lever on price. The more precisely you can express it in numbers, the more precise the quote.

  • External addresses. The number of public IP addresses and hostnames, and above all how many actually expose a service. A range where half the addresses run nothing takes less time than its size suggests.
  • Web applications and APIs. What counts is size, not the number of applications: how many screens and functions, how many API endpoints and how many user roles. Each role is its own set of permissions to test.
  • Internal network. How many segments, whether Active Directory or Entra ID is in scope, and whether the tester comes on site or works through a remote access point.
  • Mobile apps. iOS and Android are two apps even if they look identical, and the API behind them is often a third component.
  • Cloud and Microsoft 365. Configuration, permissions and shared access are a separate review alongside the network.

If you are not sure what is exposed, start with an inventory or vulnerability scanning. That cheaper work sharpens the scope of the test, and a tester who first has to work out what exists spends testing days doing it.

Black box, grey box, white box: what the tester knows

A black box test starts with nothing: no accounts, no documentation. It shows how far an outsider gets, but part of the days goes on reconnaissance and getting in, and what sits behind the login gets less attention.

In grey box testing the tester receives accounts, ideally one per role, and a short walkthrough of the application. For most web applications that is the best balance between time and findings: the days go on what a logged-in user or a compromised account can do, which is where the serious flaws are.

White box adds source code, architecture diagrams or configuration. It needs more preparation on your side and a tester who reads code, and it produces the most findings in the same time.

Choose deliberately and put it in the request. Two quotes where one assumes black box and the other grey box cannot be compared, even if the number of days is the same.

External, internal, web, mobile or social engineering

“A pen test” is an umbrella term. Each of these is a different discipline, and a provider offering all of them usually puts different people on each:

  • External infrastructure: what can be reached from the internet.
  • Internal infrastructure: what someone already inside can do, with a stolen laptop or a compromised account.
  • Web application and API: logic, permissions and input handling, usually following OWASP guidance.
  • Mobile app: the app, its storage on the device and the API behind it.
  • Social engineering: phishing, phone calls or a visit to reception. That needs agreements with management and HR beforehand, and the preparation is work that counts.

In the UK, government and public sector work often asks for testers under the NCSC’s CHECK scheme, and many private clients ask for CREST accreditation. A red team exercise is something else again: not a list of weaknesses but a scenario over weeks that also tests detection. Do not let one be sold as the other.

Time windows, lead time and what is off limits

The conditions of testing decide how much calendar time and how many testing days are needed. If production may only be tested out of hours, or only in a maintenance window, the engagement stretches and often costs more per hour.

A staging environment identical to production removes that, but only if it really is identical: different versions or integrations give you a report on a system you do not run.

Urgency costs too. A test that must be done next week because a client wants the report does not fit the planning of a provider who books testers months ahead. If you know a test recurs every year, book it early.

And write down what is off limits: no production outages, no real data taken, no pressure on staff. Every restriction is a choice that makes the test safer and the report narrower; it belongs in the quote, not invented during the test.

The report, the retest and who does the testing

What you hold afterwards is the real product. Ask for an anonymised sample report beforehand and check that it serves two readers: a summary a board can read without translation, and for each finding a description with severity, evidence, steps to reproduce and a remediation proposal.

The retest is the item most often missing. After remediation you want to know the findings are really closed, and a client or auditor often wants to see that too. Ask whether it is included, within what period, and whether it covers all findings or only the serious ones.

Finally, ask who tests. Individual certifications such as OSCP or the CREST examinations say something about what a person can demonstrably do. A certificate is no guarantee, but it is a question a serious provider is happy to answer. Ask too whether the work is subcontracted, and to whom.

How to make quotes comparable

Send every provider the same request and ask for the same answers back. Then you can see where the difference in price comes from.

  • The scope in numbers: addresses, applications, roles, endpoints, segments, apps.
  • Black, grey or white box, and which accounts you will provide.
  • Testing days per component, and how many of them are manual.
  • Who tests, with which qualifications, and whether work is subcontracted.
  • The methodology, and what is explicitly out of scope.
  • A sample report, and whether the retest is included.
  • Time windows, lead time and when the report will be delivered.

If one quote is strikingly low, look first at the number of manual testing days. A scan wrapped in a report is useful, but it is a different product, and our page on penetration testing explains the difference.

Where our work stops

A penetration test with us starts with a proposal setting out the scope, the approach and what the report will contain, and afterwards we can fix the findings as part of ongoing management. If we already manage your environment, it is sensible to give the test to another party: whoever tests their own work tests it with the eyes that built it.

What we do not do: we certify nobody, and a pen test report is not a certificate. It states what was found within the agreed scope and time; it is not a statement that you comply with ISO/IEC 27001, NIS2 or a client requirement. That is for your auditor to judge. And which residual risk you accept is a decision for your own organisation, not for the tester.

Frequently asked

Questions we get about this

The five that come up most often.

How much does a pen test cost on average?

An average says little, because the price follows almost entirely from the number of testing days, and that number from the scope. A small web application with two roles is different work from an internal network with several segments. State the scope in numbers and ask each provider for testing days per component; then the difference between quotes can be explained.

How long does a penetration test take?

Testing itself takes a few days for a limited scope and a couple of weeks for a larger engagement. Preparation, scheduling and report writing come on top, often followed by a retest after remediation. Out-of-hours time windows stretch the lead time further.

What is the difference between a pen test and a vulnerability scan?

A vulnerability scan is automated and looks for known weaknesses and missing updates. In a pen test a person tries to actually exploit and chain those weaknesses, and also finds flaws in logic or permissions. Scanning is continuous; testing happens for a new application, a major change or an external requirement.

How often should you have a pen test?

For most organisations there is no fixed legal frequency. Common practice is to test a new application or major change, and periodically when a client, insurer or standard asks for it. If you test every year, keep the scope comparable so the reports can be compared.

Does a pen test give you a certificate?

No. A pen test report describes what was found within the agreed scope and time, and is not a statement that you meet a standard or law. We certify nobody; whether you comply with ISO/IEC 27001 or NIS2 is for an auditor to judge. The report is evidence that you had testing done and what you fixed afterwards.

Related services

Further reading

The service itself, the scan that comes first, and where it fits in the whole.

A request you can compare

Tell us what needs testing and why. You will get a proposal with the scope in numbers, the approach, the number of testing days and what the report will contain.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call