Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 38 ยท Reporting and Remediation

Remediation, Retesting and Communicating Results

Learn how to prioritize fixes, set remediation timelines, plan a retest, and run a constructive findings walkthrough so a penetration test leads to real improvement.

Delivering the report is not the finish line. A penetration test creates value only when problems get fixed and the fixes are confirmed. Many organizations receive a good report, file it, and discover the same weaknesses again a year later. Your job as a tester extends to helping the client turn findings into changes, and to checking that the changes work.

From findings to fixes

Developers and administrators rarely get to drop everything for a report. They need a prioritized, realistic plan.

Prioritize by risk and effort

Rank fixes by the risk they remove and the effort they need:

Low effort High effort
High risk reduction Do first: quick wins (disable an exposed service, rotate a leaked key, patch) Plan now: projects (network redesign, identity overhaul)
Low risk reduction Do when convenient Schedule or accept

Also look for root causes. Ten injection findings usually mean "no standard for database access", so one fix (a shared data layer with parameterized queries, plus code review and developer training) removes the whole class. A finding on one server may point to a base image used by two hundred.

Typical remediation timelines

Organizations often set target times by severity. These are common examples, and each organization's policy decides the real numbers:

Severity Typical target to fix
Critical Immediately to 7 days
High 30 days
Medium 60 to 90 days
Low 180 days or next release
Informational Backlog

When a fix cannot be done in time, the organization can use compensating controls (a web application firewall rule, network restriction, extra monitoring) and then record a risk acceptance that names the owner and an expiry date. An accepted risk with no owner and no review date is just a forgotten risk.

From report to fixed

Triage Confirm and assign owners
Fix Root cause first
Verify Retest each fix
Prevent Tests, training, standards

A finding is closed only when someone proved it is gone.

1 / 2

Track the work

A shared tracker with owners and due dates keeps the process honest. Each finding should have an owner (a team or person who can change it), a due date from the severity policy, a status (open, in progress, fixed, retest passed, accepted risk) and a link to the ticket. The stand-in computes due dates and flags overdue items.

Python Remediation tracker with due dates

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The output shows what a project manager wants to see: what is overdue, who owns it, and which fixes are waiting for verification. The highest-risk overdue items need escalation to management, not just a reminder email.

Retesting

A retest (also called a verification or remediation test) checks that each fix really works and did not break anything. It is usually shorter than the original test and covers only the reported findings, plus a quick look at whether the fix is complete.

When you retest:

  • Use the same steps to reproduce from the report, and record the result for each: fixed, partially fixed, not fixed or cannot be retested.
  • Check for bypasses: a developer may have blocked the exact string you used but not the underlying flaw (a blocklist for one SQL keyword, say). Try variations.
  • Look for regressions and new issues introduced by the fix.
  • Update the report as a new version with the retest date and results; never silently edit the original.
  • Agree the retest window in the contract (many engagements include one retest within 60 to 90 days).
Python Summarize retest results

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Partial fixes and missed subdomains are the typical retest discoveries, and each note tells the engineering team exactly what is left.

The findings walkthrough

Offer a live walkthrough of the report with the technical team and, separately, a short briefing for management. In the walkthrough:

  • Start with what went well; people need to know their effort counted.
  • Explain findings in terms of how the attack works and what it would mean, then show the fix.
  • Be collaborative, not triumphant. The aim is a safer system; nobody wins by making the team defensive.
  • Answer "how do we know this is real?" with evidence and, where safe, a short live demonstration.
  • Agree owners and dates in the meeting, and send a short written summary afterwards.
  • Be open to disagreement: if the client believes a finding is a false positive or an accepted risk, discuss the evidence and record the outcome in the report.

Building prevention into the process

Long-term improvement beats one-off fixes. Recommend:

  • Secure development practices: secure code review, static and dependency scanning in CI, threat modeling for new features, automated tests for fixed vulnerabilities so they cannot return.
  • Hardened baselines and configuration checks for servers, containers and cloud accounts, defined as code.
  • Patch management with measured time-to-patch.
  • Detection and response: if your test was not detected, work with the defenders to add alerts and rehearse the response (a purple-team session shares attacks and detections in the open).
  • Regular testing: annual external and internal tests, plus targeted tests after major changes.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A report contains ten injection findings in different pages. What is the most effective recommendation?

    Fixing the cause removes the class of problem, not just the examples.
  2. 2. A critical fix cannot be deployed for three weeks. What is the proper interim step?

    Compensating controls reduce exposure meanwhile, and the documented acceptance keeps accountability.
  3. 3. What should a retest do besides repeating the original steps?

    Fixes are often incomplete or break something else; variations and regression checks reveal that.
  4. 4. How should a findings walkthrough with the technical team feel?

    The goal is a safer system, which needs the team's cooperation.

Summary

  • Prioritize fixes by risk reduction and effort, and look for root causes that remove many findings at once.
  • Use severity-based timelines, owners and a tracker; use compensating controls and expiring risk acceptances when needed.
  • Retest with the original steps, try bypasses, watch for regressions and issue a new report version.
  • Run a respectful walkthrough, agree actions and follow up in writing.
  • Build prevention into development, configuration, patching and detection.

Next: Project: a findings tracker and report builder