You fixed it. Prove it, the same day.
A retest is a focused re-run against the findings you name. It is confined to the assets those findings live on, so it cannot wander into the rest of your estate, and the result updates the original finding rather than opening a second one.
Why is a retest confined?
Because a retest is a narrower authorization than the engagement that produced the finding, and treating it as a full re-run would quietly widen what you agreed to.
- What it touches
- Only the assets carrying the target findings.
- What it does
- Re-runs the steps that proved the issue and checks whether the behaviour is still there.
- Result
- Fixed, partially fixed, not fixed, or inconclusive.
- Effect
- The original finding is updated and the history stays attached to it.
A retest is checked by the same gate as any other action, so the scope, the window and the action policy all still apply.
The confinement is an additional restriction, not a replacement: an asset that is in scope but not carrying a target finding is refused.
Nothing is silently reopened. A finding a human marked as a false positive is never reopened by an automated pass.