What a retest is
After a penetration test, your team fixes the findings. A retest is a focused follow-up in which the tester repeats the steps that proved each finding, to confirm the fix works. The report is then updated to show which findings are fixed and verified, and which remain open.
What a retest covers
A retest checks the specific findings in the original report. It is not a new penetration test: it does not look for new weaknesses in features added since, although a tester will mention anything obvious they notice. For major changes, plan a new test.
Preparing for the retest
Retests go faster and give clearer results when you:
- Fix findings in the same environment that was tested, or tell the tester where the fix is deployed.
- Send a short note per finding: what you changed, and any finding you accept as a risk instead of fixing.
- Keep the test accounts active until the retest is complete.
Accepted risks
Not every finding has to be fixed. Some are accepted as a business decision, often with compensating controls. A good report records them as accepted risks with your reasoning, rather than leaving them as unexplained open items.
How results appear in the report
The updated report shows the status of every finding, the date it was verified and a short note on how. Reviewers and auditors look at this status first, so a clear retest section often matters as much as the original findings.
Timing
Agree the retest window when you book the test. Fixes for high and critical findings usually take a few days to a few weeks, depending on your release cycle. ESCOSS includes one retest of the reported findings in its testing engagements.



