Skip to content

Resource

How to prove a vulnerability was fixed

A closed ticket is not proof that risk was removed. This resource explains how to produce verified remediation evidence: independent corroboration that the original finding no longer applies, bound to a specific release decision.

The problem

Development teams mark vulnerabilities as fixed every day. But "fixed" often means the ticket was closed or a scanner no longer reports the issue in a single run. When a consequential release depends on that fix, the organization needs proof.

What verification requires

  • The original finding and the evidence that supported it.
  • The new artifact produced after the claimed fix.
  • A repeatable way to evaluate whether the original risk is still present.
  • A policy-defined threshold for what counts as verified.

The verification steps

  1. Preserve the original finding. Capture scanner output, location, version, and context so later verification can compare outcomes.
  2. Identify the fix artifact. Record the commit, build, or deployment that contains the claimed fix.
  3. Re-evaluate with independent evidence. Run the original test or scanner against the new artifact. Add a second source such as runtime telemetry or reviewer attestation for corroboration.
  4. Record one of three outcomes. Risk absent, risk present, or indeterminate. Indeterminate must be escalated.
  5. Bind to policy and release. The verified evidence is evaluated against the policy version active at release time, and the decision record links the finding, fix, evidence, and outcome.

Evidence strength

EvidenceStrengthWhy
Ticket closureWeakWorkflow state, not risk state
Single retest passModerateShows scanner no longer detects the issue
Retest + reviewer attestationStrongCombines tool evidence with human review
Retest + runtime corroborationStrongerIndependent source confirms behavior changed
Policy-bound decision recordVerifiableDecision can be replayed and audited

Frequently asked questions

What counts as proof that a vulnerability was fixed?

Proof includes a retest result showing the original behavior is absent, a reviewer attestation with artifact references, and corroboration from an independent source. The evidence must be bound to the specific release decision.

How does GoSentrix verify fixes?

GoSentrix re-evaluates the original evidence against the new artifact and compares outcomes. If the evidence still shows the original behavior, the fix did not work. Verified fixes are bound to the policy version active at the time.

Validated fixes, not just ticket closure.

GoSentrix verifies whether remediation evidence satisfies policy for a consequential release decision.