Contents
- PTaaS at a Glance
- What is Penetration Testing as a Service?
- How PTaaS Differs from a One-Off Penetration Test
- How PTaaS Works in Practice
- What’s Automated in PTaaS, and What Still Needs a Human Tester
- The Main PTaaS Delivery Models
- The Benefits of PTaaS
- The Limitations and Pitfalls of PTaaS
- Which Organisations Benefit Most from PTaaS?
- PTaaS and Compliance
- How Much Does PTaaS Cost?
- Questions to Ask a PTaaS Provider
- Ongoing Testing Programmes with Fortifi
- PTaaS FAQs
Penetration Testing as a Service (PTaaS): What You Get and When It Makes Sense
For years, penetration testing followed the same pattern. You’d agree on a scope, a tester would spend a few days or weeks on your systems, and a PDF report would arrive at the end. Then nothing would happen until the same time the following year.
Penetration testing as a service, usually shortened to PTaaS, was designed to break that cycle. Instead of a single engagement once a year, PTaaS gives you ongoing access to testing through a platform, with findings delivered as they’re discovered, retests on demand and a mix of automated checks and human testing running throughout the year.
It’s an appealing idea, and for the right organisation it’s a genuine improvement. But the term is used to describe some very different services, from fully automated scanning tools with a dashboard to properly resourced programmes led by experienced testers. This guide explains what PTaaS actually includes, how it differs from a one-off test, what can be automated and what still needs a human, and which organisations are most likely to benefit.
PTaaS at a Glance
If you only have a minute, here’s the summary:
- PTaaS is a delivery model, not a type of test, so it changes how and how often testing is delivered, but the testing itself can still cover networks, web applications, cloud environments, and more.
- Good PTaaS combines automation with human testers. Automated tools handle continuous monitoring and repetitive checks, while people carry out the deeper testing that finds the most serious issues.
- It suits organisations that change often because, if your systems, applications or cloud environments change every few weeks, an annual snapshot goes out of date quickly.
- It isn’t automatically better value. A PTaaS subscription that tests the same narrow scope every month can cost more than a well-planned programme of traditional tests, while telling you less.
What is Penetration Testing as a Service?
Penetration testing as a service is a way of buying penetration testing as an ongoing subscription, not as a series of separate projects. So, rather than commissioning a test, waiting for a report and starting again next year, you get continuous or regular testing over the length of a contract, usually managed through an online platform.
Interestingly, PTaaS has been recognised as a distinct category for several years. Gartner has included it in its Hype Cycle for Security Operations since at least 2021, as BreachLock’s announcement of its inclusion shows. In that time, the model has spread from specialist providers to much of the wider penetration testing market.
Most PTaaS offerings are built around a few common components:
- A platform or portal where you manage scope, view findings, track remediation and download reports.
- Real-time findings, so vulnerabilities appear on the platform as soon as they’re confirmed, without waiting for a final report.
- On-demand retesting, which lets you ask for a fix to be checked without arranging a new engagement.
- Continuous automated monitoring of your attack surface, usually focused on internet-facing systems.
- Scheduled human testing at agreed intervals, such as quarterly or after major releases.
- Integrations with ticketing and development tools, so findings can flow straight into your team’s existing workflow.
Crucially, the balance between those components varies enormously between providers. Some PTaaS products are almost entirely automated, while others are essentially a consultant-led testing programme with a platform on top. Understanding which one you’re being offered is the most important part of buying PTaaS well.
How PTaaS Differs from a One-Off Penetration Test
| Traditional penetration test | Penetration testing as a service | |
| How it’s bought | A fixed-scope project, usually priced by tester days | A subscription over a contract period, often 12 months or longer |
| Frequency | Typically annually and after significant changes | Continuous monitoring, plus regular scheduled testing |
| When you see findings | In a report at the end of the engagement | On a platform as they’re confirmed |
| Retesting | Arranged separately, and sometimes charged extra | Usually available on demand within the subscription |
| Coverage between tests | None, until the next engagement | Ongoing automated checks, with human testing at intervals |
| Best suited to | Stable environments and specific compliance deadlines | Environments that change often and need continuous assurance |
With a traditional annual test, a new vulnerability introduced the week after testing finishes can sit undetected for nearly a year. PTaaS narrows that window, which is the main reason organisations adopt it. We look at the wider question of testing frequency in Annual vs. Continuous Penetration Testing.
That said, a traditional test still has a lot going for it. For a stable environment, or where you need a single, clearly scoped report for an audit, a well-planned annual test can be the simpler and more cost-effective option. Our guide to annual penetration testing explains how to get the most from that approach.
How PTaaS Works in Practice
Details vary by provider, but a typical PTaaS engagement follows a similar pattern.
Onboarding and scoping
Like any penetration test, PTaaS starts with scoping. You agree which systems, applications and environments are covered, how often human testing will take place, and which rules of engagement apply. Good providers will also map your external attack surface at this stage, because many organisations have internet-facing systems they’ve forgotten about. Our guide to attack surface assessment explains why that matters.
Continuous monitoring
Once the service is running, automated tools monitor your in-scope systems for changes and known vulnerabilities, such as newly exposed services, expired certificates or software that’s fallen behind on patches. This is the part of the PTaaS platform that runs constantly in the background.
Scheduled human testing
At agreed intervals, experienced testers carry out deeper, manual testing. This might be quarterly testing of a core web application, testing triggered by a major release, or a rotating programme that focuses on a different part of your environment each time. This is where most of the serious findings come from.
Real-time reporting and remediation
Findings are added to the platform as they’re confirmed, with severity ratings, evidence and remediation guidance. Your team can start fixing issues straight away and can often ask questions of the tester directly through the platform.
On-demand retesting
When a fix is in place, you request a retest through the platform, and the tester confirms that the issue is resolved. This closes the loop much faster than waiting for the next annual test, and it gives you a clear audit trail. We explain why that matters in our post on retesting after fixing vulnerabilities.
Periodic reports
Most PTaaS providers can also produce formal reports or attestation letters at set points, which is useful for audits, customer questionnaires and board reporting.
What’s Automated in PTaaS, and What Still Needs a Human Tester
This is the question that matters most when you’re comparing PTaaS providers, because it determines what you’re actually paying for.
What automation does well
Automated tools are good at tasks that are broad, repetitive and well-defined. In a PTaaS platform, that usually includes:
- Discovering internet-facing assets and spotting new ones as they appear.
- Scanning for known vulnerabilities and missing patches.
- Checking for common misconfigurations, such as exposed services or weak encryption settings.
- Re-running the same checks frequently, so changes are picked up quickly.
AI-driven tools are pushing that boundary further, as they can now reason about what they find and attempt simple attack chains. Our guide, What is AI-led Penetration Testing? explains what these tools can and can’t do.
What still needs a human tester
Perhaps most importantly, the issues that cause the most serious breaches are often the ones automation struggles with. Experienced testers are still needed for:
- Business logic flaws, such as a user being able to approve their own payment or access another customer’s account by changing a value in a request.
- Chaining weaknesses together, where several minor issues combine into a serious compromise.
- Access control testing across different user roles, which requires an understanding of what each role should and shouldn’t be able to do.
- Judgement and context, such as recognising that a low-severity issue on a payroll system matters more than a medium-severity issue on a test server, and knowing how to test sensitive environments, such as fragile internal networks and operational technology, without causing disruption.
The difference between the two is explained in more depth in our guide to automated vs manual penetration testing. The short version is that automation gives PTaaS its breadth and speed, while human testers give it depth. A PTaaS service without meaningful human testing is really continuous vulnerability scanning with a better interface.
The Main PTaaS Delivery Models
Because the term covers so much, it helps to think of PTaaS in three broad categories:
- Automation-led platforms, where most of the testing is carried out by tools, with limited human review. These are usually the cheapest, and they’re useful for broad, continuous coverage, but they’re the least likely to find complex issues or satisfy strict compliance requirements.
- Hybrid PTaaS, where a platform provides continuous monitoring and reporting, and human testers carry out scheduled manual testing within the subscription. This is what most people mean by PTaaS, and it’s where the model works best.
- Managed penetration testing programmes, where a consultant-led provider plans and delivers a year-round testing programme, rotating the focus across your environment and using automation to support the testers. The platform matters less here, and the quality of the people matters more.
None of these is right for everyone. The best choice depends on how often your environment changes, what you need the testing to prove, and how much in-house capacity you have to act on findings.
The Benefits of PTaaS
When it’s delivered well, PTaaS offers some genuine advantages over traditional testing:
- Shorter exposure windows, because new vulnerabilities are found closer to the time they’re introduced.
- Faster remediation and easier retesting, since your team can start fixing issues as soon as they’re found and prove the fixes have worked without arranging a new engagement.
- Better fit for modern development, where applications change every week or two and an annual test can’t keep up.
- More predictable budgeting, with a fixed subscription in place of a series of separate projects.
The Limitations and Pitfalls of PTaaS
PTaaS isn’t a cure-all, and some of its weaknesses are easy to overlook.
Testing the same thing more often
Notably, more frequent testing only helps if it’s testing the right things. Many PTaaS products focus on external infrastructure, because that’s the easiest part of an environment to test continuously.
If your subscription runs the same checks on the same systems every month, while your Microsoft 365 tenant, cloud configuration or internal network are never looked at, you’re simply testing the same things every year, only more often.
That’s a fast route into the Pentest Trap, where a steady stream of clean results creates confidence the real risk doesn’t justify. We explore this in more detail in our post on why scope matters more than frequency.
Automation presented as testing
Some services marketed as PTaaS include very little manual testing. If you’re paying for penetration testing as a service, find out how many tester days are included and what those testers will actually do.
Compliance acceptance
Not every auditor will accept findings from an automated platform as evidence of a penetration test. PCI DSS, for example, expects testing to be carried out by a qualified person following a documented methodology. Make sure the human testing within your subscription, and the reports it produces, will meet your auditor’s expectations.
Capacity to act on findings
Continuous testing produces a continuous stream of findings. If your team doesn’t have the capacity to triage and fix them, PTaaS can create a growing backlog instead of reducing your risk.
Long-term cost
Subscriptions accumulate quietly. Over two or three years, a PTaaS contract can cost more than a well-planned programme of traditional testing, which is worth weighing up honestly before you commit. We look at a similar trade-off in Why AI Pen Testing Can Cost More Than a Human-Led Test.
Which Organisations Benefit Most from PTaaS?
PTaaS tends to make the most sense for organisations where change is constant, and the cost of a gap in testing is high. That typically includes:
- SaaS and technology companies that release code frequently, where each release can introduce new vulnerabilities.
- Organisations with large or changing external attack surfaces, such as businesses with many websites, cloud services or remote access systems.
- Regulated businesses that need to show ongoing assurance to regulators, auditors or enterprise customers, such as financial services firms.
- Organisations going through major change, such as a cloud migration, a merger or a rapid expansion, where the environment looks different every few months.
Operational technology is a special case. Industrial environments need continuous assurance, but they also need testing that’s carefully controlled to avoid disrupting live processes, which changes how PTaaS has to be delivered. We cover that in our guide to PTaaS in operational technology.
When PTaaS may not be the right fit
For some organisations, a traditional approach is simpler and better value. If your environment is small and stable, if you only need testing to meet a single annual compliance requirement, or if you don’t have the internal capacity to act on a continuous stream of findings, a well-scoped annual test with retesting may serve you better. You can always move to PTaaS later as your needs change.
PTaaS and Compliance
PTaaS can support most compliance frameworks well, as long as the service includes genuine human testing and produces reports your auditor will accept.
For PCI DSS, the human testing within the subscription still needs to meet Requirement 11.4, including internal and external testing at least every 12 months and after significant changes, which we cover in our guide to PCI DSS penetration testing.
For ISO 27001 and SOC 2, the continuous record of findings, fixes and retests that PTaaS produces can be strong evidence that your controls are working.
For a wider view, see our guides to which compliance standards require penetration testing and what auditors want to see in a penetration test report.
How Much Does PTaaS Cost?
PTaaS is usually priced as an annual subscription, and the cost depends on the size of your environment, how often human testing takes place and how many tester days are included. As a rough benchmark, Stingrai’s UK pricing analysis puts annual PTaaS subscriptions at around £20,000 to £80,000, although smaller, more focused services can cost less.
When comparing a PTaaS quote with traditional testing, look at the number of tester days included and what they’ll be spent on, not just the headline price. Our guide to how much a penetration test costs explains what drives the price of testing more generally.
Questions to Ask a PTaaS Provider
Before you sign a PTaaS contract, these questions will tell you far more than the product brochure:
- How much of the testing is manual, how many tester days are included, and what qualifications do the testers hold?
- What’s in scope, and will the focus rotate across different parts of the environment over the contract?
- How are findings validated before they appear on the platform, so your team isn’t chasing false positives?
- How does retesting work, and is it included in the subscription?
- Will the reports satisfy your auditor, and can the provider produce attestation letters for customers?
- What happens at the end of the contract, including how you keep access to your findings and reports?
Ongoing Testing Programmes with Fortifi
Fortifi is a CREST-accredited penetration testing company, and our approach to ongoing testing starts with your risks, not with a platform. We plan multi-year programmes that rotate the focus across your environment, combine automation with consultant-led penetration testing, and include remediation guidance and retesting throughout, so you get the benefits of continuous assurance without paying to test the same things over and over again.
Our UK penetration testing services cover networks, web applications, cloud environments, operational technology and more. Because we don’t do sales calls, you’ll speak directly to a cybersecurity expert who can help you decide if PTaaS, a traditional annual test or a mix of the two is right for your organisation. Book a call with our team today.
PTaaS FAQs
What does PTaaS stand for?
PTaaS stands for penetration testing as a service. It’s a subscription-based model for penetration testing, usually delivered through an online platform, that provides continuous monitoring and regular testing, as opposed to a single engagement once a year.
Is PTaaS the same as automated penetration testing?
No, although some products blur the line. Automated penetration testing relies on tools, whereas good PTaaS combines automated monitoring with regular manual testing by experienced testers. A service with little or no human testing is closer to continuous vulnerability scanning.
Is PTaaS better than a traditional penetration test?
It depends on your environment. PTaaS suits organisations whose systems change often and who need ongoing assurance. For a stable environment, or a single annual compliance requirement, a well-scoped traditional test can be simpler and better value.
Does pentest as a service satisfy compliance requirements?
It can, provided the subscription includes genuine manual testing by qualified testers and produces reports your auditor will accept. Check with your auditor before relying on automated findings alone, particularly for PCI DSS.
How often does testing happen in a PTaaS subscription?
Automated monitoring usually runs continuously, while manual testing takes place at agreed intervals, such as quarterly, after major releases or on a rotating schedule across different parts of your environment. The exact cadence should be agreed during scoping.
Can PTaaS be used for operational technology?
Yes, but it needs to be adapted carefully, because uncontrolled testing can disrupt industrial processes. Our guide to PTaaS in operational technology explains how continuous testing can be delivered safely in OT environments.