Retesting

Retesting can be performed on submissions to ensure they were patched successfully.

Paid Add-On: To enable this feature on your program, contact your Account Manager.

Request Retest

Accepted Submissions Only: To request a retest a submission must be in the Unresolved or Resolved state. This is to ensure that the submission acceptance workflow is kept to.

To request a retest on a submission:

  1. Go to the recently patched submission.

  2. Scroll down the submission near the comment box, and click Request Retest. request-retest

  3. Now the retest is in a pending state, based on the priority the submission, the retest will be completed within the applicable SLA.

    pending

    One retest at a time: A retest can only be requested on a submission if it is not already pending.

Successful Retest Response

If the vulnerability is not present upon retest, the Bugcrowd ASE will mark the retest as patched. When this is done, the submission will auto update to the Resolved state.

successful

Failed Retest Response

If the vulnerability is present upon retest, the Bugcrowd ASE will mark the retest as failed. When this is done, the submission will auto update to the Unresolved state. failed

Once the vulnerability is re-patched, one can re-request a retest on the submission, following the same process as above.

Note, we’ll send an email to anyone subscribed to the submission with updates on the retest outcome.

Limited retesting per submission: Each submission is able to be retested a maximum of two times.


Onboarding
Account Management
Program Management
Reporting
Submission Management
Integration Management