
The report lands in your inbox. It is detailed, the testing is complete and there are findings to work through. What happens next?
That is where a penetration test either leads to useful changes or becomes another document waiting for attention. Getting value from the engagement starts before testing and continues after the final report.
Decide which question the test needs to answer
A test of an internet-facing application answers different questions from a test of an internal network. Adding more targets is not automatically better; each one needs enough time and access to be assessed meaningfully.
Tell the provider what prompted the work. Perhaps you are launching a customer portal, changing your remote access setup or investigating a concern about staff permissions. That context helps turn a list of systems into a useful scope.
For a customer portal, for example, ask whether the engagement includes different user roles and the actions that matter to the business. A login page is only one part of the application.
Know what a finding means
Finding vulnerabilities does not automatically mean the testing has failed. The engagement is intended to uncover weaknesses within its boundaries. Some assessments have specific acceptance criteria, but a generic pass-or-fail label can hide the detail your team needs.
Ask the tester to explain the conditions required to exploit each issue and the potential business impact. Which data or systems are affected? What was demonstrated? What remains uncertain?
The ASD security assurance guidance treats assessment as a way to understand vulnerabilities and risk. Use the results to support decisions about the affected systems, rather than treating the number of findings as a score for the whole business.
Give every action an owner
Book a results discussion with the people who will make changes. Include the business owner, the relevant IT or development team and any supplier responsible for the affected service.
A practical remediation list should record:
- The issue: a clear reference back to the finding.
- The decision: what will change, or why another treatment is being considered.
- The owner: the person accountable for moving the work forward.
- The target date: when the action will be completed or reviewed.
- The evidence: how the team will confirm the change worked.
A severity rating helps with prioritisation, but it needs context. Consider exposure, the access required and the importance of the affected system. If a full fix needs time, discuss temporary controls and record their limits.
Close the loop with a retest
A completed change ticket shows that work was done. A retest can check whether the previously demonstrated issue is still present. Agree which findings will be retested and what evidence you will receive.
Keep the result with the original report. That gives the next person reviewing the work a clearer record of what changed and what remains open. If the application has changed substantially, discuss whether a targeted retest is enough or whether broader testing is needed.
Before your next engagement, ask one final question: have we allocated time for the fixes? A well-scoped test and a team ready to act on it make a much stronger combination.
Discuss your next penetration test with Invado Tech, including scope, reporting and remediation retesting.
