← Back to blog

From £2,500: 2026 UK penetration testing costs and checklist

September 29, 2026
From £2,500: 2026 UK penetration testing costs and checklist

Budget roughly £2,500 to £3,000 for a straightforward external test and considerably more for internal networks or a full red team engagement, with prices in the low tens of thousands. The single biggest lever on that final figure is not the day rate you negotiate but how tightly you and your tester define scope and prepare in advance, a point NCSC guidance makes explicit. The worked examples and procurement checklist below show exactly where that money goes.


TL;DR:

  • External network tests typically cost between £2,000 and £3,000, while full red team assessments can reach into the low tens of thousands, depending on scope complexity.
  • Costs increase significantly with heterogeneity of assets, authentication complexity, and the need for specialist testing like IoT or AI systems.
  • Accurate budgeting relies on detailed scope definition, proper preparation, and itemized quotes, rather than solely comparing day rates.
  • Automated scans and fixed-price quotes often underdeliver, as they lack depth and do not account for scope specifics or reporting requirements.
  • Businesses should prioritize clear scope, accredited providers, and detailed contracts over low quotes to ensure effective and compliant testing.

Solusec
solusec.co.uk
Get a Penetration Test Quote
Solusec provides expert-led penetration testing with clear, actionable findings for UK businesses, without the complexity of larger firms.
Get a Pentest Quote

Table of Contents

Typical UK price ranges by test type and day rate

Penetration testing prices in the UK are built from a day rate multiplied by the number of resource days a job needs, and NCSC guidance frames test planning explicitly in resource days rather than a flat fee. Get the resource days wrong and the total moves a lot more than any discount on the daily rate would.

For common UK engagements, expect the following bands:

  • External network or infrastructure test: from around £2,000 to £3,000 for a single external IP or a small perimeter, reflected in Solusec's Penetration Testing pricing.
  • CMS-based website test: from around £2,500 for a standard content management system build, similar to Solusec's External IP test, CMS website test service.
  • Internal network test: usually higher than an external-only test because of the extra segments, hosts and privilege paths a tester has to work through.
  • Full red team or multi-scenario assessment: the most expensive category, running into the low tens of thousands once social engineering, physical access or long attack simulations are included.

A simple way to sanity-check a quote is the formula: day rate multiplied by resource days, plus reporting time. If a consultant costs £900 a day and the job needs four testing days plus one reporting day, that is five days at £900, or £4,500 before any specialist add-ons.

Market day-rate signals vary widely. Public-sector procurement listings on the Digital Marketplace show day-rate pricing for security testing services ranging from £400 to £2,885 a day, a spread that reflects everything from junior scanning support to senior CREST-accredited consultants leading complex engagements. Seniority, accreditation and specialism all push a quote toward the top of that range.

Typical UK price ranges by test type and day rate — overview diagram

Factors that move the quote: scope, complexity and specialist items

Two businesses asking for "a penetration test" can receive quotes thousands of pounds apart, because the underlying estate is never really the same. Testers price against what they actually have to touch, not against a generic label.

  • Asset count and heterogeneity: a handful of static pages costs far less to assess than an estate mixing APIs, microservices, cloud infrastructure and legacy on-premise servers.
  • Authentication complexity: single sign-on, multiple privileged roles and the need to provision several test accounts all add setup and testing time.
  • Specialist testing: mobile applications, wireless networks, AI or large language model systems, and hardware or IoT devices each demand skills and tooling outside a standard web or network test.
  • Reporting and compliance constraints: a report that must satisfy an insurer's wording, meet CHECK requirements or map findings to CVSS severity consistently takes longer to write and quality-check than a standard summary.

Red team engagements sit at the far end of this scale. CREST guidance describes intelligence-led approaches such as STAR and STAR-FS as realistic, regulator-friendly engagement types, but that realism is resource intensive and priced accordingly.

Pro Tip: Ask your provider to itemise the quote by test component rather than accepting a single lump figure; it makes it far easier to see which part of your estate is actually driving the cost.

Preparation, mobilisation and the timeline you need to budget for

Testing time is only part of the bill. Mobilisation, the work needed before testing starts, regularly adds one or two resource days to a medium-sized engagement, and skipping it tends to cost more later, not less.

  1. Provide documentation and topology diagrams up front. The example CHECK buyer's guide letter lists topology diagrams, current vulnerability reports and nominated contacts as standard preparatory tasks, and missing them forces testers to spend billable time on discovery instead of testing.
  2. Set up test accounts before day one. Sample accounts across each privilege level let testers get straight into the work rather than waiting on access requests mid-engagement.
  3. Agree out-of-hours windows and data handling terms early. Any requirement to test outside normal hours or under a specific data handling agreement should be settled during scoping, not discovered once the clock has started.
  4. Decide your position on mid-test scope changes before they happen. NCSC guidance notes that when testers find a high-impact system outside the agreed boundary, the client faces a genuine choice: accept a documented limitation at no extra cost, or approve a scope change and pay for the additional days.

