Platform
Retests
Verify that remediated vulnerabilities are actually fixed.
Retests let you validate that a finding has been properly remediated by re-running the specific exploit against the target.
How retests work
- Open a finding in the findings dashboard
- Click Retest
- CodeWall launches a focused test that specifically targets the vulnerability described in the finding
- The retest produces one of four outcomes:
| Outcome | Meaning |
|---|---|
| Remediated | The vulnerability is no longer exploitable |
| Still Vulnerable | The vulnerability still exists |
| Inconclusive | The agent couldn't determine the status (e.g., target unreachable) |
| Running | The retest is still in progress |
Viewing retests
Navigate to Pentests > Retests to see all retest results:
- Summary cards showing counts by outcome
- Filter by project and outcome
- Sort by outcome, finding, target, project, start time, or duration
- Each row shows: finding name, target, project, start time, and duration
Best practices
- Retest after deploying a fix, not before — avoid unnecessary runs
- If a retest comes back Still Vulnerable, review the remediation and verify it was deployed
- Use retests as evidence of remediation for compliance and audit purposes
- Retests of previously Remediated findings confirm fixes haven't regressed