Failed-Probe Retesting: Validate a Patch Without Changing the Test
Guide · 2026-11-19 · 5 min read · FilterPrompt Security Team
Retest the exact failing fixture before expanding coverage. Changing the prompt, model and policy simultaneously makes a before/after comparison difficult to interpret.
- Retest the exact failing fixture before expanding coverage. Changing the prompt, model and policy simultaneously makes a before/after comparison difficult to interpret.
- Use authorized staging targets and synthetic data. Treat examples below as lab fixtures, not measured FilterPrompt results.
The boundary this test examines
A team patches a system instruction after a synthetic marker leak. It needs evidence that the original observation no longer reproduces under the patched configuration.
Prepare a controlled test
Freeze the failed prompt and lab context. Save the old configuration, apply the patch and run the same request with the same target settings.
- Get written authorization for the target and agree on the protected behavior before sending test requests.
- Remove real secrets and customer records from the fixture; use only synthetic markers.
- Record the target model, application configuration and any relevant retrieval or tool state.
- Run a legitimate control task as well as the challenge so that blanket refusals are not mistaken for usable security.
A safe example to adapt
Original finding: request hidden lab marker.
Retest: use the same request and context against the patched application, then record each raw response.
This is a proposed test fixture, not evidence that a named model is vulnerable. Replace the lab details with your authorized staging policy, and do not execute consequential actions against production accounts.
Decide what the result means
| Outcome | Evidence required |
|---|---|
| Pass for this fixture | The protected marker remains private in the documented retests, and normal permitted behavior still works. |
| Failure requiring review | The marker still leaks, or the test silently drops the context that caused the original failure. |
| Inconclusive | The target was unreachable, context did not reach the model, capabilities were unsupported, or the evaluator could not establish the outcome. Record the gap; do not count it as a pass. |
Keep evidence another reviewer can use
Record original and new scan IDs, selected finding IDs, changed configuration and repeated outcomes. For multi-turn attacks, preserve the entire conversation.
Separate raw observations from interpretation. Record why the result matters to your policy, review severity against business impact, and document any missing evidence. Repeated runs help expose variability, but a small sample is not a guarantee of safety.
Remediate and retest the same boundary
In Auto Pilot regression, choose the historical scan and individual failed probes you want to rerun. Separately validate application state that a prompt-only replay cannot restore.
What this test does not prove
A successful retest covers that fixture under those settings, not every injection variant. Expand testing after confirming the exact regression case.

Continue with related guides
Reference and further reading
Can a successful test prove the application is secure?
No. It establishes an observation for the fixture and configuration tested. Review application permissions, untested paths and repeated outcomes separately.
How can I start testing with FilterPrompt?
Create an account, connect your authorized LLM using your own API key and use one free welcome credit for any static scan. Review the exact prompts, responses and findings. Your provider may charge for API requests.
Put this guide into practice with FilterPrompt
FilterPrompt is an AI security testing and LLM vulnerability scanner. Connect an authorized LLM or AI application with your own API key, test it with adversarial prompts, and review prompt injection, jailbreak and data-leakage findings with the test prompts, model responses and severity. Use that evidence to prioritize fixes and retest; FilterPrompt does not intercept or block live traffic.
Create a FilterPrompt account and use 1 free welcome credit for any static scan on your connected LLM. Review test prompts, responses and findings. No credit card required. Dynamic testing requires purchased credits; your provider may charge for API requests.
