Configure integration behavior for carried over findings
When you conduct a pentest on an asset that still has unfixed findings from a previous pentest, pentesters can “carry over” the findings to the new pentest. When the pentester carries over the finding, the original finding’s state will be set to “Carried Over”.
By default, ticketing integrations will treat carried over findings as new findings. This means that your integration will create a new ticket for the carried over finding regardless of the existence of a ticket for the original finding.
If you do not want your integration to create a new ticket for a carried-over finding when a ticket already exists for the original finding, you can configure your integration to use the alternative carry-over handling logic.
By following the steps below, you can configure the default carry-over finding handling behavior of your integrations for all newly created pentests. This configuration change will not apply to pentests that have already been created.
By following the steps below, you can configure the carry-over finding handling behavior of your integrations for a single pentest.
When the carried over finding is moved to the Pending Fix state, the following will happen: