When do you need a pentest retest or a new assessment?

Request a focused penetration test retest when you need to verify fixes for known findings within the original scope. Scope a new assessment when a major change introduces risks the original review did not cover, such as a new identity system, tenant model, or externally accessible API.

Two square recesses, one empty and one fitted with an amber insert.

When is a targeted retest enough?

A targeted retest fits when the original finding and acceptance criteria still describe the problem, the relevant application and roles are available, and engineering can identify the deployed fix. Agree on the findings to verify and the environments the assessor can access before booking the retest.

If a fix changes a shared component, ask whether follow-up should cover other workflows that use that component. A narrow retest may confirm the behavior for the original finding while a broader follow-up answers whether adjacent workflows were affected.

When should you reopen scope?

  • A new trust boundary. Changes to tenant isolation, delegated access, or integration permissions often change which parties can access data.
  • A new surface. A new partner API or independently deployed admin portal may need its own coverage and acceptance criteria.
  • Limited original coverage. If the affected environment or role could not be reviewed due to missing access, schedule time to assess it and update the scope.
  • A different decision. If the original goal was to verify one fix and the new goal is to decide whether to launch a redesigned product, commission coverage for the launch decision.

For example, a SaaS team tightening export permissions on an existing admin API can request a retest against the original finding. If it also launches a partner API with a new service-account model, it can verify the existing fix and scope a separate review for the new access boundary.

What should a retest record say?

Keep the finding ID, assessment environment, time of verification, the version checked, and the result. Distinguish verified fixed, still open, and unable to verify. A missing test account or unavailable environment belongs in the last category with a reason and a named owner for the next step. Bring any deferred risk back to the person empowered to accept it.

Record which issues were verified and which areas the retest covered. This lets leadership use the results for a release decision without assuming the entire system was assessed again. NIST SP 800-115 discusses assessment results and mitigation.

See the pentest report checklist for what to capture in the original assessment and the SaaS pentest scope guide for planning new coverage.

All articles