Best Penetration Testing Companies

Practical guide · November 17, 2026

Before the next pentest, deal with last year’s unresolved findings

Bring unresolved findings into the next penetration-test scoping conversation before the testing schedule is agreed. Decide which claimed fixes need verification, which old paths need current investigation and where the new assessment should explore changes. Preserve the history even when a particular finding is not retested.

There is a real tradeoff. Repeating a known path can consume time that might uncover something new. Omitting it without explanation can make a later report look cleaner even though nobody established that the weakness was resolved.

Bring forward the history without freezing it

Start with the earlier finding IDs, affected systems and evidence, then add what has happened since. Separate a developer's completed ticket from a tester's verification. Record a system retirement or architectural change as something to understand, not an automatic reason to erase the finding.

A discussion among pentesters handling repeat clients makes the disagreement concrete: should limited assessment time revisit acknowledged issues or look for additional paths? Commenters offer contrasting approaches. Their experience motivates the question; it does not establish a universal testing or compliance rule.

A useful working record distinguishes at least these situations:

These are suggested working descriptions, not a mandatory classification scheme. Keep the basis beside the status so a reader can tell an assertion from an observed result.

Separate three different uses of testing time

Verifying a claimed correction asks whether the change addresses the finding under the agreed conditions. Give the tester the relevant version, environment and account access, along with a clear description of what changed.

Investigating a previously reported path asks what can be established now. The old evidence remains part of the history, but current exposure and reachable systems may differ. Agree with the tester what investigation is appropriate rather than assuming an old exploit either still works or no longer matters.

Exploring new scope or paths asks a different question again. New features, changed trust boundaries or an agreed objective may justify work beyond replaying the previous assessment.

The balance depends on the engagement's purpose, current risk and any applicable obligations. It is not a universal allocation of hours. Our web application scope guide helps define the assessment boundary; the old findings are an input to that decision, not the entire scope.

Make exclusions visible to the next reader

If an issue is not retested, say so. Distinguish a deliberate scope choice from a test that could not be completed because access or functionality was unavailable. Neither situation should silently become “fixed.”

OWASP's Web Security Testing Guide reporting section suggests documenting scope and limitations and, for a retest, summarizing previous findings with updated status and cross-references. It describes a possible reporting approach, not a compulsory template.

Ask how the new report will connect to the old one. A reader should be able to distinguish findings observed during this engagement from historical issues carried forward with another evidence basis. If a separate register carries that history, agree how the report points to it and who receives it.

A documented exclusion is not a remedy or an automatic legal protection. Check any required assessment scope with the people responsible for the relevant customer, contractual or regulatory obligation. Do not assume your preferred allocation of time satisfies it.

A renewal conversation with something to decide

Hypothetical example: a software company has three items from last year's assessment. Engineering says one has been corrected. A second remains open while a replacement service is built. Nobody can explain the third item's current status because its original owner left.

Sending last year's report with “please test again” leaves the important choices unstated. Instead, the buyer and tester can discuss verification of the claimed correction, current assessment of the open exposure, and the work needed to resolve the uncertain item. They can also identify new functionality that deserves attention.

That conversation may show that the proposed time is insufficient. The response should be an explicit choice about additional time, priorities or documented limitations—not a promise to cover everything within an unchanged budget.

It should also produce work outside the test. The open exposure needs an accountable decision and remediation plan now; the uncertain item needs investigation. A future assessment date is not a reason to postpone handling an urgent risk.

Leave with evidence, not a cleaner-looking list

Agree how statuses, evidence and references will be delivered before the next engagement begins. Keep the original findings available, record what the new work established and identify anything it could not establish.

Check retest terms and windows separately from the scope of the new assessment. A new annual engagement and an included retest of an earlier finding are not interchangeable simply because both involve the same provider.

The useful outcome is a clearer account of risk and progress. Fewer findings on a page are meaningful only when you understand why the list changed.

Research basis: practitioner discussion and OWASP reporting guidance inspected November 17, 2026. The renewal scenario and planning approach are editorial examples; no assessment was commissioned and no particular compliance requirement is certified here.