Retesting Findings

​

Overview

Retesting checks whether a previously reported red-team finding still reproduces after you apply a fix. MindFort attempts to reproduce the reported issue against the live target and updates the finding with the result. Use a retest after your team deploys a remediation. A retest focuses on the existing finding; it does not replace a full assessment when you need broader coverage of the target.

​

Before You Retest

Confirm that:

• the remediation is deployed to the target environment
• the target is reachable by MindFort
• any credential required to reproduce the finding is still valid
• the finding is not already queued or being retested

If the original finding requires authentication, MindFort uses the finding’s saved credential selection, including a secondary credential when required, to prepare an authenticated session. You do not need to provide credentials again when starting the retest.

​

Retest One Finding

1. Open Findings from the sidebar.
2. Select the target that contains the finding.
3. Open the finding details.
4. Click Retest in the finding actions.

The button shows the one-credit cost. After you submit the request, the finding displays Retest queued and starts automatically when capacity is available.

​

Retest Multiple Findings

You can queue several eligible findings from the same target:

1. Open the target’s Findings view.
2. Select the red-team findings you want to verify.
3. Click Retest Issues in the bulk action bar.

MindFort reports how many retests were queued, skipped, or failed to queue. A finding is skipped when it is not eligible for a new retest, such as when another retest is already active. To retest every open finding for a target, use the retest action in the findings toolbar. The credit indicator shows the number of open findings that will be submitted.

​

Understand Retest Status

The finding details show the current or most recent retest state. A failed or incomplete retest does not mean the vulnerability is fixed. Only Confirmed fixed resolves the finding. Review the retest evidence to understand the conditions tested and the basis for the result.

​

Capacity and Queueing

MindFort queues accepted retests and starts them as execution capacity becomes available. If you cannot start a retest, review the displayed reason and retry when capacity is available. Queued work starts automatically. You can leave the finding page and return later to review the result and completion time.

​

Troubleshooting

If a retest cannot complete:

• confirm the target is online and reachable
• verify the remediation has been deployed to the tested environment
• update expired or changed authentication credentials
• check that login instructions still match the target’s current flow
• wait for available capacity if the retest action is disabled
• start a new retest when the finding reports that the previous run timed out

If the issue continues, contact support@mindfort.ai with the finding ID and the failure reason shown in MindFort.

​

Recover from an authentication failure

If a retest fails because a credential could not authenticate, was deleted, or is unavailable, you can choose a replacement from the finding details:

1. Open the finding and read the retest failure message.
2. Select Choose another credential.
3. Choose a stored credential for the same target. The picker shows Verified, Verification failed, or Not verified to help you check its readiness.
4. For a finding that requires two accounts, review Primary credential and Secondary credential. You can replace either account, but the two selections must be different.
5. Select Retest to queue a new attempt.

If no credentials are saved, add one in Target Inventory > Stored Credentials, then return to the finding. Update incorrect account details or login instructions and verify the credential before retrying. Your selections also apply to future retests of this finding. The original finding evidence is preserved. Choose another credential appears after an authentication or unavailable-credential failure and requires permission to retest findings. Review the failure message for billing information. Authentication or unavailable-credential failures can report that you were not charged.

​

Automatic retest status

An organization can configure automatic retesting in Settings > Features. Two separate settings apply:

• Auto-Retest Mode validates eligible red-team findings after they are resolved, including resolution through linked tickets. The finding is already resolved when validation is queued; a result that remains vulnerable reopens it. Won’t Fix resolutions, including canceled Linear issues, do not trigger this mode.
• Auto-retest after patch merge checks a MindFort patch after its pull request merges. Merging the patch alone does not resolve the finding. Resolution requires a retest result indicating the issue is fixed under the tested conditions.

Patch-merge retests can have an After Merge Retest Time Delay from 0 to 60 minutes to allow deployment to finish. A delayed run shows Retest scheduled after patch merge and its scheduled time. Queuing still depends on access, credentials, and retest eligibility. An incomplete retest is not confirmation of a fix, even if a manual action or ticket transition already set the finding to Resolved.

​

Next Steps

• Review the complete finding lifecycle.
• Generate a proposed fix with Patching.
• Run a broader assessment when you need coverage beyond one finding.