Quick Answer: How much do penetration testing services cost?
A single web application test usually runs $1,500 to $5,000, while mid-size or more complex applications and network tests commonly land between $5,000 and $15,000. Enterprise-scale or compliance-driven engagements often reach $15,000 to $50,000 or more, and very large scopes can pass $100,000. Many providers also quote by consultant-day, typically $1,000 to $2,500 per day.
Cheaper options exist, such as automated scanning tools or crowd-sourced bug bounty programs, but they differ in depth, reporting, and accountability. A manual test gives you a human attacker’s judgment; a scanner gives you a list of possible issues.
Before you request quotes, compare the number of applications and IP addresses in scope, authenticated versus unauthenticated testing, black-box versus white-box access, retesting fees, report depth, and whether a compliance standard is driving the test.
What makes a penetration test quote feel like a guessing game? You ask three vendors the same question and get three wildly different numbers, sometimes with a tenfold gap. That is normal in this market, and it is not a sign that one provider is overcharging or another is cutting corners. It is a sign that “penetration test” describes a service with almost no fixed boundaries. The price depends far more on scope, methodology, and reporting depth than on any published rate card.
This guide breaks down what penetration testing actually costs, why the ranges are so wide, and how to compare quotes without getting fooled by a low headline number.
What a Penetration Test Actually Involves

