Carried Over Findings
What is a Carried-Over Finding?
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”.
Default Integration Behavior for Carried-Over Findings
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.
Avoid Creating New Tickets for Carried-Over Findings
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 (at the pentest level) to use the alternative carry-over handling logic. If you would like to use the non-default carry-over handling logic, we recommend performing the following configuration steps before launching a new pentest:
- Navigate to the new pentest in the Cobalt UI
- Navigate to the Integrations tab
- In the “Ticket creation for carry over findings” tile, click the radio button for the “Re-associate existing ticket” option
- Click save
What Does Re-associating the Existing Ticket Do?
When the carried over finding is moved to the Pending Fix state, the following will happen:
- The ticket will be unlinked from the original finding
- The ticket will be linked to the carried over finding
Which Integrations Are Supported?
- Native Jira Cloud integration
- Native Jira Data Center (server) integration
- Integration Builder External Ticket References