Retest
Trying the same finding again after fixes; a finding only counts as closed once a retest confirms it.
- 01
Why it matters
What proves a flaw is closed is not the person who made the fix but the same attack path being tried again. A fix sometimes removes only a symptom, leaves the root cause elsewhere or introduces a new bug. A retest closes the report and provides the evidence shown in audits.
- 02
Example
A developer says a form flaw is fixed by filtering the character the attack used. During the retest the same attack is tried with a different encoding and still works; this time the fix is made by encoding the input properly.
- 03
Common mistake
Not scheduling a retest, or buying a report without one. If the retest is not put in the budget and timeline from the start, findings get marked fixed but are never verified.
- 04
Related terms
Related services and guides
Let's talk about your project.
Tell us what you need; we will define the scope together.