Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A retest re-examines the findings of an earlier penetration test to confirm that remediation actually worked, producing evidence that each issue is closed rather than merely marked done.

What Is a Retest in Penetration Testing?
A retest verifies that the problems found in a penetration test have genuinely been fixed. The tester returns to each reported finding, attempts the same attack again, and records whether it still works. The output is a short report that marks every issue as resolved, partially resolved, still present, or formally accepted as a risk.
It sounds like a formality. It is not. A substantial share of findings presented as remediated turn out to be fixed in one place and not another, patched on the application server but not the load balancer, or addressed in development and never deployed to production. Without verification, nobody knows which case applies.
The patterns repeat across engagements:
A retest catches all five, which is why it belongs in the original contract rather than being discussed afterwards.
Scope is deliberately narrow: the previously reported findings, not a fresh assessment. The tester repeats the documented reproduction steps, checks whether the underlying weakness class has been addressed more broadly where that is feasible, and watches for anything the fix itself broke. New vulnerabilities discovered incidentally are reported, but hunting for them is not the job.
| Status | Meaning |
|---|---|
| Resolved | The attack no longer succeeds and the root cause has been addressed |
| Partially resolved | The specific case is fixed; the weakness remains reachable elsewhere |
| Not resolved | The original steps still work |
| Risk accepted | No fix applied, with a documented owner, rationale, and review date |
| Compensating control | The flaw remains but a separate control blocks exploitation |
Most providers include a retest within a fixed window after the original engagement, commonly thirty to ninety days. That window exists because the environment drifts: six months later the application has changed enough that a comparison means little, and the work becomes a new test rather than a verification.
Critical and high findings should not wait for the window to close. Fix them, retest them individually, and keep the scheduled retest for everything else. Where a finding cannot be fixed inside the window, agree the acceptance in writing with a named owner and a date for revisiting it, rather than letting it quietly expire.
Retest evidence is frequently the artefact an assessor asks for. PCI DSS requires that exploitable vulnerabilities found during penetration testing are corrected and that testing is repeated to verify the correction, so a report showing only the original findings does not satisfy the requirement. Cyber Essentials Plus assessments check that known issues are no longer present on sampled devices. ISO 27001 auditors look for the full cycle, from identification through remediation to verification, as proof that the control operates rather than merely exists.
For organisations under the NIS Regulations, or financial entities within scope of DORA, documented verification supports the wider argument that testing feeds a working vulnerability management process.
Treat findings as tickets with owners and dates as soon as the report lands, not as a document to file. Fix root causes rather than individual instances, since a retest that keeps returning “partially resolved” is telling you the remediation approach is wrong. Record what changed for each finding, which makes the retest faster and cheaper. Where a finding is accepted rather than fixed, write down why, because the next assessor will ask.
And expect some findings to come back. Regression is normal in active codebases, which is the argument for continuous scanning between engagements as well as periodic depth testing.
Our Penetration Test Services include a retest of remediated findings and an updated report you can hand to an auditor.
It depends on the provider, and it is worth asking before you sign. Many include one retest within a defined period, commonly thirty to ninety days, covering the findings from the original engagement. Others price it separately. Clarify what is covered, how long you have, and whether findings fixed after the window require a new engagement.
Document it as an accepted risk with a named owner, a clear rationale, any compensating controls in place, and a date when the decision will be reviewed. Auditors accept informed risk acceptance far more readily than a finding that simply disappears from tracking. Make sure the acceptance is approved at a level appropriate to the potential business impact.
No. Its scope is the previously reported findings, which keeps it short and affordable. Testers will report anything serious they notice while verifying fixes, but they are not performing fresh discovery. If the application has changed substantially since the original engagement, a new test is the appropriate choice rather than an extended retest.
Annually at minimum for most organisations, and after any significant change to architecture, authentication, or internet-facing services. PCI DSS requires at least annual testing plus testing after significant change. Retesting follows each engagement. Continuous vulnerability scanning covers the gaps between tests by catching newly published issues as they appear.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.