Pentest Report Actions
In the pentest report action section, program managers have the ability to manage reports in an efficient manner by taking various actions on them. These actions include:
Marking the status of a report as ignored or resolved
Requesting a retest for a vulnerability
Connecting the report to various integrations
Adding comments and notes to the report
Printing a specific vulnerability report
Marking the Status of the Report
This allows program managers to update the status of a vulnerability report to indicate that it has been addressed or is not a valid issue.
To change the status of a report
Go to the metadata panel and click on the "Mark Vulnerability Status" button.
This will bring up a dropdown menu where you can select the desired status for the report, such as "Ignored" or "Resolved."
Requesting a Retest
If a program manager is unsure about the validity of a report, they can request a retest to have the vulnerability re-evaluated.
To request a retest of a vulnerability
Go to the metadata panel and click on the "Request Retest" button.
Connecting to Various Integrations
Program managers can connect their pentest reports to various integrations such as Jira, Asana and Github. This allows program managers to integrate their pentest program with their existing workflows and processes.
To connect to various integrations,
Go to the metadata panel and click on the "Connect to * " button.
Adding comments
Program managers can add comments to a report in order to provide feedback or additional information to the pentester who submitted the report.
Printing Vulnerability Report
Program managers can print a report in order to have a physical copy for record keeping or for sharing with other team members.
To print a vulnerability report
Go to the metadata panel and click on the "Print Report" button.
This will open a printable version of the report that you can print or save as a PDF.
Last updated