Continuous penetration testing

Every role. Every route. Every release.

For teams that ship every week, often with AI assistants: agents test each release and a researcher reviews what changed.

  • Per release
  • Monthly retainer
  • Change monitoring

Scope and deliverables

What we look at

  • New features and routes as they ship
  • Regression checks on every past issue
  • New hosts and changes on your external surface
  • The same assigned researcher every month

What you get

Issues as they are confirmed rather than at the end, plus a monthly summary for leadership.

Typical length

Monthly, cancel any time

Methods aligned with

OWASP ASVS, OWASP API Top 10, CVSS 3.1

Why it matters

Teams that ship every week, often with AI assistants, change their attack surface every week too. A yearly test describes an app that no longer exists.

Continuous testing keeps our hackbots on each release and a researcher on what changed, so new issues reach you as they are confirmed rather than at the end.

How we test it

Hackbots for breadth. Hackers for depth. Every lead is proven or discarded by a researcher before it reaches your report.

Our hackbots

  • Test new features and routes as they ship
  • Re-run every past issue so old bugs stay fixed
  • Watch your external surface for new hosts and changes

Our researchers

  • Review what changed in each release and test it by hand
  • Send each confirmed issue as soon as it is proven
  • Write a monthly summary for leadership

How an engagement runs

Five steps from the first call to the retest. You work directly with the researchers testing your systems at every one of them.

  1. Scope

    1 to 3 days

    We agree on assets, test accounts and rules of engagement, then send a fixed price.

  2. Recon

    First days of testing

    Hackbots map every host, route and role. A researcher builds the threat model.

  3. Exploit

    Most of the window

    Hackbots run the matrix at scale while researchers test by hand and take each lead to the end.

  4. Report and fix

    Within 5 working days

    Verified issues only, each with a CVSS 3.1 vector, replayable proof and a patch.

  5. Retest

    Free, within 90 days

    We confirm each fix and issue an updated report and attestation letter.

Tell us what you run. We’ll send a fixed quote.

No obligation and no sales sequence. A senior researcher reads every request and replies within one working day.