Plan and execute a pentest retest — re-scope, re-execute the validation steps from prior findings, detect regressions, and write the retest report. Use when the user mentions retest, re-test, remediation validation, regression coverage, "verify the fixes", "validate remediation", retest scoping, retest report, posture trajectory, or compares "before vs after" findings.
Plan and execute a pentest retest — re-scope, re-execute the validation steps from prior findings, detect regressions, and write the retest report. Use when the user mentions retest, re-test, remediation validation, regression coverage, "verify the fixes", "validate remediation", retest scoping, retest report, posture trajectory, or compares "before vs after" findings.
Engagement Retest
Drive a focused retest using the prior engagement's findings as the test plan.
Library root
$PENTEST_LIBRARY — caminho absoluto deste repositório clonado (definido pelo instalador; veja INSTALL.md).
Inventory prior findings — collect the prior engagement's findings (IDs, severity, status, asset, methodology used). For each, the validation steps live in the prior Reproduction steps and per-library checklist item.
Re-scope window — confirm:
Which findings are in scope for this retest (typically all High+ closed/mitigated, plus Medium fixes).
Whether the asset surface has changed (new endpoints, new accounts, new build) — material change shifts retest into a delta-pentest.
Test perspective (which credentials / role / network position to re-use).
Time window + blackout windows.
Per-finding execution — for each finding:
Re-read the original Reproduction steps.
Re-execute exactly. Record the new request/response.
Classify the outcome:
Closed — exact reproduction no longer succeeds.
Partially mitigated — original payload blocked, but a near-equivalent variant still succeeds (document the variant).
Open — still reproducible.
Regressed — was Closed at some point, now Open again.
Mitigated by compensating control — root cause unfixed, but a control (WAF, MFA, network ACL) prevents exploitation; document residual risk.
For variants: walk the matching library checklist item's How to test block to broaden test coverage in the same vulnerability class.
Regression sweep — for each fix, test the adjacent attack surface (same parameter family, same role boundary, same trust edge). A correct fix at one entry point rarely covers siblings.
Posture trajectory — quantify before/after counts by severity; flag categories of finding that recurred (indicates process gap, not just a missed patch).
Report — fill templates/retest-report-template.md:
