Add-ons: extra testing layers

Last updated: April 13, 2026

Add-ons are additional capabilities that expand continuous testing coverage across assets, adapting it to each business's specific needs.

They don't replace the baseline of continuous validation — they act as a complementary layer that adds depth, speed, or context in specific scenarios.

What Add-ons are for

Add-ons let you:

  • Shorten the exposure window between testing cycles

  • Zero in on recent changes

  • Go deeper on critical assets

  • Match testing to the pace of the business

👉 They're especially useful in fast-moving environments where changes happen often.

Types of Add-ons

Change-based testing

This Add-on assesses the risk introduced by recent changes to an asset.

Instead of waiting for the next testing cycle, it zeroes in on:

  • New features

  • Changes to business logic

  • Relevant system modifications

This allows you to:

  • Catch vulnerabilities faster

  • Validate changes in real time

  • Shrink the exposure window

It can run:

  • Manually

  • Automatically (integrated into CI/CD)

👉 It doesn't replace continuous testing — it complements it.

Human hacking (Strikers)

This Add-on adds an extra layer of manual validation performed by offensive security experts.

It enables:

  • Manual testing on specific assets

  • Extra validation of findings

  • Deeper analysis in complex scenarios

👉 Recommended for:

  • Highly critical assets

  • Compliance requirements

  • Cases where a higher level of confidence is needed

How they work on the platform

Add-ons apply to existing assets as an extension of continuous testing.

  • No need to create a new asset

  • They're activated as needed

  • They can be combined with each other

👉 They act as an additional layer on top of baseline coverage.

How they're set up

Activating Add-ons depends on each organization's context:

  • They're defined by asset type

  • They're applied based on changes or criticality

  • They can be integrated into development workflows

How pricing works

Add-ons aren't included in the baseline coverage — they're added on as needed.

Their scope depends on:

  • How often the system changes

  • The asset's criticality level

  • The need for additional testing

  • Specific business requirements

👉 They're structured as service extensions, tailored to each case.

When to use Add-ons

They're especially useful when:

  • You ship releases frequently

  • You're introducing relevant changes

  • You need to validate specific features

  • You want to go deeper on critical assets

Best practices

✔ Use change-based testing to validate every relevant change

✔ Bring in manual testing for critical assets

✔ Integrate Add-ons into development pipelines

✔ Always combine them with continuous testing

Add-ons let offensive security keep pace with the business, adding speed and depth without breaking the continuity of testing.