Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Knowledge hub / Pentest as a service

Knowledge hub

Pentest as a service

Penetration testing bought as an ongoing subscription rather than a one-off project.

Illustration explaining Pentest as a service

What it means

Pentest as a service, often shortened to PTaaS, is penetration testing delivered as an ongoing service. You subscribe, scope your applications, and receive testing and findings on a continuing basis through a platform. A traditional pentest is a project with a start date, a report and an end.

The usual features: scheduling tests around releases, a live view of findings as they appear, a place to discuss fixes with the testers, and a retest when you say a fix is ready. The mix of human and automated work varies between providers, so ask what is actually behind the platform.

Why it matters

Software changes weekly, while a yearly test describes the application as it was on one date. A subscription fits teams that ship often, because testing keeps pace with change. Findings appear sooner, so fixes are cheaper and the report is less of a surprise.

It also changes how the money works. Spread-out testing is easier to budget and connects to continuous pentesting. The trade-off is that a subscription is only worth paying for if the findings are real and the retests happen. Otherwise you pay monthly for noise.

How it shows up

You meet it as a dashboard of findings with severity, evidence and status, tied to your ticketing system, and often to your build pipeline. Tests may run on a schedule, on a new release, or on request. The same platform records fix verification, which becomes evidence for audits.

Mistakes: buying a platform that runs a scanner on repeat and calls it a service, scoping only the main app and leaving APIs out, letting findings pile up with no owner, and assuming a subscription satisfies a compliance test requirement. Check what the auditor accepts, and ask who does the manual work.

Questions people ask

Pentest as a service, answered

Is PTaaS the same as a vulnerability scan?

No. A scan matches known signatures, while a penetration test tries to exploit weaknesses and finds logic flaws. Some PTaaS offerings are mostly scans with a nicer interface, so ask how findings are verified.

Look at a sample finding.

Does PTaaS replace an annual pentest?

It can, if the testing is thorough and your auditor or customers accept it. Check the requirement: some frameworks ask for a defined test at a set interval with a formal report.

Ask for a report that meets that format.

Who is it for?

Teams that release often, SaaS companies with customers asking for evidence, and agencies that want to offer recurring testing. A site that rarely changes may do fine with a project test.

Release speed is the main factor.

Can it run in our CI/CD pipeline?

Many services can trigger tests from a pipeline or gate a build on results. Check how long a run takes and how the gate treats findings of different severity.

Slow gates get switched off.

How does retesting work?

You mark a finding fixed, and the provider repeats the original exploit against the new code to confirm. This is stronger than running a fresh scan and noting that nothing came up.

Ask whether retests are included.

Cyberlop mark

Is the subscription finding real flaws?

Cyberlop can run on a schedule or in CI/CD and gate a build, reporting only what it exploited. A fix is proven by re-running the exact exploit against the new code. Book a pilot on one app.

Or start with a $199 pilot on one application: thirty days, success criteria agreed before day one, credited against the annual if you convert.