How to request a retest

Last updated: October 19, 2026

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

Who can request a retest

  • Users with the Owner or Operator role.

  • It can be requested on any vulnerability, except those in Discarded status.

  • Users with read-only access can view retest results and history.

This way, validating the remediation stays in the hands of the people who manage the asset.

How to request it

  1. Open the vulnerability detail.

  2. In the Retest section, click Request retest.

  3. Confirm the request.

What happens next

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

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

  • If the check fails, the cause is shown.

From that point on, the Retest Agent takes care of everything and notifies you of the result. To understand each result, see How to interpret retest results.

Manual retests

Some vulnerabilities cannot 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 see it in progress and receive the result when it finishes.