Performing a retest

This guide contains:

  1. Duplicate your previous project
  2. Bulk-update the Issues/Evidence
  3. Perform the retest
  4. Quality Assurance/Review
  5. Export your retest report

1. Duplicate your previous project

Since this is a retest, you've already tested this system/network before! Locate that project on the Projects page and click the Duplicate button.

The project will be duplicated, with copy_01 appended to the original project's name. Edit the project's name to reflect the retest!

2. Bulk-update the Issues/Evidence

The specifics of this step will depend on how your report template is configured to differentiate between retest and new findings as well as open and closed findings. After duplicating, you could bulk-update the relevant Issue field(s) or custom tag to mark all of the findings from last time as retest findings.

3. Perform the retest

Next up, do the actual retest! Upload a new scan or manually check to see whether the findings from the last project are still open or whether they've been resolved. Add new findings that weren't in the last project and get the project ready to be reviewed.

4. Quality Assurance/Review

Before exporting, use our QA feature to review each Draft finding and make sure that the spelling, grammar, and technical details are all polished before setting the finding to Published.

5. Export your retest report

Generate your report and deliver that report to the correct person. Start over at Step #1 if you have to do yet another retest in the future!

Great job, you reached the end of the guide! Have you read all of them?

Seven Strategies To Differentiate Your Cybersecurity Consultancy

You don’t need to reinvent the wheel to stand out from other cybersecurity consultancies. Often, it's about doing the simple things better, and clearly communicating what sets you apart.

  • Tell your story better
  • Improve your testimonials and case studies
  • Build strategic partnerships

Your email is kept private. We don't do the spam thing.