A penetration test is an authorized simulated attack against your systems, carried out to find security weaknesses before real attackers do. Unlike a vulnerability scan, which is largely automated, a penetration test relies on human testers who chain small findings together into realistic attack paths.
Most engagements follow a recognizable rhythm. Testers scope the work with you, gather information about the target, attempt exploitation, escalate privileges where they can, and then write up findings with severity ratings and remediation advice. Many providers align their work with PTES, the Penetration Testing Execution Standard, or the OWASP Testing Guide for web applications. Those frameworks matter for your budget because each phase takes time, and time is what you are buying.
One detail people miss: the report is often the most valuable deliverable. A tester who finds twelve issues but delivers a three-page summary has given you less than one who finds eight issues and explains exactly how to fix each one. When you compare quotes, compare the report structure too.
The Main Pricing Models You Will See
Vendors generally price penetration testing in one of three ways, and each has trade-offs.
| Pricing model | Typical range | Best for | Watch out for |
|---|---|---|---|
| Fixed-price per asset | $1,500–$5,000 per web app | Small businesses, single apps | Scope creep charges if you add targets |
| Day rate | $1,000–$2,500 per consultant-day | Custom or evolving scopes | Estimates that grow mid-project |
| Retainer or subscription | Varies widely | Continuous testing needs | Vague deliverable definitions |
Fixed-price quotes are easiest to budget for, but they usually assume a tightly defined scope. Day-rate pricing is flexible and common for larger networks, yet the final invoice depends on how long testers actually need. Retainers spread cost across the year and suit teams shipping code regularly, but they only work if the deliverables are spelled out clearly.
A practical tip from the field: ask every vendor to quote both a fixed price and an estimated day count. If the two numbers tell very different stories, ask why. That single question exposes more about a provider’s honesty than any sales call.
Typical Price Ranges by Scope
Exact figures vary by region, vendor size, and tester seniority, but the broad bands below reflect commonly cited industry ranges from vendor pricing surveys published between roughly 2020 and 2023. Treat them as planning anchors, not quotes.
Small business and single web application
A straightforward web application with a handful of user roles typically costs $1,500 to $5,000. This usually covers one application, a defined testing window, and a standard report. It is the most common entry point for small companies that need a test for a customer security questionnaire or an initial baseline.
Mid-size applications and internal networks
Once you add multiple applications, an internal network segment, or authenticated testing across several user roles, expect $5,000 to $15,000 or more. Complexity here is the enemy of accuracy: every extra login, API, or subnet adds hours.
Enterprise and compliance-driven engagements
Large networks, multi-application estates, and regulated environments frequently run $15,000 to $50,000 or more, with very large scopes exceeding $100,000. Compliance requirements push costs up because they demand defined scope, formal reporting, and re-testing to prove fixes worked.
Why Quotes Vary So Much: The Cost Drivers
If two quotes differ by 300 percent for what sounds like the same job, one of these factors is almost always responsible.
Number of targets. Applications, IP addresses, APIs, and mobile apps each add effort. A quote covering one app is not comparable to one covering five.
Authenticated versus unauthenticated testing. Logged-in testing finds deeper bugs but takes longer, because testers must map permissions and business logic.
Black-box versus white-box. Black-box testing mimics an outsider with no inside knowledge. White-box testing gives testers source code or architecture details, which finds more but costs more.
Retesting. Many vendors charge separately to verify fixes. Ask whether a free retest window is included.
Report depth. A compliance-grade report with executive summary, technical detail, and remediation guidance takes real time to produce.
Methodology and standards. A test scoped to a recognized framework involves more structured effort than an ad hoc scan-and-report job.
Legal and scoping overhead. In the UK, the Computer Misuse Act 1990 makes written authorization essential, and in the US the CFAA (18 U.S.C. § 1030) plays the same role. Proper scoping and sign-off add a little cost but protect everyone.
Compliance Standards and Their Effect on Price
Compliance is one of the biggest hidden multipliers in penetration testing budgets. A test performed purely for internal assurance can be scoped loosely. A test performed because a standard requires it usually cannot.
PCI DSS, maintained by the PCI Security Standards Council, mandates penetration testing for organizations handling card data, and it specifies expectations around scope, methodology, and remediation. ISO/IEC 27001 certification similarly pushes organizations toward regular, documented testing as part of an information security management system.
The practical effect is that compliance-driven tests often include more formal scoping documents, more detailed reporting, and mandatory retesting. Each of those steps has a price. If a standard is driving your test, say so at the quoting stage. Vendors price differently when they know the output must survive an auditor’s review.
It also helps to look at how other technology costs stack up against security spending. A single penetration test can cost more than a year of some software subscriptions, which is why teams often compare it against tools like password managers or hosting. If you are weighing budgets, it is worth seeing what other line items actually run, whether that is how much 1Password costs or how much Redis costs for a small project or business. Security testing is rarely the only item competing for the same money.
How to Compare Penetration Testing Quotes Properly
Comparing quotes line by line beats comparing headline totals. Here is a sequence that works in practice.
- Write a scope document first. List every application, IP range, API, and user role you want tested, and state whether testing is authenticated.
- Ask each vendor to price that exact scope, plus a separate line for retesting.
- Request a sample report with client details removed. Read the remediation section closely.
- Confirm who actually does the testing. Some firms subcontract, which affects quality and accountability.
- Check tester certifications and experience tied to your stack, in addition to general credentials.
- Ask what happens if testers find a critical issue mid-engagement. Good vendors pick up the phone.
- Confirm the authorization paperwork is included in the price.
A common mistake is choosing the cheapest quote for a compliance-driven test. If the report does not meet the standard’s expectations, you pay twice: once for the test and again for the one that actually counts.
Another mistake is scoping too narrowly to save money. Testing one application while ignoring the API it depends on often produces a clean report and a false sense of security.
Free and Low-Cost Alternatives: What They Really Deliver
Budget pressure is real, and there are cheaper ways to get security signal. Automated scanners can surface known vulnerability patterns for a fraction of a manual test, and bug bounty programs pay only for confirmed findings. Both have a place.
The distinction matters, though. Scanners produce false positives and miss logic flaws that require human judgment. Bug bounties reward researchers for finding issues but do not give you a structured report mapped to a compliance framework, and coverage depends on researcher interest. For an early-stage product, a scanner plus a focused manual test of your most sensitive flow is often a smarter spend than a broad, shallow engagement. For anything touching regulated data, a proper manual test is hard to replace.
It is also worth putting security spending in context with other recurring costs. Teams often discover that a modest annual testing budget compares reasonably with subscriptions they already pay for, whether that is what WordPress really costs once you count hosting and plugins or what Google Chrome costs an organization over time. Framing the test as a fixed annual line item makes it easier to defend.
Practical Tips That Save Money Without Cutting Corners
Experienced buyers tend to do a few things consistently, and those habits reduce cost more than hard negotiation.
They test after major changes, not on a random calendar date, so findings are actionable. They fix low-hanging issues found by scanners before commissioning a manual test, so consultant hours go toward hard problems. They bundle related applications into one engagement to share scoping and reporting overhead. And they ask for a retest window in the original contract rather than paying for it separately later.
One more field-tested habit: keep a short internal log of what was fixed after each test. When the next quote arrives, you can show a vendor exactly what changed, which tightens scoping and often trims the price.
Conclusion
Penetration testing costs anywhere from roughly $1,500 for a single small web application to well over $100,000 for large enterprise scopes, with most mid-size engagements landing between $5,000 and $15,000. The number itself matters less than what sits behind it: how many targets are in scope, whether testing is authenticated, how deep the report goes, and whether a compliance standard is calling the shots. Get a written scope, compare quotes line by line, read a sample report, and confirm who actually does the work. Done that way, the price you pay reflects the assurance you get, which is the whole point of buying a test in the first place.
FAQ
Is penetration testing worth it for a small business?
For most small businesses handling customer data or payment information, yes. A single breach typically costs far more than a test, and many enterprise customers now require evidence of security testing before signing contracts. A focused test of your most sensitive application is usually the right starting point rather than a broad engagement.
How often should a company run a penetration test?
Common practice is at least annually, plus after major infrastructure or application changes. Compliance standards often set their own cadence. Organizations shipping code frequently increasingly move toward continuous or retainer-based testing rather than a single yearly event.
Does a penetration test price include fixing the vulnerabilities?
No. Testing identifies and documents issues; remediation is separate work, usually handled by your own team or a development partner. Some vendors offer remediation support as an add-on, but it is rarely bundled into the test price. Budget for the fix as well as the finding.
What is the difference between a vulnerability scan and a penetration test?
A vulnerability scan is largely automated and produces a list of potential weaknesses. A penetration test uses human testers who attempt to exploit those weaknesses and chain them into realistic attack paths. Scans are cheaper and faster; tests are deeper and produce actionable, prioritized findings.
Can I negotiate the price of a penetration test?
Often, yes, especially on scope. Reducing the number of targets, testing unauthenticated first, or bundling multiple applications into one engagement can lower the total. Asking for a retest window to be included is another common and reasonable negotiation point.
What should be in a penetration testing contract?
At minimum: a defined scope, testing window, methodology reference, report format and delivery date, retesting terms, confidentiality clauses, and written authorization to test. The authorization piece is not optional, since testing without it can be unlawful under laws such as the Computer Misuse Act 1990 in the UK.