What very low prices typically buy, and the red flags to watch for

A quote that undercuts the market by a wide margin is rarely a bargain; for a thorough approach accounting for security and deliverability considerations, consider an Email Deliverability Audit UK to add cross-discipline procurement perspective. It usually reflects less human time on your systems, not more efficiency.

  • Automated scanning dressed up as a penetration test: automated tools find known vulnerabilities quickly, but they miss business logic flaws, chained exploits and anything requiring a human to think like an attacker.
  • No scoping call: a provider willing to quote a fixed price without ever discussing your environment has priced against guesswork, not your actual estate.
  • No named senior tester: you should know who is doing the work and what they are accredited to do, not just the name of the company invoicing you.
  • Unrealistic turnaround: a promise to test and report a complex estate in a day or two usually means shallow coverage.
  • Offshore-only delivery with no UK accountability: fine for some services, but it makes remediation conversations and contractual recourse harder if something goes wrong.

Insist instead on CREST or CHECK status where relevant, a sample report you can actually read, and a clear retest policy once fixes are in place.

Sample budgets for typical UK SMEs

These are worked examples built on stated assumptions, useful as a starting point rather than a quote.

These figures are illustrative calculations from stated day rates and days, not published market prices, and any real quote will move with the complexity factors covered above.

Procurement checklist: what to ask and what to put in the contract

A good scoping call and a clear contract do more to control your final bill than any amount of haggling over the day rate.

  1. Confirm the scope boundary precisely: which IPs, domains, applications and environments are in scope, and which are explicitly excluded.
  2. Ask how sample accounts and privileged access will be provisioned, and who on your side needs to arrange them before testing starts.
  3. Agree testing windows: whether work happens during business hours, overnight or across a weekend, and what that means for cost.
  4. Insist on a change-control clause covering what happens if the tester finds something significant outside the agreed scope.
  5. Check the retest terms: how many retest days are included, and what happens if remediation is not complete by the retest date.
  6. Confirm the reporting format: does it map to CVSS, does it satisfy your insurer's wording, and will it hold up to a client or auditor request.
  7. Weight your selection criteria toward value, not price: expertise, accreditation and a sample report matter more than the lowest number on the page.

Pro Tip: Request a sample report before you sign anything; a vague, generic report is the clearest early warning that the testing behind it was equally vague.

Fixed-price, retainer or project-based: which pricing model fits

Most UK penetration testing is sold under one of three models, and each suits a different pattern of need.

Three penetration testing pricing models compared

Fixed-price engagements quote a single figure for an agreed scope, such as Solusec's External IP test, CMS website test offering. They suit organisations with a well-defined, stable estate and a clear compliance deadline, because the cost is known before work starts and there is little room for surprise invoices.

Project-based pricing covers larger, one-off engagements where the scope is more variable, such as a red team simulation or a multi-application assessment. The total is still agreed in advance, but it is built up from several components priced separately, which suits complex estates that do not fit a standard fixed-price template.

Retainer arrangements suit organisations that test repeatedly through the year rather than once. Instead of commissioning a fresh scoping exercise every time, a retainer sets an agreed rate and cadence for ongoing work, which fits businesses running continuous development cycles or facing regular compliance checkpoints. It tends to suit larger or fast-moving organisations more than a small business testing annually, where a single fixed-price engagement is usually simpler to plan and budget against.

Post-test support and the cost of ongoing security work

A penetration test report is a snapshot, not a guarantee. The Gov is explicit that a test validates known issues only as they stood on the day of testing, and recommends pairing periodic tests with ongoing vulnerability management rather than treating a single report as lasting assurance.

That has direct budgeting consequences. Most quotes include a defined retest window, commonly covering the fixes made in direct response to the report, but anything beyond that scope usually incurs additional cost. Businesses that expect to keep finding and fixing issues between annual tests should budget separately for that ongoing work, whether through a vulnerability management service or a security retainer, rather than assuming one test a year covers the gap.

For organisations weighing this up, the practical question is less "how much was the test" and more "what happens for the other 11 months of the year." Continuous or more frequent testing cadences exist precisely to close that gap, and are worth costing alongside the headline test price rather than as an afterthought once the report lands.

CHECK versus commercial testing: when you actually need it

CHECK is not the default UK standard for penetration testing, and paying a CHECK premium when you do not need one is a common way SMEs overspend. NCSC's CHECK buyer guidance states plainly that CHECK is intended for government, public-sector and critical national infrastructure buyers, and that private organisations should choose assurance appropriate to their own contractual and risk requirements rather than defaulting to it.

For most SMEs, charities and educational institutions, a commercial test delivered by CREST-accredited testers meets contractual and insurance requirements without the added cost structure CHECK engagements carry. The exception is when a contract, regulator or public-sector client specifically demands CHECK status, in which case it is not optional and should be scoped as such from the outset. Outside that scenario, ask any provider quoting a CHECK-only service whether that assurance level is actually required for your contract, because it may simply be adding cost without adding relevant protection.

