Skip to main content

Penetration testing as a service (PTaaS), from order to verified fix

Configure a penetration test online, choose how much auditor involvement the report needs, and follow the run in a dashboard your team logs into.

B-52 is the platform that carries out the test, built and operated by Security Brigade. Findings arrive with their evidence, and each one stays tracked until a retest confirms the fix.

What changes when a penetration test becomes a service

A penetration test bought as a project has a start date, an end date and a document. Bought as a service, it has a standing scope, a login and a record of each finding from discovery to closure. The difference shows at five stages.

A booked engagement and PTaaS with B-52, stage by stage
StageA booked engagementPTaaS with B-52
Ordering A scoping exercise, a proposal and a start date agreed around an assessor’s availability. You configure the target online and see the scope and an itemised price. A scoping call is there when the engagement needs one.
While the test runs Status arrives by email or on a call. The dashboard shows which of the six phases each run is in and how much of its test set has been worked.
The deliverable A document delivered when the engagement ends. A report, and the same findings in the dashboard with the request, the response and the reproduction steps on each one.
After the fix The status of each finding moves into a spreadsheet or a ticket queue. Each finding is tracked in the dashboard from open, through a retest, to a verified fix.
The next test Scoped again from the beginning. The scope is standing. The next run happens on your cadence or on your next build.

A booked engagement and PTaaS with B-52, stage by stage

Ordering

A booked engagement
A scoping exercise, a proposal and a start date agreed around an assessor’s availability.
PTaaS with B-52
You configure the target online and see the scope and an itemised price. A scoping call is there when the engagement needs one.

While the test runs

A booked engagement
Status arrives by email or on a call.
PTaaS with B-52
The dashboard shows which of the six phases each run is in and how much of its test set has been worked.

The deliverable

A booked engagement
A document delivered when the engagement ends.
PTaaS with B-52
A report, and the same findings in the dashboard with the request, the response and the reproduction steps on each one.

After the fix

A booked engagement
The status of each finding moves into a spreadsheet or a ticket queue.
PTaaS with B-52
Each finding is tracked in the dashboard from open, through a retest, to a verified fix.

The next test

A booked engagement
Scoped again from the beginning.
PTaaS with B-52
The scope is standing. The next run happens on your cadence or on your next build.

One service, three delivery models

Every model tests the same eleven coverage classes through the same platform. You choose where the auditor sits.

Fully autonomous

One person at your organisation authorises the scope. B-52 tests, proves and reports, and findings pass an independent automated cross-check on the way out.

For engineering and security teams who want proved technical findings on every release.

Autonomous, expert verified

The platform runs the assessment. A senior Security Brigade auditor verifies each finding before it is delivered.

For teams who want a senior auditor through every finding before it reaches them.

Human led

A named Security Brigade auditor scopes the engagement, directs it and owns the report, with B-52 doing the testing underneath.

For scopes and assurance requirements that call for an auditor in charge from the start.

Each of the three produces a report signable under Security Brigade’s CERT-In empanelment, held since 2008, so a subscription can feed a regulated filing whichever model runs it.

Compare the three delivery models

Continuous assessment on a scope you agree once

A service can test as often as you release. The scope is authorised once, and each run after that happens inside it.

Continuous penetration testing with B-52

  • Your cadence

    Runs go on a frequency you set, with the same six phases each time.

  • Your pipeline

    A build can start a run. GitHub Actions, GitLab CI and Jenkins are in production with customers, and a result can fail the build against a severity threshold you set.

  • New targets

    A target added to an authorised scope is tested on the next run.

The dashboard your engineers work from

Results are written into the dashboard by the run itself. Your team reads them in four screens.

Findings
What was found and how severe it is, with the evidence that proved it one click away.
Attack chain
The findings in the order they were chained, so you can read which one made the next reachable.
Test runs
The phase each run has reached and its progress against the test cases generated for that target.
Remediation
Every finding followed from open, through its retest, to a verified fix.

Look inside the dashboard · How the platform runs a test

See your scope and price before you commit

Ordering takes three steps, and the first two happen on the pricing page.

  1. 1. Configure the assessment

    Pick the target type and its size on the pricing page. Web, API, mobile, cloud, network and source-code assessments show the scope and an itemised price before you commit.

  2. 2. Choose who verifies it

    Fully autonomous assessments are priced online. Expert-verified and human-led testing are scoped and priced by our team.

  3. 3. Authorise the scope

    We confirm the scope and the authorisation with you, and testing starts after that.

FAQ

Questions about PTaaS

What is penetration testing as a service (PTaaS)?+

Penetration testing as a service is penetration testing bought and delivered through a platform. You order a test online, follow it in a dashboard as it runs, receive findings there as well as in a report, and track each one to a verified fix. With B-52 the platform also carries out the test.

How is PTaaS different from a traditional penetration test?+

The testing objective is the same. The delivery differs: a traditional test is scoped, scheduled and reported as one project, and the next test starts again from scoping. A PTaaS scope stands between tests, results arrive in a dashboard your engineers log into, and each finding is tracked there until a retest verifies the fix.

What can B-52 test as a service?+

Eleven coverage classes, including web applications, APIs, mobile apps, networks, cloud, Active Directory, source code and LLM applications. All three delivery models cover all eleven.

Does anything need to be installed in our network?+

Nothing is required inside your network for external and application testing. A deployment is needed only for internal testing, and B-52 can run on-premise or inside your own VPC.

How is PTaaS priced?+

Web, API, mobile, cloud, network and source-code assessments are priced on the pricing page, where you configure the scope and see an itemised price. Expert-verified and human-led testing are scoped and priced by our team. A continuous programme is priced on three things: how many targets, how often they are tested, and which delivery model runs them.