Why a retest catches half-finished fixes

Two testers reviewing a dark wall console together

A patched host behind an unchanged rule is still open. That is why every Critical and High gets run again on day 38, and why the retest is free.

Nobody hides a fix on purpose. The ticket says done because the patch went in. The path we used last month is often still there, one step to the left.

What we check

  • The exact steps from the report, in the same order.
  • The same flaw on neighbouring hosts and sister services.
  • Whether the alert the client added actually fires.
  • Whether the old account or token was really retired.

A finding closes when the path is gone, not when the ticket is.

What you get

You get a short letter with each finding marked closed, partly closed or still open, and the proof for each. It goes to whoever asked for the report in the first place.

About the author

Ines founded Wardline and still reads every scope before it leaves the building. Fictional author, demo content.

Related field notes