Scope sets the price. Here are the published ranges by test type, what moves the number, and how to tell a real test from a cheap scan.
A penetration test is priced by effort: how many systems, applications and user roles are in scope, how deep the testers go, and what the report must satisfy. The ranges below come from rate cards and cost guides that security vendors publish in U.S. dollars, read in October and November 2026.
They are planning ranges from vendors that sell testing, not independent benchmarks and not InfoSight prices or a quote. To scope a test for your own environment, start with InfoSight's zero-cost 15-minute scoping call.
Tightly scoped single test
From about $5,000
Standard engagement
$10,000 to $35,000
Complex, enterprise-wide work
$100,000 or more
Testing subscription (PTaaS)
About $5,000 to $100,000+ a year
Published price lists and cost guides in U.S. dollars, read October and November 2026. Not InfoSight prices or a quote. The PTaaS low end rests on one published guide.
A common way to price a test is a day rate multiplied by the planned testing days. Published guides put day rates at about $1,200 to $3,000, depending on the tester's seniority and the firm. These seven choices move the quote.

The count of targets is a major lever: external IP addresses, internal hosts, applications, user roles and API endpoints. Give the firm an accurate asset list before it quotes, so the number is not padded for unknowns.

An unauthenticated test sees what an outsider sees. Credentials for each user role open the logged-in side of an application, where access-control and business-logic flaws tend to sit, and each added role adds testing time.

A report that goes to an outside assessor or examiner needs to document scope, methods and findings in the form that reviewer expects. One published guide puts that premium at 10 to 25 percent.

Many firms include one re-test of fixed findings within 30 to 90 days; others bill it separately. A cheaper quote with paid re-testing can cost more by the time you hold a report that shows the fixes validated.

Software does most of the work in a scanner-led assessment, which is why it is cheap. A penetration test may use scanners too, but its testers go on to exploit and chain what they find. Manual testing, where a tester chains weaknesses the way an attacker would, takes skilled hours, and tester time is a major cost driver.

A test that has to start next week, or finish before an audit date, can carry a premium. Booking ahead of your compliance calendar avoids it.

Physical testing, and some internal testing, puts testers in your building. Travel and lodging are added to the testing days.
A low quote can mean fewer tester days, a narrower scope, more automation or excluded re-testing, so ask what the proposal includes before you compare prices. NIST describes vulnerability scanning as a technique to identify hosts and their associated vulnerabilities. A penetration test goes further: evaluators mimic real-world attacks and look for combinations of weaknesses that gain more access than any single flaw would.
A scan sold as a penetration test may miss those chains and the business-logic flaws that take a person to find. If your auditor, examiner or customer expects a penetration test, the scan report may not be accepted, and you may end up paying for the test as well. Scans still have a place between tests, and InfoSight offers vulnerability assessments as a separate service.
A point-in-time test is a single engagement: testers work an agreed scope over a set window and deliver a report. Penetration testing as a service (PTaaS) is a subscription that pairs a platform with scheduled or on-demand testing. One published guide puts a PTaaS subscription for a single web application at $5,000 to $15,000 a year, and published guides put broad coverage at $100,000 or more.
| Point-in-time test | PTaaS subscription | |
|---|---|---|
| How it is billed | A fixed fee or time and materials, per engagement | An annual subscription |
| Cadence | A snapshot, scheduled by the rule or contract that applies (often yearly or after a major change) | Continuous or scheduled testing through the term |
| Re-testing | Often one round within 30 to 90 days, or billed separately | Usually included through the term |
| Strength | Deep manual work on complex logic and chained exploits | Steady coverage and quick checks after fixes |
| Watch for | Months can pass between tests | Tiers differ in how much human testing they include |
The two models can work together: a yearly manual test where a rule or an auditor expects one, with subscription coverage in the months between.
How often you test is the other half of the budget. PCI DSS Requirement 11.4 calls for internal and external penetration tests at least once every 12 months and after any significant infrastructure or application upgrade or change. The FTC Safeguards Rule requires the financial institutions it covers to run annual penetration testing unless they have effective continuous monitoring or other ongoing vulnerability detection, and exempts institutions holding customer information on fewer than 5,000 consumers from that requirement. New York's DFS cybersecurity regulation requires covered entities, subject to size exemptions, to run a penetration test at least annually. The HIPAA Security Rule requires a periodic evaluation and does not name penetration testing; a January 2025 federal proposal to require one every 12 months, with vulnerability scans every six, had not been finalized as of October 2026. Our penetration testing services page covers each test type and the rules that require testing, and the Miami penetration testing page covers South Florida's regulated buyers.
It depends on scope. In October 2026, published price lists started around $5,000 for a tightly scoped single test, and published guides put a standard engagement at about $10,000 to $35,000 and complex enterprise work above $100,000. The table on this page breaks the ranges out by test type.
Because the same label covers very different work: a few IP addresses or hundreds, one user role or many, a scanner-led pass or manual testing with chained exploits. Each changes the tester days you pay for.
No. A scan identifies hosts and their known vulnerabilities. In a penetration test, people mimic real attacks and chain weaknesses together to show how much access an attacker could gain. Scans are useful between tests, but they do not replace one.
It depends on which rule applies. PCI DSS Requirement 11.4 calls for internal and external tests at least every 12 months and after significant changes. The FTC Safeguards Rule sets annual testing for the institutions it covers unless they run effective continuous monitoring or other ongoing vulnerability detection, and New York's DFS regulation sets an annual test for covered entities, subject to size exemptions. HIPAA requires a periodic evaluation but does not name penetration testing. Outside those rules, your risk assessment and your rate of change set the cadence, and the scoping call turns it into a schedule.
Not always. Many firms include one re-test of fixed findings within 30 to 90 days, and others bill it separately, so get the terms in writing. With InfoSight, after you patch you click "Re-Test" in the portal and the testers re-attack those CVEs within 24 hours.
Usually the low end of each range when the environment is small and tightly scoped, because fewer IP addresses, applications and user roles mean fewer tester days; a small company with a complex application or several cloud tenants sits higher. Published starting prices for a tightly scoped test, such as a small external network or a simple web application, cluster around $5,000.
Published guides put a small, simple web application at about 3 to 7 days of testing, one with a few user roles at about 5 to 10 days, and a complex one at 2 to 3 weeks or more. One firm lists its external perimeter test at up to 5 days, and one guide puts red team exercises at 2 to 8 weeks or more. Scoping comes first and report writing after.
Yes. InfoSight offers a preliminary budget estimate without scheduling a consultation or speaking with a salesperson. For a scope built around your environment, book the zero-cost 15-minute scoping call; it comes with a preliminary scan report to share with stakeholders and executives.
The price ranges and testing days on this page come from the documents below: vendors' own published prices and vendor-written guides to market prices, read on the dates shown. They are not InfoSight prices and not a quote.
Book a zero-cost 15-minute scoping call and instantly receive a preliminary scan report to share with stakeholders and executives.
No spam—one expert follow‑up, guaranteed.
Stay informed of the latest cyber trends.