Integrations

Push DAST findings to your ticketing system!

Overview

The DAST ticketing integration allows you to push your DAST findings to your ticketing system as soon as vulnerabilities are detected. This integration supports several ticketing systems, including but not limited to:

• Jira Cloud
• GitHub Issues
• Azure DevOps Boards

For a complete list of supported applications, please refer to the available connectors section.

How it Works

The DAST ticketing integration uses Cobalt’s Integration Builder to push DAST findings to your ticketing system. The integration builder is a no-code workflow builder that enables you to create highly customizable integrations. We provide integration quickstart templates for the above-mentioned ticketing systems that allow you to get your DAST integration up and running quickly!

Steps to Integrate with Ticketing Systems

https://www.loom.com/share/7d61c971c7cc47daa750bf41ff247831

Frequently Asked Questions

Click to view answers.

Does it create duplicate tickets?

-The DAST ticketing integration will not create duplicate tickets as long as you follow our guidance regarding external ticket references.

Can I route tickets from different targets to different tools or projects?

-Yes. You can create one ticket-push recipe per DAST target and configure the recipes differently. You should use trigger filters to ensure that each recipe is triggered only by findings that are associated to the correct target. Checkout the video above for a walkthrough of this process.

Can I update a DAST finding from my ticketing tool?

-No. Our public API does not currently have functionality that can be used to update a DAST finding. The Integration Builder uses our public API, so it doesn’t support updating DAST findings either. This functionality is on our roadmap.

How do I know if a ticket has been created for a finding?

-When everything is working correctly, you can see tickets associated to your DAST findings directly within the DAST user interface. It is possible in failure scenarios that the integration could correctly create a ticket but fail to record an external ticket references. If this situation occurs, a ticket would exist, but it would not show up in the DAST user interface. You can investigate failures using our troubleshooting steps.

Troubleshooting

Checkout our general Integration Builder troubleshooting documentation here.