Know whether the fix actually closed the risk.

Only the agreed findings and their direct verification paths. Each finding receives a pass, fail, or needs-more-evidence status with the observed evidence.

Yes. Bring the original finding, the deployed change, the target environment, and the person who can explain what changed. The retest remains bounded to the agreed evidence path.

We repeat the agreed reproduction path and test the control that should now hold. The record states what was observed, the environment tested, and whether the finding passed, failed, or needs more evidence.

Yes, when they are part of the agreed finding. The specific code path, configuration, or environment setting is set before access starts so the retest has a clear boundary.

The target environment is agreed in advance. We use the safest environment that can produce the needed evidence and do not run unapproved or disruptive testing against production.

Yes. We can retest the agreed identity, authorization, tenant boundary, or row-level security finding against the direct path that was previously at risk.

Yes, if the original finding involves those systems. The retest focuses on the agreed action, its failure path, and the control intended to prevent duplicate or unsafe behavior.

No. Fix Validation is an independent retest. New engineering work or open-ended debugging can be scoped separately when the evidence shows it is needed.

The record explains the observed failure or remaining uncertainty, the evidence collected, and the next owner. Any remediation work is separately scoped so the retest stays independent.

Yes. You receive a compact record for each agreed finding with a pass, fail, or needs-more-evidence status and the evidence behind it.

Timing depends on the number of findings, environments, and evidence paths. The retest boundary and delivery timing are agreed before access starts.

$350 to $750, depending on the number of agreed findings, environments, and evidence paths.

No. It is a focused retest of agreed findings. It does not replace a full penetration test, compliance audit, legal assessment, or broad security review.

Yes, when an agreed launch-impacting accessibility or user-flow issue has a clear reproduction and acceptance path. The service stays focused on the listed findings rather than a broad redesign.

It is for teams that have completed fixes for a short list of launch findings and need an independent, evidence-based record before they release or close the risk.