What actually makes up your total cost

The headline day-rate figure is rarely the whole bill. A realistic total usually includes several components that are easy to overlook when comparing quotes side by side.

Reporting time is billable work, not a free extra: writing findings clearly, mapping severity consistently and producing an executive summary suitable for a board or an insurer takes real hours, and NCSC guidance treats reporting requirements as part of the scoped plan, not an afterthought.

Retest costs depend on how many days are included in the original quote. A retest beyond that allowance, or one delayed well past the original engagement, is usually charged separately.

Mobilisation and preparation gaps convert directly into cost. Missing topology diagrams or absent test accounts, both listed in the CHECK buyer's guide example letter as standard preparatory tasks, can turn what looked like a three-day engagement into five or seven days with little extra assurance delivered.

There are no software licence fees in a typical penetration test the way there might be for a vulnerability scanning subscription, but any tooling costs a provider passes through should be itemised in the quote rather than folded silently into the day rate.

Cyber Essentials Plus: a separate assessment with its own price

Cyber Essentials Plus is often confused with penetration testing, but it is a distinct certification assessment with its own test specification, sampling rules and cost structure. The Cyber Essentials Plus test specification v3.2 sets out defined sample sizes, prescribed test cases and pass or fail criteria that differ sharply from the adversary-simulation approach a penetration tester uses.

Because it is sample-based and prescriptive rather than open-ended, Cyber Essentials Plus is often cheaper than an equivalent adversary-led test for basic hygiene verification, though pricing depends on organisation size and scope. It should never be scoped or quoted as if it were a substitute for a full penetration test, and vice versa: a business needing both should expect two separate line items, not one blended price. Solusec's Cyber Essentials Plus service runs this assessment as its own engagement, alongside the standard Cyber Essentials certification route for organisations that need the base-level badge without the technical verification.

What the pricing debate gets wrong

Most guidance on penetration testing cost fixates on the day rate, as if the market were a simple auction where the lowest bidder wins. It is not. The Digital Marketplace day-rate spread from £400 to £2,885 shows the market will happily sell you a cheap day rate that delivers a shallow, automated-heavy engagement dressed up in the same language as a thorough manual test.

The conventional advice to "get three quotes and compare" undersells the real variable, which is scope definition. Two identically priced quotes can cover wildly different amounts of actual testing, and a buyer comparing only the bottom line has no way to see that. The reader's first priority should not be negotiating the rate down. It should be writing a scope tight enough, with topology diagrams and test accounts ready, that every quote received is pricing the same job. Only then does comparing numbers mean anything.

— Solusec Admin

How Solusec prices penetration testing for UK businesses

Some providers offer fixed-price penetration testing for external IPs and CMS-based websites, delivered by experienced testers rather than sales teams.

Solusec

That matters most for the businesses this pricing guide is written for: startups, SMEs, schools, colleges and charities that need a clear number to put in a budget, not an open-ended day-rate negotiation.

  • Fixed-price clarity: Solusec's External IP test, CMS website test service quotes a defined figure for a defined scope, so there is no surprise invoice once testing starts.
  • UK-based, CREST-accredited delivery: testing and reporting come from accredited professionals working directly with you, with plain English findings rather than a generic template.
  • A pathway beyond the test: for businesses that also need certification, Solusec's Cyber Essentials certification service sits alongside penetration testing as a separately scoped option.

If you want a scoped quote for your own environment, get in touch through Solusec's penetration testing page for a fixed-price assessment built around your actual estate.

Sources

FAQ

How much should you charge for a penetration test?

UK day rates for penetration testing range widely, with public-sector procurement listings on the Digital Marketplace showing figures from £400 to £2,885 a day depending on seniority and specialism. A full project total then depends on that day rate multiplied by the resource days the scope actually requires, plus reporting time.

How much does a penetration tester earn in the UK?

Published salary figures for UK penetration testers are not covered in the sources behind this guide, so no specific figure can be stated here reliably. What is clear from procurement data is that day rates for penetration testing services vary substantially by seniority and accreditation, from around £400 to £2,885 a day on the Digital Marketplace.

Penetration testing is legal in the UK when carried out with proper written authorisation from the system owner, defining scope and boundaries in advance. The NCSC's guidance frames this authorisation and scoping process as the foundation of any legitimate engagement, and testing without it would fall outside the law.

Is penetration testing being replaced by AI?

Automated scanning tools, some using AI-assisted techniques, are increasingly used to find known vulnerabilities quickly, but they are not a substitute for the manual, human-led testing that uncovers business logic flaws and chained exploits. Guidance from bodies like NCSC and CREST continues to describe penetration testing as a manually driven discipline, with automation supporting rather than replacing the tester.

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.