How to request a retest

Last updated: July 28, 2026

Once your team remediates a vulnerability, you can request a retest directly from the platform to confirm the fix, without waiting for the next Threat Emulation.

Who can request a retest

  • Available to users with the Owner or Operator role.

  • You can request a retest on any vulnerability, except those in Discarded status.

  • Read-only users can also view the results and retest history.

👉 This way, remediation validation stays in the hands of whoever manages the asset.

How to request it

  1. Open the vulnerability detail view.

  2. In the Retest section, click Request retest.

  3. Confirm the request.

What happens next

  • First, a preliminary configuration check runs to make sure the asset can be tested. This initial step can take a few minutes.

  • If the check passes, the retest starts and the vulnerability shows the Retest in progress status.

  • If the check fails, the cause is displayed.

👉 From there, the Retest Agent takes care of everything and notifies you with the result.

Manual retests

Some vulnerabilities can't be retested automatically — for example, findings from mobile or infrastructure projects. In those cases:

  • The button shows Request manual retest.

  • A Striker performs the retest.

  • Results usually take a few business days.

👉 Once the retest starts, the experience is the same: you can see it in progress and you'll receive the result when it's done.